Skip to content
Use cases

Send offline conversions to Google Ads

Report deals from sales back to Google Ads, through the Data Manager API with gclid, gbraid and wbraid, or as enhanced conversions for leads with hashed contact data.

The problem

Google Ads sees the form on your website, but not what happens in sales afterwards. Uploading offline conversions by CSV is tedious, and the gclid often gets lost between form and CRM.

How to do it

  1. Create a conversion actionIn Google Ads, create a conversion action of the type "Import from clicks" per sales step, for example "call" and "deal".
  2. Connect your Google loginSign in with Google in TSO and allow access for the Data Manager API. For enhanced conversions for leads, the customer data terms must be accepted in the Google Ads account.
  3. Set up the destinationPick the account and conversion action from the list and choose the event this action counts.
  4. Report the sales stepsSend calls and deals to TSO by webhook, API, CSV import or Stripe.
  5. TestIn test mode, Google checks every conversion without taking it. Afterwards the delivery log shows what was sent.
Destinations
  • Meta dataset
    Conversions API · Lead, deal won, purchase
    active
  • Google Ads
    Import from clicks · enhanced conversions
    active
  • LinkedIn
    Conversions API · own token
    active
  • Microsoft Ads
    UET Conversions API
    Test mode
DeliveryDeal won · €4,800
  1. Ad click · Meta
    Oct 12 · Sales call · Lookalike
  2. Lead · form detected
    Oct 12 · email and phone
  3. Deal won · webhook from the CRM
    Nov 3 · €4,800
  4. Sent to platforms
    Meta ✓Google Ads ✓LinkedIn ✓

What the conversion sent to Google contains

For each conversion, TSO sends:

  • the person's latest Google click (gclid, else gbraid or wbraid),
  • hashed email addresses, phone numbers and names, normalised by Google's rules,
  • IP address and user agent of the visit, unless you hold them back,
  • value and currency, and the event ID as the transaction ID.

You can hold back fields per destination. Whether Google processed a conversion shows later in the conversion action's diagnostics in Google Ads.

Website and offline conversions together

For website actions, the TSO script can load the Google tag and report events with the same ID the server uses. That way one setup covers both: the form in the browser and the deal from sales.

The result

Deals from sales arrive in Google Ads as conversions automatically, with a click ID or hashed contact data. Smart Bidding can bid on calls and deals instead of forms.

Common mistakes

Works with

  • Google Ads
  • Webhook
  • CSV import
  • Stripe

Frequently asked questions

How is this different from uploading through the Google Ads API?

For new integrations, Google takes click conversions through the Data Manager API. TSO uses it directly; you don't need a developer token of your own.

What happens without a gclid?

TSO then sends gbraid or wbraid if available, and hashed email addresses, phone numbers and names for enhanced conversions for leads.

Is consent passed to Google?

Yes. Consent comes from the visits that click, page and IP come from. For deals without a visit, you set on the destination what is reported.

Does Google count twice if the tag reports too?

No. The event ID goes along as the transaction ID, and Google counts a conversion with the same ID once.

More use cases

Set it up in your project.

Hosted in Germany · Built in Austria