Campaign Tracking across domains

[gmrsic]

We want to track users across domains, however the results we got from our tests made us question if it is working properly. We tested by setting a specific tracking code and navigating across domains. Then we checked in Adobe Analytics by looking at the visit metric and breaking down to platforms or pages - while having a filter in place with the tracking code we have set initially. We expected to see all platforms / pages we visited across domains, which was not the case. We would only see the pages of the first domain we visited.

to give more context:

• we are using the Web SDK's appendIdentityToUrl function to append the user identity cross-domain from domainA to domainB and can see that the value in the "kndctr_xxx_AdobeOrg_identity" is identitcal on both domains
• both domains track into the same Analytics report suite
• domainA and domainB have a dedicated platform name that is captured in the same eVar
• domainB is not showing a visit with a tracking code though

=> The question is whether there is a break in campaign tracking when you are leaving domain borders (which we think should not be the case)?

Thanks in advance!

[bjoern__koth]

to give more context:

• we are using the Web SDK's appendIdentityToUrl function to append the user identity cross-domain from domainA to domainB and can see that the value in the "kndctr_xxx_AdobeOrg_identity" is identitcal on both domains
• both domains track into the same Analytics report suite
• domainA and domainB have a dedicated platform name that is captured in the same eVar
• domainB is not showing a visit with a tracking code though

[Jennifer_Dungan]

No, there should be no break...

I have multiple domains, not even "sub-domain" in some cases... In my case, we have our main site (i.e. www.domain.com) and our subscription site that is shared for the majority of our sites (i.e. purchases.org.com) 

I have entries with campaigns to www.domain.com, and I can see those campaigns apply to the Orders that occur on purchases.org.com 

I am not using WebSDK, but that shouldn't make a differences... the values should be stored against the user / session.

However, there may be things that are breaking the session? For instance, have you ensured that both domains are listed as "internal urls" in your report suite configuration... also, this one is going to sound weird, but I had issues in the past if I also didn't code those into the "never track" for the automatic exit link tracking...  even though the suite was configured to have both as internal, if the actual tracking triggered an exit click to another internal domain the pathing / session info seemed to get weird... so I always make sure to configure in both places.... this also helps with efficiencies (to not track an extra server call when moving between domains). I assume WebSDK has a similar exit tracking configuration...

Check if that might be causing an issue?