Google Ads Enhanced Conversions integration

Upload confirmed conversions from SourceTrack to Google Ads as click conversions, matched on the Google click ID the visitor arrived with. When the conversion carries an email address, SourceTrack adds it as a SHA-256 hash.

Server-side sending to ad platforms is in beta. Every attempt, success, failure and skip is listed in SourceTrack so you can check what reached Google Ads. Google decides what it accepts and how it counts it.

What SourceTrack records

• Google click IDs: gclid, gbraid and wbraid from the landing page URL. The standard tracker keeps the latest click ID in the browser, so a conversion on a later page of the same site can still carry it.
• A delivery log: each upload attempt appears under Delivery Health as sent, failed (with Google’s error) or skipped (with the reason). A conversion with no Google click ID is not listed, because there was nothing to upload.

What SourceTrack sends to Google Ads

• The click ID (gclid, gbraid or wbraid) and the conversion time.
• The conversion action you chose for that kind of conversion.
• The value and currency, only when they are known. A conversion with no measured value is sent without one, never as zero, and a currency is never guessed.
• The order ID as the transaction ID, which Google uses to ignore a repeat of the same conversion.
• A hashed email, when the conversion has one, normalized the way Google documents before hashing.
• A hashed phone number, when the order or checkout includes one: SHA-256 of the number in E.164 format. It is sent only when the number carries a country code, or is a US or Canadian number on a US or Canadian address; otherwise no phone is sent.
• Consent signals (ad_user_data, ad_personalization), only when your consent banner set them through Google Consent Mode.

What SourceTrack does not do

• It does not upload a conversion that has no Google click ID.
• It does not send names or addresses to Google Ads, and it sends no phone number it cannot put in E.164 form with certainty.
• It does not send a conversion the visitor declined consent for, or one from a browser that sent Global Privacy Control or Do Not Track.
• It does not send test conversions, or browser conversions that were never confirmed (see below).
• It does not create or edit conversion actions in your Google Ads account.

Step-by-step setup

Server-side sending is not part of the free plan.

Step 1: Connect Google Ads

In SourceTrack, open Integrations and connect Google Ads with your Google account, then select your Google Ads Customer ID. This is the same connection that imports your Google Ads spend.

Step 2: Add a conversion action

Under Advanced Tracking → Server-side Conversions (CAPI), open the Google Ads card. Enter the numeric ID of the default conversion action (used for purchases), and click Enable forwarding. In Google Ads, create this action for SourceTrack with the type Website (Import from clicks). Set it as primary only if no Google Ads tag or GA4 import already counts the same sale as primary.

Step 3: Optional actions per conversion type

You can enter separate action IDs for leads, trial starts, subscriptions and lead stages (qualified, MQL, SQL). A lead stage is only ever sent to its own action. Without one, it is skipped rather than counted as a purchase.

How it works under the hood

A conversion is uploaded only after something SourceTrack trusts has confirmed it: a Stripe or Shopify payment webhook, your inbound webhook signed with your secret API key, or a CSV import by a site owner or admin who ticks the box confirming the sales are real. A conversion reported by the browser alone is held for up to 72 hours and released only when a payment webhook confirms the same order.

SourceTrack signs in to Google with the connection from Step 1 and calls the Google Ads API’s click-conversion upload. Google can accept the request but reject the row inside it, for example a click outside the action’s click window. SourceTrack reads that answer and records the upload as failed, not as sent. Temporary errors are retried for up to 24 hours.

Common problems and fixes

• Conversions never show up for Google Ads. They most likely had no Google click ID. Check that auto-tagging is on in Google Ads and that the landing page keeps the gclid in its URL.
• A skip says no account or conversion action is set. The connection has no conversion action for that type yet. Add one in Step 2 or Step 3.
• The connection stopped working. The Google grant was revoked or expired. Reconnect Google Ads from the card.
• A conversion is counted twice. SourceTrack sends to its own click-import action. If a Google Ads tag or a GA4 import also records the same sale, keep only one of those actions as primary for bidding. Google removes duplicates by transaction ID only within one conversion action, so a matching transaction ID does not merge two different actions.

Related guides

• Google Ads setup guide
• Click IDs explained: gclid, fbclid, msclkid
• Why Google Ads and GA4 numbers don’t match
• Troubleshooting tracking problems
• All integrations

---

Frequently Asked Questions

Is this the same as Google’s enhanced conversions?

Partly. SourceTrack adds a hashed email and, when it has one in E.164 form, a hashed phone number to a click conversion. It does not send names or addresses, and it does not upload conversions that have no click ID.

What if a visitor buys days after clicking the ad?

The standard tracker keeps the latest click ID in the browser, so a later purchase on the same browser can still carry it. Google decides whether the conversion falls inside the action’s click window.

Is it live for every account?

It is in beta. Check Delivery Health after your first conversions to see what Google accepted.