Currently we have a page we display on our www website property on successful Marketo form fill that gives out links to download our product(s).
Now we want to have a Marketo lander (on a subdomain: info.) pass a cookie to this same page so the downloads page will successfully render (without the cookie you are redirected to our product page).
I have tried to direct my developers to use the munchkin script on our www page to release the page via the marketo cookie. He says that this cannot be done.
So I have two problems. One I need to pass a cookie from the marketo lander to our www. so the page can be exposed OR I need to convince my developer to use the munchkin script which he says is not what i need and is different from the marketo form.
You're referring to "a cookie" but I highly doubt just any cookie will do.
It's extremely easy to append the Munchkin cookie to the query string of a Thank You URL using the onSuccess event. But again, why would that cookie be relevant on your main domain (esp. because it should already be shared with that domain, not even needing to passed)?
Hi Sanford and thank you for your reply 🙂
I think I may have the terminology wrong. Let me try again:
The question here is not "passing a cookie". We need to verify if the user has ever successfully submitted a marketo form or not. I am told this cannot be done using a munchkin cookie (this cookie gets created every time user visits the downloads page so it cannot be used to determine the marketo form submission).
I am being told the fastest way to get success here is to add the cookie we are currently using to the info. site (the marketo landing page). I have the script but I am not sure how to call to it on successful form submit.
I am being told the fastest way to get success here is to add the cookie we are currently using to the info. site (the marketo landing page).
Sure, as you'll see on your other thread you have to set the cookie at the parent domain.
Otherwise you're only setting it on the LP domain info.example.com, and it won't be set on www.example.com.