Name the moment.
Make a trigger like Payment failed. Its key follows the name, and under Payload you list the details each event carries, or paste an example and apply it to the fields.
When something happens in your product, the follow-up starts.
From one event to the right email.
Send it from your server.
Each time it happens, your backend sends the event with the person’s email. A key with Send events only access can send events and nothing else. On your website, the snippet’s behavly.track does the same.
The person enters the moment it arrives.
Every active Trigger Campaign that starts on it takes the person in at once. The sending window, the frequency cap and review still apply, and someone already on the path is left alone.
Try it without code.
Every trigger’s page has Send a test event. It sends the event for the address you enter, exactly as your server would, and the last 25 events show what each one did.
The details
- Plans
- Trigger Campaigns are on Starter and above. Each active one holds one of your plan’s always-on campaign slots.
- Product events
- Events from your server count toward your plan’s monthly product events, from 1,000 on Free to 1,000,000 on Scale. Events from your website snippet don’t.
- Safe retries
- Send an idempotency_key when you retry: the same key twice is one event, counted once.
- Many at once
- send_events takes up to 100 events in one request, and each answer names the campaigns it started.
- Events you didn’t describe
- An event with a new key is still accepted. Its trigger appears as not described yet, with fields read from the first event.
- Re-entry
- With Re-entry on, someone who finished the path can go round again on a later event, 90 days or more after leaving.