I have a form on my WordPress site that posts to a SalesForce URL.
When the form is submitted, the post happens to SaleForce, the user is directed to the SalesForce URL briefly and then returns to the WP site.
Analytics is wrongly tracking leads from Ads as if they are coming from SalesForce. I have excluded the SalesForce domain in my Analytics. However, I'm not sure if what I've done is the best practice.
Does anyone have any ideas?
Thanks
Chris
Yes, excluding a referral is a best practice for example for payment gateways in an e-commerce (i.e. paypal.com). In this way the traffic from paypal.com (when you return after the payment) will be recognized in Google Analytics as direct traffic, so the session is not interrupted and the source remains the original one (i.e. organic or ads). The same thing makes sense with your case and SalesForce.
Related
Our email marketer is sending email from GetResponse with a tracking code generated from another tool,
but we can't see if the users are coming from the email source.
Is it possible, because it is with tracking code generated from other tool, GA to mark it as direct traffic and is there a way to know it is coming from the email campaign? Also, I am not sure it is tracking it at all, becouse I don't see much traffic in the landing page. The GA is fired, I checked!
The tracking code includes the main domain and it redirects to a specific page.
Example: tracking.ourdomain.com/aff_c?offer_id=46&aff_id=76
You have to check in Landing Pages report (or All pages report), filtering by aff_id, if there are any sessions.
To track in correct mode the source you have to use UTMs parameters. You can build your URL with UTM parameters using this tool. It allows you to easily add campaign parameters to URLs so you can track Custom Campaigns in Google Analytics. Then you can find those sessions in source / medium report.
When using the SagePay Form integration, the referrer in Google Analytics always shows as live.sagepay.com rather than the original referrer. This is because, when using this integration method, the user gets redirected to live.sagepay.com to complete the payment process before getting redirected back to the original website.
Since the payment templates on SagePay don't allow external scripts, we can't add the analytics tracking script here, which means cross-domain tracking is out of the question.
Is there a workaround for this problem? As many payment gateways are external and behave in a similar way I'm guessing this must be a fairly common issue?
You can add a referral exclusion in the Google Analytics account itself. This should prevent new sessions being created as per the docs:
https://support.google.com/analytics/answer/2795830?hl=en
Google Analytics tracks the following acquisition types (ways in which its users reached your site):
Referrals
Search
Direct link
A direct link means entering a site name directly into the browser URL. A search means doing a google search and clicking on one of the results. A referral means someone clicked on a hyperlink which got them to your site.
It is obvious that since google search is run by google, clicking on a link in the google search results can submit the information of what clicked to the google analytic servers.
What is obvious is the other two cases (direct link and referrals). It seems to me that since these requests don't go through google, that google would have to own some software on interim TCP/IP routers for this to work.
So, my question is, how does Google Analytics manage to track referrals and direct links at the software level?
So, my question is, how does Google Analytics manage to track
referrals and direct links at the software level?
If there is no referrer (accessible via http headers) it's a direct type-in. If there is a referrer and it's not from a list of known search engines or social networks it's a referrer.
Since the referrer is accessible both via javascript (via document referrer) and via the http headers there is really not mystery here and they do not need to intercept traffic - source attribution works simply by way of exclusion (i.e. if it's not campaign traffic as per campaign parameters in the url it's a referrer or a direct visit).
In fact Google has a very nice flowchart to show how source attribution works. Once you realize that the referrer is public information (except for those user agent that choose not to send a referrer in the http headers) it's easy to understand how this works.
I give each visitor who signs up to my Google Form an unique url to my landing page for them to share with their friends. The idea is the more they share and their friends visits the site through their given unique url, I'll move them up the waiting list for a product launch.
So for each visitor I gave them example.com/?ref=uniqueCode which is unique to each visitor. Currently I'm using Google App scripts to programatically generate individual url to each visitor who signs up my Google Form.
The goal is if I see traffic coming in from eg: example.com/?ref=a, and I know tag a belongs to John Doe, I'll move John Doe up the waiting list.
Tried googling for a solution but couldn't find any. All solution directs me to creating a particular campaign in Google Analytics with the URL building which really isn't the right solution for this purpose.
How do I set this up with Google Analytics and track the incoming traffic for each unique code of the ref tags of each user?
Going over your question I cannot see why URL builder does not fit your needs.
However, when it comes to immediate and accurate statistics of incoming referrals you may also use a server side script to track incoming visitors.
Also for lots of existing CMS there are plugins to track referrals. If you use a CMS please update your question.
A client of mine is having some issues with regards to tracking campaigns in Google Analytics that I was hoping one of you can advise me on.
They have recently sent out an email with the Google Analytics campaign information in the links back to the site from a button in the email (link created with the URL builder).
As well as the Google Analytics information they also send their own parameter for tracking using a bespoke system of theirs. In the end the url that visitors would go to after clicking the button in the email was something along these lines:
http://www.domain.com/pagename/?bespokecampaign=lead_gen/email/email_btn/boxcampaign&utm_source=email_pure&utm_medium=email&utm_term=email_btn&utm_campaign=boxcampaign
Looking at Acquisitions in the Google Analytics report I can see in the past this page has been viewed and has the correct Source/Medium set as email_pure/email.
However, there was a lead gen form that was filled out on the site after landing on this particular page that sends an event action that the form was filled out. When trying to view the campaign information for these events I do not see any information regarding the Source / Medium for that event being the correct information from the URL.
The Salesforce model in place to receive these leads took the referrer URL correctly, containing the Google Analytics parameters, but there was no record in Analytics to suggest one of the form events had the Source/Medium of email_pure/email.
Does anyone have any ideas on what could be causing this and potential fixes?