I use Google Adwowrds and Analytics for my website, when I check, as the main source of sessions, is shown paid searches (adwords), but Google Analytics shows that most of the referrals for transactions (Purchases) from my own website.
There are two possible reasons for this in my situation. Cross Domain Tracking and Page Dropping Cookie.
Regarding Cross Domain Tracking, I use single domain, but after the customer checks out, the Thank You page comes with Shopify domain, can it be considered that I use multiple domain?
Regarding the Cookie Drop out, how can I find it out? and fix it.
When a user moves from one domain (your domain) to another domain (the Shopify domain) then a new Google Analytics cookie is generated and this cookie has a difference client ID stored in it for Google Analytics. So even if the Shopify domain is sending data to the same Google Analytics property, since the client ID is different, Google Analtyics will treat this as a new user and a new session and in the eyes of Google Analytics, this session will be a referral from the first domain (your website).
If you want to prevent this from happening, you must implement cross-domain tracking which you can read about here.
Related
I'm currently using the same Google analytics account id for two different domains (and cross-domain tracking not enabled, on purpose). My understanding is that Google analytics will assign the same Google analytics account id to the browser for all websites that are using the same Google analytics account ID (even if cross-domain is not enabled), but when I check it seems that I'm assigned two separate Google analytics account id's.
What you know about clientId is wrong. ClientId values are stored in cookies on a per-domain basis, and websites on one domain cannot access cookies set for another domain.
To keep the same clientId across different domains you need to implement cross-domain tracking.
https://support.google.com/analytics/answer/1034342?hl=en
I have a website and its booking engine (2 different domains) at work and visitors land on the website and then proceed to the booking engine.
I have installed Google Analytics correctly to measure conversions that take place in the booking engine domain. Everything getting recorded correctly in Google Analytics account.
We recently launch Google Ads campaign and I saw that there is another parameter named '_gl' needed to append to the booking engine URL when a visitor proceeds to the booking engine via the website for correct cross domain tracking (probably to avoid Safari tracking prevention).
Just wanted to know, how important this _gl parameter for cross domain tracking since I already have correct Google Analytics setup in place and have linked Google Analytics and Ads accounts.
Thank you!
The parameter you mention is very important in order to correctly track users between two domains, otherwise GA cannot link the same user when they browse from one domain to another.
I have my UA setup across three sites www.aerserv.com, platform.aerserv.com, and support.aerserv.com. I want to be sure I'm tracking users across the domains properly so the analytics don't see each visit from one user as a "new user".
Is there a way to verify that I've setup my tracking correctly and Google isn't mis counting visitors?
Subdomain tracking is done out of the box in GA, and the only thing you need to make sure is that the cookie domain setting is set to 'auto', and that the referral exclusion list includes the main domain. Once you have those set, and if all pages across all applicable subdomains are tagged, then you should not have any issues. If you need to check, then you can look at the client ID (cid) for each pageview hit from one subdomain to the next. The client ID should be the same.
We are currently using Marketo for our landing pages but it is not the same domain as our company site. We are also using Google Analytics.
We have used this guide to tie our Analytics session to our anonymous or known Marketo record by inserting the Marketo User ID as a Google Analytics User ID and added the Marketo User ID dimension & set the scope as User.
Per this article, if we would like to have our Lead ID be recognized on non-Marketo landing pages, like our Corporate website, that we will need to do some extra API connections. Has anyone done this with success? I found that there is some Cross Domain Sub-Domain Tracking located here.
Would I only need to tie the visit to our corporate site to the Marketo Sub-Domain site visit as stated in the link above, which would then be tied to the MarketoID dimension that we just made shown in the first link provided?
Not sure what to do to make this happen or if it is as simple as doing the cross domain sub-domain tracking.
Apologies if I am not making any sense.
Thank you so much!
I'm not sure I understand your question entirely.
Are you trying to link/merge a known Marketo record on one domain to an anonymous Marketo record on another domain, and then pass that single Marketo record ID to Google Analytics?
This would involve matching the Munchkin cookies on both domains to Marketo records, probably via the REST API, then merging the two records.
Once you have merged the records from the two domains, you could pass this single Marketo ID to Google Analytics, using the same ID for both domains.
Resources:
http://developers.marketo.com/javascript-api/lead-tracking/api-reference/#munchkin_associatelead
http://developers.marketo.com/blog/get-a-visitors-cookie-id-and-then-query-associated-lead-data/
You can develop a javascript that capture the GA ID and MKTO cookie and store them in a databased. Then, sync the database with mkto and append the GA ID to the lead record.
We've developed a tool that does that automatically, without any coding and allows you to track leads/visitors cross devices and domains.
Check it out: https://gapidu.com/
I manage a website that sells business cards: Oubly.com
I believe the previous developer did not install the Google e-commerce tracking correctly.
Every single transaction since 2014 has been attributed to
Direct.
Coming from previous experience working with another e-commerce site I know that this is impossible. The previous e-commerce site I worked with had various transactions from various sources.
conversions
The amount of transactions is correct, I just know that they all cant be coming from Direct.
How can the current developer tell if the tracking code was installed correctly?
Right now there's not enough information to tell you 100% what is your problem. But likely you are losing the cookie when tracking the transaction.
The most common cause is that the hostname of the page that tracks the transaction is different than the hostname on your website. Google Analytics stores a unique and random clientId in a cookie when a user visits your website. If your site suddenly changes to a new domain such as a payment partner domain the cookie won't be accessible anymore, so GA thinks this is a new user and recreates a cookie. That starts a new User and a new Session in GA often with the trafficSource of (direct).
The solution is to implement cross-domain tracking for GA. Cross-Domain tracking helps you pass cookies from one domain to another so GA knows that it's the same user.