Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Thanks! I created a webhook that calls mergeLeads automatically any time a lead is created in Salesforce so that fixes this issue.
I have a webhook that I'm using to associate a _mkto_trk cookie with leads as suggested by Marketo support. There's a lot of background there, but my goal was to associate a user's _mkto_trk with a duplciate lead synced in from Salesforce using the webhook. The problem is that the form uses Email is...
Thanks Justin. That's exactly what I was looking for and support told me it couldn't be done.It would be cool if you supported the option to add it as an anchor too as it would only require a small modification to Munchkin and your redirect page. This is mostly for caching but could be used when peo...
I wanted some variation of this too and eventually found the solution after support said it wasn't possible.Now you can remove the tracking code while still tracking clicks in the email or remove tracking altogether. The redirects in the email allow you to see click link in email activitiy and the m...
That was more for example, but the problem is no different for a thousand or a hundred thousand emails. Users are impatient and every hundred ms you add to that makes a big difference. Having a unique query string (read server request) for each page view breaks a CDN, thus adding probably 100-500ms ...
A big issue with email tracking is that is breaks caching. When you click on a tracked link in an email and the user ends up at http://example.com/page.html?mkt_tok=[unique_for_every_user], it makes the page uncacheable, hammers servers, and prevents any CDN from working properly. When sending out a...
I'm ending up with duplicate leads in Marketo because we convert anonymous users to leads with associateLead and Munchkin, but also have Salesforce sync setup to add custom objects such as customer order data into Marketo.I've read some documentation that says to 'solve' this by only adding leads in...
Thanks Calvin. I'll go with the suggestion of adding my own info to track whether the lead is associated or not since anonymous lead tracking is important to me.Even better, I'm now looking for _mkto_trk before Munchkin initializes so I can know to call associateLead immediately if I know the user's...
I'm just implementing Munchkin now, but I'm wondering if I can figure out if associateLead needs to be called. I have a variety of ways of detecting who the current user is on my site such as through cookies or localStorage. I want to avoid making superfluous calls to associateLead to reduce request...