Once per person
A person is sent a triggered project or campaign once. Tagging someone who already has the tag does nothing. Taking the tag off and putting it back does not send again.Who it starts with
The first time you start a tag-triggered project or campaign, it asks one question.
You must choose; there is no default. Resuming a paused project or campaign does not ask again.
Once a tag trigger has started, you cannot point it at other tags, or turn it into another kind of trigger. End it and create a new one instead. Until it starts you can change anything.
Tagging many people at once
Tagging people into a tag that a live triggered project or campaign listens for sends messages, so you are asked before it happens. When you tag in the dashboard (a person, a selection, a whole list, an upload, or a rule), a confirmation names the projects and campaigns that would start, how many people would be reached, and an estimated cost. Each message is charged as it sends.- Tag and send. People who newly get the tag are sent the message. Anyone already sent it is not sent it again.
- Tag without sending. The tag is applied and nobody is messaged. People tagged this way are not sent the message later, because they already have the tag.
- Cancel. Nothing happens.
Who is and is not texted
A tag says who to send to, and a list row says the person can be sent to. For a text project:- A tagged phone number on a list the project can use is texted, and the message uses that list row’s merge fields, such as
{first_name}. - A tagged phone number on no list at all is texted too, with your merge-field defaults in place of anything missing.
- A tagged phone number whose only list rows belong to another brand, toll-free number or short code is not texted. The project’s report counts it as skipped, and it has not used its one entry.
- A phone number that has opted out is never texted, and an email address that has unsubscribed or is suppressed is never emailed.
Pausing, ending, and deleting a tag
A tag cannot be deleted while a triggered project or campaign that is not finished, archived or deleted listens for it. End that project or campaign first.Over the API
- A trigger is
{"source": "tag", "tag": {"tag_ids": ["<tag id>"]}, "start": "immediate"}, onPOST /v1/projects(typetriggered) orPOST /v1/email/campaigns.startisimmediateornext_day;next_dayneeds the time zone and time of day in the same request. See Triggered texts and emails. - Start it with
POST /v1/projects/{id}/start, orPOST /v1/email/campaigns/{id}/schedulefor email, with{"audience": "current_and_new"}or{"audience": "new_only"}. It is required for a tag trigger’s first start, and any other project or campaign refuses it. GET /v1/tagsshowslive_triggerson every tag: the triggered projects and campaigns that listen for it, each with itsid,nameandchannel. It is empty when none do.POST /v1/tags/{id}/contactsandPOST /v1/tags/contactstakefire_triggers. With phone numbers or email addresses (identifiers) it defaults totrue; with acontact_list_idit defaults tofalse.POST /v1/contact-lists/importtakes it too, defaultfalse. When the tag has live triggers, a synchronous response carriestriggers.entered, the number of people entered; a queued list or import echoesfire_triggers. Removing a tag from contacts takes nofire_triggers.
