GA4 can bring advertising costs together with measured website outcomes to compare Google Ads, Meta Ads and TikTok Ads. In eligible properties, cross-channel budgeting adds projections and scenarios based on historical data. The first step is correctly joining spending with traffic and conversions. This guide describes the setup and conditions documented as of November 21, 2026; planning tools do not change budgets in connected advertising accounts.
1. Define the outcome before comparing channels
Choose the outcome the business wants to track: a purchase, a qualified inquiry or another defined commercial action. Preserve the same definition throughout the analysis period. A submitted form and a completed sale are different events; cost per form should not be labeled cost per customer. For ecommerce, check the transmission of purchase values and currencies so that every channel is compared on the same economic basis.
For the DDA budgeting model, Google requires eligible web conversions. Merely marking an event as a key event in reports does not automatically make it an accepted conversion for that model. Separate current measurement from planning eligibility. A dashboard can compare costs and outcomes even for a business that does not yet have enough history for a budget allocation model.
Workflow: from cost data to a budget decision
- Inputs
Linked Google Ads, imported Meta/TikTok costs and defined conversions.
- Validation
Account, period, currency, UTMs, totals and joining with GA4 activity.
- Eligibility
History and model checks; straightforward reporting if history is insufficient.
- Planning
Projection monitors the period; Scenario compares future allocations.
- Separate decision
The administrator approves and applies the budget in the ad account. GA4 does not change it.

2. Link Google Ads and prepare external sources
For budgeting in the Advertising section, Google's documentation requires linking Google Ads and setting up conversions. Costs and campaign data from other platforms arrive through imports. Google Ads campaign management and measurement configuration need to use the correct GA4 property and advertising account. Account identity matters as much as enabling a connection: a successful import from the wrong account can produce a comparison answering a different question.
For external data, GA4 supports imports through files and sources such as Google Sheets or BigQuery, as well as dedicated connections for certain advertising platforms. Before setup, inventory existing imports, their covered periods and their source accounts. Two connections bringing in the same costs for the same period can duplicate reported spending. Resolve source overlap before using totals in calculations or scenarios.
3. Match Meta and TikTok campaign parameters
The Meta connection documentation requires at least the Editor role in the Analytics property and the necessary Meta accounts. The source and medium configured for import must match utm_source and utm_medium in ads sending visitors to the website. For Meta Ads campaigns, Facebook and Instagram sources can be mapped separately or assigned the same shared source, depending on existing tagging. Keep the same convention in configuration and ad destination parameters.
For TikTok, the documentation requires at least the Analyst role in TikTok Ads and Editor in Analytics. The dedicated connection uses one unique source value and one medium value matching the traffic. Campaign ID and campaign name are recommended for detail. Dedicated connectors attempt to retrieve available history covering at least 24 months; that request does not create data that never existed in the advertising account.
Reporting, DDA budgeting and Meridian have different requirements
| Approach | Data and access | Output |
|---|---|---|
| Comparable reporting | Costs joined with measured activity; defined conversions | Observed costs and outcomes over comparable periods |
| DDA budgeting — beta | Eligible GA4/360 property; at least 1 year; Google and at least one non-Google channel | Projections and scenarios based on attribution and history |
| Meridian — limited alpha | Selected Analytics 360 properties; at least 2 years of costs, conversions and revenue | MMM estimates and modeled incremental metrics |
4. Validate the import before interpreting performance
For a campaign import prepared by the business, source, medium and date are required fields; currency is required when cost is included. Campaign ID and name are recommended. Values need to match the import schema and traffic convention, including letter case. An uploaded amount and an amount successfully joined to measured Analytics activity are different technical outcomes.
Check the Campaign data import validation report. It distinguishes joined data, missing campaign data and missing Analytics data for joining. Compare cost, click and impression totals with the source platform over the same period. The import percentage shows which rows were accepted, while match rate shows their association with Analytics data. Data can take up to 24 hours to appear in reports.
5. Check eligibility for DDA budgeting
Data-driven Attribution budgeting is documented as a beta for GA4 and Analytics 360, with access in eligible properties. It requires at least one year of data for the selected conversion and one year of costs from at least two channels, including Google and a non-Google source. App conversions and key events as such are not supported by the documented model. Associated event history can backfill conversions when the requirements are met.
After the requirements are met, Google checks import correctness and model quality; evaluation can take up to two days. Major data gaps and changes in conversion implementation can prevent validation. The model uses attribution history and statistical regression to estimate paid-channel outcomes. Organic traffic is excluded from budgeting results. Attributed data and future estimates need to be read in the context of that mechanism.
6. Use Projection for the current planning period
The Advertising section is available in the desktop version of Google Analytics. In an eligible property, open Budgeting, then Projection, and create a plan with a name, period and objective. The objective can be budget, conversion count or revenue. Select a conversion available to the model and a period matching the business decision, such as the remaining month of a seasonal campaign, without combining incompatible intervals.
The chart separates recorded values from the projection and displays the model's confidence bounds. Check spending pace and distance from the chosen objective. A difference between plan and actual performance calls for examining data, timing and campaign changes. The projection is calculated from the property's history; values for upcoming days are model estimates, separate from conversions and revenue already recorded.
7. Build a Scenario for a future decision
Scenario is intended for comparing future budget levels and allocations. Define the period, amount and objective, then examine the distribution proposed by the model across included channels. A scenario plan retains its estimates until it is modified or a new plan is created. Use Source platform to understand how investment is grouped, and avoid comparing a platform total with only a subset of campaigns from another source.
A strictly illustrative example: a RON 6,000 budget can be described as RON 3,000 for Google, RON 2,000 for Meta and RON 1,000 for TikTok. An alternative of RON 2,800, RON 2,200 and RON 1,000 preserves the same total. These amounts illustrate two distributions, rather than market recommendations or measured results. The estimated effect is read from the business's eligible model; changes are applied separately in the appropriate advertising account.
8. Distinguish Meridian from the attribution-based model
Meridian budgeting in Analytics 360 is a limited-access alpha feature. The documentation requires a linked Google Ads account, created conversions and at least two years of cost history and conversion and revenue history. Meridian uses marketing mix modeling with aggregate data. Unlike the DDA model, it does not use attribution as an input. Its estimated incremental metrics describe the effect the model assigns to advertising investment within the MMM methodology.
A report about attributed conversions and a model about incremental conversions answer different questions. The first perspective allocates credit across measured journeys; the second estimates marketing's contribution relative to a modeled baseline. Preserve the methodology's name when comparing results. Access to a standard GA4 property or the presence of imported costs does not automatically enable the Meridian feature in Analytics 360. Its requirements and access stage are separate from those for DDA budgeting.
9. Keep a working record for budget decisions
If the property lacks the required history, start with a consistent table of costs and outcomes by platform. Correct missing sources, overlaps, UTM conventions and conversion definitions. Record the period, currency, last update date and source of each metric. A business dashboard with automated reporting can place that information alongside orders and commercial stages from business systems, keeping reported values separate from estimates.
Before applying a reallocation, check data coverage, the available total, the objective and the campaign plan receiving the change. Record the amount moved, the reason and the evaluation period. Then compare results over comparable intervals, accounting for when conversions are recorded. This keeps the decision grounded in business data: imports supply costs, validation confirms joins, the model estimates scenarios, and the administrator approves and applies the change in the advertising platform.