Verify Google Ads conversions

Use Signals → Google Ads to verify conversions uploaded by CJM. The page shows attempts that reached the Google Ads delivery history; connecting an account alone does not create these signals.

Before expecting conversions:

1. connect Google Ads and select the correct Customer Account under Setup → Channels;
2. open Setup → Offline Conversion and create the five standard CJM conversion actions for automatic MQL and pipeline signals;
3. if you want to map a Pixel event to a different conversion action, create an active Server Tracking rule.

Automatic conversions

If Fit and Intent both meet the threshold during the first MQL qualification, CJM can upload both MQL conversions. Lead capture and ordinary web engagement do not create automatic Google Ads conversions; use a Server Tracking rule when you intentionally want one of those Pixel events to reach a conversion action.

How Google identifies the conversion

CJM looks for the most relevant Google Ads session and saved attribution. It can use:

• gclid, wbraid, or gbraid captured from an ad visit;
• normalized and SHA-256 hashed email and phone when no click identifier is available and adUserData is granted;
• the Profile ID as the order identifier for automatic milestones;
• the ecommerce transaction ID as the order identifier for a matching Server Tracking event, which allows separate repeat purchases;
• the configured conversion action, value, and currency.

When a click identifier exists, CJM uses it instead of contact identifiers. This reconnects the later CRM milestone to the original advertising click. Enhanced conversions provide a fallback when a click identifier is not available, but only with permitted contact data.

For automatic conversions, the currency defaults to EUR when none is provided. The value uses the monetary value first, then the score, then zero. For Server Tracking, ecommerce value and currency take precedence over the rule; otherwise the rule can use a fixed value or the Profile monetary value.

Consent and delivery conditions

CJM always passes the available adUserData and adPersonalization consent state to Google Ads. adUserData specifically controls whether email and phone can be included.

• With a click identifier, CJM can upload the conversion with the declared consent state and without contact data.
• Without a click identifier, CJM needs granted adUserData and at least an email or phone number.
• A gclid older than 90 days is not used by the current processor.
• The connection must be Active, the Customer Account selected, and the conversion action configured.

CJM checks duplicates both before sending and against saved conversion history. Automatic milestones are unique for the Profile and conversion action; ecommerce Server Tracking can distinguish transactions by transaction ID.

Read the Google Ads page

1. Open Signals and select Google Ads.
2. Choose the date range.
3. Filter by Status or the originating CJM Event when needed.
4. Select a row to inspect its friendly conversion-action name, raw conversion resource, origin, linked Lead, value, payload, response, and error.

The page tries to resolve the current conversion-action name from Google Ads. If it cannot, the raw resource identifier remains the reliable reference. Unmapped means the action does not match one of the five actions currently configured for automatic CJM milestones; it can be a Server Tracking action or an older configuration.

An Active row means CJM completed the Google Ads API request and saved it as successful. It does not guarantee immediate appearance, campaign attribution, or a particular reporting result in Google Ads.

If a conversion is missing or wrong

Check, in order:

1. the MQL or pipeline condition actually occurred, or the source event matched the Server Tracking rule;
2. the correct Google Ads Customer Account is selected;
3. the required conversion action exists and is configured under Offline Conversion, or is selected in the rule;
4. the Profile has a usable click identifier, or permitted email/phone;
5. value and currency exist at the intended source;
6. the conversion is not a duplicate already sent for that Profile and action.

Open an Error row for the stored response. If no row exists, focus first on the trigger, identifiers, consent, connection, and conversion-action setup.