Hey guys, absolutely! Thanks for bringing this up. I think this solution would work well for a centralized marketing execution team with more technical folks to ensure that it's done correctly. What I was hoping for with this 'idea' is to have a more marketer-friendly out of the box solution within the tool itself, like a checkbox or something similar next to the link tracking. This way it would be a more seamless experience.  ... View more

ALL THE YES. This would also be great as an email performance report option. It would be great to remove operational emails from general performance reports. ... View more

Gotcha - sorry Sanford. This works for our purposes, but obviously not for all. ... View more

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 ... View more

EXACTLY, Grégoire! That would be perfection. ... View more

What type of campaign would this be for? Can you simply exclude the segment in the "choice" statements of the flow steps and remove them there? ... View more

This needs to get back to the top of the pile as it can become a huge problem. This is especially difficult to deal with when inheriting systems with hundreds of unnecessary custom fields. Thanks! ... View more

I would vote for it, too! ... View more

Yes, I've recently inherited a system and I'm doing some cleanup with lead records that do not have email addresses. It occurred to me when trying to pull a SmartList that SFDC wasn't an available option which set me off on this path. I created the "SFDC ID_Value" field as a way to push the SFDC ID number into a searchable field. After speaking with Support it seems as though we can use a Salesforce workflow to populate that value, which will then flow into Marketo and be searchable and able to be used as a token in the flow steps of a campaign. Thanks for your help! ... View more

Yes, definitely! I've liked the thread and will remove mine. Thanks for bringing attention to it! ... View more

Hi Josh --  I mean more what changes were made to the actual SmartCampaign or program, not how it was run or which leads were affected. More like what our internal users have done, i.e. "Filter Changed: Country is US to Country is United States" or "Triggered Campaign Turned off by #### User", etc. To keep track of how the program has been altered over time.  Thanks, Abby ... View more