All updates

You can now send backend conversion data into the same web conversion action as…

Share on LinkedIn

Until now, a CRM connection through Data Manager fed a separate offline conversion action. That meant the same sale could be counted twice, or one source ignored for bidding.

The new Beta in the conversion action settings changes that:
Tag and backend data live in one conversion action
Google deduplicates using the transaction ID
Conversions your tag missed are recovered from your backend
Your backend can be the source of truth for conversion value, so real revenue and refunds count
A 14 day trial lets your tag keep bidding as usual while you check the match rate

It works with HubSpot, Salesforce, Klaviyo, BigQuery, Snowflake and Google Sheets.

Watch out: without a transaction ID in your tag there is no deduplication, so you will overcount. Keep the same currency and units in tag and backend.

Spotted by Thomas Eccel.

The week in Google Ads, in one email.

Free. Read by 125K+ marketers every week.

Subscribe for free

Seen something new in your account?

Send me the screenshot