Remind people before they renew.
The details, in every reminder.
The plan and the date, filled in.
Your backend sends the event before a plan renews, with the person’s email and its details. They enter at once, and an event that arrives at night waits for the sending window.
Name the moment and its details.
Make a trigger like Renewal upcoming. Its key follows the name, and under Payload you list the details each event carries, each with a type, or paste an example and apply it.
See it with a real event.
Preview as a contact shows the email with a sample event of the trigger that starts its campaign, or No trigger to read the words used when a detail is missing.
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 events show what each one did.
From a renewal date to a reminder.
Make a trigger.
Give it a Name, like Renewal upcoming. The Key follows it (renewal_upcoming): it is what your code sends. Under Payload, list the details each event carries: the plan, the amount, the date.
Send the event from your server.
Create an API key with Send events only access, keep it on your server, and send each event to send_event with the person’s email and its details.
The details go into the email.
Each payload field can go into the emails as a merge tag, like {{event.plan|your plan}}. Text and numbers go in as sent, in the subject, plain-text emails and designed ones.
Choose when it may go out.
Set the Sending window: the days and hours emails may go out, Monday to Friday, 9:00 AM to 6:00 PM by default, in each person’s timezone. An event at night starts the path, and the email waits for the window.
Next year, again.
Set If it happens again to Again after a break, and 7, 30 or 90 days after leaving the path, the next renewal can take them through it again.
The rules around every renewal.
- Merge tags
- {{event.plan|your plan}} fills in the plan the event carried; the words after the | are used when it carried none.
- Text and numbers
- Go in as sent, numbers with thousands separators (1,250). A list or a nested object never goes in: its tag shows the fallback.
- If it happens again
- Once per person by default. Again after a break lets someone go through again 7, 30 or 90 days after leaving.
- Send as designed
- A template sent as designed goes out exactly as you built it and uses none of your personalized emails.
- Sending window
- An event that arrives at night starts the path, and the first email waits for the window you set.
- Safe retries
- Send an idempotency_key when you retry: the same key twice is one event, counted once.