Munchkin Code on Third Party Site

[Anonymous]

Hello friends,

I was wondering if anyone here has given a vendor their munchkin code to put onto their website for tracking. We host some of our tools on a third-party site and I'd like to gain some info on this idea before reaching out to them.

Thanks!

[Anonymous]

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)

[SanfordWhiteman]

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.

[Anonymous]

Thanks a bunch for the info Gregoire, Dan and Sanford.

So I just want to clarify, but if the site is, "www.OurSite.TheirSite.com" then we should be able to utilize munchkin tracking with out-of-the-box functionality right? Just so as long as we are sharing a parent domain?

[Grégoire_Miche2]

Hi Danny,

On all sites which domain is .theirsite.com, the same cookie will work as long as it is correctly placed in the top domain, not in the subdomain.

-Greg

[Anonymous]

Thanks for the clarification

[Grégoire_Miche2]

Hi Jamie,

You are welcome

-Greg

[Anonymous]

So if the lead signs in from our website and is transferred to this third-party site, then we don't need a form at all? Or do we still need a hidden form? If it's the former, can you please elaborate on how we'd go about using a trigger smart campaign when they reach the destination site?

[SanfordWhiteman]

"Third-party site" is too ambiguous.  If it's a site that shares a parent registered domain with your website (www.example.com and info.example.com share such a domain) then it will also share the Munchkin cookie, assuming you've set the domainLevel param correctly (it will already be set correctly for a .com or other TLD of 3 letters or more).

If the sites do not have a parent registered domain in common, it becomes significantly more complex.  If you control all the entry points to the third-party site (that is, people always come from a form on your site to their site) then you can append their email address to the link, then do a hidden form post as Greg advises.

[Grégoire_Miche2]

Good point. I was assuming that 3rd party meant different parent domain. Typically the site of a business partner.

Also, you will need a little JS dev to capture the email from the URL and post it into the form using the forms 2.0 API.

-Greg

[SanfordWhiteman]

Good point. I was assuming that 3rd party meant different parent domain. Typically the site of a business partner.

I agree, typically it is a different parent when the word "vendor" is used, but I wanted to be sure.

Also, you will need a little JS dev to capture the email from the URL and post it into the form using the forms 2.0 API.

Hidden field to capture the Email, but yes, a little bit o' JS to do the auto-submit.

[Grégoire_Miche2]

Hi Danny,

When the lead is transported from your site to the third party one, the tracking of the lead will be lost, since they are not on the same domain: the cookie on your domain cannot be read on the 3rd party domain (and vice versa).

There are some techniques to pass minimum lead information through the transfer URL that may help. For instance in the form of "http://www.thirdparty.com/page?email=leademail@leaddomain.com//www.thirdparty.com/page?email=leademail@leaddomain.com".

But when arriving on the 3rd party site, a new cookie will be placed by your Marketo munchkin and you need a form post there to associate this second cookie with the lead entry in Marketo.

-Greg

[Dan_Stevens_]

What do you want this trigger campaign to do?

[Anonymous]

I want the trigger to shoot the visitor an email asking if they would like assistance or could use XYZ resource to guide them while using our tools.

[Anonymous]

Hey Grégoire - So would the hidden form be able to be submitted without any action taken on the lead's part? As soon as they visit the page we can have it as though the form was submitted?

[Grégoire_Miche2]

Hi Danny,

The hidden Mkto form needs to be submitted with some minimum lead info, at least email address.

Unless the site in question can recognize the lead (for instance with their own cookie system) and provide this info, you will need the lead to fill out a form on the 3rd party web site.

-Greg

[Anonymous]

Thanks, Grégoire. That definintely helps 

[Grégoire_Miche2]

Hi again Danny,

2 additional points :

• Forget about form prefill if you choose the visible embedded form
• Forget a bout any other type of integration (server side form post: quoted in the community but non supported, server side REST API: limited daily volume, client side REST API: significant security breach).

-Greg

[Grégoire_Miche2]

Sanford Whiteman​, you can see I am learning

-Greg