There isn't a one-stop workaround for this gap in functionality w/variables.
I'm glad to hear you care about the Text version (many more people should!) but you'll need to build that part separately.
... View more
Personally, I completely commiserate and understand the frustration and you, me, and other markers feel when we simply want to be able to measure the impact and engagement of our marketing campaigns and spam checkers, etc,. make that difficult.
However... if you put yourself on the OTHER side of the equation I kind of DO understand why it's such a challenge. If you or I were able to without a doubt know which engagements or activities were happening by real humans vs. those by a bot, couldn't malicious parties do the same thing and leverage that information for the wrong reasons? The reason I think spam checking platforms have to mimic human behavior is so that they can mimic what will happen when a real human DOES click a link or open an email. The ability to differentiate by it's own definition causes risk for spam technology, right?
My only point here is that while yes it's frustrating, it does absolutely make complete sense WHY it's such a hard nut to crack. I think there are tons of options for platforms like Marketo to step up and use the literally billions of sends they do at an aggregate level to appropriately clean up reporting and things of that nature to provide an accurate representation of engagement, but I'm personally a lot less confident them or anybody can really stop the bot triggering from happening to begin with, but instead could help us users filter those out. If we could know how to stop those bot actions from triggering activities, I don't see what's stopping other less well-meaning people from using the same techniques for phishing scams, etc.
Just sharing my perspective!
... View more
Sounds like I just need to modify the low-value criteria to exclude the other 3 categories so that it can serve as the default.
Well, yes... but I worry about any instance that's triggering on every Visit Web Page.
Depends on the load on your site(s), but this isn't sustainable if you're getting over, say, 100,000 hits per day (just speaking generally, different instances have different characteristics overall due to other processes).
I guess I don't really understand what it means for the criteria to be "pre-run."
Meaning if the trigger is constrained to particular webpages, then the back end has to do the least possible work to determine that it shouldn't continue (i.e. that the trigger's campaign doesn't even need to start running). This is very, very different from running the campaign, then having a lookback Add Choice that parses the Activity Log, only to determine that there's no work to do. (Not to mention that qualifying everyone regardless of work done means you can't even use one-time qualification rules to reduce load.)
There's not a hard-and-fast number of listening triggers. Some say 500, some 1000. But it closely depends on whether the action you're triggering on is happening 100 times a day or 100,000. You could have one constantly-firing trigger and kill the instance.
In your case you might think about doing the web page-based scoring in a batch if/when performance suffers.
... View more