Tags in the REST API
Tags are listable and creatable over the API, and adding a tag to a contact is what triggers a tag-based sequence.
app.sendheron.com/contacts
Enrollment moves to where the truth is
Your application already knows when a trial started, when a payment failed, and when somebody stopped logging in. Making a tag the trigger means the decision about when a journey begins lives in the system that has the facts, rather than in a filter language that has to be told about them.
It also means the entry condition is one HTTP call and is testable from your own test suite, which a rule defined in somebody else's dashboard is not.
Creating and listing, not just attaching
Both halves are over the API: tags can be listed and created, and a tag can be attached to a contact. That matters for provisioning, because a script that sets up a workspace can create the tags a sequence expects rather than depending on somebody having created them by hand first.
The listing side is what makes the whole thing debuggable. When a sequence is not enrolling anybody, the first question is whether the tag your backend is sending matches the tag the trigger is watching, and that is now a request rather than a support conversation.
Related: Add tags to a contact, Tags and segments
Private beta
See the next one land
Beta members get the release note in the same batch email that opens their account.