GA4 Cost Data Import: Setup, UTM Matching and Troubleshooting

To import advertising costs into GA4, create a Campaign data import source, map daily advertising data to the campaign labels your website actually collected, then check whether the imported rows joined. An accepted file is only the first check: spend can appear even when GA4 cannot associate it with your campaign traffic.

This guide uses a small, fictional LinkedIn campaign to show the CSV workflow. It also explains when a native connector is more suitable. The examples are instructional, not results from a live advertising account. Google documentation was reviewed on October 9, 2026.

What GA4 cost data import does

Google now calls this feature Campaign data import; “cost data import” remains a useful search term. You supply advertising cost, clicks or impressions and identifiers that connect those daily totals to campaign activity in GA4. Google’s current campaign import documentation

Data Import can enrich reporting using data collected earlier. Its query-time model is different from adding information to an event at collection time. It cannot recreate website sessions or purchases that your tag never collected. For historical work, test a small period and inspect the resulting joins before committing a full backfill. Google’s Data Import overview

The practical outcome is a campaign comparison that can include spend alongside measured website outcomes. It does not force GA4 to agree with an advertising platform’s conversion attribution, and it does not import an ad platform’s view-through conversions as website events.

Linked advertising products and manual tagging populate different traffic-source fields. Review Google’s tagging and integration guidance before treating a UTM import as a replacement for a product link.

Requirements and the 2026 changes

You need an Editor or higher role for the GA4 property. Have the correct property open, a daily campaign export, and a record of the UTM values used during the export period. The import wizard supports source-specific connections, including file and Sheets workflows. Import-source setup and permissions

Two recent changes matter: Google’s release notes record the currency update on July 28, 2026 and the campaign import validation report on August 10, 2026. Older tutorials may omit these. Analytics release notes

Gather exports at the campaign and date level, with the identifiers and metrics you need. Each platform’s export interface differs; do not assume every report has the same columns. Google’s platform export instructions provide starting points. Preserve the original export separately from your cleaned import file.

How UTM matching works

The import schema requires source, medium and date, plus at least one supported metric. Campaign ID and campaign name are optional but highly recommended. Matching is case-sensitive. The schema supports cost, clicks and impressions; utm_content and utm_term are not cost-import join fields. Required and optional schema fields

For this example, an ad would use the following destination:

https://example.com/demo?utm_source=linkedin&utm_medium=paid_social&utm_id=li-1042&utm_campaign=autumn-demo

Use the values visitors received, not a platform’s display labels. If GA4 collected linkedin / paid_social, importing LinkedIn / social creates a different key. If a campaign was renamed, retain the name used by each day’s landing URLs when that name is part of your mapping. Do not rewrite old website labels simply because the ad account now uses a cleaner name.

A stable ID makes campaign management easier, but adding utm_id today does not populate it on earlier visits. Inspect historical dimensions first. If old traffic has no ID, consider a compatible mapping rather than inventing IDs for it. Google’s import-source guidance explains how the selected schema dimensions control the join.

UTMCraft’s campaign name and ID guide explains the labeling choices; the naming conventions guide helps keep future campaigns consistent. Use the UTM builder to prepare labels, then verify collection separately.

Prepare a small, currency-ready CSV

Start with two dates from one campaign, rather than months of spend. The downloadable file below is a fictional template: replace every value and inspect the mapping before uploading it.

date,source,medium,campaign_id,campaign_name,cost,currency,clicks,impressions
2026-10-01,linkedin,paid_social,li-1042,autumn-demo,85.50,USD,114,6200
2026-10-02,linkedin,paid_social,li-1042,autumn-demo,92.75,USD,121,6600

Download the fictional cost-import CSV · Download the printable import QA checklist

1. Keep headers in the first row. These header names are your labels; the GA4 wizard maps them to its schema.
2. Aggregate before importing. If an ad-level export contains several rows for one daily campaign key, sum the relevant metrics into one row. Do not upload several copies of a campaign’s full daily cost.
3. Use unambiguous dates. YYYY-MM-DD avoids regional date confusion. Google supports other formats, but a date such as 03/04/2026 is harder to review safely. Supported input formats
4. Keep identifiers as text. Check for lost leading zeros, spreadsheet scientific notation, whitespace and altered casing.
5. Review the reporting day. Compare the ad account’s time zone with the GA4 property’s reporting time zone. If they differ, document the limitation; renaming the date column does not realign underlying activity.
6. Reconcile raw totals. Record the source export’s spend, currency, clicks and impressions for the selected dates before any transformation.

For each chosen join key, use one daily row. Google documents replacement behavior when another upload supplies metrics for the same key, so do not assume a later file is automatically added to an earlier total. Keep a versioned record of corrections and the intended resulting totals. Upload and matching behavior

Create and map the GA4 import source

1. Open the intended GA4 property. Go to Admin → Data collection and modification → Data import.
2. Select Create import source, give it a meaningful name, and choose Campaign data.
3. Choose the file connection offered by the wizard and select your prepared CSV. Follow any connection or upload prompts shown in your property.
4. Map date, source and medium. For this example, also map campaign_id and campaign_name.
5. Map cost, clicks and impressions. Map currency for the sample. If you use a fixed-currency option instead, confirm every row genuinely uses that currency.
6. Review the selected fields and preview. Finish the import-source setup and inspect the import result.

The connection-specific screens can vary. Use Google’s current wizard instructions alongside the interface rather than looking for an older tutorial’s button names.

Do not call the setup complete when the file is merely accepted. Record the import source, file version, date range, currency configuration and mapped join fields. Then move to validation.

Validate the join, not just the upload

The Campaign data import validation report is under Reports → Data Import. If it is absent from the navigation, an Editor can add it. The report’s default view focuses on paid manual campaigns and excludes Google/search medium combinations; review that filter before using its coverage to judge all your campaigns. Validation report setup and filtering

Match rate and report coverage have different denominators. Match rate considers the most recent two years of imported data. Coverage is based on rows with collected Analytics data in the report, so dimensions and filters matter. The status labels distinguish Joined, No campaign data and No Analytics data. Read a low figure as a reason to inspect rows, not an automatic instruction to change every campaign.

1. Restrict the report to the pilot dates and campaign.
2. Find joined rows and compare their daily metrics with the retained export.
3. For No campaign data, inspect whether a spend row exists and whether its key matches.
4. For No Analytics data, inspect tagging, collection and the selected mapping before changing the cost file.
5. Check currency and totals separately from join status. A joined row can still contain a mistaken amount.

Allow the documented processing window before concluding the import failed; Google notes that campaign import data can take up to 24 hours to appear in reports. Avoid repeated uploads while investigating a reporting delay.

Native connectors and Google Sheets: choose deliberately

Google documents direct campaign imports for Meta, Pinterest, Reddit, Snapchat and TikTok. For example, the Meta integration uses configured source and medium values and attempts to bring in historical data. Check for overlapping manual imports before enabling it. Its source/medium configuration also needs to match your existing labels; do not expect a connector to repair inconsistent historical tagging.

Keep platform URL setup separate from importing metrics. The Pinterest tracking guide and TikTok tracking guide explain those destination-side checks.

The Google Sheets Campaign Data Import add-on currently describes Meta and TikTok. It prepares campaign data in Sheets; you still need a configured GA4 import. A successful scheduled platform pull is not evidence that GA4 accepted and joined the data.

Troubleshoot missing cost or unmatched campaigns

When the website side is failing, follow the UTM testing workflow and the redirect troubleshooting guide. The UTM checker can inspect URL structure; it cannot prove that an event reached your GA4 property.

Common GA4 cost import questions

Is utm_id mandatory?

Not universally. The current campaign schema makes campaign ID optional but recommends it. Use it consistently for new campaigns and inspect historical availability before mapping it into an old-data import.

Can I import ad-level costs using utm_content?

The documented campaign import schema does not support that join field. Retain creative-level detail in your source reporting or another analysis system instead of promising ad-level cost matching through this feature.

Will importing cost fix ROAS?

It supplies a cost input. A useful return-on-ad-spend comparison also needs correctly collected revenue, compatible currency and a clearly defined attribution scope. Neither an accepted file nor a high match rate proves those conditions.

Should I upload the whole account immediately?

Prove the process with one campaign and a few dates first. Expand only after the mapped labels, join status and totals reconcile. Keep the printable checklist with your original export so another reviewer can repeat the checks.

For the broader setup, read UTM Operations: How to Build a Reliable Campaign Tracking Workflow. Browse the UTM Operations, Automation & QA guides to choose another troubleshooting task.