This content has been marked as final. Show 6 replies
I imagine there are a few ways to do it, but here's what we do:
Trigger: "Clicks Link in Email"
Email contains "[program name]".
Constraint: "Link Not Contains" unsubscribe.
Constraint: "Minimum number of times"
Here we set our interesting moments, set acquisition program/lead source if empty, and change the program status to success.
Note: You'd need a separate one of these Smart Campaigns for each engagement program
When I do this, it only shows people who clicked at least twice in any one of the emails, not at least once in at least 2 emails.
Could you do a simple clicked link in email trigger that adds them to a list? Then, if they are a member of any two-list combination (ex: A and B, A and C, or B and C), you change program status to success. Something like that might be one way to Jimmy rig it.
I had a similar challenge and here's what I did:
- Create a custom score type field - Nurture Email Click Counter.
- In each of the campaigns for recording email clicks, I would do a +1 for Nurture Email Click Counter.
- When the lead goes to a new stream, I would reset it back to 0.
- Similarly, when a lead goes to a new drip campaign, I would reset it back to 0.
Not the most efficient way to achieve this but is easy way around MKTO limitation to track email clicks separately.
Jeff - I tried your suggestion but received an error when I tried to create the smart list with the suggested logic of (1 and 2) or (1 and 3) or (1 and 4) or (2 and 3) and so on...
It will not save the logic with repeated filters.
Richit - We have several engagement programs running at the same time, where any of our contact could be receiving any or all of the program emails. Unless we create a Click Counter for every Engagement Program, I don't think this will work for us.
I'm not sure why you'd get an error, unless you've got it entered exactly as you've shown above. You can't repeat numbers in the logic. It would have to be (1 and 2) or (3 and 4) or (5 and 6) or (7 and 8), where each of those is a Member of List filter. 2 and 7 may in fact point to the same list, for example. I can't see why it would reject that logic.