GA4, Meta Pixel and Conversions API: A Setup Checklist

Most ad accounts we audit in Amman share one problem: Meta, GA4 and the store never agree. A small gap is normal; a large one means you optimise on bad data. This checklist walks you through a clean GA4, Meta Pixel and Conversions API setup, in the order we build it for clients.

Why does conversion tracking break?

Tracking used to rely on one browser script that set a cookie and reported every visit. That model is weaker now, for three reasons:

• Browsers limit cookies. Safari's Intelligent Tracking Prevention shortens the life of cookies set by scripts, and Firefox and Brave block many trackers by default. A buyer who clicks today and buys next week may not be linked to that click.
• Ad blockers stop scripts. Many blockers prevent the Meta Pixel, and sometimes the Google tag, from loading at all. Those visits and purchases never reach the platform.
• iOS privacy features. Since iOS 14.5, apps must ask permission before tracking people across other apps, and many users say no. Newer iOS versions also remove some tracking parameters from links opened in Mail, Messages and private browsing.

Consent banners add another layer: if a visitor declines cookies, consent-aware tags will not fire fully. The fix is a stack, not one tool: clean browser tags, a server-side connection, consistent campaign tagging and regular testing.

What should a complete tracking setup include?

Build it in this order. Each step depends on the one before.

How do you set up GA4 and Google Tag Manager?

1. Create the GA4 property. Set the reporting time zone to Jordan (or your client's market) and the currency to JOD, SAR or AED, so revenue reports make sense.
2. Add a web data stream for your domain. Keep enhanced measurement on: it records scrolls, outbound clicks and site search automatically. Copy the Measurement ID, which starts with G-.
3. Install Google Tag Manager on every page, in the head and body, as Google instructs. On Shopify or other hosted platforms, follow the platform's current recommended method.
4. Add the Google tag in GTM with your Measurement ID, set to fire on all pages. Publish only after testing in Preview mode.
5. Send your business events. For a store: view_item, add_to_cart, begin_checkout and purchase, with value, currency and transaction_id. For a lead business: generate_lead on the thank-you page or the form's success event.
6. Mark key events. GA4 now calls the actions that matter most key events; the old name was "conversions". Mark purchase or generate_lead as key events, not every click.
7. Link Google Ads to GA4 and keep auto-tagging on.

How do you connect the Meta Pixel and Conversions API?

The Meta Pixel is the browser side. The Conversions API sends the same events from your server or platform directly to Meta, so they still arrive when a browser blocks the Pixel. Meta recommends using both together.

1. Create or select your Pixel (Meta also calls it a dataset) in Events Manager, inside the right business portfolio. Keep one Pixel per business, even when agencies change.
2. Install the Pixel through GTM, a direct code snippet or a partner integration.
3. Turn on the Conversions API. The easiest route is a partner integration. Shopify's built-in Meta integration, for example, can send server events once you choose the higher data-sharing level in its settings. Custom sites need developer code or a server-side tagging container.
4. Send customer information that the platform allows, such as hashed email and phone, so Meta can match more events to real people. Events Manager shows an Event Match Quality score for each event.
5. Verify your domain in Business settings, using a DNS record or a meta tag. This proves the site is yours and gives your business control over its events.
6. Check your events. Confirm that the standard events you need (PageView, ViewContent, AddToCart, InitiateCheckout, Purchase or Lead) arrive with value and currency, and pick the right one as the optimisation event in your campaigns.

Why does event deduplication matter?

When the Pixel and the Conversions API both send a Purchase, Meta receives it twice. If it cannot tell they are the same, your results look inflated and the algorithm learns from false signals. Meta deduplicates when both events share the same event name and the same event ID. The rule: create one unique ID per action (the order ID works well for purchases), send it as eventID in the Pixel and as event_id in the server event. Partner integrations usually handle this; confirm it in Events Manager.

How do UTM parameters fit in?

Pixels report each platform's own results. UTM parameters tell GA4 where every visit came from, across all channels. Add them to every campaign link:

• utm_source: the platform, such as facebook, tiktok, snapchat or newsletter
• utm_medium: the channel type, such as paid_social or email
• utm_campaign: the campaign name
• utm_content: the ad or creative, useful when you test

Write down one naming convention for the team. Meta can insert dynamic values, like the campaign name, in its URL parameters field. Google Ads uses auto-tagging, so you rarely need manual UTM tags there. Build clean, consistent links with our free UTM builder.

How do you test tracking and keep it healthy?

Test before you spend:

• GTM Preview: confirm each tag fires once, on the right page, with the right values.
• GA4 DebugView: with Preview or debug mode on, watch events and their parameters arrive in the DebugView report.
• Meta Events Manager, Test Events: open your site, browse and buy, and check each event arrives from browser and server, deduplicated.
• One real test order or lead: check its value and currency in both platforms.

A simple weekly health check

Block 20 minutes in your calendar each week:

1. Compare last week's orders or leads in your store or CRM with GA4 and Meta. A sudden bigger gap means something broke.
2. Open Events Manager diagnostics and fix any new warnings.
3. Check Event Match Quality for your Purchase or Lead event.
4. In GA4, look for traffic labelled "(not set)" or "Unassigned". It usually points to missing or broken UTM tags.
5. After any theme, app, checkout or landing page change, re-test the full path.

This is the routine we teach in our Tracking, Analytics & Dashboards course in Amman, on a real or practice site.

Learn it hands-on in Amman

A checklist tells you what to do; building it on a live site is how you learn it. In Algurus Academy's Tracking, Analytics & Dashboards course in Jordan, you set up GA4, Google Tag Manager, the Meta Conversions API and a live dashboard step by step, and learn to report which campaign brings each sale and lead. It runs for 4 weeks (8 live sessions), in person in Amman or live online. The price is 220 JOD, or 3 payments (74 + 73 + 73 JOD).

Questions? Contact us or message us on WhatsApp.