SanfordWhiteman

No, those are only the clicks you recognize as mail scanners.All the other mail scanner activity is not detected by Act-On, nor Marketo.Not sure why it's so hard to get across, but mail scanners do not all run from distinct IP subnets. They run from VMs all over the world, and their activity (of nec...

Act-On has exactly the same behavior except for a small number of old Barracuda subnets.This is not something that has been fully solved by any tracking provider, for good reason.

Yeah, you can use JS webhook or Apex in SFDC (I have a blog post on that) to gen the associator tokens. Or Velocity (which would be perfect) though I never posted the code for that.

Munchkin API calls aren't metered (I definitely didn't mean the REST API!). But you can't just use the Lead ID, you need the associator token (hash of secret + email). So that needs to exist beforehand.

If it's solely for cases when you have a mkt_tok (thus the lead must be knowable) can you not run associateLead with a precomputed associator token? That is, store the associator token on the lead itself, serve it up as a {{lead.token}}, run associateLead. Thus you have an associated session but no ...

From the appliance's perspective, it doesn't really hurt them if you recognize their IP addresses, as their job is done, once they inspect your links. This is 100% not true.If I am a malicious actor and I can tell whether a mail scanner is checking my phishing links, I can return safe content to the...

"announced" != "successfully implemented"Nothing is obvious. What you're referring to as "security appliances" are in fact VMs on cloud and private infrastructure whose IPs are shared by human users. That is the whole idea, to not be able to tell the mail scanners apart from humans. If your infrastr...

Having an FTP drop wouldn't speed an import. It would merely disguise the amount of time taken to complete it by shifting the experience completely to the background.You can build the same architecture in 15m with any off-the-shelf FTP server and a REST API bulk import.

Support is wrong (happens all the time, because they don't know the platform as well as veteran users). Search for "fixing Marketo pURLs" and you must also familiarize yourself with the docs on pURLs.

Already exists. Use a pURL and pass the Marketo Unique Code or Marketo Unique Name. See my blog post from a couple of years ago.