Google Ads
This section discusses how to migrate the Adobe-built Google Ads extension to the Acronym-built Google Site Tag (gtag) extension.
Last updated
Was this helpful?
This section discusses how to migrate the Adobe-built Google Ads extension to the Acronym-built Google Site Tag (gtag) extension.
Last updated
Was this helpful?
This extension does not have any extension configuration to migrate. However, since the is a required extension to make the Adobe-built Google Ads extension work properly, that extension to ensure the Acronym-built Gtag is configured correctly.
The Adobe-built extension only has one rule action to migrate: Track Conversion.
The track conversion rule action sends conversion data to Google Ads.
Below is an example of what a successful migration would look like for the Track Conversion action:
The Track Conversion action is equivalent to the the gtag extension provides. There are five fields that should be migrated over:
The conversion ID is the same as the Account ID in the gtag extension (starts with AW- or DC-). If you haven't already done so for this conversion ID, in the gtag extension.
The conversion label should be migrated to the new Acronym-built gtag action, under the for the Ads account.
The conversion value should be migrated to the for the event action.
Both currency code and order ID will need to be migrated as an in the event action. You should use the field names currency and transaction_id, respectively.
Note: If you're only using Google Ads for this rule, then you may need to add the , which wasn't previously required in the Track Conversion action. If you're using Google Analytics as well, then you likely already have an event name to use!
