Google gtag.js Issues (Explanation of the issue and request for Tealium to update)

After digging through a lot of other posts regarding various issues with the tealium approach the the new gtag formats, I believe I have uncovered the fundamental issue. First, let's look at how this is supposed to work without a tag manager. There are 2 tags that need to be used to track DCM conversions.

A global snippet and an event snippet.

The global snippet should only contain the account IDs for your google products while the event snippet should contain your unique floodlight activity ID.

The global tag needs to fire first and looks for a "gclid" value and writes a first party cookie of that value (_gcl_aw). The event snippet should then fire and look for that cookie and insert it into the server call. A successful server call looks like this:

The request for Tealium to fix this would be to edit their template to fire as the above snippet while replacing the ID variables as well as adding the data mapping capabilities for the custom parameters. There should be one tag in the marketplace for the Global gtag.js which is an all pages rule for account IDs and a 2nd tag template for event snippets which are just the JS code and do not attempt to assemble a server call. Thanks and I hope this helps someone.

Google gtag.js Issues (Explanation of the issue and request for Tealium to update)

@gderkatch I know this is an old post, but this issue should now be resolved in the latest version of the Floodlight tag in the marketplace. It does trigger conversion events as you described, by calling gtag('event', 'conversion', {send_to: "adid/group/activity+method"});