Hi
We've been experiencing problems with our Google Adwords tracking code not working now for a couple of weeks, since we installed an SSL certificate on the site. No conversion data is coming into Adwords.
We've subsequently upgraded from Sellerdeck 2013 to 2016, reverted the Google Analytics / Adwords tracking elements to factory settings and it's still not working. The Adwords tracking code is just before </head> as recommended by Sellerdeck.
For some strange reason it's not possible to view the source file for a live receipt page on the site - it times out straight away. However, looking at the source file in preview mode, I might've found the problem. This is the Adwords code that's present:
<!-- Google Code for Purchase/Sale Conversion Page -->
<script type="text/javascript">
/* <![CDATA[ */
var google_conversion_id = 1071478598;
var google_conversion_language = "en";
var google_conversion_format = "1";
var google_conversion_color = "ffffff";
var google_conversion_label = "OBdhCNb5QxDG7vX-Aw";
var google_conversion_value = <actinic:variable name="OrderTotalBaseUnit" />;
var google_conversion_currency = "GBP";
var google_remarketing_only = false;
/* ]]> */
</script>
<script type="text/javascript" src="file:///C:/ProgramData/SellerDeck/SellerDeck 2016/Sites/Site1/PreviewHTML_Administrator///www.googleadservices.com/pagead/conversion.js">
</script>
<noscript>
<div style="display:inline;">
<img height="1" width="1" style="border-style:none;" alt="" src="//www.googleadservices.com/pagead/conversion/1071478598/?value=<actinic:variable name="OrderTotalBaseUnit" />¤cy_code=GBP&label=OBdhCNb5QxDG7vX-Aw&guid=ON&script=0"/>
</div>
</noscript>
I'm particularly interested in this part:
<script type="text/javascript" src="file:///C:/ProgramData/SellerDeck/SellerDeck 2016/Sites/Site1/PreviewHTML_Administrator///www.googleadservices.com/pagead/conversion.js">
It's adding a local file path to the destination of the Google javascript. Could this be the problem? Would it do something similar with the live site? How can I stop it from doing this?
Or do you think it could be something else causing the problem?
Many thanks for any help you can give on this
Jon
We've been experiencing problems with our Google Adwords tracking code not working now for a couple of weeks, since we installed an SSL certificate on the site. No conversion data is coming into Adwords.
We've subsequently upgraded from Sellerdeck 2013 to 2016, reverted the Google Analytics / Adwords tracking elements to factory settings and it's still not working. The Adwords tracking code is just before </head> as recommended by Sellerdeck.
For some strange reason it's not possible to view the source file for a live receipt page on the site - it times out straight away. However, looking at the source file in preview mode, I might've found the problem. This is the Adwords code that's present:
<!-- Google Code for Purchase/Sale Conversion Page -->
<script type="text/javascript">
/* <![CDATA[ */
var google_conversion_id = 1071478598;
var google_conversion_language = "en";
var google_conversion_format = "1";
var google_conversion_color = "ffffff";
var google_conversion_label = "OBdhCNb5QxDG7vX-Aw";
var google_conversion_value = <actinic:variable name="OrderTotalBaseUnit" />;
var google_conversion_currency = "GBP";
var google_remarketing_only = false;
/* ]]> */
</script>
<script type="text/javascript" src="file:///C:/ProgramData/SellerDeck/SellerDeck 2016/Sites/Site1/PreviewHTML_Administrator///www.googleadservices.com/pagead/conversion.js">
</script>
<noscript>
<div style="display:inline;">
<img height="1" width="1" style="border-style:none;" alt="" src="//www.googleadservices.com/pagead/conversion/1071478598/?value=<actinic:variable name="OrderTotalBaseUnit" />¤cy_code=GBP&label=OBdhCNb5QxDG7vX-Aw&guid=ON&script=0"/>
</div>
</noscript>
I'm particularly interested in this part:
<script type="text/javascript" src="file:///C:/ProgramData/SellerDeck/SellerDeck 2016/Sites/Site1/PreviewHTML_Administrator///www.googleadservices.com/pagead/conversion.js">
It's adding a local file path to the destination of the Google javascript. Could this be the problem? Would it do something similar with the live site? How can I stop it from doing this?
Or do you think it could be something else causing the problem?
Many thanks for any help you can give on this
Jon
Comment