Triggers decide who gets into an automation, and when. Set them up well, and the right contacts come in on their own while everyone else stays out. Here's how they work.
A trigger is the event that starts a contact down an automation path. When a contact does that thing, like submitting a form, buying a product, clicking an email link or visiting a page, they enter the map at that trigger. Triggers always sit at the top of a path, and you can add as many as you need, so each one is another way into the map. Goals are similar, but a goal creates a path inside a larger map. Goals get their own lesson.
Go to Automations, then New Automation, and start from scratch. If you've turned on other objects, like Companies or Deals, you'll find automations under Contacts instead. Triggers should be the first thing you add.
Click the plus icon, choose Add Trigger, and pick the event. Triggers are grouped into CRM, External Events and Sales, and you can type to search the list. For example, choose "When contact is added to tag" and pick a tag, like "Interested in cardio." Now anyone who gets that tag enters the map. Want a second way in? Add another trigger for "Interested in strength training." A few triggers need setup first. "Sends you an email" needs Email Sync, and "Contact visits URL" needs the Ontraport tracking code on sites outside Ontraport. Click Done when you're finished, and remember that nothing goes live until you publish the map.
Conditions limit which contacts a trigger moves. Say you have a lead nurture sequence and you don't want existing customers in it. Add the condition "Contact doesn't have Tag" with your customer tag. Conditions can check tags, field values, email opens and clicks, how much someone has spent on a product, page visits and more.
Every trigger has a few settings. First, "Who can activate this trigger?" "Any contact in account" is the most common, and it's how you add new contacts to a map. "Any contact on this map" limits the trigger to people already on the map, which is useful for moving them from one path to another.
Next, "If contact is already on map, then…" "Move here when triggered" is the most common. It moves the contact to this trigger. "Ignore this trigger" leaves them where they are, so filling out a form a second time doesn't restart their journey. "Add here again when triggered" creates another instance of the contact on the map, which is handy when you offer several lead magnets.
Finally, check "This trigger can only be activated once per contact" when someone should only come through once, like for a one-time discount.
Three triggers work on dates. "Today matches contact's date field" fires when today matches a date in the contact's record, like their birthday. "Today is relative to contact's date field" fires a set number of days before or after that date, like a week before their credit card expires.
"Today is specific date" fires on a calendar day you choose, like the last day of a promotion. It only moves contacts who are already on the map, so they need to come in through another trigger first, usually a form. That makes it great for newsletters. Pair date triggers with a wait so you can choose the time of day your email goes out.
Every map also has a default trigger called Added to Automation. It lets you add contacts by hand, and you can't delete it. If no other triggers add contacts, build right below it. If other triggers add contacts too, use a Go To filter to send people from it to wherever they should start. And if only your other triggers should add people, put an End element under it.
You can give a map several entry points that lead to the same follow-up. For example, add one trigger each for forms A, B and C, and put a Go To filter under each one that connects to the shared path. The Filters lesson covers Go To in detail.
Separate triggers also help your reporting. Performance Mode shows stats on each element, so you can see how many contacts came in each way. Just keep in mind that if a trigger adds a contact again, they're only counted the first time.
So: triggers bring contacts in, conditions keep the wrong ones out, and the settings decide what happens when someone's already on the map. Next up: waits, which control the timing between the steps in your automation.