Trigger
Choose the event that starts the work.
checkout.started, checkout.abandoned should fire from a real Plandalf checkout, payment, invoice, subscription, deadline, or affiliate event, not from a front-end success page alone.
Sequence playbook
Checkout started to abandonment recovery
Recover a checkout that opened but did not complete by sending the buyer and offer context to the email or automation tool.
Triggers
- checkout.started
- checkout.abandoned
Actions
- send_abandonment_email Send Abandonment Email
- tag_abandoned_checkout Tag Abandoned Checkout
- sync_offer_context Sync Offer Context
Implementation
How this sequence should be wired.
A named sequence is useful only when the trigger, commercial context, and downstream handoff are all explicit across checkout, integrations, webhooks, and fulfillment.
Context
Carry the commercial state with the event.
The sequence should know the offer, product, price, buyer, payment state, coupon, invoice, and integration context before it touches another tool.
Handoff
Route each action to the right product or platform.
send_abandonment_email, tag_abandoned_checkout, sync_offer_context should land in the connected tools that actually fulfill, notify, reconcile, or update the customer record.
Product surfaces
Where the operator checks the work.
These are real Plandalf app surfaces tied to the products, features, integrations, invoices, payment settings, API docs, and sequences this playbook depends on.
Reference links
Everything this playbook touches.
Use these links when a builder needs to move from the sequence concept into the exact product, feature, integration, platform, workflow, stack, or documentation page.
Product
OffersThe checkout surface where your customers actually decide.
Product
AutomationsThe work that happens after a customer buys.
Feature
AutomationFeature
Purchase automationsFeature
Sequences with multiple similar triggers and any set of actionsFeature
NotificationsFeature
Customer identifyData
Feature
MetadataData
Feature
Form dataData
Integration
Klaviyoemail · marketing · website · sdk
Integration
Customer.ioemail · marketing · website · sdk
Integration
Zapiermarketing · sdk
Docs
Offers overviewImplementation reference for checkout events, webhooks, API, SDK, hosted checkout, and offer setup in this sequence path.
Docs
Hosted checkoutImplementation reference for checkout events, webhooks, API, SDK, hosted checkout, and offer setup in this sequence path.
Docs
WebhooksImplementation reference for checkout events, webhooks, API, SDK, hosted checkout, and offer setup in this sequence path.
Docs
API referenceImplementation reference for checkout events, webhooks, API, SDK, hosted checkout, and offer setup in this sequence path.
Docs
SDK eventsImplementation reference for checkout events, webhooks, API, SDK, hosted checkout, and offer setup in this sequence path.
Stack
The API-First ProductSplit transactional email from lifecycle email so each tool does what it's good at.
Stack
The Checkout Optimization LabTest checkout layouts, sessions, mobile flow, and recovery without turning the sales page into a custom app.
Stack
The Coupon Deadline FunnelRun a deadline offer with coupon rules and follow-up paths that stay attached to the checkout.
Stack
The Drop ShopRun a time-boxed drop with a real countdown, a bundle upsell, and segmented re-engagement.
Related products
The checkout surface where your customers actually decide.
The work that happens after a customer buys.