Google Analytics this week updated its campaign data import feature to require a currency field whenever a marketer uploads cost data, closing a gap that had allowed financial figures to enter reports without any currency attached to them.

What changed in the July 28 update

According to Google's release notes published in the Analytics Help Center, the platform now mandates a currency value on any campaign data import that includes cost figures. Previously, cost uploads could be submitted without specifying a currency at all, relying instead on an implicit assumption that the imported figures matched whatever currency the Google Analytics property happened to be set to. That assumption held only as long as nobody touched the property's currency setting. If an administrator later changed it - say, moving a property from euros to dollars to reflect a business reorganization - historical cost imports would silently be reinterpreted under the new currency, distorting cost-per-click and return-on-ad-spend figures that finance teams had already reported on.

The fix is structural rather than cosmetic. Marketers configuring a campaign data source that includes cost metrics must now choose one of two paths. They can map the currency directly from a column already present in their data source, letting each row carry its own currency code pulled from the underlying file. Alternatively, they can apply a single, fixed currency across the entire dataset, useful for advertisers whose campaigns run in one currency throughout. Google Analytics did not specify a fallback for imports that omit both options; the practical implication, drawn from the feature's design, is that such uploads will not process until a currency is supplied.

Existing imports are unaffected by the change in a specific and important way. According to the documentation, any campaign data import already configured before the update will continue to report under the prior assumption - that the imported cost matches whatever currency the property currently uses. Google Analytics did not require retroactive remapping. This grandfathering approach avoids breaking dashboards and automated reports built on historical data, but it also means the underlying risk that prompted the fix - a currency mismatch between an old import and a changed property setting - remains live for any configuration created before July 28, 2026, until that source is edited or replaced.

Why the previous system created risk

The vulnerability traces back to how Google Analytics has long required imported cost currency to match property currency, a rule PPC Land documented as far back as its coverage of the February 2025 field simplification. That earlier update reduced the mandatory fields for cost data import to three parameters - source, medium, and date - stripping out explicit currency specification as a required input at the point of matching. The system instead expected currency alignment implicitly, checking that imported costs corresponded to the property's configured currency rather than asking the uploader to state it directly for every file.

That implicit design worked adequately so long as property currency settings stayed fixed. Agencies managing accounts across multiple regions, or companies restructuring finance operations after a merger or a shift in reporting currency, represented the scenario where the old system broke down. A cost import uploaded in, for instance, Japanese yen would be silently read as whatever currency the property later switched to, with no warning surfaced to the analyst pulling return-on-ad-spend figures from a blended report. Given that campaign data import numbers feed directly into non-Google cost-per-click and return-on-ad-spend calculations - metrics finance and marketing leadership use to judge channel performance - a silent currency reinterpretation could inflate or deflate reported efficiency without any visible error message.

Technical mechanics of the currency field

Google Analytics processes campaign data import as daily aggregates, a mechanic unchanged by the July 28 update. What has changed is the mandatory presence of a currency dimension whenever the cost metric is part of the upload. The two configuration methods differ in operational burden. Mapping currency from a column requires that the underlying data source - whether a CSV file, Google Sheets tab, BigQuery table, or a connection through Amazon Redshift, Amazon S3, Google Cloud Storage, HTTPS, MySQL, PostgreSQL, SFTP, or Snowflake - contains a field already populated with ISO 4217 currency codes, such as USD, EUR, or GBP. Fixed currency, by contrast, requires no per-row data; an administrator selects a single currency during setup, and every cost value in that import inherits it.

The choice between the two methods likely depends on how an advertiser's underlying campaign structure is built. A single-country retailer running all campaigns in one currency has little reason to map a column when a fixed value accomplishes the same result with less setup. A multinational agency consolidating spend data from campaigns priced in several currencies - a common scenario given that Google Analytics supports direct third-party cost data import from Meta, Pinterest, Reddit, Snap, and TikTok, none of which enforce a single reporting currency across an agency's client base - has a clearer incentive to map currency at the column level, since a fixed value would misrepresent every row not denominated in that one currency.

Neither Google's announcement nor the accompanying Help Center documentation specifies whether the two methods can be mixed within a single import job, nor whether currency conversion is performed automatically once a non-property currency is detected, or whether Analytics simply reports the raw imported figures alongside a currency label without converting them into the property's base currency for blended reporting. The existing "About campaign data import" documentation states broadly that Analytics handles all conversions of data for aligned reporting, referencing a general currency reference resource, but the July 28 release notes themselves do not restate that conversion behavior in the specific context of the new mandatory field.

The imported-data ecosystem this update touches

This currency requirement sits inside a data pipeline that Google Analytics has been expanding steadily since 2024. PPC Land reported that Google enhanced cost data import functionality on November 19, 2024, improving how the system handled unmatched imported cost data - a separate technical issue concerning join failures between imported rows and existing session data, distinct from the currency question addressed by the July 28 update.

The requirement for imported cost currency to match property currency is not new in principle; it is the enforcement point that has moved. PPC Land's coverage of the February 2025 simplification noted that the technical specifications already expected imported cost currency to match the Google Analytics property currency, describing this as a requirement that ensures consistency in financial reporting across advertising channels - but that expectation was not, at the time, backed by a mandatory field forcing an explicit statement of currency at upload.

The feature underwent a naming change separate from this currency update. PPC Land documented that Google announced on November 19, 2025, that cost data import would be renamed campaign data import, a change affecting terminology only. According to that announcement, Google stated the change better aligned the feature's name with its primary function of importing campaign-level attributes and metrics, such as cost, clicks, and impressions, from non-Google advertising platforms. That article's reporting confirmed the platform continued requiring that import currency match property currency at the time of the rename, meaning the underlying rule the July 28 update now enforces through a mandatory field had already existed in documentation form for at least eight months prior, without a technical gate preventing violation of it.

Data source expansion has run in parallel with these naming and requirement changes. Google Analytics added nine new data sources for cost data import in June 2025, including Google Sheets, Amazon Redshift, Amazon S3, BigQuery, Google Cloud Storage, HTTPS, MySQL, PostgreSQL, and Snowflake. Direct platform integrations followed in sequence: Reddit Ads gained native cost tracking, Snap Ads and Pinterest received integrations in September 2025, and Meta and TikTok integrations arrived on October 7, 2025, as PPC Land reported at the time. Each of those direct integrations pulls cost, click, and impression data automatically from the respective advertising platform, and each - under the July 28 currency requirement - would now need a currency field specified as part of its configuration if it has not already been set up with one.

Why this matters for cross-channel budgeting

The currency requirement has consequences beyond the import screen itself. PPC Land's coverage of the January 16, 2026 beta launch established that cross-channel budgeting - a feature allowing advertisers to project performance and test budget allocation scenarios across all paid channels - depends on imported cost data from advertising platforms using campaign data import, alongside properly configured conversion tracking and sufficient historical data. That article noted the projection functionality particularly benefits businesses managing substantial advertising budgets across multiple platforms, since scenario planning enables what-if analysis that previously required manual spreadsheet modeling or third-party planning tools.

Budget projections built on cost data carrying an unverified or mismatched currency would compound the same distortion risk documented above, but scaled across an entire cross-channel planning exercise rather than a single report. If a property's currency setting changed after a cost import was configured under the old system, and that import fed both a standard cost-per-click report and a cross-channel budget projection, the projection itself would inherit the same silent misstatement. The July 28 field requirement addresses the entry point for new imports; it does not, on its own, retroactively correct projections already built on legacy imports that predate the fix, since those imports continue reporting under the prior currency assumption as Google's documentation specifies.

Attribution accuracy work happening elsewhere in the platform reinforces why currency-level data hygiene has taken on more weight recently. PPC Land's reporting on the Source Group field, introduced June 11, 2026, described how cross-channel budgeting tools are more reliable when the underlying source data is consistent, and how attribution models produce cleaner output when a single advertising platform is not split across a dozen variant source strings. Currency inconsistency represents a parallel failure mode to source-string fragmentation: both corrupt cross-channel comparisons at the data-ingestion layer rather than in the reporting layer where the error would otherwise be caught and flagged to an analyst.

What administrators should verify

Google's release notes direct users toward the existing "Learn more about campaign data import" support article for full configuration guidance, rather than publishing a standalone walkthrough specific to the currency field. The documentation makes one grandfathering point explicit: any existing campaign data imports will continue to report under the assumption that the imported cost matches the current property currency, meaning organizations do not need to immediately reconfigure sources that were already functioning correctly.

Where the update does introduce new friction is at the point of creating or editing a cost-bearing import source going forward. Google Analytics' third-party direct integrations - covering Meta, Pinterest, Reddit, Snap, and TikTok - along with its file- and database-based connectors, would each require a currency field the next time a cost-bearing source is newly configured or reconfigured under the platform's standard setup flow, based on the update's stated scope of applying whenever a marketer uploads cost data.

Timeline

Summary

Who: Google Analytics administrators and marketers who configure campaign data import sources containing cost figures, spanning agencies, multinational advertisers, and any organization importing advertising spend data from non-Google platforms.

What: Google Analytics now requires a currency field on every campaign data import that includes cost data. Configurators can either map currency from a column already present in their data source or apply a single fixed currency across an entire dataset. Existing imports configured before the change continue reporting under the previous assumption that imported cost matches the property's current currency setting.

When: Google published the update in its "What's new in Google Analytics" release notes dated July 28, 2026.

Where: The change applies across Google Analytics properties globally, affecting every campaign data import method - CSV, Google Sheets, BigQuery, Amazon Redshift, Amazon S3, Google Cloud Storage, HTTPS, MySQL, PostgreSQL, SFTP, Snowflake, and direct third-party connections to Meta, Pinterest, Reddit, Snap, and TikTok.

Why: The mandatory currency field closes a gap where cost imports lacking explicit currency data relied on an implicit match to property currency, a match that could silently break if a property's currency setting changed after an import was configured. Since campaign data import feeds directly into non-Google cost-per-click, return-on-ad-spend, and cross-channel budgeting calculations, an unstated or mismatched currency risked distorting financial metrics without surfacing any error to the analyst relying on them.