Google Ads Offline Conversion Tracking

How Google Ads Offline Conversion Tracking Works

Google Ads offline conversion tracking connects an ad interaction to a later CRM outcome. SupaBook can send eligible Qualified lead and Converted lead events through the Google Ads Data Manager API after your workspace records advertising-data consent and matching evidence. This helps Google learn from deeper business outcomes instead of optimizing only for initial form submissions.

Tips

• SupaBook preserves the original GCLID, GBRAID, or WBRAID when one is available.
• For enhanced matching, SupaBook normalizes eligible email or phone data and applies SHA-256 hashing on the server before upload. Raw email and phone values are not sent to Google by the browser snippet.
• Qualified lead values use the best supported estimate available. Converted lead values can reflect signed proposals and completed payments.
• Lost and Not qualified outcomes remain CRM evidence and are not sent as positive Google Ads conversions.

Official resources

• Google Ads guide to enhanced conversions for leads
• Google Ads offline conversion import guidelines

Connect Google Ads and Choose Conversion Actions

A workspace administrator completes Google OAuth once. SupaBook then discovers the advertiser accounts the connected Google user can access, including advertiser accounts reached through a manager account. You choose the correct advertiser and confirm the Qualified lead and Converted lead actions before automatic uploads begin.

1. Open Google Ads settings

   In SupaBook, open Settings, Integrations, then select Connect on the Google Ads card.

2. Approve Google access

   Choose the Google account that can access the advertiser and approve the requested Google Ads and Data Manager permissions.

3. Choose the advertiser

   Select the advertiser from the discovered list. SupaBook detects the required manager account path when applicable, so you do not need to type customer IDs manually.

4. Confirm or create conversion actions

   Review the recommended Qualified lead and Converted lead actions. If suitable import-from-clicks actions do not exist, use the create-actions option, then confirm the new selections.

5. Turn on automatic uploads

   Enable Automatic uploads and save. Only eligible events with the required consent and matching information enter the upload pipeline.

Important notes

• Use the advertiser account that owns the selected conversion actions. Choosing a manager account by itself is not enough.
• Do not turn an untested conversion action into a primary bidding goal immediately. Confirm diagnostics and allow enough conversion cycles to evaluate data quality first.

Send Qualified Lead and Converted Lead Outcomes

SupaBook queues the deeper event when your team records a supported CRM outcome. Marking a lead Qualified can send the Qualified lead action. A signed proposal or completed payment can create or update the Converted lead value with a stable transaction identifier so later revenue updates do not create a second conversion.

1. Capture the lead correctly

   Use a SupaBook form or pass the required attribution and consent fields from your existing form. The developer guide at /help/integrations/google-ads-form-attribution includes copy-ready examples.

2. Record the real sales outcome

   Open the lead and record Qualified only after your team confirms the opportunity meets its criteria. Record Not qualified or Lost when that is the true result.

3. Connect closed revenue

   Use signed proposals and completed payments so SupaBook can connect won revenue to the lead and update the Converted lead value accurately.

4. Review upload status

   Open Attribution and lead quality to see queued, processing, accepted, blocked, or failed events. Use Send pending conversions only when a manual retry is needed.

Tips

• Accepted means Google received the event. It does not guarantee that Google matched or attributed it to an ad interaction.
• An organic lead can remain useful CRM and revenue evidence. Do not relabel it as Google Ads traffic. Google can attribute it only when eligible consented identifiers match a prior ad interaction.
• Keep qualification rules consistent. Sending every inquiry as Qualified teaches the bidding system the wrong outcome.

Monitor Campaign Performance in Ads Manager

Open Ads Manager from the Google Ads integration card or workspace navigation. Compare Google campaign metrics with CRM funnel outcomes, identifier coverage, consent coverage, upload health, linked revenue, and bidding readiness across 30, 90, or 180 days.

Tips

• Run free review uses deterministic checks and costs 0 AI credits.
• Run AI analysis is optional and can use up to 1 AI credit. A matching cached result costs 0 credits.
• Campaigns load 25 at a time, up to 100. Use Load more campaigns for the next page.
• Recommendations are read-only. SupaBook does not silently change bids, budgets, campaigns, or conversion settings.

Troubleshoot Missing or Unmatched Conversions

Start with the blocked reason in Attribution and lead quality, then verify Google Ads diagnostics. Matching and reporting can take time, so separate SupaBook upload acceptance from Google attribution and bidding eligibility.

1. Check advertising consent

   The lead must have a recorded GRANTED advertising-data consent value. An absent or unknown consent record blocks user-data uploads.

2. Check identifiers

   Confirm the lead has an original GCLID, GBRAID, or WBRAID, or usable email or phone information for enhanced matching.

3. Check connection and action mapping

   Reconnect Google if requested, confirm the advertiser, and verify that both selected actions are enabled import-from-clicks actions owned by that advertiser.

4. Check the event age and diagnostics

   Upload promptly. Google documents shorter eligibility windows for enhanced lead imports than for some legacy click imports. Review the Google Ads offline data diagnostics before changing bidding.