In our Google Analytics ecommerce PayPal is getting credit as the referrer. I've found many articles outlining use on the utmnooveride to ensure PayPal transactions pass the data so that the original referrer gets credit.
在我们的Google Analytics电子商务中，PayPal正在获得赠送金额。我发现许多文章概述了在utmnooveride上使用以确保PayPal交易传递数据，以便原始推荐人获得信用。
We use PayPal to process our credit cards as well as allow people to pay with their PayPal account. When a visitor pays with credit card they never leave our site, so we are only seeing this inaccuracy when a user leaves our site to pay with their PayPal account.
我们使用PayPal处理我们的信用卡，并允许人们使用他们的PayPal帐户付款。当访客使用信用卡付款时，他们从不离开我们的网站，因此当用户离开我们的网站使用他们的PayPal帐户付款时，我们只会看到这种不准确性。
More accurately we are using PayPal express checkout and using NVP (name value pair) API. https://developer.paypal.com/docs/classic/api/NVPAPIOverview/
更准确地说，我们使用PayPal express checkout并使用NVP（名称值对）API。 https://developer.paypal.com/docs/classic/api/NVPAPIOverview/
We've implemented the suggestions and code changes we have found but PayPal is still getting credit. We've even talked with PayPal and Google techs and aren't getting any thing more from them than what we are finding online.
我们已经实施了我们发现的建议和代码更改，但PayPal仍然获得了信誉。我们甚至与PayPal和谷歌技术人员进行了交谈，并没有从他们那里得到任何更多的东西，而不是我们在网上找到的东西。
Is anyone else encountering this issue, have you found a solution or have any suggestions? Your help is much appreciated.
是否有其他人遇到此问题，您是否找到了解决方案或有任何建议？非常感谢您的帮助。
-- Solution Update --
- 解决方案更新 -
Moved to the answers.
移动到答案。
4 个解决方案
#1
7
Per request.. I am moving the answer from a followup in the question to the actual answer.
每个请求..我正在将答案从问题的后续内容转移到实际答案。
Based on some various articles on how to improve accuracy of data reporting I just happened to be messing with property settings in Analytics and came across the Referral Exclusion List. I've mostly used this to just cancel out links from other sites in our domain structure; subdoimain.foosite.com -> foosite.com, but decided to investigate adding PayPal to this and came across this support doc from Google.
基于一些关于如何提高数据报告准确性的文章，我恰好在分析中搞乱了属性设置并遇到了推荐排除列表。我主要使用它来取消我们域结构中其他网站的链接; subdoimain.foosite.com - > foosite.com，但决定调查将PayPal添加到此，并从Google获得此支持文档。
After reading that article I wondered what would happen. The result = NO MORE PAYPAL referrals and referrals from the original source without having to worry about utm=nooverride=1 usage.
读完那篇文章后，我想知道会发生什么。结果=来自原始来源的NO MORE PAYPAL推荐和推荐，而不必担心utm = nooverride = 1用法。
I have verified with a Google support specialist that the below has no negative effects on ecommerce reporting and they have submitted my case to their help team for future use. He also mentioned that this methodology actually recently added which is why there is little documentation about it.
我已与Google支持专家确认，以下内容对电子商务报告没有任何负面影响，他们已将我的案例提交给他们的帮助团队以供将来使用。他还提到这种方法实际上最近添加了，这就是为什么关于它的文档很少。
Here is how.
这是怎么回事。
- Make sure you are using Universal Analytics
- 确保您使用的是Universal Analytics
- Admin -> Property Settings -> Tracking Info -> Referral Exclusion List
- 管理员 - >媒体资源设置 - >跟踪信息 - >推荐排除列表
-
- Add Referral Exclusion
- 添加推荐排除
- 添加推荐排除
- Insert referral domain - my case was paypal.com but you may have this issue with others - key here is to identify any domain that might be hijacking ecommerce transactions. So if you are seeing anything that has ecommerce credit that you don't think should; add it
- 插入推荐域名 - 我的案例是paypal.com，但您可能与其他人有此问题 - 这里的关键是识别可能劫持电子商务交易的任何域名。因此，如果您看到任何具有电子商务信誉的内容，您认为不应该这样做;添加它
This should solve the problem but I would suggest taking things a few steps further.
这应该解决问题，但我建议进一步采取措施。
-
Adjust your session settings. Admin -> Property Settings -> Tracking Info -> Session Settings
调整会话设置。管理员 - >属性设置 - >跟踪信息 - >会话设置
- A few notes about session settings- depending on your site and how users engage I would initially adjust the session timeout so that session is longer than 30 mins. I set mine to 2 hours for testing. Then for campaign timeout I set it 1 day (much shorter time than our normal campaigns.
- 关于会话设置的一些注意事项 - 取决于您的网站和用户参与方式，我最初会调整会话超时，以便会话超过30分钟。我把我的时间设置为2小时进行测试。然后，对于广告系列超时，我将其设置为1天（比我们的正常广告系列短得多）。
- This allowed me to initially see that it was indeed eliminating PayPal from the referral source and but that my transactions in GA matched my internal reports.
- 这让我最初看到它确实从推荐来源中删除了PayPal，但我在GA中的交易与我的内部报告相符。
- After verification I set the session timeout to 45 mins - 15 mins longer than our site session settings and set the campaign timeout to 7 days.
- 验证后，我将会话超时设置为45分钟 - 比我们的站点会话设置长15分钟，并将广告系列超时设置为7天。
-
Make use of Google URL builder and add parameters to your URLs.
使用Google URL构建器并向您的网址添加参数。
- This is not only good practice it saves you tons of time trying to segment out your referral sources in GA. It is especially helpful if you collect acquisition source in your internal reports or logs because you can compare those to GA to ensure you are getting accurate ecomm numbers from GA.
- 这不仅是一种良好的做法，它还可以节省大量时间来分析GA中的推荐来源。如果您在内部报告或日志中收集采购源，则会特别有用，因为您可以将其与GA进行比较，以确保您从GA获得准确的ecomm编号。
#2
1
Let me share my experience with the 'referral exclusion list' in UA:
让我与UA中的“推荐排除列表”分享我的经验：
I added paypal.com and another similar payment provider to the list.
我将paypal.com和另一个类似的支付提供商添加到列表中。
Consequence: The traffic attributed to those referrers was reduced from that moment on - but far from beeing zero. (Let's say it was halfed.)
结果：归因于这些推荐人的流量从那一刻开始减少 - 但远未达到零。 （假设它已经减半了。）
No idea why it is working for parts of the traffic only.
不知道为什么它只适用于部分流量。
#3
1
Just wanted to add my answer in case anyone comes across this same issue.
只是想添加我的答案，以防任何人遇到同样的问题。
From my understanding the following no longer works with newer GA code:
根据我的理解，以下内容不再适用于较新的GA代码：
utm_nooverride=1
utm_nooverride = 1
However if you pass the _ga parameter google analytics will be able to relate the two instances before being transferred to paypal. Okay great so all you have to do is add the _ga parameter to the return URL...but how do you get it?
但是，如果您传递_ga参数，Google Analytics将能够在转移到PayPal之前将这两个实例关联起来。好的，所以你要做的就是将_ga参数添加到返回URL ...但是你如何得到它？
Unfortunately you need to grab it client side first:
不幸的是，你需要首先抓住客户端：
ga(function(tracker) {
var linkerParam = tracker.get('linkerParam');
});
Hope this helps someone.
希望这有助于某人。
Reference
参考
https://ecommerce.shopify.com/c/ecommerce-marketing/t/tracking-true-referrals-in-google-analytics-when-using-paypal-163514
https://developers.google.com/analytics/devguides/collection/analyticsjs/cross-domain
https://developers.google.com/analytics/devguides/collection/analyticsjs/cross-domain
#4
0
I just wanted to add my experience. I have been having the very same problem, and as you have mentioned the solution is putting paypal.com on the Referral Exclusion List. You must be upgraded to the new Google Universal Analytics in order for to have access to it.
我只想添加我的经验。我遇到了同样的问题，正如您所提到的，解决方案是将paypal.com放在推荐排除列表中。您必须升级到新的Google Universal Analytics才能访问它。
#1
7
Per request.. I am moving the answer from a followup in the question to the actual answer.
每个请求..我正在将答案从问题的后续内容转移到实际答案。
Based on some various articles on how to improve accuracy of data reporting I just happened to be messing with property settings in Analytics and came across the Referral Exclusion List. I've mostly used this to just cancel out links from other sites in our domain structure; subdoimain.foosite.com -> foosite.com, but decided to investigate adding PayPal to this and came across this support doc from Google.
基于一些关于如何提高数据报告准确性的文章，我恰好在分析中搞乱了属性设置并遇到了推荐排除列表。我主要使用它来取消我们域结构中其他网站的链接; subdoimain.foosite.com - > foosite.com，但决定调查将PayPal添加到此，并从Google获得此支持文档。
After reading that article I wondered what would happen. The result = NO MORE PAYPAL referrals and referrals from the original source without having to worry about utm=nooverride=1 usage.
读完那篇文章后，我想知道会发生什么。结果=来自原始来源的NO MORE PAYPAL推荐和推荐，而不必担心utm = nooverride = 1用法。
I have verified with a Google support specialist that the below has no negative effects on ecommerce reporting and they have submitted my case to their help team for future use. He also mentioned that this methodology actually recently added which is why there is little documentation about it.
我已与Google支持专家确认，以下内容对电子商务报告没有任何负面影响，他们已将我的案例提交给他们的帮助团队以供将来使用。他还提到这种方法实际上最近添加了，这就是为什么关于它的文档很少。
Here is how.
这是怎么回事。
- Make sure you are using Universal Analytics
- 确保您使用的是Universal Analytics
- Admin -> Property Settings -> Tracking Info -> Referral Exclusion List
- 管理员 - >媒体资源设置 - >跟踪信息 - >推荐排除列表
-
- Add Referral Exclusion
- 添加推荐排除
- 添加推荐排除
- Insert referral domain - my case was paypal.com but you may have this issue with others - key here is to identify any domain that might be hijacking ecommerce transactions. So if you are seeing anything that has ecommerce credit that you don't think should; add it
- 插入推荐域名 - 我的案例是paypal.com，但您可能与其他人有此问题 - 这里的关键是识别可能劫持电子商务交易的任何域名。因此，如果您看到任何具有电子商务信誉的内容，您认为不应该这样做;添加它
This should solve the problem but I would suggest taking things a few steps further.
这应该解决问题，但我建议进一步采取措施。
-
Adjust your session settings. Admin -> Property Settings -> Tracking Info -> Session Settings
调整会话设置。管理员 - >属性设置 - >跟踪信息 - >会话设置
- A few notes about session settings- depending on your site and how users engage I would initially adjust the session timeout so that session is longer than 30 mins. I set mine to 2 hours for testing. Then for campaign timeout I set it 1 day (much shorter time than our normal campaigns.
- 关于会话设置的一些注意事项 - 取决于您的网站和用户参与方式，我最初会调整会话超时，以便会话超过30分钟。我把我的时间设置为2小时进行测试。然后，对于广告系列超时，我将其设置为1天（比我们的正常广告系列短得多）。
- This allowed me to initially see that it was indeed eliminating PayPal from the referral source and but that my transactions in GA matched my internal reports.
- 这让我最初看到它确实从推荐来源中删除了PayPal，但我在GA中的交易与我的内部报告相符。
- After verification I set the session timeout to 45 mins - 15 mins longer than our site session settings and set the campaign timeout to 7 days.
- 验证后，我将会话超时设置为45分钟 - 比我们的站点会话设置长15分钟，并将广告系列超时设置为7天。
-
Make use of Google URL builder and add parameters to your URLs.
使用Google URL构建器并向您的网址添加参数。
- This is not only good practice it saves you tons of time trying to segment out your referral sources in GA. It is especially helpful if you collect acquisition source in your internal reports or logs because you can compare those to GA to ensure you are getting accurate ecomm numbers from GA.
- 这不仅是一种良好的做法，它还可以节省大量时间来分析GA中的推荐来源。如果您在内部报告或日志中收集采购源，则会特别有用，因为您可以将其与GA进行比较，以确保您从GA获得准确的ecomm编号。
#2
1
Let me share my experience with the 'referral exclusion list' in UA:
让我与UA中的“推荐排除列表”分享我的经验：
I added paypal.com and another similar payment provider to the list.
我将paypal.com和另一个类似的支付提供商添加到列表中。
Consequence: The traffic attributed to those referrers was reduced from that moment on - but far from beeing zero. (Let's say it was halfed.)
结果：归因于这些推荐人的流量从那一刻开始减少 - 但远未达到零。 （假设它已经减半了。）
No idea why it is working for parts of the traffic only.
不知道为什么它只适用于部分流量。
#3
1
Just wanted to add my answer in case anyone comes across this same issue.
只是想添加我的答案，以防任何人遇到同样的问题。
From my understanding the following no longer works with newer GA code:
根据我的理解，以下内容不再适用于较新的GA代码：
utm_nooverride=1
utm_nooverride = 1
However if you pass the _ga parameter google analytics will be able to relate the two instances before being transferred to paypal. Okay great so all you have to do is add the _ga parameter to the return URL...but how do you get it?
但是，如果您传递_ga参数，Google Analytics将能够在转移到PayPal之前将这两个实例关联起来。好的，所以你要做的就是将_ga参数添加到返回URL ...但是你如何得到它？
Unfortunately you need to grab it client side first:
不幸的是，你需要首先抓住客户端：
ga(function(tracker) {
var linkerParam = tracker.get('linkerParam');
});
Hope this helps someone.
希望这有助于某人。
Reference
参考
https://ecommerce.shopify.com/c/ecommerce-marketing/t/tracking-true-referrals-in-google-analytics-when-using-paypal-163514
https://developers.google.com/analytics/devguides/collection/analyticsjs/cross-domain
https://developers.google.com/analytics/devguides/collection/analyticsjs/cross-domain
#4
0
I just wanted to add my experience. I have been having the very same problem, and as you have mentioned the solution is putting paypal.com on the Referral Exclusion List. You must be upgraded to the new Google Universal Analytics in order for to have access to it.
我只想添加我的经验。我遇到了同样的问题，正如您所提到的，解决方案是将paypal.com放在推荐排除列表中。您必须升级到新的Google Universal Analytics才能访问它。