Thanks for the clarification
Hi Jamie,
You are welcome
-Greg
Is this correct?
- The user will have had to fill out a form on www.DomainA.com so that their email address is stored in a cookie.
- The script will be included on a web page on www.DomainB.com but run from DomainA.com, so that the script on a DomainB.com Web Page can get to DomainA.com cookies, to get the email address
- The script submits a hidden form when the page on DomainB.com loads
Thank you,
Also, does this mean that there is no way to track Web Page Visits of anonymous leads (who haven't filled out a form yet) -- across domains?
(because we don't know their email address)
Also, does this mean that there is no way to track Web Page Visits of anonymous leads (who haven't filled out a form yet) -- across domains?
(because we don't know their email address)
No, you can do this even without the email address. But it has the same requirement that you must control all the entry points to the second domain. That is, if the only way to get to Domain B (or the only way that you care about) is via Domain A, then you can track the anonymous lead activity across domains, because you can pass identifying information in the URL.
But if there are any other direct visits to Domain B that don't go through Domain A, you will have a very hard time (it is not impossible, but it will require complex development) attributing the web activities to the active visitor on Domain A.
Hi James,
- The user will have had to fill out a form on www.DomainA.com so that their email address is stored in a cookie.
This is not correct: the email will NOT be stored in a cookie (at least not without some custom development) and if it was, that cookie could not be read in DomainB.com. You will have to make sure that, on the link to domainB in domainA, the email is included in the URL.
- The script will be included on a web page on www.DomainB.com but run from DomainA.com, so that the script on a DomainB.com Web Page can get to DomainA.com cookies, to get the email address
This does not make sense (sorry for being so blunt): the script runs on the client side and is dependent on the domain you are reading. so the script will run on domainB, so it can only read cookies created in domainB. Hence again the need to transfer the lead identification (email) through the URL and not through a cookie.
- The script submits a hidden form when the page on DomainB.com loads
Yes, but the hidden form submission reads the URL parameter through a hidden field (as explained by Sanford above).
-Greg
Being blunt is good, this is helpful. Thank you.
Can I have the script on www.DomainA.com send the information about what page was visited on www.DomainB.com? I think that could work because the URL of the page being visited is not in the cookies.
Can I have the script on www.DomainA.com send the information about what page was visited on www.DomainB.com? I think that could work because the URL of the page being visited is not in the cookies.
You mean send to DomainB the URL of the page that was visited on DomainA before they switched sites?
This information is already passed as the document.referrer. (Except for the specific case where DomainA is on https:// and DomainB is on http://. In this case, the referrer will not be automatically passed, so you can manually append the current page to the destination URL: http://www.exampleB.com/?prev=https://www.exampleA.com/sourcepage.html.)
I mean, send to Marketo...
Visited Web Page {URL}services.html on DomainB.com
another way to put it
Visited Web Page DomainB.com/services/
Hi James,
"Visit web page" activities are logged by the munchkin code, not by the URL click tracking (which would lead to a "click link" activity). The activity will be logged only if the lead is known in both domains, meaning a Marketo form has been posted in both domains.
-Greg