Why can’t I create a list or set a workflow to tag the people who have opened any email in a specific campaign or with an email name that contains “Campaign Code”? Having to find every email in our weekly newsletter campaigns is a nightmare, and could be as easy as adding Marketing Emails as their own objects with their own properties. This is a big Roadblock for us as we run several weekly newsletters. Upkeep on those lists could be a full-time job.
Hi @kcostello,
Other users have requested this before: https://community.hubspot.com/t5/HubSpot-Ideas/Additional-quot-Contain-any-of-quot-filters-for-Marketing-email/idi-p/531981
The product team reviews these requests based on popularity, I’d recommend upvoting and commenting. You can also help other users find the request more easily (and drive traction) by accepting my reply as a solution.
As far as workarounds go, there is a neat one using score properties.
- Create a contact engagement score: Understand the lead scoring tool
- Call it ‘Number of newsletter emails opened’
- Add event group > Add event criteria > Marketing email > Opened email
- Filter event:
- Select ‘Email name at send time contains any of Newsletter’ (or whatever applies)
- Keep the scoring to 1 point per open and adjust the score limit (at the top) if you think that contacts might have opened or might open more than 100
Save the score. You now have a property that counts how many times a contact has opened an email with they keyword ‘Newsletter’ in its name.
Best regards
Hi! Was looking for another and surprise - the Help team wasn’t helpful. TY just upvoted.
I used Lead Scoring and it said everyone opened it. Which is not true when I do my manual lists. So far the “new” Lead Score tool has done me no favors and ruined my previoously set up scores.
Thanks for the attempted workaround! I just need a marketing system that can handle marketing reporting.
@kcostello can you please share a screenshot of your lead score configuration? This is very likely (my apologies if I’m being too direct) a configuration error, not a bug.
