Receive lifecycle recipe events

Install recipes from the Recipes section of the Triggers page. Each guide says what to build on the receiving side and lists every field the event carries there.

• Klaviyo
  Each recipe sends one Klaviyo event. A flow triggered by that event’s metric sends the message.
• Braze
  Each recipe sends one Braze custom event. A Canvas that starts on that event sends the message.
• Marketing Cloud Engagement
  Each recipe fires a Journey Builder API event. A journey with that entry source sends the message.
• Marketing Cloud Next (Data 360)
  Each recipe writes one axo_lifecycle_event record to Data 360. A flow that starts from new records sends the message.
• Webhook
  Each recipe posts one signed JSON event to your endpoint. Your code checks the signature and acts on the fields.

When AXO sends

A recipe is installed as an ordinary AXO trigger, turned off. Once you turn it on, AXO watches for the moment, waits where the recipe waits, skips people who converted or are in their cooldown, and sends the event. Every lifecycle event needs the person’s marketing consent. A holdout group gets nothing so that the trigger’s lift can be measured. Event names:

• Abandoned cart: axo.lifecycle.abandoned_cart
• Abandoned browse: axo.lifecycle.abandoned_browse
• Abandoned checkout: axo.lifecycle.abandoned_checkout
• High-intent return: axo.lifecycle.high_intent_return
• Lapsed visitor: axo.lifecycle.lapsed_visitor

See Create a trigger for cooldowns, holdout and fire history.