Your pipeline. Your cloud. Your data.
Events from every source on one schema, identities resolved, segments described in plain language. Above 10B events a month the data plane runs in your own account and your data never reaches us.
0.0on G2Segment moves your data. RudderStack moves your data. Neither one can build the audience.
What's in the CDP
Every event, profile and object on one schema. Identity resolution built in, no taxonomy to define upfront.
Sources in, destinations out. Unlimited on every tier, including free.
Predictive traits the platform computes for you. Churn risk, lifetime value, propensity, updated live.
Describe the audience in plain language. The segment resolves itself, no query to write.
Route records to your own Kafka, to webhooks, and to every destination you already use.
Describe the audience. Skip the query. In plain language.
Marketing asks for an audience, you write the SQL, and the backlog becomes your team's reputation. Here they describe what they want and the segment resolves itself against live data.
- Plain-language audience definitions that resolve against live events
- Segments stay current as behaviour changes, with no rebuild
- No connector or segment caps on any tier, including free
One schema for every event and object. Identities resolved.
Anonymous sessions stitch to known profiles the moment someone identifies. Events, profiles and custom objects share one taxonomy, so nothing needs a warehouse round-trip before it becomes useful.
- Events, profiles and custom objects on a single taxonomy
- Anonymous to known identity stitching on identify
- Client, server and cross-platform SDKs feed the same schema
Publish records to a Kafka cluster you own. Your infrastructure.
Topic routing rules, partition keys and your choice of JSON or Avro. Records land in your cluster, on your topics, in the shape your consumers already expect.
- Ordered topic routing rules, first match wins
- Partition key and message format under your control
- Webhooks, CRM and messaging destinations alongside Kafka
At scale, the pipeline runs in your cloud. We never see it.
Above 10B events a month, hosting stops making sense for either of us. The data plane runs inside your own account, the control plane stays with us, and your customer data never reaches Intempt.
- Data plane in your VPC, control plane with us
- Installed with a Terraform module or a CloudFormation template
- Counts cross the boundary for billing. Events never do.
Collect from everywhere
Client, server and cross-platform
Seven SDKs feeding one schema. Instrument the browser, the app and the backend, and every event lands in the same taxonomy with the same identity resolution behind it.
Client-side
Auto-capture from the surfaces your customers actually touch.
No cap on sources at any tier, including free. Instrument everything.
Pricing
Published to 200M events. Then it runs in your cloud.
Segment and RudderStack both stop at “contact sales” well below this. Work out your own number, and know what happens past the point where hosting stops making sense.
CDP Cloud
We host it. First 1M events every month are free.
- 1M events/moFree
- 10M events/mo$1,080
- 50M events/mo$4,180
- 100M events/mo$6,680
- 200M events/mo$10,680
Annual commitment takes 20% off. No overage - you move up the same ladder at the same rates.
Full calculator →CDP Data Plane
A dedicated deployment in your own cloud account.
- Setup$10,000 once
- Control plane$3,000 per month
- Managed data plane$2,000 per month
- Usagemetered on events ingested
from $99,000/year
Including up to 456M events a month. Twelve-month term, minimum 100M events a month. Your cloud costs are yours, at your own negotiated rates.
Connect every trusted source.
Plug into the tools your team already runs on.
%201.svg){kind=logo}
%201.svg){kind=small}
Your customer data stays yours, and stays secure.
The teams that made the switch
We were losing visitors before they signed up. Intempt's personalized experiences changed that - we started meeting people where they were instead of guessing. Once they're in, Intempt's automated email takes over and keeps the relationship moving. Acquisition and retention finally feel like one connected motion instead of two separate problems.
Jim Stromberg, CEO
StockInvest
Case Study
StockInvest needed to turn anonymous traffic into registered users before any retention strategy could work. With Intempt's Experiences, they personalized the anonymous visitor flow, surfacing the right content and CTAs to boost signup conversion. Once users signed up, automated Journeys nurtured them through onboarding and deeper engagement, steadily increasing lifetime value.
Frequently asked questions
Everything you need to know about the Intempt CDP.
They move data. Neither can tell you who belongs in a segment without someone writing the query. Intempt collects and routes the same way, then computes attributes and resolves segments in place, so an audience request stops becoming a ticket for your team.
Your pipeline. Your cloud. Your data.
Collect events from every source, resolve identities, and let anyone describe an audience without writing SQL. 1M events a month free, with no cap on sources or destinations.