Google Analytics Goal Source - google-analytics

I have a goal which detects if someone made a purchase on my website. I want to know where that person came from (adwords, facebook, organic, etc).
The problem is that Analytics tells me the source of all these people is the payment processor. This isn't surprising as the flow looks as follows:
Checkout Page -> Paypal.com -> Payment Success Page
It tells me all my goals came from paypal. I want to know where these people came from originally. How would I do that?

You probably forgot to add the payment processor to the referral exclusion list in the property settings. If you do that it will be ignored as a traffic source and the original channel information will be retained. It will also affect the number of sessions - a change in traffic attribution starts a new sessions, so after the change you should expect somewhat fewer sessions with more pageviews.
Unfortunately the setting is not applied retroactively, so traffic data up until you implement the setting is lost for good.

Related

GA: How much time have my 100 most "obsessed" users spent on my site

Does Google Analytics have enough information to answer the question of how much time have my top 100 users spent on my site? I don't need their user information, I don't care about ID or name which I know it doesn't even have. Just the identification of individual users by the cookie GA uses, and a report of how much time the top 100 loyal users spent on my site.
is such a thing possible at all with GA?
From your comment on Colwin's answer:
I don't need google if I have to track this for GA, I just hoped it already has this information such as "page visit duration" on a per-user, ongoing basis. If I had to feed Google that information myself, I can feed my own database and run analytics on it. Thanks anyway.
The Google analytics sessions is
a group of user interactions with your website that take place within a given time frame. For example a single session can contain multiple page views, events, social interactions, and ecommerce transactions.
Average session duration will be calculated as
total duration of all sessions / number of sessions
I don't think this is available from GA out of the box. But you can build something like this with Custom Dimensions available within GA
This will let you setup and send custom metrics dimensions for users that you can then create reports for.
Google Analytics doesn’t allow you to out in PII but random visitor id's should be fine. You can then compare against your own database outside of GA if needed too.
This will allow tracking the same visitor even without them being logged in to your site.
Sending the custom dimensions could possibly look like this.
ga('send', 'pageview', {
'dimension5': '1234567890'
});
You get 20 free custom dimension slots with GA and 200 with GA 360 -> More info here
I think this article has what you are looking for
https://webanalyticsguy.com/2018/01/18/google-analytics-capture-client-id-reporting-purposes/
It shows how to capture the client id which is a decent way to track a specific user. And goes further to explain how to associate that with a metric, in this case the author uses PageView.
You could change this to Average Session Duration or another metric that gives you a sense of time spent.
I guess that you are looking for something like this:
http://www.analytics-ninja.com/blog/2015/02/real-time-page-google-analytics.html
You can get the counts of the users on your site. You can get the seconds they spent on your website page.
I guess this answer will be helpful too: https://qr.ae/TWpkI0

How do duplicate UTM parameters affect reporting in Google Analytics?

I recently ran an e-mail campaign with a partner, who sent me over a URL with their own UTM parameters so they could track performance on their side.
When I handed the information over to our e-mail team and checked as the campaign went live, it appeared that they, out of habit, had added their own UTM parameters on top of the ones sent over by the partner, resulting in a click-through URL that looked like the following -
http://spirit.cruises.com/?cm_mmc=partner_email-_-sprt-multi_product--20161028--clia_plan_a_cruise_month&utm_medium=partner_email**&utm_source**=sprt-multi_product**&utm_campaign**=20161028&utm_content=clia_plan_a_cruise_month**&utm_source**=responsys**&utm_medium**=email**&utm_campaign**=20161028_50pct__Dual_Cruise_Email
As you can see, there are duplicate source, medium, and campaign parameters.
Does anyone know what happens in this situation? Does Google Analytics count both, or just the first, or just the last, or none? What is best practice when there are two parties that want to track performance of a URL in a campaign, and they may have different naming conventions?
(This is my first question, so please be nice :) Thanks!)
GA counts the last set. The proper way to deal with this is to avoid the situation. Email Software is often set to automatically add utm parameters to links (do you do not have to do it manually), but then all email marketing software I know would allow to override the configured default parameters.
I am not sure how your partner could track performance "on their site" via utm parameters unless they have their own GA code integrated in your website (or do you mean that they have access to your GA ?).
If there are two sets of analytics code that require different campaign attribution you would have use differently named parameters - let's say utm_medium2, utm_source2 and utm_campaign2 - and manually override campaign attribution for the second tracker:
// add this to after your usual tracker
ga('create', 'UA-XXXXX-Y', 'auto', 'partnerTracker');
ga('partnerTracker.set','campaignName',<value of utm_campaign2>)
ga('partnerTracker.set','campaignMedium',<value of utm_medium2>)
ga('partnerTracker.set','campaignSource',<value of utm_source2>)
ga('partnerTracker.send','pageview')
That would send data to a second account and override campaign attribution fields. It seems quite unlikely that you have or want that, but if you want to allow your partner to independently track utm values on your website (and everything else with it) that would the way to go.
Frankly I think you should just remove your partners utm parameters. Utm parameters make only sense for the owner of the respective GA account, and that is probably you, not the partner.
I agree with the first answer except for that last point where has says to remove the partner's UTM parameters.
In your case, the destination for the link provided to you by your partner is NOT your own website. The link goes to your partner's website. Therefore, your GA account has zero relationship with the link he sent you.
The way we're getting around this (without doing anything in analytics) for our many partners that we send links to is by using different email subjects per partner. Most email platforms use the subject line (or the internally defined Campaign "Name") as the value for UTM_Campaign.
So different subjects that include the partner organization in them:
"Special discount for ABC Organization members!"
"Special discount for XYZ Company members"
We can then analyze each unique campaign name in GA.

Google Analytics Bloated Data

I manage an internal website and we recently implemented campaign tracking for our emails and homepage links to see where traffic comes from.
I set up the URLs using the Google URL builder.
The data we're receiving is very bloated. We ran a test URL with 8 people, and we received 129 "views", with an average of 9 views per day for over a month. No one clicked this link after the first day.
Our average session times were about 30 minutes, which is very strange.
My questions are:
how does google track campaigns? If you use a tracking URL, does the cookie track views for any organic views after that?
Is there a tool we can use to only track first time visits using a campaign URL?
Admittedly, I'm fairly new to Google Analytics, but no one on our marketing analytics team was able to help.
Since you used the Google URL builder I don't think you have made any mistakes there. However I strongly think that the bloated data is due to Bot traffic in your account. And yes, the bot traffic does increase average session duration.
So here's a set of steps I'll suggest:
1) Create 3 views in Google Analytics (It is a best practice):
Unfiltered, Master, Test
2) Check for Langauage spam and weird referrals in your report.
3) Add filters to "Test" view to remove these bots & spam referrals. You'll need to write a regular expression for each of these filters. Also make sure you have enabled "bot filtering" in view settings for master & test view. (I am leaving Unfiltered view as it is our data backup in case if anything goes wrong.)
4) Check your traffic for next few days and try doing the URL test again and see the results.
5) If the results in Test View are correct, then apply the same filters to "Master" view.
I hope this helps.

Google Analytics Ecommerce / Difference between 'ec:addItem', 'ec:addTransaction' and 'ec:send'

I would look for some feedback on tracking user activity on an commerce website using th google analytics commerce capabilities.
I can't fully understand those 3 parts :
Adding an item (ecommerce:addItem) : obviously when some user add a thing to the cart
Adding a Transaction (ecommerce:addTransaction) : that's where I'm very confused
Sending the data (ecommerce:send) : that's obvious
Can those 3 event append at a different moment ? in what manner ?
What would be a real-world use case that would make you use execute ecommerce:addTransaction and ecommerce:send at a different moment ?
This thing makes me wonder a lot, and I'd like to have some experienced feedback on this as you tend to easily break your stats if something is not done week enough
Thanks in advance
EDIT
So the main purpose right here is to get stats for the pending orders (you add stuff to your cart), and the complete orders (you paid for the things you added).
Right now I only send it all when the order is complete, and things are working pretty good in analytics, but I just don't know anything about the ones that did not complete.
This question was a lack of knowledge.
Simple ecommerce plugin has nothing to do with the enhanced ecommerce plugin
You won't track that much with the first one, except the checkouts. A plain, one order at a time, revenue value.
If you want a deep insight on your users behaviors (when i say deep, I mean it), You have to go for the second one.
We might be able to debate over the unusefullness of the first one; and the fact that its existence in itself compared to the second is completely misleading, as when you first get in, as usual with google, you get flooded by an endless documentation
ecommerce:addItem does not add items to a cart; it adds items to a transaction (with "conventional" ecommcerce tracking there is no cart tracking, you'd have to use enhanced ecommerce tracking. Actually your title refers to enhanced ("ec:") and your question to conventional ecommerce ("ecommerce:") tracking).
So ecommerce:addTransaction starts a transaction; here goes the stuff that affects the transaction as a whole, like transaction id, tax on the total purchase or shipping costs.
Now that you have started the transaction you can add items to it that are associated via the transaction id.
Finally the ecommerce:send command tells Universal Analytics that the transaction should be processed on the server. "send" is actuall a misnomer; addItem and addTransaction do already send data to the server (they each create an request to the tracking server and thus count towards your hit quota).
The reason for this is, as far as I can tell, that the information is transmitted via url parameters (you call the Google Analytics endpoint which returns an transparent pixel). The maximum length for an url request is limited (actual limits depend on browser and browser version).
So the transaction is broken up into multiple parts not because you want to execute the commands at different moments but so it can be transmitted via Url parameters without being truncated. The send command merely tells that you are now finished adding new parts to the transaction and the data can now be processed.

Inundated with marketing tracking pixels (Campaigns with multiple vendors)!

We have some third parties that are sending us traffic and have asked us to put a tracking pixel on the confirmation page so they can track through the sales.
We are currently using Google analytics for our own usage.
Google will remember the original referral through cookies. This may be a good or bad thing. If someone purchases through company B's link but they had originally found our site through company A - then company A still gets the 'referal'. That doesn't seem fair, but it seems to be the way google analytics works:
For example, if this is the user's
first visit to your site, the tracking
code will add the campaign tracking
information to the cookie. If the user
previously found and visited your
site, the tracking code increments the
session counter in the cookie.
Regardless of how many sessions or how
much time has passed, Google Analytics
"remembers" the original referral.
This gives Analytics true
multi-session tracking capability.
Currently we only have one tracking pixel on our 'receipt page' from a company that we're not even doing business with. Having a second company ask me for us to add one makes me thing 'wait a minute - we're going to suddenly be inundated with these things!'. Plus it means someone can look at the source and see all the people we do business with.
This isn't Oprah - you cant ALL have tracking pixels. Right ?
How should we manage sales from multiple traffic sources in the most honest way for both sides - especially if they already have a system set up that they insist on using?
Here's how I solved the problem at our company: we gave our partners a URL that has a parameter in the query string. This parameter triggers a cookie. On the "goal"/confirmation page (where the tracking pixel is usually inserted), we insert some logic to see if the cookie value is correlated with a one of our recognized partners (chained if-else or switch statement). If a match is found, then the tracking pixel is displayed.
Even though you asked this question a while ago, I hope that this still helps you or someone else with the same problem!

Resources