GA4 Campaign Data Import Validation: Meta Ads Agency Checklist

Direct answer

Google Analytics now includes a Campaign data import validation report for checking whether non-Google campaign cost, click and impression data joins correctly. Agencies importing Meta Ads data should reconcile UTM values, campaign IDs, dates, currencies and totals before using GA4 for cross-channel budget decisions. The report can expose missing or incompatible data; it cannot reconcile attribution-model differences or prove incrementality.

What changed in Google Analytics?

Google announced the Campaign data import validation report on August 10, 2026. The report is designed to help users assess non-Google campaign data, identify campaigns missing cost, click or impression data and review previously imported campaign data.

Google documents the report at Reports > Data import > Campaign data import validation. It can be used before an import to inspect the paid manual and third-party traffic values already reaching the property, and after an import to compare imported cost, clicks and impressions with the third-party platform.

For an agency, that turns a vague question such as "Did the Meta costs reach GA4?" into a repeatable validation record. It does not make Meta and GA4 attribution models identical.

What should an agency validate before importing Meta Ads data?

Start with the join keys, not the dashboard totals.

Google says utm_source, utm_medium and the imported date are required for Campaign data import. Campaign ID through utm_id and campaign name through utm_campaign are optional but highly recommended. The values in the imported data must exactly match the values collected from destination URLs. Even case differences such as Facebook and facebook can prevent a clean match.

Before connecting Meta or uploading a file, preserve:

1. the GA4 property ID, timezone and currency;
2. the Meta ad account ID, timezone and currency;
3. the exact source, medium, campaign ID and campaign name values used in destination URLs;
4. the import method and source owner;
5. the intended date range;
6. the platform totals for cost, clicks and impressions; and
7. any earlier import source that overlaps the same campaigns and dates.

Google warns that overlapping Meta Campaign Data Import sources can duplicate data because Analytics does not deduplicate between separate import methods. An agency should therefore map the existing import inventory before enabling a new connector.

Original artifact: the three-layer import validation ledger

Use this ledger for each client and date range.

The ledger deliberately keeps platform evidence, import configuration and GA4 output separate. A green GA4 row without a preserved source total is not a reconciliation.

How should agencies use the validation report after import?

1. Confirm that the expected traffic values exist

Check whether GA4 has already collected the source and medium values used by the Meta destination URLs. If the property records facebook / paid_social but the import maps meta / cpc, the imported metrics may not join as intended.

2. Compare one controlled date range

Choose a closed range, preferably several full days that have finished processing in both systems. Compare campaign-level cost, clicks and impressions between Meta, the import source and the GA4 validation report.

Do not begin with an account-wide lifetime total. A narrow range makes timezone, currency, missing-day and duplicate-source errors easier to isolate.

3. Investigate missing dimensions before changing attribution settings

A missing cost row is usually an import or join problem, not evidence that an attribution model is wrong. Check the required source, medium and date fields first, then campaign ID, name and source connectivity.

4. Record a tolerance and an owner

Define the accepted variance for each metric before the review. The right tolerance depends on upload timing, currency handling and the source platform's finalization window. Name the person responsible for reauthentication, schema changes and failed imports.

Google notes that Meta logins used by the Campaign Data Import for Google Sheets add-on can expire after 60 days. Treat connector authentication as an operational control, not a one-time setup task.

Does the currency workflow differ by import method?

Yes. Document the path instead of assuming one universal rule.

Google's current direct Meta connection documentation says Campaign Data Import standardizes currency handling for imported cost. The separate Google Sheets add-on guidance says Meta and TikTok currency should already be converted to the GA4 property's currency and warns that Analytics may not display an error when a sheet indicates a different currency.

For manual or general Campaign data imports that include cost, Google requires a currency field. It can be mapped from the source or set as a static ISO 4217 value.

An agency should therefore record whether the client uses the direct Meta connection, the Sheets add-on or another import source. Never copy a currency assumption from one path into another.

Will this make Meta ROAS match GA4 ROAS?

No. The validation report checks the completeness and compatibility of imported campaign metrics. It does not force Meta and GA4 to use the same attribution model, conversion window, identity signals, consent state or event definition.

Imported Meta cost can improve the denominator in a cross-channel report, but the conversion credit in GA4 still follows GA4's measurement and attribution configuration. Meta's own interface may credit conversions differently.

Before changing budgets, an agency should separate three questions:

• Did the correct cost, click and impression data reach GA4?
• Are the key events, values and conversion windows configured as intended?
• Which decision model will the client use for budget allocation?

The Google Ads versus Facebook Ads framework can support the channel decision. It should not replace the import validation record.

Can public competitor-ad research help this workflow?

Public ad research can help explain what competitors visibly promote, but it cannot provide their private cost or attribution data.

Use the multi-platform ad-intelligence framework to compare observable Meta and Google messages, formats and landing pages. Use the ad creative analysis rubric to turn those observations into evidence for an original brief. Keep that research layer separate from the client's private GA4 and ad-account reconciliation.

If the agency is researching visible Google ads, the Google Ads Transparency Center workflow provides a source-bound method for recording advertiser identity, creative and landing pages.

What can public ad data not prove?

Public Meta or Google ad records cannot prove a competitor's spend, impressions, clicks, targeting, campaign IDs, UTM values, GA4 property configuration, import source, currency treatment, conversion windows, attribution model, revenue, ROAS, profit or incrementality.

A visible ad can establish that an advertiser used an observed message, format or landing page during an observed period. It cannot validate a competitor's campaign data import or explain why a private analytics dashboard moved.

What should the agency deliver to the client?

Create a compact import assurance pack containing:

1. the three-layer validation ledger;
2. the import-source inventory and overlap check;
3. the exact UTM naming convention;
4. source and property timezone and currency rules;
5. source-platform totals for a closed test range;
6. GA4 validation-report evidence;
7. explained variances and unresolved gaps;
8. the connector owner and reauthentication date;
9. the approved tolerance for future checks; and
10. the reporting caveat that import validation does not align attribution models.

This pack gives the client a traceable basis for cross-channel reporting without pretending that one dashboard creates a causal truth.

Frequently asked questions

Where is the Campaign data import validation report?

Google documents it under Reports > Data import > Campaign data import validation in eligible Google Analytics properties.

Which fields are required for campaign data import?

Google lists campaign source, campaign medium and date as required dimensions. Campaign ID and campaign name are optional but highly recommended. At least one of cost, clicks or impressions is required, and currency is required when cost is included.

Can agencies import Meta Ads cost into GA4?

Yes. Google documents a direct Meta connection and a Google Sheets add-on that supports Meta and TikTok. The setup, currency and authentication controls differ by path.

Does GA4 deduplicate overlapping import sources?

Google warns that using a Meta connection alongside overlapping previously uploaded data can duplicate reporting. Map and remove overlap before enabling a new source.

Does a successful validation prove the campaign was profitable?

No. It supports confidence that specified source metrics joined into GA4. Profitability still depends on reliable conversion values, commercial costs and an agreed decision model.

A restrained next step

Run the ledger on one closed seven-day Meta campaign range before rolling the workflow across clients. If the agency also needs an evidence library for visible competitor creative, the Advertisng Ad Library can organize public Meta and Google references. It cannot access private spend, GA4 imports or competitor performance.

Primary sources

1. Google Analytics Help: What's new in Google Analytics, Campaign data import validation report announced August 10, 2026; reviewed August 31, 2026.
2. Google Analytics Help: Import campaign data, including required fields, UTM matching, import sources, limitations and the validation report; reviewed August 31, 2026.
3. Google Analytics Help: Connect Meta to Google Analytics, including overlap and currency guidance; reviewed August 31, 2026.
4. Google Analytics Help: About the Campaign Data Import for Google Sheets add-on, including supported platforms, authentication and Sheets currency guidance; reviewed August 31, 2026.
5. Google Analytics Help: About Data Import, including import behavior, roles and quotas; reviewed August 31, 2026.
6. Google Analytics Help: All channels performance report, including report access and data requirements; reviewed August 31, 2026.
7. Google Ads Help: Google Display Ads campaigns have a new home in Demand Gen, reviewed August 31, 2026.
8. Google Ads Help: In-stream only video reach efficient reach campaigns are being upgraded to multi-format ads, reviewed August 31, 2026.
9. Google Search Central: Latest documentation updates, reviewed August 31, 2026.
10. Advertisng: Live sitemap, 17 published articles and 32 canonical URLs reviewed August 31, 2026.