Cidipi Pulse
The server-side pipeline your Klaviyo never had.
Pulse is the event layer that sits between your backend and every downstream tool. One authenticated API, one identity graph, one consent gate, one source of truth. If your revenue depends on it, it goes through Pulse.
Server-side by default
No cookies, no pixels, no iOS or ad blocker loss.
Typed schema, versioned
Every event has a contract. Bad payloads are rejected, not silently swallowed.
Replay and backfill
Ship a new segment or workflow and replay 90 days of history through it.
Warehouse-first
Every event lands in your database in the same shape used by segments and analytics.
POST https://pulse.cidipi.com/v1/events
Authorization: Bearer sk_live_•••
{
"event": "order.paid",
"occurred_at": "2026-07-28T18:02:11Z",
"identity": {
"user_id": "u_84120",
"email": "ana@brand.com",
"phone": "+385981234567"
},
"properties": {
"order_id": "N-10241",
"value": 148.90,
"currency": "EUR",
"items": [{ "sku": "AW-24-BLK", "qty": 2 }],
"channel": "web"
},
"consent_context": "promotional_email",
"source": "shop-api"
}Event fires on your backend
Order paid, subscription renewed, refund issued, cart abandoned, ticket closed. Your server calls the Pulse API with a signed key. No pixel, no ad blocker, no iOS 17 in the way.
Identity resolution
Pulse stitches the event to a single customer record using email, phone, user_id, device_id and anonymous_id. One person, one timeline, across web, app, POS and CRM.
Consent and governance check
Every event passes the nine-consent GDPR matrix and your retention rules before it lands. What is not allowed is dropped at the edge, with an audit line.
Stored in your database
Postgres, BigQuery, Snowflake, Redshift or a Cidipi-hosted warehouse. Raw event, resolved profile and derived traits. You own the schema and the rows.
Triggers segments and workflows
The same event updates live segment counts and fires lifecycle flows in milliseconds. Email, SMS, transactional or a webhook to your app.
Pulse architecture
The identity graph and consent gate, drawn.
Every Pulse event resolves against the same identity graph, passes the same nine-state consent gate, and lands on the same profile that segments and analytics read.
Pulse write latency at the edge, measured monthly
Replay window included on every plan, backfillable further on request
HMAC-signed events, rotating server keys, no browser secrets
Security & compliance
GDPR is a data model here, not a footer link.
Nine-state consent matrix
Awareness, promotional and special across e-mail and SMS, plus tracking, T&C and legitimate interest. Enforced at send, not in a spreadsheet.
Proof per record
Every consent change stores the form, timestamp, source and exact wording. A regulator audit is an export, not a project.
Your keys, your data
You own the database, the ESP account, the SMS gateway. We hold no monopoly credential you cannot revoke tomorrow.
Server-side by default
Pulse events are signed and validated server-side. No pixels to be blocked, no iOS 17 to lose events on, no ad blocker to defeat.
Twenty minutes
Bring one Klaviyo invoice.
Leave with a scoped plan.
No demo theater. We open your account, read the workflows and the consent state, and give you a real number for setup and monthly retainer before you hang up.