Cross-domain affiliate tracking is not working properly when multiple marketing sites redirect traffic to a central store site for checkout. Let me explain this with an example:

• Site1: The main store site used exclusively for checkout and account management.
• Site2, Site3, Site4: Marketing sites that promote products and deals.

We have implemented a cross-domain tracking plugin on all three marketing sites (Site2, Site3, Site4) and connected it with the main store site (Site1).

Here’s the scenario:

1. Black Friday Page on Site2: A dedicated Black Friday deals page is created on Site2. This page lists not only Site2’s own products but also products from Site3 and Site4.
2. Affiliate Promotion: An affiliate promotes the Black Friday deals page on Site2 using their affiliate link.
3. Visitor Behavior:
   • If the visitor clicks a product listed on Site2 and goes directly to the checkout on Site1, the affiliate receives their commission correctly.
   • Problem: If the visitor first navigates from Site2 to Site3 (e.g., clicks on a product listed from Site3), and then proceeds to checkout on Site1, the affiliate does not receive their commission.

This issue arises because the affiliate tracking is breaking when the visitor’s journey includes multiple marketing sites (e.g., Site2 → Site3 → Site1). The tracking plugin fails to carry over the affiliate information across all domains involved.

This needs a solution to ensure affiliate data persists through the entire journey, regardless of how many marketing sites are involved before checkout on the store site.

• Affiliate site: https://affiliate.rnbgroup.com.pk — where affiliates register and are managed.
• Main site: https://rnbgroup.com.pk — where customer registrations and interactions occur.

Our primary goal is to have a system that allows for accurate tracking of commissions when users register on the main site, based on their initial referral from the affiliate site.Problem Details

1. Expected Behavior:
   • We anticipate that when a user arrives at the main site through an affiliate link (e.g., from affiliate.rnbgroup.com.pk), their registration on the main site should trigger a commission to be awarded to the corresponding affiliate.
   • This tracking should be seamless and managed entirely within the affiliate site, ensuring that all data remains centralized for reporting purposes.
2. Current Behavior:
   • However, it appears that the Affiliates Manager plugin does not currently register commissions for user registrations on the main site. This limitation prevents us from effectively managing our affiliate program as intended, similar to issues we faced with a previous plugin.

Desired Outcome

We need assistance to ensure that:

1. User registrations on the main site are tracked as referrals from the affiliate site and generate appropriate commissions for affiliates.
2. All affiliate data, including commissions for registrations, is consolidated and reported exclusively on the affiliate site.

Request for Support

Could you please provide:

• Recommended Configuration: Are there specific settings within the Affiliates Manager plugin that would facilitate this kind of tracking for registrations?
• Implementation Steps: If there are additional customizations required, we would appreciate any guidance on how to implement them effectively within the existing framework of the plugin.

Thank you for your attention to this matter. This feature is crucial for the success of our affiliate program, and we appreciate your support in resolving these issues.

1. I’m using plugin version 5.3.9
2. I’ve got cross-domain tracking turned on and I have confirmed that the cross domain is entered correctly tracking code/advanced settings page (synxis.com)

3. When I complete the reservation form (middle of the page) and click on “check rates,” be.synxis.com (a subdomain of synxis.com) opens in a new browser tab but the URL is not decorated with the GA cookie identifier (example: &_ga=2.146270516.1288110898.1573225544-1237297763.1556214672)

What’s going on?

If i have the main domainA and i want to cross track domainB

I need to activate the crossdomain setting in domainB, set there domainA, and also change the tracking code from domainB to domainA?

Is this right thing to do?

https://prntscr.com/n1e80i

Thank you

When I put the target URL in the list of domains to ignore for the external links plugin settings, the cross domain tracking seems to be working again.

So warning to those doing cross domain tracking – put your target domain in the ignore list.

Has anyone here been successful implementing cross domain tracking with Google Analytics code? I can find stuff on the web for this, but it is above my level of knowledge.
If you can share a piece of code containing the calling of the analytics.js file and the different tracking ID’s that might be very helpful to me.

Thanks in advance!

– Jan

I can’t find any documentation on setting up cross domain tracking.

Can you please confirm that plugin will work with any type of cross domain, for example, domain1 and sub-domain on domain 2 (www.domain-one.com with blog.domain-two.com) …?

For cross domain tracking, are these the correct steps?:

1. Install plugin on both sites and select the same GA property in the plugin settings

2. In the plugin’s Advanced Settings tab, turn on cross domain tracking, and enter both domain urls? Separate with comma?

3. No further additional settings to change or do for this to work? No extra property to add in Google Analytics – just use the same property?

Thanks for your help!

I followed your step-by-step tutorial for cross-domain tracking but could not make it work.
I later realized there’s a typo(?) in the custom code that was given.

__gaTracker(‘require’, ‘linkid’);
__gaTracker(‘linker:autoLink’, [‘example-2.com’] );

^
It should be linker instead of linkid

__gaTracker(‘require’, ‘linker’);
__gaTracker(‘linker:autoLink’, [‘example-2.com’] );

After making the change, the cross-domain tracker worked flawlessly.

Any suggestions on how to accomplish this in Google Analytics, with help from this plugin?

If not, also possibly some other scenarios of when you would use Cross-domain user tracking.

Thanks,
-crssp