How to correctly use referral exclusion list in Google Analytics
What is a referral exclusion list in Google Analytics?
A referral exclusion list lists domains whose incoming traffic is treated as direct traffic (instead of referral traffic) by Google Analytics.
Direct traffic is a Google Analytics session (or visit) which starts without a referrer being passed by a user’s web browser.
Referral traffic is a Google Analytics session (or visit) which starts with a referrer being passed by a user’s web browser.
Technically speaking, traffic from any website to your website is referral traffic (as long as a referrer is being passed by a user’s web browser).
But in the context of Google Analytics, traffic from search engines and most PPC/CPM ads (like Google Ads) is not reported as referral traffic.
When you add a domain to the referral exclusion list, people who arrive at your website from the excluded domain do not trigger a new GA session and the traffic from the excluded domain is reported as direct traffic by Google Analytics.
However, there is one exception here.
If the excluded domain is a third party domain (like PayPal.com) then people who arrive at your website from the excluded domain still trigger a new GA session.
When you add PayPal.com to the referral exclusion list then all the sales that were earlier attributed to Paypal is now being attributed to direct traffic.
So, there is absolutely no advantage of adding PayPal.com to the referral exclusion list.
Many marketers add PayPal to the referral exclusion list, thinking it will help them see the original source of sales.
But it does not work like that.
If you really want to see the original source of sales then use the payment gateway where a website user can complete the purchase without leaving your website.
Otherwise, you would continue to see your sales attributed either to your payment gateway or to the direct traffic.
How does referral traffic affect GA session count?
By default, all referrals (websites that send traffic to your website) trigger a new GA session. This can affect the count of the total number of GA sessions in your analytics reports.
For example, consider the following user’s journey:
- A user visited the website www.first-website.com for the first time.
- The user navigates to www.second-website.com from www.first-website.com.
- The user navigates back to www.first-website.com from www.second-website.com
As soon as the user arrives on www.first-website.com, he will start a new GA session and be treated as a new user.
As soon as the user arrives on www.second-website.com, he will again be treated as a new user (as, by default, the client ID is not shared across domains).
However, his existing GA session with www.first-website.com will continue, and a new GA session with www.second-website.com will start.
When the user navigates back to www.first-website.com, his existing GA session with www.second-website.com will continue, but a new GA session with www.first-website.com will start.
Now, if you do not want the new GA session to be triggered for www.first-website.com when the user navigates back to www.first-website.com then you need to add the domain www.second-website.com in the referral exclusion list of the GA view meant for www.first-website.com:
Similarly,
If you do not want the new GA session to be triggered for www.second-website.com when the user navigates back to www.second-website.com, then you need to add the domain www.first-website.com in the referral exclusion list of the GA view meant for www.second-website.com:
How to add a domain to the referral exclusion list?
To add a domain to the referral exclusion list, follow the steps below:
Step-1: Navigate to your GA reporting view’s ‘Admin‘ section.
Step-2: Click on the ‘Tracking Info’ link under the ‘Property‘ column.
Step-3: Click on the ‘Referral Exclusion List‘ link:
Step-4: Click on the ‘+ ADD REFERRAL EXCLUSION’ button:
Step-5: Enter the domain name you want to exclude from your referral traffic:
Step-6: Click on the ‘Create’ button.
Step-7: Repeat steps 5 and 6 to add more domains to the referral exclusion list.
Important points about referral exclusion list
#1 If you add example.com to the referral exclusion list, then all of its sub-domains (e.g. www.example.com, music.example.com, art.example.com, etc.) will also be automatically added to the referral exclusion list.
#2 If you add www.example.com to the referral exclusion list, its sub-domains (e.g. music.example.com, art.example.com, etc.) will not be automatically added to the referral exclusion list.
#3 Whenever you create a new GA property, your domain name is automatically added to the referral exclusion list.
#4 The referral exclusion list feature won’t work if you use the outdated version of Google Analytics (ga.js library).
Using the following version of the Google Analytics tracking code:
#5 Referral exclusion does not work retroactively.
#6 When you add your own domains to the referral exclusion list, the traffic from excluded domains does not trigger a new GA session.
How to remove a domain from the referral exclusion list?
Step-1: Navigate to your GA reporting view’s ‘Admin‘ section.
Step-2: Click on the ‘Tracking Info’ link under the ‘Property ‘column.
Step-3: Click on the ‘Referral Exclusion List’ link.
Step-4: Click on the ‘remove‘ link next to the domain you want to remove from the referral exclusion list.
How to check whether the referral exclusion list is working?
Let us suppose you added the domain ‘www.second.com‘ to the referral exclusion list of the GA property associated with the website ‘www.first.com‘
Now follow the steps below:
Step-1: Install the Google Tag Assistant Chrome extension in your Google Chrome web browser.
Step-2: Navigate to the web page of the website www.first.com (in your case, your own website).
Step-3: Click on the Tag Assistant icon in your web browser:
Step-4: Scroll down and click on the ‘Record’ button to turn on the Google Tag Assistant Recording:
Step-5: Now reload the web page of your website (in our case www.first.com) from where you want to start the recording. This reload will send a request/hit to Google Tag Assistant, and your recording will start.
Step-6: Navigate from your website (in our case www.first.com) to www.second.com and then return to the website www.first.com.
Step-7: Stop the Google Tag Assistant Recording by clicking on the ‘STOP RECORDING’ button.
Once you click on this button, you will be redirected to the ‘Google Tag Assistant Recordings’ interface.
Step-8: If you see a notification like the one below, then click on the ‘Dismiss’ button:
Step-9: Analyze the ‘Recording Summary‘ and look for the following similar alert: “This hit starts a new session, most likely because the client ID changed“:
If you see such an alert for your website (in our case www.first.com), then your referral exclusion list is most likely not working.
Note (1): Referral exclusion list feature won’t work, if you are using classic Google Analytics (ga.js)
Note (2): Referral exclusion does not work retroactively.
Why do you sometimes see the traffic from excluded domains?
Suppose your GA property has been set up to track traffic across www.first-website.com and www.second-website.com.
Suppose a user arrives on the website www.first-website.com from www.second-website.com before www.second-website.com was added to the referral exclusion list.
Now the GA session on www.first-website.com will be attributed to www.second-website.com
You then added www.second-website.com to the referral exclusion list.
Now let us suppose the same user visited www.first-website.com, but this time directly via a bookmark and within six months of the last visit.
Now, the second GA session on www.first-website.com would still be attributed to www.second-website.com instead of the direct traffic.
This is because,
By default, Google Analytics uses the last non-direct click attribution model which assigns all the credit for a session to the last non-direct click.
The last non-direct click, in this case, is www.second-website.com
Had the user directly returned to the website www.first-website.com after six months from the last visit, the second GA session on www.first-website.com would be attributed to direct traffic.
This is because the default campaign timeout is set to 6 months.
So for up to 6 months from the last visit, the last non-direct click continues to get all the credit for the second GA session.
Impact of referral exclusion list on cross-domain traffic
If your GA property has been set up to track traffic across multiple primary domains then you should add all your primary domains to the referral exclusion list.
Let us suppose your GA property has been set up to track traffic across www.first-website.com and www.second-website.com
So you should add the domain www.second-website.com to the referral exclusion list of the GA property meant for www.first-website.com.
Similarly, add the domain www.first-website.com to the referral exclusion list of the GA property meant for www.second-website.com.
Let us suppose you decided not to add your websites to the referral exclusion list.
In that case, every time a user navigates from one of your websites to another, a new GA session would be triggered.
That way, cross-domain traffic can inflate the total session count in your reporting view.
Impact of referral exclusion list on cross sub-domain traffic
If your GA property has been set up to track traffic across multiple subdomains then you should add your own domain name to the referral exclusion list.
When you add your website to the referral exclusion list, then users can navigate from one subdomain on your website to another subdomain without triggering a new GA session.
For example, if optimizesmart.com is your website and in the referral exclusion list, users can navigate from www.optimizesmart.com to say music.optimizesmart.com (and vice versa) without starting a new GA session.
Let us suppose you decided not to add your own website to the referral exclusion list.
In that case, when a user navigates from one subdomain on your website to another subdomain, it triggers a new GA session.
That way, cross subdomain traffic can inflate the total session count in your reporting view.
Impact of referral exclusion list on third party domains
If you add a third party domain (like amazon.com) to the referral exclusion list, a new GA session is still triggered by the referral but the referral is reported as direct traffic.
Suppose your domain name is www.abc.com, and you have not added www.amazon.com to the referral exclusion list.
Let us also suppose a user navigated from www.abc.com to www.amazon.com in order to checkout.
When the user returns to your website from www.amazon.com, a new GA session will start, and GA will attribute the user session to www.amazon.com.
Let us suppose you added www.amazon.com to the referral exclusion list.
When the user returns to your website from www.amazon.com, Google Analytics will still start a new session, but this time will attribute the user session to direct traffic instead of www.amazon.com.
Impact of referral exclusion list on payment gateways
Many businesses use PayPal and other third party payment gateways to accept online payments. But this can create tracking issues in Google Analytics.
Whenever a customer leaves your website to make payment via a third party payment gateway and later returns to your website from the gateway website, Google Analytics often attributes sales to the payment gateway instead of the original traffic source.
This is quite common in the case of PayPal.
You can often find PayPal.com appearing as a top revenue source in the Google Analytics Referral report:
Many optimizers add PayPal.com to the referral exclusion list under the impression that it will help them track the original referrer.
However, adding paypal.com to the referral exclusion list will NOT help you track the original referrer.
Google Analytics will then report the traffic from PayPal.com as direct traffic.
The best way to track original referrals while using paypal.com is to use one of the direct payment gateway solutions provided by PayPal like: ‘PayPal Payflow Pro‘ or ‘PayPal Payments Pro‘.
When you use a direct payment gateway, your customers can complete transaction without leaving your website and Google Analytics do not attribute sales to paypal.com but instead to the original traffic source.
The referral exclusion does not work retroactively. So,
Any visit/sales attributed to paypal.com before adding paypal.com to the referral exclusion list will still be attributed to paypal.com in GA reports.
Therefore you need to make sure that once you have added a domain to the referral exclusion list, you look at the referral report from the time period when you first implemented referral exclusion.
Is referral exclusion not working for PayPal.com?
Google Analytics uses the last non-direct click attribution model for non-multi channel funnel reports.
This model assigns all the credit for conversions to the last non-direct click on a conversion path.
Consider the following scenario
A user returned to your website (say ‘www.abc.com‘) from ‘www.paypal.com’ before you added ‘www.paypal.com‘ in the referral exclusion list of the ‘www.abc.com‘ GA property.
Now, here GA will attribute the user session to ‘www.paypal.com‘.
You added ‘www.paypal.com‘ to the referral exclusion list of the ‘www.abc.com‘ GA property.
The same user directly returns to your website ‘www.abc.com‘ within six months.
In that case, GA will still attribute the second session to ‘www.paypal.com‘ and not direct traffic because of the last non-direct click attribution model.
So even when you exclude the website ‘www.paypal.com‘, the returning users from the excluded domain can still appear in your reports.
To minimize this problem, set your campaign timeout setting to one month:
Other articles on specialized tracking in Google Analytics
- How to see Organic Search Keywords in GA4 (Google Analytics 4)
- Google Analytics Ecommerce Tracking Tutorial
- Google Tag Manager Event Tracking Tutorial
- Google Analytics Event Tracking Tutorial
- Google Analytics Store Visits Tracking Tutorial
- Offline Conversion Tracking in Google Analytics – Tutorial
- Ecommerce Tracking Google Tag Manager (GTM) – Tutorial
- Tracking Virtual Pageviews in Google Tag Manager – Tutorial
- Google Tag Manager YouTube Video Tracking
- Google Analytics Virtual Pageviews Tutorial
- Google Analytics YouTube Integration & Analysis Tutorial
- Google Analytics for Facebook Tutorial
- Cross Domain Tracking in Google Analytics – Complete Guide
- How to use two Google Analytics codes on one page
- How to correctly use referral exclusion list in Google Analytics
- Google Analytics Calculated Metrics – Tutorial
- Creating your own Google Analytics Tag Auditing System
- Google Tag Manager Search Tracking without Query Parameter
- Tracking Google Analytics Paypal Referral and other payment gateways
- How to Track Phone Calls in Google Analytics 4 – Call Tracking Tutorial
- How to track leads in Google Analytics via CRM
- Postbacks in Google Analytics Explained
- Subscription & Recurring Revenue Analytics in Google Analytics
- Track the Impact of Google Analytics Cookie Consent on Website Traffic
- Tracking Offline Conversions in Google Ads
- Implementing Scroll Tracking via Google Tag Manager
- Scroll Depth Tracking in Google Tag Manager – Tutorial
- Site Search Tracking In Google Analytics Without Query Parameters
- Google Tag Manager Youtube Video Tracking via YouTube Video Trigger
- How to Correctly Measure Conversion Date & Time in Google Analytics
- Google Analytics Social Tracking – Twitter, Facebook, Google Plus and LinkedIn
- Cross Domain Tracking in Google Analytics – Complete Guide
- Google Analytics Linkedin & Twitter Tracking
- Creating Content Group in Google Analytics via tracking code using gtag.js
- Google Analytics Site Search Tracking via Query Parameters
- Google Analytics Site Search Tracking Tutorial
- Creating and Using Site Search Funnel in Google Analytics
- How to add Facebook Pixel to Google Tag Manager
- AMP Google Analytics Tracking – Learn to track AMP pages
- Setting up Sales Funnel across websites in Google Analytics
- Google Analytics 4 Regex (Regular Expressions) Tutorial
Frequently asked questions about how to correctly use the referral exclusion list in Google Analytics
What is a referral exclusion list?
A referral exclusion list lists domains whose incoming traffic is treated as direct traffic (instead of referral traffic) by Google Analytics.
When you add a domain to the referral exclusion list, people who arrive at your website from the excluded domain do not trigger a new GA session. The traffic from the excluded domain is reported as direct traffic by Google Analytics.
What is the difference between direct traffic and referral traffic?
Direct traffic is a Google Analytics session (or visit) that starts without a referrer being passed by a user’s web browser.
Referral traffic is a Google Analytics session (or visit) which starts with a referrer being passed by a user’s web browser.
What is the impact of the referral exclusion list on cross sub-domain traffic?
When your website is on the referral exclusion list, then users can navigate from one subdomain on your website to another without starting a new session.
For example, if example.com is in the referral exclusion list, users can navigate from www.example.com to say music.example.com without starting a new session.
What is a referral exclusion list in Google Analytics?
A referral exclusion list lists domains whose incoming traffic is treated as direct traffic (instead of referral traffic) by Google Analytics.
Direct traffic is a Google Analytics session (or visit) which starts without a referrer being passed by a user’s web browser.
Referral traffic is a Google Analytics session (or visit) which starts with a referrer being passed by a user’s web browser.
Technically speaking, traffic from any website to your website is referral traffic (as long as a referrer is being passed by a user’s web browser).
But in the context of Google Analytics, traffic from search engines and most PPC/CPM ads (like Google Ads) is not reported as referral traffic.
When you add a domain to the referral exclusion list, people who arrive at your website from the excluded domain do not trigger a new GA session and the traffic from the excluded domain is reported as direct traffic by Google Analytics.
However, there is one exception here.
If the excluded domain is a third party domain (like PayPal.com) then people who arrive at your website from the excluded domain still trigger a new GA session.
When you add PayPal.com to the referral exclusion list then all the sales that were earlier attributed to Paypal is now being attributed to direct traffic.
So, there is absolutely no advantage of adding PayPal.com to the referral exclusion list.
Many marketers add PayPal to the referral exclusion list, thinking it will help them see the original source of sales.
But it does not work like that.
If you really want to see the original source of sales then use the payment gateway where a website user can complete the purchase without leaving your website.
Otherwise, you would continue to see your sales attributed either to your payment gateway or to the direct traffic.
How does referral traffic affect GA session count?
By default, all referrals (websites that send traffic to your website) trigger a new GA session. This can affect the count of the total number of GA sessions in your analytics reports.
For example, consider the following user’s journey:
- A user visited the website www.first-website.com for the first time.
- The user navigates to www.second-website.com from www.first-website.com.
- The user navigates back to www.first-website.com from www.second-website.com
As soon as the user arrives on www.first-website.com, he will start a new GA session and be treated as a new user.
As soon as the user arrives on www.second-website.com, he will again be treated as a new user (as, by default, the client ID is not shared across domains).
However, his existing GA session with www.first-website.com will continue, and a new GA session with www.second-website.com will start.
When the user navigates back to www.first-website.com, his existing GA session with www.second-website.com will continue, but a new GA session with www.first-website.com will start.
Now, if you do not want the new GA session to be triggered for www.first-website.com when the user navigates back to www.first-website.com then you need to add the domain www.second-website.com in the referral exclusion list of the GA view meant for www.first-website.com:
Similarly,
If you do not want the new GA session to be triggered for www.second-website.com when the user navigates back to www.second-website.com, then you need to add the domain www.first-website.com in the referral exclusion list of the GA view meant for www.second-website.com:
How to add a domain to the referral exclusion list?
To add a domain to the referral exclusion list, follow the steps below:
Step-1: Navigate to your GA reporting view’s ‘Admin‘ section.
Step-2: Click on the ‘Tracking Info’ link under the ‘Property‘ column.
Step-3: Click on the ‘Referral Exclusion List‘ link:
Step-4: Click on the ‘+ ADD REFERRAL EXCLUSION’ button:
Step-5: Enter the domain name you want to exclude from your referral traffic:
Step-6: Click on the ‘Create’ button.
Step-7: Repeat steps 5 and 6 to add more domains to the referral exclusion list.
Important points about referral exclusion list
#1 If you add example.com to the referral exclusion list, then all of its sub-domains (e.g. www.example.com, music.example.com, art.example.com, etc.) will also be automatically added to the referral exclusion list.
#2 If you add www.example.com to the referral exclusion list, its sub-domains (e.g. music.example.com, art.example.com, etc.) will not be automatically added to the referral exclusion list.
#3 Whenever you create a new GA property, your domain name is automatically added to the referral exclusion list.
#4 The referral exclusion list feature won’t work if you use the outdated version of Google Analytics (ga.js library).
Using the following version of the Google Analytics tracking code:
#5 Referral exclusion does not work retroactively.
#6 When you add your own domains to the referral exclusion list, the traffic from excluded domains does not trigger a new GA session.
How to remove a domain from the referral exclusion list?
Step-1: Navigate to your GA reporting view’s ‘Admin‘ section.
Step-2: Click on the ‘Tracking Info’ link under the ‘Property ‘column.
Step-3: Click on the ‘Referral Exclusion List’ link.
Step-4: Click on the ‘remove‘ link next to the domain you want to remove from the referral exclusion list.
How to check whether the referral exclusion list is working?
Let us suppose you added the domain ‘www.second.com‘ to the referral exclusion list of the GA property associated with the website ‘www.first.com‘
Now follow the steps below:
Step-1: Install the Google Tag Assistant Chrome extension in your Google Chrome web browser.
Step-2: Navigate to the web page of the website www.first.com (in your case, your own website).
Step-3: Click on the Tag Assistant icon in your web browser:
Step-4: Scroll down and click on the ‘Record’ button to turn on the Google Tag Assistant Recording:
Step-5: Now reload the web page of your website (in our case www.first.com) from where you want to start the recording. This reload will send a request/hit to Google Tag Assistant, and your recording will start.
Step-6: Navigate from your website (in our case www.first.com) to www.second.com and then return to the website www.first.com.
Step-7: Stop the Google Tag Assistant Recording by clicking on the ‘STOP RECORDING’ button.
Once you click on this button, you will be redirected to the ‘Google Tag Assistant Recordings’ interface.
Step-8: If you see a notification like the one below, then click on the ‘Dismiss’ button:
Step-9: Analyze the ‘Recording Summary‘ and look for the following similar alert: “This hit starts a new session, most likely because the client ID changed“:
If you see such an alert for your website (in our case www.first.com), then your referral exclusion list is most likely not working.
Note (1): Referral exclusion list feature won’t work, if you are using classic Google Analytics (ga.js)
Note (2): Referral exclusion does not work retroactively.
Why do you sometimes see the traffic from excluded domains?
Suppose your GA property has been set up to track traffic across www.first-website.com and www.second-website.com.
Suppose a user arrives on the website www.first-website.com from www.second-website.com before www.second-website.com was added to the referral exclusion list.
Now the GA session on www.first-website.com will be attributed to www.second-website.com
You then added www.second-website.com to the referral exclusion list.
Now let us suppose the same user visited www.first-website.com, but this time directly via a bookmark and within six months of the last visit.
Now, the second GA session on www.first-website.com would still be attributed to www.second-website.com instead of the direct traffic.
This is because,
By default, Google Analytics uses the last non-direct click attribution model which assigns all the credit for a session to the last non-direct click.
The last non-direct click, in this case, is www.second-website.com
Had the user directly returned to the website www.first-website.com after six months from the last visit, the second GA session on www.first-website.com would be attributed to direct traffic.
This is because the default campaign timeout is set to 6 months.
So for up to 6 months from the last visit, the last non-direct click continues to get all the credit for the second GA session.
Impact of referral exclusion list on cross-domain traffic
If your GA property has been set up to track traffic across multiple primary domains then you should add all your primary domains to the referral exclusion list.
Let us suppose your GA property has been set up to track traffic across www.first-website.com and www.second-website.com
So you should add the domain www.second-website.com to the referral exclusion list of the GA property meant for www.first-website.com.
Similarly, add the domain www.first-website.com to the referral exclusion list of the GA property meant for www.second-website.com.
Let us suppose you decided not to add your websites to the referral exclusion list.
In that case, every time a user navigates from one of your websites to another, a new GA session would be triggered.
That way, cross-domain traffic can inflate the total session count in your reporting view.
Impact of referral exclusion list on cross sub-domain traffic
If your GA property has been set up to track traffic across multiple subdomains then you should add your own domain name to the referral exclusion list.
When you add your website to the referral exclusion list, then users can navigate from one subdomain on your website to another subdomain without triggering a new GA session.
For example, if optimizesmart.com is your website and in the referral exclusion list, users can navigate from www.optimizesmart.com to say music.optimizesmart.com (and vice versa) without starting a new GA session.
Let us suppose you decided not to add your own website to the referral exclusion list.
In that case, when a user navigates from one subdomain on your website to another subdomain, it triggers a new GA session.
That way, cross subdomain traffic can inflate the total session count in your reporting view.
Impact of referral exclusion list on third party domains
If you add a third party domain (like amazon.com) to the referral exclusion list, a new GA session is still triggered by the referral but the referral is reported as direct traffic.
Suppose your domain name is www.abc.com, and you have not added www.amazon.com to the referral exclusion list.
Let us also suppose a user navigated from www.abc.com to www.amazon.com in order to checkout.
When the user returns to your website from www.amazon.com, a new GA session will start, and GA will attribute the user session to www.amazon.com.
Let us suppose you added www.amazon.com to the referral exclusion list.
When the user returns to your website from www.amazon.com, Google Analytics will still start a new session, but this time will attribute the user session to direct traffic instead of www.amazon.com.
Impact of referral exclusion list on payment gateways
Many businesses use PayPal and other third party payment gateways to accept online payments. But this can create tracking issues in Google Analytics.
Whenever a customer leaves your website to make payment via a third party payment gateway and later returns to your website from the gateway website, Google Analytics often attributes sales to the payment gateway instead of the original traffic source.
This is quite common in the case of PayPal.
You can often find PayPal.com appearing as a top revenue source in the Google Analytics Referral report:
Many optimizers add PayPal.com to the referral exclusion list under the impression that it will help them track the original referrer.
However, adding paypal.com to the referral exclusion list will NOT help you track the original referrer.
Google Analytics will then report the traffic from PayPal.com as direct traffic.
The best way to track original referrals while using paypal.com is to use one of the direct payment gateway solutions provided by PayPal like: ‘PayPal Payflow Pro‘ or ‘PayPal Payments Pro‘.
When you use a direct payment gateway, your customers can complete transaction without leaving your website and Google Analytics do not attribute sales to paypal.com but instead to the original traffic source.
The referral exclusion does not work retroactively. So,
Any visit/sales attributed to paypal.com before adding paypal.com to the referral exclusion list will still be attributed to paypal.com in GA reports.
Therefore you need to make sure that once you have added a domain to the referral exclusion list, you look at the referral report from the time period when you first implemented referral exclusion.
Is referral exclusion not working for PayPal.com?
Google Analytics uses the last non-direct click attribution model for non-multi channel funnel reports.
This model assigns all the credit for conversions to the last non-direct click on a conversion path.
Consider the following scenario
A user returned to your website (say ‘www.abc.com‘) from ‘www.paypal.com’ before you added ‘www.paypal.com‘ in the referral exclusion list of the ‘www.abc.com‘ GA property.
Now, here GA will attribute the user session to ‘www.paypal.com‘.
You added ‘www.paypal.com‘ to the referral exclusion list of the ‘www.abc.com‘ GA property.
The same user directly returns to your website ‘www.abc.com‘ within six months.
In that case, GA will still attribute the second session to ‘www.paypal.com‘ and not direct traffic because of the last non-direct click attribution model.
So even when you exclude the website ‘www.paypal.com‘, the returning users from the excluded domain can still appear in your reports.
To minimize this problem, set your campaign timeout setting to one month:
Other articles on specialized tracking in Google Analytics
- How to see Organic Search Keywords in GA4 (Google Analytics 4)
- Google Analytics Ecommerce Tracking Tutorial
- Google Tag Manager Event Tracking Tutorial
- Google Analytics Event Tracking Tutorial
- Google Analytics Store Visits Tracking Tutorial
- Offline Conversion Tracking in Google Analytics – Tutorial
- Ecommerce Tracking Google Tag Manager (GTM) – Tutorial
- Tracking Virtual Pageviews in Google Tag Manager – Tutorial
- Google Tag Manager YouTube Video Tracking
- Google Analytics Virtual Pageviews Tutorial
- Google Analytics YouTube Integration & Analysis Tutorial
- Google Analytics for Facebook Tutorial
- Cross Domain Tracking in Google Analytics – Complete Guide
- How to use two Google Analytics codes on one page
- How to correctly use referral exclusion list in Google Analytics
- Google Analytics Calculated Metrics – Tutorial
- Creating your own Google Analytics Tag Auditing System
- Google Tag Manager Search Tracking without Query Parameter
- Tracking Google Analytics Paypal Referral and other payment gateways
- How to Track Phone Calls in Google Analytics 4 – Call Tracking Tutorial
- How to track leads in Google Analytics via CRM
- Postbacks in Google Analytics Explained
- Subscription & Recurring Revenue Analytics in Google Analytics
- Track the Impact of Google Analytics Cookie Consent on Website Traffic
- Tracking Offline Conversions in Google Ads
- Implementing Scroll Tracking via Google Tag Manager
- Scroll Depth Tracking in Google Tag Manager – Tutorial
- Site Search Tracking In Google Analytics Without Query Parameters
- Google Tag Manager Youtube Video Tracking via YouTube Video Trigger
- How to Correctly Measure Conversion Date & Time in Google Analytics
- Google Analytics Social Tracking – Twitter, Facebook, Google Plus and LinkedIn
- Cross Domain Tracking in Google Analytics – Complete Guide
- Google Analytics Linkedin & Twitter Tracking
- Creating Content Group in Google Analytics via tracking code using gtag.js
- Google Analytics Site Search Tracking via Query Parameters
- Google Analytics Site Search Tracking Tutorial
- Creating and Using Site Search Funnel in Google Analytics
- How to add Facebook Pixel to Google Tag Manager
- AMP Google Analytics Tracking – Learn to track AMP pages
- Setting up Sales Funnel across websites in Google Analytics
- Google Analytics 4 Regex (Regular Expressions) Tutorial
Frequently asked questions about how to correctly use the referral exclusion list in Google Analytics
What is a referral exclusion list?
A referral exclusion list lists domains whose incoming traffic is treated as direct traffic (instead of referral traffic) by Google Analytics.
When you add a domain to the referral exclusion list, people who arrive at your website from the excluded domain do not trigger a new GA session. The traffic from the excluded domain is reported as direct traffic by Google Analytics.
What is the difference between direct traffic and referral traffic?
Direct traffic is a Google Analytics session (or visit) that starts without a referrer being passed by a user’s web browser.
Referral traffic is a Google Analytics session (or visit) which starts with a referrer being passed by a user’s web browser.
What is the impact of the referral exclusion list on cross sub-domain traffic?
When your website is on the referral exclusion list, then users can navigate from one subdomain on your website to another without starting a new session.
For example, if example.com is in the referral exclusion list, users can navigate from www.example.com to say music.example.com without starting a new session.
My best selling books on Digital Analytics and Conversion Optimization
Maths and Stats for Web Analytics and Conversion Optimization
This expert guide will teach you how to leverage the knowledge of maths and statistics in order to accurately interpret data and take actions, which can quickly improve the bottom-line of your online business.
Master the Essentials of Email Marketing Analytics
This book focuses solely on the ‘analytics’ that power your email marketing optimization program and will help you dramatically reduce your cost per acquisition and increase marketing ROI by tracking the performance of the various KPIs and metrics used for email marketing.
Attribution Modelling in Google Analytics and BeyondSECOND EDITION OUT NOW!
Attribution modelling is the process of determining the most effective marketing channels for investment. This book has been written to help you implement attribution modelling. It will teach you how to leverage the knowledge of attribution modelling in order to allocate marketing budget and understand buying behaviour.
Attribution Modelling in Google Ads and Facebook
This book has been written to help you implement attribution modelling in Google Ads (Google AdWords) and Facebook. It will teach you, how to leverage the knowledge of attribution modelling in order to understand the customer purchasing journey and determine the most effective marketing channels for investment.