How to connect Meta Ads with Google Analytics 4: current process and limitations

Reports show visits and conversions from Facebook or Instagram, but Meta Ads costs remain in another system. Every campaign evaluation then turns into exports, spreadsheets and arguments over different attribution. The direct Google Analytics 4 connector reduces this problem — if you expect the right thing from it.

The current integration imports aggregate campaign data from Meta into GA4: costs, clicks and impressions. It does not import Meta Pixel events into GA4 and does not send GA4 conversions back to Meta. Campaign optimisation in Meta still uses Pixel and, where appropriate, Conversions API as a separate layer.

What the integration gives you

• costs, clicks and impressions from Meta campaigns directly in GA4,
• a shared view of paid channels in acquisition and advertising reports,
• the ability to relate costs to visits and conversions measured in GA4,
• fewer manual exports for regular reporting.

You do not get one indisputable truth about attribution. Meta and GA4 use different identifiers, models, windows and available consent. Different numbers are therefore not automatically an error. What matters is knowing which system you use for which decision.

Prepare before connecting

According to the current Google Analytics documentation, you need:

• an Editor role or higher in the relevant GA4 property,
• access to the Meta Business account and advertising account,
• consistent UTM parameters in the ads’ destination URLs,
• a decision on whether the same data is already being imported into GA4 another way.

The last two points are frequent sources of trouble. The connector must match an advertising row to a GA4 session using source and medium values. If one campaign sends utm_source=facebook, another utm_source=meta and a third sends nothing, the report will not be clean.

Recommended UTM tagging

Google requires source and medium for the import. I also recommend adding the campaign and its identifier. You may choose the exact values, but they must be stable and match exactly between the import settings and the links in the ads.

utm_source=facebook
utm_medium=paid_social
utm_campaign=campaign_name
utm_id=campaign_identifier

For Instagram you can use a separate source, such as instagram, if you want to report it that way. Decide in advance whether you need to distinguish platforms or want to keep Meta campaigns in one group. Rewriting a taxonomy later is usually more expensive than thinking for ten minutes at the start.

Current Meta and GA4 connection process

1. Open the correct property in Google Analytics 4 and go to Admin.
2. In the property section open Data import and choose to create a new data source.
3. Select Campaign data as the type and Meta as the source. Some accounts may also offer the entry in product integrations.
4. Sign in to the Meta account and grant the connector the requested access.
5. Select the correct Meta Business account and advertising account. For companies with several accounts, check the ID rather than only a similar name.
6. Enter the UTM source and medium exactly as the ads send them. Complete the campaign settings according to your taxonomy.
7. Save the import and wait for the first processing.
8. Check the data in reports and compare several specific campaigns with Meta Ads Manager.

Google says the first import may take approximately 30 minutes and appear in reports after up to 24 hours. The connector may also attempt to load up to 24 months of historical data. Do not expect everything to appear immediately after clicking Save.

Watch for duplicate costs

If you previously uploaded costs through CSV, another connector or a data warehouse, periods may overlap. Google recommends removing older overlapping imports, otherwise costs can be doubled in summaries.

The configuration of an existing Meta connector also cannot be changed arbitrarily. When changing an account or mapping, you may need to delete the source and create it again. First record the original settings and check which periods GA4 already contains.

Where the integration most often fails

Source and medium do not match

paid-social, paid_social and cpc are three different values. Likewise, Facebook and facebook can create an unexpected split. Take the real destination URL from an active ad and check the settings character by character.

The ad loses UTMs during a redirect

A shortener, intermediate domain or incorrectly configured redirect can remove parameters. Test the final URL in a browser and use DebugView or the Realtime report to verify what actually reaches GA4.

You expect identical conversions in Meta and GA4

Meta may attribute a conversion using information and attribution settings that GA4 does not have. GA4 sees the user journey across sources according to its own model. Compare trends and explain differences; do not force two identical numbers.

You connected the wrong account

Agencies and company groups often have several Business and advertising accounts with similar names. Prepare their IDs before authorisation and check the currency and time zone.

Meta Pixel, Conversions API and GA4 have different roles

Meta Pixel measures browser events for Meta. Conversions API can send marketing data server-side and complement browser measurement. GA4 analyses the website and application across sources. A direct campaign import into GA4 only adds advertising costs and related metrics.

All three layers can therefore run at once in practice. Each needs its own quality checks. If you are still getting oriented in events and conversions, my Google Analytics 4 guide continues from here.

Consent and measurement

The technical integration does not solve the legal basis or user consent. Consent Mode passes Google information about the user’s choice, but it is not a cookie banner and does not itself ensure legal compliance. Handle the measurement scope and consent method according to the specific website, region and legal assessment.

How to tell whether the integration helped

Not by a green connector status. Select several stable campaigns and compare costs, clicks, currency, period and UTM values. Then check whether the report answers the business question: which campaigns bring relevant enquiries at a sustainable cost.

Older versions of this guide used a process through partner integrations in Meta Business Suite and suggested that Pixel events were transferred to GA4. That no longer matched the current product, so I rewrote the guide. If you need to check a specific account, UTM taxonomy and import duplicates, contact me via contact.