Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hi Sanford, all,anything else I could try, any ideas? If not I can just go back to the timeout solution and close this topic.
Ok, I put it into the initial config and called the below code after the accept. Unfortunately this didn't work either, again the Visit Web Page is logged against anonymous. Munchkin.init(); var restoredLoc = document.createElement("a"); restoredLoc.href = document.location.href; restore...
Ok, I tried this one as well. Without luck though. Again it did not record the Vist Web Page on the known lead directly.Here's the code I put in after the cookie accept:Munchkin.init( "642-ZQB-201", {apiOnly: true} ); var restoredLoc = document.createElement("a"); restoredLoc.href =...
Hi Sanford,first of all, thanks for the rapid response. I am just not sure if I implemented your code correctly. Apparently the way I did didn't work. I tried it in a couple of different ways as well then, but neither created the Visit Web Page activity right after accepting the cookie, we're back t...
Hi everyone, I tried to implement Sanford's solution for deferring the Munchkin.Init() call for GDPR compliance on Marketo Landing Pages, as per https://blog.teknkl.com/conditionally-loading-munchkin-on-marketo-lps-for-gdpr-related-policies/. My problem was initially that - directly after accepting ...