Use cases
Four common shapes we see every week. If yours is not here, the 20-minute audit still applies.
Pulse captures every checkout event server-side. Segment on last-purchased category, LTV, days since order. Post-purchase, replenishment and win-back flows that fire on the right cohort.
Ingest product events through Pulse, resolve to accounts, trigger lifecycle by plan, feature adoption or workspace health. Sales sees the same timeline marketing does.
Per-topic and per-brand consent, paywall event tracking, subscription state as a first-class segment dimension. Every send is enforceable against the ledger.
Subscription state, days-to-refill, cancellation reason and reactivation window as native segment fields. Workflows branch on the same logic the analytics dashboards show.
Deeper cuts
Shop pixel, warehouse orders, returns feed, help-desk tags, POS and paid ads unified on one identity. Post-purchase, replenishment and win-back flows fire on the true cohort, not the segment your last snapshot happened to include.
Pulse ingests product-usage events, resolves them to accounts, and turns feature adoption into first-class segment fields. Sales sees the same timeline marketing does, and PQL is a query, not a nightly export.
Newsletter opt-ins, per-topic consent, paywall events and subscription state are first-class fields. Every send is enforceable against the ledger, and the regulator audit is an export away, not a project.
Days-to-refill, cancellation reason and reactivation window as native segment fields. Workflows branch on the same logic the analytics dashboards show, because they read the same rows.
Shared identity, per-brand consent, per-brand sender reputation. A customer with three brand relationships is one profile with three consent contexts, not three duplicate contacts fighting each other in send.
POS events land on the same record as web behavior and CRM tags. A tier change is a segment change and a workflow trigger, on the same timeline the store manager sees.
Signal, not testimonials
“We were paying Klaviyo more than we were paying our lead developer. Cidipi took us off the meter in three weeks. The retainer is a rounding error next to what we spent last year on features we never opened.”
“The real value was not the price cut, it was finally having server-side events into one profile. Our attribution stopped being a religion.”
“The team coded three backend hooks with our engineers and stayed on the standup until we shipped. That is not a SaaS relationship, that is a partner.”
Twenty minutes
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.
