Klaviyo
Ecommerce-focused marketing automation.
Klaviyo dominates Shopify-shaped ecommerce email and SMS. Deep integrations with storefronts, predictive analytics, and template builder. Less developer-centric than Customer.io, but the data model is rich.
An agent stack treats email as a two-way primitive. Inbound has to arrive as structured JSON a tool call can consume, sends have to be safe to retry when a model loop repeats itself, and every action needs an audit trail. A provider without inbound parsing only solves half the problem.
Against inbound parsing into tool calls and model-generated sends that must not duplicate, Klaviyo covers webhook coverage, event stream, batch sending, and SDK breadth, and does not cover inbound parsing, idempotency keys, operating track record, and multi-tenant support. Whether that gap matters depends on how central those are to the build.
- Inbound parsing: No
- Idempotency keys: No
- Webhooks: Yes
- Operating since: 2012
- Event stream: Yes
- Best published rate per 1,000: Tiers not published in comparable form
- Batch sending: Yes
- SDKs: node, python, php, ruby
- Multi-tenant: No
Solid for ecommerce traffic.
Shopify and ecommerce teams.
- › Ecommerce integrations are deep
- › Predictive analytics
- › Weak for non-ecommerce use cases
- › Pricing climbs fast with contact growth
Features at a glance
| API | Yes |
| SMTP | No |
| SDKs | node, python, php, ruby |
| Webhooks | Yes |
| Templates | rich |
| React Email | No |
| Batch send | Yes |
| Scheduled send | Yes |
| Suppressions | Yes |
| Multi-tenant | No |
| Inbound parsing | No |
| Event stream | Yes |
| Idempotency keys | No |
| Dedicated IP | Yes |