5.9K members online now
5.9K members online now
Use AdWords conversion tracking and reporting to measure your results. Have a question about Google Analytics? Post it here, on the Google Analytics Community!
Guide Me

https and conversion tracking

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭

Hi Guys,


Are there any known issues around Adwords conversion tracking code on secure thank you pages?

Recently a site I'm working with changed to https and conversions reported seem to be down substantially.


They are using the latest version of the Adwords conversion tracking code, so that is not an issue. I was wondering if something else may be responsible, such as https pages slower load time meaning conversion tracking may not be fired before the visitor closes the page?


Any thoughts?



1 Expert replyverified_user

Re: https and conversion tracking

Top Contributor
# 2
Top Contributor
Hi David.

No, there's no issue that I'm aware of and every single website I'm tracking has the code on https, as they're E-Commerce websites and all the checkout process, including the thank you page, is on secure areas of the website.

Is it possible for you to try some test conversions yourself to see how the elements on that page load in the developer console? In theory it is possible for someone to close that page after seeing the thank you message, especially if they're using a buggy internet connection and the trip to is a long one.
Calin Sandici, AdWords Top Contributor | Find me on: Google+ | Twitter | LinkedIn | myBlog
Was my response helpful? If yes, please mark it as the ‘Best Answer.’ Learn how here.

Re: https and conversion tracking

Follower ✭ ✭ ✭
# 3
Follower ✭ ✭ ✭
For what @AdWiser mentioned, I like to run this debugger:

Do the http: pages all redirect to https:?

Are you seeing goals firing in Analytics at all? Because the gaq.push there is probably more reliable to fire if the case @AdWiser mentioned is true.
Marked as Best Answer.
Accepted by topic author David O
September 2015

Re: https and conversion tracking

Visitor ✭ ✭ ✭
# 4
Visitor ✭ ✭ ✭
Turns out a code change that went live at the same time as the change to https cause the conversion tracking code to be pushed into the head of the page, instead of the body.
Thanks guys.