My company uses GA for a landing site we have. When a user sends us an email from the site, GA counts this as a conversion. However, the referrer is our own site so we never know where they came from. The referrer information gets lost once they arrive at the "Send us an inquiry" page.
How can we get this information?
Thank you.
Related
A user clicks on a referring link to visit our eCommerce website, but does not yet place an order. Then the user goes back directly to our website at a later point and places an order. How can we set up in google analytics / tag manager that the initial referrer should stay the referrer for this user?
Example: A customer visited example.com and clicked on a link to our website. Then the customer bookmarked our website url. Then at a later point, the customer visits our website through the bookmark or through a Google search. How do we track that example.com was the original referrer for this customer?
Thank you for your help.
If the user returns with the bookmark, the previous source will automatically result as a consequence of the standard Google Analytics attribution model. While if accessed from organic search this will overwrite the previous source.
What you can do to save the first source is to install a cookie on the user's browser so that the first time it saves the source in a custom dimension, while if the cookie already exists it does not save it.
I have a Flickr account with some photos that have links in their description linking to my website. However, when checking in my Google Analytics account the Source/Medium, it appears as direct/none, although I would expect it to be flickr/referral.
I have read here that it could be due to the ad blockers, but it is not the case since I did the test with a browser without any ad blocker extension installed.
Also, according to this:
https to https = should send referral info
http to http = should send referral info
http to https = should send referral info
https to http = no wont send referral info
To track https to http:
If you use custom campaign tagging on the url then it should pass whatever info
you put into the tags as the medium/source etc.. make sure to test
that though
Other alternatives would be to:
either change the site B
to https too
or
use an internal redirection script to send visitors
to a http page on the https site before then passing them thru to the
http website
Flickr is https, my site http.
However, facebook is also https and I am getting those properly. According to this other post:
sites like facebook and similar are https but are setup specifically
on their side to allow passing of referral information
How can I make that GA shows those visits as flickr/referral?
The only solution I found is, as suggested in the second quote of the question, to use a custom campaign tagging and add the following to the link:
?utm_medium=social&utm_source=flickr.com&utm_campaign=photo
Then it will be shown properly in Google Analytics.
I found this article very useful to learn about Custom Campaigns.
Note that this does not work if one cannot edit the description, i.e., it will work for own content only.
We have Multiple products, all are using one SSO (Single Sign On & Registration). So when visiting product A: www.AAA.com, the user (when register or sign-in) will have to go to: sso.mainsite.com to go through registration or login, then it will redirect him to the product page that he came from.
I want to track unique users properly so:
I know each user from where he was acquired. (e.g. Mailchimp campaign? Social Media?..etc)
Each user activity in the product is always linked to him (Made purchase, did an activity...etc)
Statistics Not be affected by the common SSO site, where multiple product users are directed there to login or register. I want to be able to identify product A users.
We have Analytics Account for the main site (inc. SSO) and an account for product A. I'm having difficult time:
Should I use the product A tracking code in the SSO (to have multiple tracking codes on that page)?
Identifying users by Google's new User ID, should we let the SSO identify them (assign ID) or by Product A, when the user get transferred there?
I know i'm asking a lot, but i'm having difficult time knowing what is the best approach, not to damage any statistics. Thank you!
If you want to track the session on www.AAA.com without interruption it should be enough to add sso.mainsite.com to the referral exclusion list in the property settings in www.AAA.com's GA account.
That way sso.mainsite.com will not appear as a referrer, instead the session including channel attribution will be continued when you redirect back from sso.mainsite.com. This will completely ignore the pageviews on your sso page.
The alternative would be to set up cross domain tracking, if you want to include the detour to sso.mainsite.com into the tracking. That would be somewhat complicated, and unless you signal that this is really what you want I will not even bother to explain the setup.
We're using Google and Facebook SSO allowing our users to sign up and login with these services. However, if a user signs up or logins in with either service (rather than creating a standard email login), we lose the referral source in Google Analytics -- and, instead, sign up and upgrade sources are attributed to accounts.google.com or Facebook.com. Anyone have some thoughts on a workaround?
This requires some backend work. Whenever one of your users clicks on the login button with either services, you backend should 'remember' him using a cookie or any other parameter. In that way whenever he comes back from exactly the url of your Facebook SSO or accounts.google.com you should set the GA tracker referrer parameter to the one of your site's URL. You can do this in basic js code like this
ga('set', 'referrer', 'mydomain.com');
In this way you won't see these invalid referrals anymore.
Been searching for an answer for this for a while but nothing that I can find that is useful.
Basically in the organisation I work in we use Shibboleth for user authentication.
We probably have 200+ sites & Shibboleth works effectively for these.
However, one site in particular is protected using Shibboleth (if the user is not a valid user they have to sign up for an account in this process also) which is causing an issue with our Analytics (Google Analytics). The referrer to the site is ALWAYS the shibboleth authenticator.
What we need is a facility to track conversions on this site based on source/campaign the user arrived from. The proposed solution right now is to use a Tag Manager product to fire off specific tags based on a combination the referrer or campaign. This one single site is used for a multitude of things (all prospective leads to EPR) but we need different information based on how the user landed on that page.
We are tracking all the interaction points that lead up to this (i.e. tracking potential leads) but a lot drop out during the signup process and right now we do not have actual conversion data, meaning the Marketing etc is being spent based on highest traffic source rather than which source or campaign is most effective.
The problem is when a user signs in, signs up using Shibboleth, Shibboleth sets a new cookie for that session. In Google Analytics all the referrer to this site are from the authenticator.
Is there some configuration issue with GA that I am overlooking for this scenario or is there something that can be done with Shibboleth so that the initial referrer (rather than the authenticator) being passed as the referrer which in turn would facilitate the rule creation of the Tag Manager to fire off the required tags
If you use Universal Analytics, you might be able to overcome using the new Referral Exclusion:
You can exclude specific domains from being recognized as referral
traffic sources in your Analytics reports. A common use for this
feature is to exclude traffic from a third-party shopping cart to
prevent customers from being counted in new session and as a referral
when they return to your order confirmation page after checking out on
the third-party site.
Google Analytics recognizes the URL you use to set up a new property
in your account and automatically excludes this domain from your
referral traffic, so you won’t see self-referrals in your Analytics
reports.
https://support.google.com/analytics/answer/2795830?hl=en
Another option might be to pass a parameter across the login page when you request an authentication. If you set your fields in the request correctly, you could have Shibboleth send your user back to any page or with any query string, such as adding ?source=original_page_name. After authentication, these parameters should be available to manipulate or pass on to GA. This won't actually spoof your referrers, but it will get you the data you need.