Talk to support. Tell them about this feature*, and see if they can turn it on if it's a real problem for you:
My client turned it on recently and the results have been much more sensible than before.
*just don't ask me what it does exactly and if it actually has any impact on reporting metrics.
Hey All,
I just wanted to chime in with another solution that's been working for us for a while. We, too, noticed a large uptick in the number of false clicks about two years ago. One of the reasons behind this was that when I first started here I worked with IT to have the SPF and DKIM set up properly, which had a positive impact on our delivery (~97% up from ~70%), but because we were able to 'hit' more companies now, we were also encountering more spam filtering software. As machine learning continues to grow and expand, we knew we needed to draw a hard line under how we track our emails.
We now use the "Visited Web Page" trigger, with Querystring Parameter Constraints built in every time. We utilize special UTM parameters (UTM_source, UTM_medium, UTM_campaign, etc.) to delineate visitors to the page who came from the email. It's important to set these Querystring constraints to use "contains" and NOT "equals". This is because the string will not only contain the UTM, but also the user's munchkin code, etc. and you don't want to lose data. See screenshot below for an example.
To make sure that we're not double-processing or double-scoring any lead, we also exclude the email's UTM from the overall web campaign that's tracking the asset on it's own (see screenshot below).
Overall this is a bit easier to track once it's set up, and a huge benefit is that it keeps you from having to rely on long wait steps, which can also push your campaigns further down the campaign queue in priority and can lead to race condition errors.
I hope this was useful!
Thanks,
Abby
.png)