Hello everyone !
We use Adobe Analytics and Adobe Launch with the Experience Cloud ID Service extension to identify unique visitors.In addition to the main site, where everything works great,wehave partner pages with our IFrame on them.
When users visit partner pages after visiting main site,we expect to see previously assigned Visitor ID , but new Marketing Cloud Visitor ID assigne to visitor, though there is amcv cookie(id stores here) with the right old one(if user visited main pages before ofc).
Specifically : We use _satellite.getVisitorId().getMarketingCloudVisitorID() and get one id(let it be 1234) in the main page, then we go on our additional page, use this command again and expect to see 1234, but another one(5678) returned.
Any thoughts on what may be wrong with additional pages and why is it working like that ?
Solved! Go to Solution.
Views
Replies
Total Likes
So the different domain using a different adobe library would be the problem. even though you have your iframe in place. The users are crossing 2 domains so each report into their own report suites and hence generate 2 different visitor IDs.
You could try and add the partners domain to your report suite whitelist see if that helps but concern is if there are indeed 2 separate Adobe code bases/accounts may not easily be able to fix this.
(document.location.host == "domain.main.com" || document.location.host =="domain.iframe.com" ){
s_account = "domain.main.com";
GLTU
Views
Replies
Total Likes
So is the partner page with iframe the same domain as your main domain? Is it a separate sub domain? Is code base the same for both main and subdomain?
Views
Replies
Total Likes
In the partner's page the domain is different and it's not a sub-domain.
Adobe libraries are not connected at the partner's page, but we use them inside the iframe.
Views
Replies
Total Likes
Is this happening with some partner sites or all of them?
Views
Replies
Total Likes
Only on partner sites, where domain is not ours, we use our Iframe on these pages.
Views
Replies
Total Likes
So the different domain using a different adobe library would be the problem. even though you have your iframe in place. The users are crossing 2 domains so each report into their own report suites and hence generate 2 different visitor IDs.
You could try and add the partners domain to your report suite whitelist see if that helps but concern is if there are indeed 2 separate Adobe code bases/accounts may not easily be able to fix this.
(document.location.host == "domain.main.com" || document.location.host =="domain.iframe.com" ){
s_account = "domain.main.com";
GLTU
Views
Replies
Total Likes
Hi, we tried to add new url in the list of internal URLS, but it didn't help.
Can you please say what do you mean by 'report suite whitelist' and where can i find it ?
Views
Replies
Total Likes
This white list is part of s.code in the Adobe analytics extension in Launch you need to add lines there to allow this domain to be associated to the desired rsid. Click open editor to add there.
Views
Replies
Total Likes
Views
Like
Replies