Google Conversion Tag Not Working on Pageload

[#1]

Hello, I'm trying to implement a Google Conversion tag for page load. I've created a page rule according to the following instructions:  http://digitalinsightsworld.com/tag-manager/setting-up-conversion-tracking-with-adobe-dtm/#gref . But I'm getting sort of a mixed response, it seems to be going through when I look at the Network windo in the dev console, but I'm getting an error that comes in the form of 'no HTTP response detected' in the google tag helper. Help? Not sure what's happening, and Google is not helping in any way.

[#2 · Accepted solution]

Hi,

I had implemented this before but never faced this issue. i would suggest you to check this alternative approach link How to Implement Google Re-Marketing Tag in DTM?  and see if that solves your problem.

thanks,

Muthu

[#3]

Thanks Muthu, That did the trick.

This was for the click conversions tag so all I did was change the URL, and added the conversion label variable.

Thanks!!

[#4]

Hi Leo,

I performed some research online and found this:

AdWords Remarketing Tag & Tag Containers  |  AdWords Remarketing Tag  |  Google Developers (Non-Adobe article)

If you are using the 'asynchronous AdWords Remarketing Tag', it seems using customized image tag should help resolved this for you.

Just to re-iterate, I don't have visibility into how these tags work, but this information may help. Let us know.

[#5]

Unfortunately, I'm not that familiar with Google's tags. Hopefully, another community member with a bit more experience in Google tags will see this and be able to provide better insight.

[#6]

Thanks, Jantzen. I'm seeing a google pagead call in the network with QSPs and everything, but I'm also getting an error in the console:

Refused to execute script from 'https://www.googleadservices.com/pagead/conversion/js&d=DwIBaQ&c=fP4tf--1dS0biCFlB0saz0I0kjO5v7-GLPt...' because its MIME type ('image/gif') is not executable, and strict MIME type checking is enabled.

I'm thinking that because the image/gif isn't executable then that might actually be keeping the tag from transferring data despite the fact that it's firing.

[#7]

Are you seeing the data come through on the other side (inside Google's reporting)?

Typically, the network tab of your browser is the most accurate tool to use when determining if a tag is being sent. Many of the browser plugins are watching for the tag to be sent a certain way. If you deploy the tag outside the normal method, the browser plugin can't see the tag. I can only assume Google wasn't planning on you deploying your tag through our Tag Management solution.