Surprised that more ESPs haven't adopted the concept of an "event" – @getdrip does it really well (though their implementation is still rough around the edges)
Everyone uses tags, right? "Customer" or "Bought Foo" or "Already Promoted Coaching"
1/
Everyone uses tags, right? "Customer" or "Bought Foo" or "Already Promoted Coaching"
1/
Tags are used to segment. "Send this broadcast email to everyone who is tagged 'Customer'"
Cool. BUT. They're limited. They don't 1) include temporal data, 2) frequency, or 3) metadata
2/
Cool. BUT. They're limited. They don't 1) include temporal data, 2) frequency, or 3) metadata
2/
Events allow so, so, so much more. Instead of tagging someone "Bought Coaching", fire a "Purchase" event with the "product" property set to "coaching".
Allows for the same segmentation ("who has bought coaching?"), but so much more...
3/
Allows for the same segmentation ("who has bought coaching?"), but so much more...
3/
- Who bought coaching within the last month? (can't do this with just tags)
- Who has bought coaching more than twice? (again, can't do with tags)
- Who bought coaching with the "summerslump" coupon code (hard to do without lots of tags)
4/
- Who has bought coaching more than twice? (again, can't do with tags)
- Who bought coaching with the "summerslump" coupon code (hard to do without lots of tags)
4/
My issue with @getdrip's current implementation:
- Can't segment (search) off of properties. So instead of an event of "Purchased Coaching" just have a global "Purchased" event and let metadata filter. Can't do that (yet?)
- Not exposed to Liquid
- SLOW. I get why, but... slow!
- Can't segment (search) off of properties. So instead of an event of "Purchased Coaching" just have a global "Purchased" event and let metadata filter. Can't do that (yet?)
- Not exposed to Liquid
- SLOW. I get why, but... slow!
