Hi,
We have 2 websites on separate domains, that we want track with a single Marketo instance.
Site 1
Munchkin tracking code
Marketo forms
Site 2
Munchkin tracking code
Salesforce commerce forms
Our plan is to submit the munchkin tracking ID along with the Salesforce form, which will then be used in a Push Lead API call to associate the visitor activity with the lead after it is synced to Marketo.
However, if a lead first fills out a standard Marketo form on Site 1, and then fills out the form on Site 2 (triggering the process above), what will happen? Will the lead become associated with the munchkin ID of Site 2 only, and Site 1 activity will no longer be tracked? Or does Marketo maintain the association of multiple tracking IDs?
Thanks,
Solved! Go to Solution.
A record can have unlimited associated cookies. Wouldn't make sense otherwise: you couldn't even click a link on desktop and mobile!
A record can have unlimited associated cookies. Wouldn't make sense otherwise: you couldn't even click a link on desktop and mobile!
That's what I figured/hoped. I just couldn't find any official documentation indicating that.
Perhaps someone from Adobe can provide a link to documentation that describes that behaviour?
Well, that’s the behavior of web analytics packages going back 30 years! So we wouldn’t expect to see it explicitly in the docs.
Every separate browser/browser profile/device has a unique tracking cookie, even for visits to the same domain. Once you have different private domain suffixes*, that’s even more guaranteed uniqueness because cookies can’t be read across domain suffixes. Invalidating data about Cookie A just because Cookie B is created is shooting yourself in the foot: if you’re lucky enough to get people to accept cookies, you preserve as much data as you can.
| * private domain suffix is another way of saying registered domain. For example, a single cookie can be shared among subdomains of example.com within the same browser profile. A cookie can’t be shared across example.com and example2.com, even in the same profile. |