Meta Ads reporting in GA4 and Looker Studio

#01The three ledgers

#02UTM standard that survives agencies

Example pattern (adapt, do not copy blindly):

• utm_source=meta
• utm_medium=paid_social
• utm_campaign={campaign.name} or controlled slug
• utm_content={ad.name}
• optional: dynamic campaign/ad ids via Meta URL parameters

Enforce in a naming doc. Audit weekly for facebook vs meta vs fb sprawl that splits GA4.

#03GA4 views to build

1. Traffic acquisition filtered to meta/paid_social.
2. Key events by session campaign and content.
3. Funnel exploration from landing to Schedule (GA4 funnels).
4. Compare against Ads Manager results for the same dates with both attribution notes in the chart title (GA4 for Marketers).

#04Looker Studio / Data Studio paths

Blend Meta spend with GA4 key events only after aligning date timezone and campaign keys (cross-channel ROI blend shipping soon).

#05Reconciliation ritual (30 minutes weekly)

1. Pull Meta spend + results (chosen window).
2. Pull GA4 key events for meta paid_social.
3. Pull CRM opportunities with Meta first/last/assist fields.
4. Compute three CPAs; paste into one slide with definitions.
5. Flag gaps > agreed threshold for debugging (UTM breaks, consent, CAPI).

#06Worked example: Ledgerline

Ledgerline is a fictional accounts-payable software company. Details are illustrative.

Walkthrough

1. Finance almost froze spend when GA4 showed 71.
2. Growth showed the dictionary slide and CRM assists; budget stayed.
3. Looker dashboard used BigQuery for GA4 + partner connector for Meta spend with labelled metrics.
4. Competitor A reported Ads Manager ROAS in the same cell as Google Ads last-click ROAS — leadership lost trust in all paid reporting.

#07Recommended Looker Studio pages for Meta

Build these once; refresh data sources carefully when Meta or GA4 schemas change (Looker Studio hub).

#08UTMs and Meta click IDs

Standardise UTMs for Meta campaigns and preserve fbclid where possible. In GA4, use clear source/medium values and investigate AI referral traffic separately (GA4 AI referrals). Do not rely on GA4 alone for Meta view-through influence.

#09Blending CAPI truth with GA4

GA4 may undercount iOS-influenced journeys that CAPI still sees. Annotate dashboards when EMQ or CAPI coverage changes so executives do not treat every CPA jump as creative failure. Link measurement incidents in the monthly review (lesson 20).

#10Weekly vs monthly reporting rituals

Do not make monthly strategic decisions from a single noisy day in Ads Manager.

#11Naming conventions that make reports usable

Enforce campaign names with market, offer, objective and date or version. Ad names should include concept ID. Without naming discipline, Looker Studio becomes a junk drawer. Publish the naming spec in the same doc as the UTM spec.

#12Connecting Meta to the rest of the stack

Useful joins:

• Meta → GA4 via UTMs
• Meta leads → CRM via lead ID
• CRM revenue → Looker
• Creative concept sheet → ad name

n8n can automate some syncs when APIs allow (n8n hub). Prefer stable contracts over one-off spreadsheet exports.

#13Ads Manager columns worth customising

Create a saved column set with: spend, impressions, reach, frequency, CTR, CPC, results, cost per result, purchases/leads value, and unique metrics you actually use. Add quality metrics if you optimise for them. Export the same column set weekly so Looker and spreadsheets do not drift.

For B2B, secondary columns for scheduling or messaging conversations help — but still join to CRM for truth.

#14Example executive narrative (illustrative)

"Meta spent €42k. CRM shows 70 SQOs at €600 each. EMQ stayed in the green band after the CAPI fix on 12 Oct. Creative concept C3 drove 40% of SQOs. We will scale C3, add two new concepts, and keep remarketing capped pending Lift." Replace figures with yours — the structure is the point: spend, pipeline, measurement, creative, decision.

#15Common mistakes

• Mixing windows across weeks without noting changes.
• No UTMs on Instant Form only campaigns (still use unique creative names + offline uploads where needed).
• Partner connector on viewer's credentials burning quotas (see Looker hygiene).
• Ignoring consent gaps in EEA that widen Meta vs GA4 deltas.
• One ROAS number for all channels.

#16Try it yourself

Export 7 days of Meta results and GA4 meta paid_social key events. Write three bullets explaining the gap for a non-marketer. Fix one UTM inconsistency you find.

#17Quick quiz

1. Name the three ledgers in the reconciliation stack.

Answer: Meta Ads Manager, GA4, and CRM/warehouse.

2. Why might Looker Studio not show Meta spend with Google connectors alone?

Answer: Google native connectors do not replace a Meta partner connector, Sheet or warehouse feed.

3. What belongs in every chart title comparing Meta and GA4?

Answer: The attribution definitions used on each side.

#18What should you check before the next lesson?

• UTM standard documented.
• Weekly reconciliation owner named.
• Ready to connect paid social to AI search discovery next.

Previous: Creative testing framework for Meta Ads. Next: Meta Ads and AI search discovery overlap. Or return to the Meta Ads for Marketers track. Related: GA4 for Marketers, Looker Studio for Marketers, GTM Meta Pixel and CAPI.

#19Common questions

Why does Ads Manager ROAS disagree with GA4? Different attribution models, windows, view-through credit, consent loss and channel grouping rules. Both can be "right" inside their definitions.

How should I UTM Meta ads? Consistent utm_source (e.g. meta or facebook), utm_medium (paid_social), utm_campaign, utm_content for ad name/id, and optionally campaign id parameters Meta supports — document one standard.

Can Looker Studio connect to Meta Ads natively? Google connectors focus on Google products; Meta usually needs a partner connector, Sheets export or warehouse sync. Budget partner connectors separately.