Track specific pages on another domain

[Anonymous]

We have two TLDs and want to track web page visits across them. So far the documentation shows that you "can't do that."

http://developers.marketo.com/documentation/websites/lead-tracking-munchkin-js/

“Munchkin creates and tracks individual cookies on a per-domain basis, so for known-lead tracking to occur across domains, a lead association event must occur for each domain.  For example, if I control two domains, marketo.com, and example.com, and a lead fills out a form on marketo.com, then navigates to example.com later, then their activity on marketo.com will be tracked on a known lead record, but their activity on example.com will be anonymous.”

But what about this scenario:

We are interested whether a known lead visited specific web pages on the second domain. We don't have to know every page they visited on the second domain.

Could we set a value of a field in a user's record to be "true" if they visited a specific web page on the second domain? Or set a value to a field such as "Visited Page X"? Or do something like this?

[John_Clark1]

Hi James,

This wouldn't work because the system doesn't know that it's the same lead on the second domain until they identify themselves.  There isn't a way to affect the record on the original domain because when the lead visits the second domain they would be tracked as a completely different anonymous record until they were identified on the second and then merged.

John

[SanfordWhiteman]

James, the main exception to the rule (leaving out some more complex technical methods) is that if you happen to strictly control all, or at least a commanding majority, of the navigation paths to "secondary" Site B, you can reuse the association on Site B.

For example -- this came up in a Commty thread recently -- if all leads must complete a signup page on Site A before seeing a link to Site B, then you can carry over their association.  Or if you redirect people back to Site A if they haven't visited Site B before, that'll work.  However, if there are hits to Site B that aren't gated through Site A, you're out of luck and will have to wait for them to self-identify on Site B.