Highlighted

Cross Domain Tracking: embedded as an iframe

jaykwon

13-08-2018

Dear all analytics professionals,

I was trying my best to track cross-domain tracking but I guess I ran into a deadlock.

Here is my case:

I have a domain A. Several pages have iframed(?) form in the page sourcing from Domain B.

In other words, a page has domain A url but its form contents are coming from Domain B.

I am using DTM and I placed same DTM embed code between Domain A and Domain B.

Now I can implement Adobe Analytics tags to Domain B's forms' submit button but this click call does not include mid value.

( I installed Experience Cloud ID Service too.) The submit data is collected but I need to map them by a unique ID.

What I found out was AppendVisitorIDsTo (Cross-Domain Tracking) but when I install this rule in DTM,

Has it to be all page rules? I published the rule but the site had an error, all pages were not loaded. T.T

Please help me out!!

Sincerely,

Jaehong Kwon

Replies

Highlighted

PratheepArunRaj

Moderator

13-08-2018

Dear Jay,

Note sure whether AppendVisitorIDsTo will help for iframes.

Also, i don't understand your statement "I placed same DTM embed code between Domain A and Domain B".

You should place DTM code both in Domain A and Domain B so that the codes work properly.

Thank You

Arun

Highlighted

jaykwon

13-08-2018

Yes I did place DTM code both in Domain A and Domain B.

My problem is the server call from Domain B has no cookie value matching to the one from Domain A.

Highlighted

PratheepArunRaj

Moderator

14-08-2018

Dear Jay,

If that is the case, make sure you ask these questions.

1. Is the the cookiedomain set properly for both the domains?

2. The namespace for the tracking is the same on both domains?

3. Are the trackingservers set to be the same across both domains?

Thank You

Arun

Highlighted

jaykwon

14-08-2018

I set the same tracking servers and experience id service.

But I don't know what you mean by namespace for the tracking' and the cookiedomain set.

Highlighted

PratheepArunRaj

Moderator

14-08-2018

Dear Jay,

Have validated the Domains as given internally.

Domain A is having cookie period : 2.

By default, cookie domain period is set to 2 and thus you don't want to set this explicitly in your base code within DTM.

So, it supported the cookie : Below the screen grab.

1548391_pastedImage_1.png

Domain B is having cookie period : 3. Since you didn't add the cookie domain variable, the domain didn't support. Check your debugger. It will be showing 'N' against the variable i shown above : Below the screen grab.

1548395_pastedImage_2.png

Your fix now is to set cookie domain period to 3 in your base code under configuration variable. Checkout the link : s.cookieDomainPeriods . It should be set only for Domain B.

If you are using same base code for Domain A and Domain B, use 'if' condition or dynamic data layer  to set the same dynamically.

Thank You

Arun

Highlighted

jaykwon

14-08-2018

Dear Arun,

I really appreciate your sincere support. I solved the cookieDomainPeriods problem and now I see "Y" in cookie supported on domain B too. But Domain A is generating mid, which is experience cloud id but Domain B is generating s_fid, which is fallback id.

Now should I tag AppendVisitorIDsTo ?

Highlighted

PratheepArunRaj

Moderator

17-08-2018

Dear Jay,

Sorry for the late revert.

Actually AppendVisitorIDsTo is needed only if your browser/domain didn't allow third party cookie.

Even for us, in UAT, the visitor ID didn't match and fallback id is generated for one of two domains. But when we pushed it live, it worked.

Might be due to UAT/Firewall restrictions on the internal network. Push the tag to live for an URL and verify it.

Thank You

Arun