I've been trying to figure out how to pass enhanced conversion data through to the Google Ads tag, per their documentation here:
I've updated the tag template to pass 'allow_enhanced_conversion':true through the config call, and that appears to be getting set properly. I've created data mappings to the enhanced_conversion_data object and keys they've defined in the documentation, as well as defining that within the tag template. I can see those values populating within the u.data object from a console.log I've placed in the tag, as well as the u.data.event_data object, however, I do not see this data within their tag request when attempting to validate how they've explained in the documentation; the "em" parameter is not appearing.
Can anyone be of assistance in implementing this feature of theirs?
I have the same issue. The request to Google Ads does not include em query string parameter.
The configuration in Tealium seems to be correct though. I believe that Enhanced Conversions must be also enabled in your Google Ads, once you configure and finalize Enhanced Converisons in Google Ads, then you should start seing em parameter being passed.
Hi @derek_miller ,
Not sure if it is still relevant, but we have solved the Enhanced Conversions puzzle :)
Your setup in Tealium sounds to be correct.
However, for Enhanced Conversions to work and "em" parameter being attached to requests you must enable Enhanced Conversions in Google settings. You can follow this documentation from Google.
Once Enhanced Conversions are enabled and configured in Google you should start seeing "em" parameter being a part of requests.