How to Set Up Conversion Tracking for Google Ads, GA4 and Meta

What Is Conversion Tracking (And Why Your Current Numbers Disagree)

Conversion tracking measures when a visitor completes a defined action and attributes it to the ad or channel that drove them there. A conversion action is any outcome you care about: a form submit, a phone call from a tracking number, a purchase, or a booking. Without that measurement, every dollar spent on ads is a guess.

Each ad platform counts conversions from its own point of view. If a visitor clicks a Facebook ad, later searches your brand name on Google and then converts, both Meta and Google Ads may claim the same conversion, because each one only sees its own touchpoints. Analytics that rely on a single touch give one channel all the credit and the rest none.

Without cross-platform reconciliation, you cannot tell which channel is driving conversions. Google Ads will report one number. Meta Ads Manager will report another. Microsoft Advertising will report a third. None of those numbers are wrong in isolation. They measure different things at different points in the same journey.

The "broken tracking" complaint usually comes down to three things: missing tags on key pages, no Conversions API to recover events lost to ad blockers and browser privacy restrictions, or no UTM naming convention, so traffic cannot be attributed back to a source. Fix those three gaps and most tracking problems resolve.

What a conversion action actually is

A conversion action is a specific event you define in your advertising platform. In Google Ads it can be a thank-you page view, a button click, or a phone call. In Meta it is a standard event such as Lead or Purchase. In Microsoft Advertising it is a goal recorded by the Universal Event Tracking (UET) tag. Each platform needs its own setup. If you set up a conversion action in Google Ads but never set up the matching event in Meta, Meta reports zero conversions regardless of how many leads you receive.

Why last-click attribution is misleading

Last-click attribution assigns 100% credit to the final touchpoint before conversion. That works only if the customer journey is a single click, and many are not. A visitor might see a social post, click a Google search result days later, then call from a different device. Last click gives all the credit to the final step. First click gives all of it to the social post. The truth sits somewhere between them, which is why Google Ads now defaults to data-driven attribution for most conversion actions.

Step 1: Audit Your Current Tracking Before You Add Anything

Before installing anything new, run through this checklist to see what is already working and what is missing. Knowing your starting point saves hours of trial and error.

1. Check Google Ads: go to Goals > Conversions and look at the status of each conversion action. "Inactive", "No recent conversions" or a warning that the tag is not verified means something is wrong. Usually the tag was removed, the thank-you page URL changed, or the action was set up but never installed.
2. Check Meta: use the Meta Pixel Helper browser extension on three key pages: your home page, your primary service page, and your thank-you page. Note which pages fire the pixel and which do not. If the pixel never fires on the thank-you page, Meta cannot see your conversions.
3. Check Microsoft Advertising: confirm the UET tag loads on every page and on your thank-you page. Microsoft offers its own UET Tag Helper browser extension for this.
4. Check UTM naming: if your paid social and email links have no utm_source, utm_medium and utm_campaign parameters, GA4 cannot attribute that traffic properly and may file it under the wrong channel.
5. Check for duplicate conversion actions in Google Ads. A common error is the same form submit counted twice because two conversion actions fire on the same thank-you page.

Google Ads conversion audit

Open Google Ads and go to Goals > Conversions. Look at the status column for each action. Active actions that are recording conversions are working. An inactive status means the tag has not fired recently. If an action shows no conversions even though leads are coming in, check that the tag is on the right page and that the conversion ID and label in the snippet match the action.

Meta Pixel audit

Install the Meta Pixel Helper extension. Navigate to your home page, your main service page, your contact page and your thank-you page. Note whether the pixel fires on each page and which events it reports. If it fires on your contact page but not your thank-you page, conversions go unreported. Events Manager in Meta also shows which events it has received and flags problems.

UTM naming audit

Look at your paid campaign URLs. Links from platforms that do not tag themselves must contain at least utm_source, utm_medium and utm_campaign. A URL missing any of these parameters makes it hard for GA4 to attribute the visit to the right channel. Build a consistent naming convention so every platform speaks the same language.

Step 2: Install Google Ads Conversion Actions (The Exact Sequence)

This section walks through creating and installing a Google Ads conversion action from scratch. Follow the steps in order and verify at each stage.

1. In Google Ads, go to Goals > Conversions and create a new conversion action for your website.
2. Choose how the conversion is recorded. For a form, the simplest option is a page load on the thank-you page, the page that loads AFTER the form submit, not the form page itself.
3. Set the value. Use the same value for each conversion if every lead is worth roughly the same amount, or leave the value off if you cannot estimate it.
4. Set the count. "One" counts one conversion per ad click and is the right choice for most lead forms, because a person who submits twice is still one lead. "Every" suits purchases, where each sale matters.
5. Install the Google tag (gtag.js) on every page of your site, then add the event snippet to the thank-you page only, or set both up in Google Tag Manager. The event snippet tells Google exactly when a conversion happens.
6. Verify with Google Tag Assistant. Load your thank-you page in a Tag Assistant session and confirm the conversion event fires.

Creating the conversion action

The conversion action definition lives inside Google Ads, not on your website. You define what counts as a conversion here: the source, the value and the count rule. The snippet you install on your site must carry that action's conversion ID and label. A mismatch between the two, or a tag on the wrong page, is a common reason conversions report zero.

Installing the Google tag

The Google tag (gtag.js) goes in the <head> of every page. It is the base code that the conversion event depends on. Without it, the event snippet on the thank-you page cannot report anything. Install it once across your entire site using your CMS template or Google Tag Manager. If GA4 already uses a Google tag on your site, you can connect Google Ads to the same tag.

Verifying with Tag Assistant

Open Google Tag Assistant, connect it to your site and load the thank-you page. Confirm that the Google tag loads and that the conversion event fires with your conversion ID. If it does not, check for a thank-you page URL that changed after the action was defined, or a snippet that sits on the wrong page.

Step 3: Install Meta Pixel + Conversions API (Don't Skip the API)

The Pixel alone misses a share of conversions. It runs in the visitor's browser, so ad blockers and browser and iOS privacy restrictions can stop it. The Conversions API sends events from your server directly to Meta, which recovers many of the events the browser misses.

Why the Pixel alone is not enough

The Meta Pixel fires when a browser loads a page and runs JavaScript. Ad blockers can strip it. Since iOS 14, Apple's App Tracking Transparency limits what Meta can measure from iPhone users who opt out, and browsers such as Safari restrict tracking cookies. How many events go missing varies by audience, which is why server-side events through the Conversions API are worth adding.

Installing the Pixel via GTM

Install the Meta Pixel through Google Tag Manager rather than editing site templates by hand. This gives you control over when and where the pixel fires. Add the Meta Pixel base code as a tag that fires on all pages, then add your conversion events as separate tags triggered on the right thank-you or booking pages.

Setting up Conversions API

Open Meta Events Manager and choose to add the Conversions API to your dataset. Many website and ecommerce platforms offer a built-in partner integration; otherwise a developer can send events from your server directly. Send the same conversion events (for example Lead and Purchase) through both the Pixel and the Conversions API, and give each matching pair the same event name and the same event_id so Meta deduplicates them. Without deduplication you double-count conversions. Use the Test Events tool in Events Manager to confirm that both browser and server events arrive and are being deduplicated.

Step 4: Name Your UTMs and Build the Attribution Bridge

UTM naming turns your ad spend into attributable data. Without it, paid social and email traffic can land in the wrong channel in GA4, and you cannot reconcile which platform drives conversions.

For Google Ads, turn on auto-tagging in your account settings. It adds a click identifier to every ad click, and once Google Ads is linked to GA4, the traffic is attributed to paid search automatically, so manual UTMs are not needed there. For every other platform, use a consistent pattern such as utm_source=facebook, utm_medium=paid_social and utm_campaign=spring_promo. Use medium values that GA4's default channel groups recognise (for example cpc for paid search or paid_social for paid social), and always include source, medium and campaign.

Use a UTM builder spreadsheet or a URL builder to enforce consistency. Every paid URL should pass through the same template so no campaign drifts outside the naming convention. Inconsistency here means GA4 splits your traffic across multiple source entries and your reports become hard to read.

Check the results in GA4 under Reports > Acquisition > Traffic acquisition, using the session source/medium view, to see which channels drive key events. Expect GA4's numbers to differ from each ad platform's. GA4 credits conversions across all channels by its own attribution model, while each ad platform counts the conversions it can link to its own ads, sometimes over a different window. A gap is a reason to investigate, not proof of untracked conversions.

UTM naming convention

The convention you choose matters less than the consistency you maintain. Pick a system, document it and stick to it. A broken convention produces more noise than no convention at all because you cannot tell which entry belongs to which campaign.

Cross-platform reconciliation

Reconciliation means comparing conversion counts across platforms and explaining the gaps. Google Ads will report one number. Meta will report another. GA4 will report a third. The differences are expected. What matters is whether the gaps are small enough to trust your spend decisions or large enough to mean something is broken.

• Google Ads

  What It Measures

  Conversions after a click (or view) on Google ads

  Why Its Number Differs From GA4

  Uses its own attribution model and counts by the date of the ad click

• Meta Pixel

  What It Measures

  Browser events on your site

  Why Its Number Differs From GA4

  Misses events blocked by ad blockers and privacy restrictions; also counts view-through conversions

• Meta Conversions API

  What It Measures

  Server-side events sent directly to Meta

  Why Its Number Differs From GA4

  Recovers many lost events; needs event_id deduplication

• Microsoft UET

  What It Measures

  Conversions after a click on Microsoft ads

  Why Its Number Differs From GA4

  Credits only its own ads, like Google Ads

• GA4 + UTMs

  What It Measures

  Sessions and key events by source/medium

  Why Its Number Differs From GA4

  Depends on consistent UTM tagging and Google Ads auto-tagging

When the Numbers Still Do Not Add Up

If you followed Steps One through Four and Google Ads still shows zero conversions, the cause is often a thank-you page URL that changed, a tag on the wrong page or a duplicate conversion action. Check those first.

If the data is inconsistent across platforms, you need a single, agreed source of truth, not more pixels. Extra tracking codes compound the problem rather than solving it. Consistent UTM naming and properly deduplicated events resolve more discrepancies than any add-on tool.

When to call in a professional

If you cannot find your thank-you page URL, if the Google tag will not install without developer access, or if your platforms report wildly different conversion counts with no clear explanation, a professional review saves weeks of guesswork. Skyline Digital Marketing sets up and audits analytics and reporting across Google Ads, GA4, Meta and Microsoft Advertising.

What a conversion audit covers

A proper conversion tracking audit checks Google Ads conversion actions, Meta Pixel and Conversions API events, Microsoft UET tags, GA4 attribution and UTM tagging, thank-you page URLs, duplicate conversion actions, and deduplication between the Pixel and the API. It does not stop at "is the tag there?" It answers whether the tag fires correctly, whether it reports the right action, and whether the data reconciles across platforms.

Skyline Digital Marketing was founded in 2024 in Anderson, South Carolina, by a team with enterprise IT and cybersecurity backgrounds, and its people hold Google Ads and Analytics certifications. To start, request a free website audit of your site's performance and technical issues, or ask for a free proposal covering your tracking setup.