5.7K members online now
5.7K 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

Tracking Conversions Across Subdomains

Visitor ✭ ✭ ✭
# 1
Visitor ✭ ✭ ✭



I have two domains, and  The www subdomain is my website; the "my" subdomain is a Web application. Leads come in through Google Adwords ads and land on the www homepage. When they click "Create an account", they're redirected to Google OAuth2 authentication where the lead logs in with his/her Google account. Afterwards, we redirect the lead to the subdomain.




I'm trying, quite unsuccessfully, to track Adwords conversions where a user lands on the www site, creates an account, and lands on the "my" application. Without having a "thank you page", the conversion code is placed in an iframe and loaded on the page from a file called "googleconversion.html".  


I can see the requests in the NET tab to Google, for both the Google Analytics as well as the Adwords conversion code; however, the page still says "Unverified".


Here is the Google Analytics code I'm using on "www" and "my":



  var _gaq = _gaq || [];
  _gaq.push(['_setAccount', 'UA-29953813-1']);
  _gaq.push(['_setDomainName', '']);
  _gaq.push(['_setAllowLinker', true]); // adwords
  _gaq.push(function() {
    var pageTracker = _gat._getTrackerByName(); // Gets the default tracker.
    var linkerUrl = pageTracker._getLinkerUrl('');
  (function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src=('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);


On the "www" website, I also overrided the click handler as per these instructions:


        // prevent default click behavior and instead use the _link functionality of GA to pass cookies to the other site and 
          // redirect. 
        $('.green_btn, .long_green_btn, #loginButton').click(function() { //alert("is this really working?")
        	_gaq.push(['_link', '']); 
        	return false;

The click handler is applied to all of the "Create account" buttons on the page.  However, I'm not sure this should even be necessary. I'm not passing the user to a completely different domain, only to another subdomain, which should theoretically have all of the cookies, since the _setDomainName argument is set to ""!


Conversion Request:


In my Chrome NET tab, I can see the following request made to Google:


Thus, it's clear the application recognizes that this is a conversion, and loads the iframe with the conversion code. 




  • Is it possible the cookies aren't being passed to the "my" domain? How can this be verified? What specifically am I looking for?
  • Is the Google Analytics code even needed to track conversions?  Can we rule this out and just focus on the conversion tracking only or is this required?
  • I've had only 2 conversions since placing the code, but I have no way to tell if those people actually clicked on an ad or was referred from another site. Thus, there is no feedback from Google as to whether this is setup properly. 
  • I noticed that the "Create Account" link, when clicked, does pass all of the parameters to the domain, but only if I'm authenticated already through Google!  If I get redirected to Google to login, the parameters are lost once the Oauth process completes and the user is redirected to!  Thus, if the _link GA command is really required for subdomain tracking, then this may explain the problem. My goal was to completely eliminate a signup process by just logging the user in via Google; however, this makes tracking conversions a nightmare.


Please let me know if there is any other information I can provide to help troubleshoot this issue. Thank you!



Suggestion to Google Adwords Engineers:

  • Add a "VERIFY NOW" button so admins can simulate an ad click through to actually 100% instantly without a doubt verify that the tracking is working. Seriously! Please! Smiley Happy  Aside from asking a question here, all I can do is wait for what I think might be a real ad click through and then repeat this entire process, using guesswork. Meanwhile, we're paying for ads for which we can't make intelligent, informed adjustments to without conversion feedback, and we can't turn them off because allegedly the only way to verify conversions is to wait for one to happen Smiley Sad
1 Expert replyverified_user
Marked as Best Answer.
Accepted by Zee (Community Manager)
September 2015

Re: Tracking Conversions Across Subdomains

Top Contributor
# 2
Top Contributor

Hi James,


Wow...lots of info there. 


Perhaps I'm under thinking this here but what is stopping you from placing your AdWords Conversion code on the page?  I may be missing something here but I think all that needs to happen is for the click cookie to meet the conversion code. 


Your Analytics set-up is separate situation and is not needed to track AdWords Conversions.  Cross domain Analytics tracking is feasible but not needed for the AdWords portion of conversion tracking.


You should also keep in mind that only users who click on ads can be counted as AdWords Conversions it's a very black and white set up when comparing to Analytics. 


Hope this helps!



Tommy Sands, AdWords Top Contributor | Community Profile | Twitter | Philly Marketing Labs
Did you find any helpful responses or answers to your query? If yes, please mark it as the ‘Best Answer.’

Re: Tracking Conversions Across Subdomains

Zee Community Manager
Community Manager
# 3
Zee Community Manager
Community Manager
Hi james-mortensen,

I approached the technical support with your query. Unfortunately, we can't provide more details for your customized code implementation.