Google Analytics on November 19, 2026, said its cross-channel budgeting tool now supports source platform dimensions, so projection and scenario plans can set individual ad platforms side by side instead of folding spend into broad channel groups. The tool has been in beta since January, still changes nothing in connected ad accounts, and remains unavailable to some properties, while its Meridian-based model is limited to an alpha for select Analytics 360 customers.
In Short
Google Analytics' budget planner can now show spend, conversions and recommended shifts for each ad platform, not only for broad groups such as paid search or paid social. That matters to advertisers who import cost data from several platforms and want one model to suggest where money should move between them, and the model doing the suggesting belongs to Google, one of the platforms being compared. Nothing changes automatically: the plans are estimates, budgets still have to be moved inside each ad account, and the version built on Google's attribution data needs at least a year of cost history from two or more channels.
What Google Analytics posted
The change surfaced in a post on the Google Analytics LinkedIn page, which had 599,310 followers, on the afternoon of November 19 in Europe. "You asked for deeper ad spend visibility, so we expanded the view," the post opened. "Cross-channel budgeting in Google Analytics now supports source platform dimensions."
Three claims followed. According to Google Analytics, the update lets advertisers "Move past broad channel groups to evaluate individual ad platforms side by side," "Track pacing and shift budget to your highest-return platforms in real time," and "Model future scenarios with response curves backed by data-driven attribution." The image in the post carried a "What's new" label and the name Source platform budgeting, with the line "Evaluate and optimize spend across individual ad platforms."
A pinned comment from the same account pointed to the Help Center article "About cross-channel budgeting." That page is undated. As of November 20, Google's "What's new in Google Analytics" page had no entry for the change; its most recent item, dated November 6, covers Data Manager.
The phrase "in real time" sits awkwardly next to the documentation. The help page describes pacing as a weekly exercise: one listed benefit is to "Track the pacing of your spend and conversions weekly to make quick, in-quarter adjustments based on overperformance or underperformance." Shifting budget is also not something the tool does. "These tools are for planning purposes only and won't affect budgets or spend in your connected accounts," according to the page.
From channel groups to platforms
Until now, the budgeting reports worked at the level of channels. The help page gives the new granularity a single sentence, placed in the section on scenario plan recommendations: "In order to improve the ease of use and actionability of your budgeting plans, we are launching new source grouping dimensions, source platform dimensions, and (alpha-only) source platform x campaign type dimensions." The page continues: "With these changes, you will be able to better analyze and optimize performance and standardize reporting for both Google and other platforms."
| Dimension named on the help page | Status stated |
|---|---|
| Source grouping dimensions | "launching" |
| Source platform dimensions | "launching"; promoted by Google Analytics on November 19, 2026 |
| Source platform x campaign type dimensions | "alpha-only" |
The groundwork was laid in June. Google added a Source Group field on June 11, 2026, and reclassified the existing Source Platform values so that variants such as "facebook", "fb" and "Meta-facebook" collapse into one value. Source Group is a separate dimension from Source Platform: the same traffic can appear as "Meta Ads" at the platform level and "Instagram" at the group level. Google said at the time that the update would improve budget analysis and make cross-channel reporting in the Advertising section simpler.
In the interface Google Analytics showed alongside the post, a scenario view plots a response curve against ads cost, marked "Plan budget: $118K", and a table breaks results out by "Source platform", with the platform names obscured. The curve flattens as spend rises, the diminishing-returns shape that mix models commonly describe with Hill curves. Three headline metrics sit above the chart: "Ads cost", "All conversions (by conv. time)" and "Cost per all conversions (by conv. time)". The figures are illustrative, and rows beneath the total split each one into "Optimized" and "Projected" values. The total of $117,846.62, in line with the plan budget, compares with $84,231.67; conversions rise 17.36%, from 3,984.81 to 4,676.69, while cost per conversion rises 19.21%, from $21.14 to $25.20. In the illustration, more spend buys more conversions at a higher cost per conversion, which is consistent with a target to "drive the most number of conversions possible with my defined budget" rather than to minimize cost per conversion.
Two plans, two jobs
Cross-channel budgeting splits into two plan types, both reached through the Budgeting menu of the Advertising section, which according to Google "is only available on the desktop version of Google Analytics."
| Projection plan | Scenario plan | |
|---|---|---|
| Purpose | Monitor in-flight performance against a target | Build quarterly or annual media plans |
| Target KPI options | Budget, Conversions, Revenue | Conversions, Revenue |
| Start date | Not restricted on the help page | "can only start on future dates" |
| Main output | Chart of actuals (solid line), projection (dotted line) and confidence bounds (shaded area) | Response curve showing the allocation with the highest ROI for the defined budget |
| Updates | Tracks pacing as the plan runs | Curve fixed at creation unless settings change |
| Conversions | List of eligible conversions shown | One conversion at a time |
| Stated requirement | Property eligible for cross-channel budgeting with "sufficient historical data" | Data-driven attribution plus campaign data from linked integrations or data imports |
Projection plans, according to the help page, answer questions such as "Am I on track to spend my plan budget?" and "Which channels are overperforming or underperforming?" Recommendations at the top of the chart highlight "the most and least efficient channels based on expected performance." Wide confidence intervals carry a meaning of their own: when performance shifts in ways "that aren't explained by seasonality or holiday effects," the bands may widen, which "indicates that performance patterns have changed, and the model may need additional data to adjust."
Scenario plans take the opposite direction in time. Google describes them as a way to "understand return on investment (ROI) at different budget levels and create future media plans that drive the highest return based on your defined budget." The response curve can be explored interactively, and a projected performance view shows "how your plan will perform if no optimizations are made." Offline data enters the model when offline imports have been set up.
How the help page describes setup
According to Google, viewing the reports first requires the Advertising section to be configured, "including linking to Google Ads and setting up conversions." The route to the reports has three steps: sign in, select Advertising from the left menu, and click a report name in the Budgeting drop-down menu.
Projection plan, eight steps
- Sign in to Google Analytics.
- Select Advertising from the left menu.
- Under "Budgeting", click Projection.
- Click Create plan.
- Enter a plan name, for example "My Q4 plan".
- Enter a planning period, for example "Q4'25".
- Under target KPI, select Budget ("To spend the entire budget during the plan period"), Conversions or Revenue.
- Enter a target value for the selected KPI.
Scenario plan, nine steps
- Sign in to Google Analytics.
- Select Advertising from the left menu.
- Under "Budgeting", click Scenarios.
- Click Create plan.
- Enter a plan name, for example "My Q4 plan".
- Enter a planning period, for example "Q4'25".
- Under target KPI, select Conversions ("To drive the most number of conversions possible with my defined budget") or Revenue.
- Select a budget plan estimate.
- Select a conversion, from a list limited by "the amount of historical data available."
The sample planning period in both procedures is still "Q4'25", a quarter that ended almost eleven months before the November update.
Rules written into the documentation
Several sentences on the page define what the plans can and cannot do. On freezing: "If you check your plan during or after its date range, the response curve will remain the same as when it was first created. The curve reflects market conditions at the time of creation and doesn't update automatically unless you actively modify any of the plan settings such as budget, date range, target metrics." The next paragraph appears to narrow that: "To check the updated response curve and projections, create a new plan." Recommendations are described as "static estimates tied to the plan parameters at the time of creation."
On data scope, a note states: "The budgeting models consider all click-through-conversions, YouTube engaged view conversions and all cost data. Include impressions in your data import when available to prepare for future updates." Impressions, in other words, are not yet an input. On guarantees, both plan types carry the same caveat: projection outputs "shouldn't be treated as guarantees of performance," and scenario outputs are "estimates based on our model, and not guarantees of performance."
A year, two channels, or two years
One reply under the post asked the practical question. "is a full year of imported ad spend data still a prerequisite for this functionality?" wrote Ross (Uroš) Djunisijevic, an analytics specialist at Littledata.
Google's model documentation answers it, and the answer depends on the model. The help page says plans are powered by "either a DDA-based model or Google's open-source Meridian model," depending on whether a property runs standard Google Analytics or Analytics 360.
| DDA-based budgeting model | Meridian-based budgeting model | |
|---|---|---|
| Status on the cross-channel page | "currently in beta" | "currently in alpha" |
| Available to | Google Analytics and Google Analytics 360 customers | "only available to select Google Analytics 360 customers" |
| Minimum campaign data | At least one year, from at least two channels, Google and non-Google (Google's DDA-based budgeting page) | At least two years of imported campaign cost data (Google's Meridian-based budgeting page) |
| Minimum conversion data | At least one year per conversion | At least two years of conversion and revenue data |
| Training window | 12 months, to account for seasonality | Up to two years |
| Uses attribution as input | Yes, with data-driven attribution as the primary input to a Bayesian regression | No |
The table also qualifies the third claim in the LinkedIn post. Response curves "backed by data-driven attribution" describe the beta DDA-based model. Google's Meridian page says that model does not use attribution as an input. Meridian is a marketing mix model, which works from aggregated spend and outcome data. According to Google's DDA-based budgeting page, app conversions are not yet supported and key events are not supported. A September 29, 2026 entry on Google's What's new page put it more broadly: cross-channel budgeting features support web conversions only.
Where the non-Google data comes from
The two-channel threshold makes imported cost data the gate. The Budgeting overview page, according to the help page, shows recently created or modified plans, "Product links" to Google products such as Google Ads and Display & Video 360, and a "Cost import" panel listing "Usage, date of last upload, and file match rate," described as the way to "upload campaign data for non-Google campaigns and channels." A fourth panel, on manual third-party integrations, currently shows only static text. "In the future, this section will dynamically show which platforms have manual integrations available for budgeting models," the page says.
Google has spent more than a year widening that pipe. It added nine data sources for cost data import in June 2025, including BigQuery, Snowflake and Amazon S3, then shipped native connectors for Pinterest and Meta and TikTok in autumn 2025, each attempting to backfill at least 24 months of history. In November 2025 the feature was renamed campaign data import. According to Google's What's new page, a currency field became mandatory for cost uploads on July 28, 2026, and a validation report flagging campaigns without cost, clicks or impressions followed on August 10.
The worked examples
The help page includes two worked examples. In the projection example, an advertiser running a 12-week initiative against a $100,000 revenue goal finds itself under-pacing on spend and revenue after five weeks. The plan shows "Channel A is the most efficient with 75 ROAS, while Channel B drives the lowest ROAS," and the advertiser shifts $5,000 from Paid Social to Paid Search. The example does not say which channel is which, nor in what unit the ROAS figure is expressed.
The scenario example is tidier. A $50,000 budget for the first quarter, $1,500 more than the fourth quarter, is reallocated by adding $1,000 to Search and $800 to Video while cutting $300 from Display, for "3% more conversions." By PPC Land's calculation, the three moves net to exactly the $1,500 increase, and the implied fourth-quarter budget is $48,500.
Meridian's separate track
The Meridian route has moved faster in announcements than in availability. When Google said at Google Marketing Live that Meridian would come into Analytics 360 on May 20, 2026, PPC Land reported that the integration was listed as globally available, with predictive scenarios to guide budget allocation. Six months later, the cross-channel budgeting page describes the Meridian-based model as an alpha for select Analytics 360 customers, and Google's own page for the model describes it as part of a limited alpha release.
The open-source model itself sits outside Analytics. Google explained in a developer podcast why it made Meridian open source, describing the Analytics 360 version as a turnkey budgeting product for marketers, and the standalone Meridian Scenario Planner entered open beta with per-channel spend constraints on August 6, 2026. That planner and the scenario plans inside Google Analytics are different products with similar names.
Why it matters for marketers
Cross-channel budgeting is not new. Google Analytics launched it in beta on January 16, 2026, alongside an attribution analysis report and new conversion management for Google Ads customers, and Google's Eleanor Stribling later presented it as a reason for advertisers to bring cost data from their other media buys into Google Analytics. What the November update changes is the unit of analysis. Channel groups blur the comparison that budget holders argue over most, which is one platform against another. Splitting by source platform turns a recommendation about channel groups, such as paid social against display, into a ranking of named platforms.
That ranking comes from a model run by one of the companies being ranked. The budgeting models count click-through conversions and YouTube engaged-view conversions, according to the help page, and the DDA-based model, the only one most properties can reach, uses Google's attribution as its primary input. Platforms whose value shows up mainly in impressions or views outside YouTube have no equivalent input until impressions enter the models, which the page describes only as a future update. None of this makes the output wrong, but it shapes what the output can see.
The guardrails are explicit, though. No plan touches a budget, scenario curves freeze at creation, and every projection carries a disclaimer. For agencies and in-house teams that already build media plans in spreadsheets or third-party tools, the question is less whether the model is clever than whether a year of clean, multi-platform cost data sits in Google Analytics to feed it.
What the documentation does not say
The help page has no publication or update date and no rollout timeline for properties that cannot see the feature. It does not list which platforms are recognized as source platforms, define "sufficient historical data" for projection plans, or say whether plans created before the update gain the new dimensions or must be rebuilt. The LinkedIn post does not explain "in real time", and no entry on Google's What's new page records the change.
Key facts
- Feature: Cross-channel budgeting in Google Analytics (beta), Advertising section > Budgeting, desktop only
- Update: Source platform dimensions ("Source platform budgeting"); source grouping dimensions; source platform x campaign type dimensions (alpha-only)
- Announcement: Google Analytics LinkedIn post, November 19, 2026, opening "You asked for deeper ad spend visibility, so we expanded the view"; https://www.linkedin.com/posts/you-asked-for-deeper-ad-spend-visibility-share-7529204639775379457-Kd9J/
- Source document: "About cross-channel budgeting," Google Analytics Help, undated; https://support.google.com/analytics/answer/14896117
- Plan types: Projection (target KPI: Budget, Conversions, Revenue); Scenario (target KPI: Conversions, Revenue; future start dates only)
- Models: DDA-based budgeting model (beta, Google Analytics and Analytics 360); Meridian-based budgeting model (alpha, select Analytics 360 customers)
- Data thresholds, per Google's model pages: DDA-based, at least one year of campaign data from at least two channels including Google and non-Google, and one year of data per conversion; Meridian-based, at least two years of campaign cost data and two years of conversion and revenue data
- Inputs: Click-through conversions, YouTube engaged-view conversions and all cost data; impressions reserved for "future updates"
- Conversion scope: Web conversions only (Google What's new entry, September 29, 2026)
- Original launch: January 16, 2026, in beta
Timeline
- June 24, 2025 - Google Analytics adds nine new data sources for cost data import, including BigQuery and Snowflake.
- September 26, 2025 - Google Analytics adds a Pinterest cost data import integration.
- September 30, 2025 - Google updates Meridian with pricing variables and new priors.
- October 7, 2025 - Google Analytics launches Meta and TikTok cost data import integrations, backfilling at least 24 months.
- November 19, 2025 - Cost data import is renamed campaign data import.
- January 16, 2026 - Google Analytics launches cross-channel budgeting in beta, with projection and scenario plans.
- January 2026 - Google's Eleanor Stribling presents cross-channel budgeting as a way to bring other media buys' cost data into Google Analytics.
- February 10, 2026 - A second "Cross-channel budgeting (Beta)" entry appears on Google's What's new page.
- May 20, 2026 - Google announces Meridian's integration into Analytics 360.
- May 28, 2026 - Google explains in a developer podcast why Meridian is open source.
- June 11, 2026 - Google Analytics adds the Source Group field and updates Source Platform values.
- July 28, 2026 - Campaign data import begins requiring a currency field for cost uploads.
- August 6, 2026 - Meridian Scenario Planner opens in beta with per-channel spend constraints.
- August 10, 2026 - Google Analytics adds a campaign data import validation report.
- September 29, 2026 - Google states that cross-channel budgeting features support web conversions only.
- November 19, 2026 - Google Analytics says cross-channel budgeting now supports source platform dimensions.
Related PPC Land coverage
- Google Analytics drops three major features that will reshape how marketers track campaigns - The January 2026 beta launch of cross-channel budgeting, conversion management and attribution analysis.
- Google Analytics quietly worked its way back into advertisers' good graces - Eleanor Stribling on the January releases and the data cross-channel budgeting needs.
- Google Analytics adds Source Group field to fix messy cross-channel data - The June 2026 field that consolidates source values and reclassifies Source Platform.
- Meridian lands inside Analytics 360 as Google links ad spend to future sales - Google Marketing Live's announcement of Meridian in Analytics 360.
- Why Google made its ad budget model open source - and who can actually read it - What Google said about Meridian's open-source design and its Analytics 360 version.
- Google opens Meridian Scenario Planner beta with per-channel spend constraints - The standalone planner's fixed and flexible budgets and spend bounds.
- Google updates Meridian MMM with pricing variables and new priors - Non-media variables and new priors added to the open-source model in 2025.
- Google's new metric counts conversions up to 180 days after an ad click - Qualified Future Conversions, introduced at the same Google Marketing Live as the Meridian integration.
- Google Analytics renames cost data import to campaign data import - The November 2025 rename and where imported campaign data appears.
- Google Analytics launches Meta and TikTok cost data import integrations - Native connectors that pull cost, clicks and impressions with 24 months of history.
- Google Analytics adds Pinterest cost data import integration - The Pinterest connector and its import timing.
- Google Analytics adds nine new data sources for cost data import - Warehouse and file sources added to cost import in June 2025.
Summary
Who: Google Analytics, for advertisers and agencies whose properties are eligible for cross-channel budgeting. The Meridian-based version is limited to select Analytics 360 customers.
What: Cross-channel budgeting now supports source platform dimensions, so projection and scenario plans can compare individual ad platforms rather than broad channel groups. The help page also lists source grouping dimensions and an alpha-only source platform by campaign type dimension. The plans change no budgets in connected accounts.
When: Google Analytics promoted the update on November 19, 2026. The help page is undated. Cross-channel budgeting has been in beta since January 16, 2026.
Where: In the Advertising section of Google Analytics on desktop, under the Budgeting menu, for properties where the feature is available.
Why: Google Analytics says the change answers requests for "deeper ad spend visibility." For marketers, it moves Google's planning model from comparing channel groups to ranking named platforms, using Google's attribution data and imported cost data that must cover at least a year and two channels before the DDA-based model will run.
Discussion