Is it possible to locate a lead's Cookie ID if we do not use an API?
Solved! Go to Solution.
What you really want to do, then is associate the Munchkin cookie with their lead record. You don't have to access the Munchkin cookie yourself outside of their browser.
But from your description, their actions are anonymous on the non-Marketo page. All web activities are either tied to a known lead (visits and clicks are both logged to the lead's ActLog) or anonymous (neither visits nor clicks are logged to the lead's ActLog). There's no way to have the Visit Web Page activity be known yet the Click Link be anonymous for the same browser session.
The best practice when running Munchkin on a non-Marketo-hosted page that does not share a registered domain with your Marketo-hosted pages is to do lead association from the browser side. To do this, of course, you need to have some way to transport the lead's primary identifier (email address) to the 3rd-party site. Then, once you have it, you can:
Not without an API call, no. Remember that a lead usually ends up with many cookies over time (so it's not just a single dimension Cookie ID).
But what is the exact problem you're trying to solve?
Thanks for the quick reply.
We're trying to connect a lead with activity performed on a non-marketo page. The page has munchkin, so we can see that they visited the page, but we'd like to tie clicks and other page actions back to that lead.
What you really want to do, then is associate the Munchkin cookie with their lead record. You don't have to access the Munchkin cookie yourself outside of their browser.
But from your description, their actions are anonymous on the non-Marketo page. All web activities are either tied to a known lead (visits and clicks are both logged to the lead's ActLog) or anonymous (neither visits nor clicks are logged to the lead's ActLog). There's no way to have the Visit Web Page activity be known yet the Click Link be anonymous for the same browser session.
The best practice when running Munchkin on a non-Marketo-hosted page that does not share a registered domain with your Marketo-hosted pages is to do lead association from the browser side. To do this, of course, you need to have some way to transport the lead's primary identifier (email address) to the 3rd-party site. Then, once you have it, you can:
That makes sense. Thank you!