customer_birthday event that your triggers can act on. Setting it up is two
steps: sync the birthday onto each customer, then tell your project which
metadata key holds it.
1. Sync the birthday into customer metadata
Birthdays live on the customer’smetadata. Pick a key (for example birthday)
and write the date there as part of your normal customer sync.
Use the
YYYY-MM-DD format with a zero-padded month and day (06, not 6).
The job matches on the trailing -MM-DD, so the month and day are what
actually drive the automation — but always store a full, valid YYYY-MM-DD
datemetadata, so include
it alongside everything else you sync (remember that sync replaces the whole
record, so keep sending it on every request).
2. Set the birthday key in your project settings
The automation needs to know which metadata key holds the birthday. Configure it once per project in the dashboard at your embed settings, under Customer Birthdate Key. Set this field to the metadata key you chose in step 1 — for the example above, enterbirthday. This is a project-level setting and applies to every business
in the project.
3. Add a birthday trigger
Once the key is set, the daily job creates acustomer_birthday event for each
matching customer. To do something with it, add a trigger that listens for that
event.
In the dashboard, this shows up under Triggers as “When it is a customer’s
birthday”. Attach the campaign you want to send, and it will run automatically
on each customer’s birthday going forward.