How is the Intempt CDP different from Segment?

Segment moves data. It cannot 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 the data team.

What counts as an event?

One record delivered out of the platform - to a broker, a lake or a messaging channel. Billing is on delivery, not on collection and not on monthly tracked users: collecting an event costs us almost nothing, delivering it is the work.

Are sources or destinations capped on the free tier?

No. Sources, destinations, segments, attributes and workflows are uncapped on every tier including free. Free caps volume per meter - 1M batch events, 10,000 streaming events and 100,000 analytics events a month - and holds them for 30 days at no charge. Paid tiers pick a retention window instead of inheriting one: Weekly at 7 days, Monthly at 30, Quarterly at 90, Standard at 13 months or Compliance at 24 months, with Standard the default. The free window does not undercut the paid ladder, because free retention is free only on the free event volume, while a paid window holds any volume. That is also what the 7-day level is for: a high-volume sender picks a short window so retention cost stays flat as volume grows, which is a volume choice rather than a smaller product. Retention is metered as a stock, so you are billed on the events you are holding rather than the events you send, and a longer window holds proportionally more.

How is delivery metered?

On two meters, not one. Real time publishes each event to a broker or a webhook as it happens; batch writes the same events to your lake on a window. Same events and same profiles either way, so you choose the latency per destination and pay for speed only where it earns it. There is no ingestion charge on either - we bill what leaves, not what arrives.

Do I need to buy seats to use the CDP?

No. Event volume prices the pipeline and seats price the applications. Neither gates the other, so a data team can run the CDP without buying anything for marketing or sales.

Data

Stop being marketing's SQL ticket queue.

Streams to your own Kafka, resolves identities, and replaces your CDP bill - the Data Engineer agent runs the pipeline, no handoff required. Start free.

Start for free

0.0on G2

10B+events

500M+users

7+years profitable

50+enterprises

Segment moves your data. It cannot build the audience.

What's in the CDP

Data Hub

Every event, profile and object on one schema. Identity resolution built in, no taxonomy to define upfront.

Integrations

Sources in, destinations out. Unlimited on every tier, including free.

AI Attributes

Predictive traits the platform computes for you. Churn risk, lifetime value, propensity, updated live.

AI Segmentation

Describe the audience in plain language. The segment resolves itself, no query to write.

Workflows

Deliver events to your own Kafka, to webhooks, and to every destination you already use - each one a step in the same recipe.

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.

Natural-language segmentsDescribe the audience in a sentence. It resolves against live events and keeps resolving as they change.
Unlimited objectsSources, destinations, segments, attributes and workflows are uncapped on every tier, free included. Only volume is metered.
Live membershipSegments re-evaluate as behaviour changes. Nothing to rebuild while the definition still holds.

Learn more about AI Segmentation

Describe an audience and the segment resolves

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.

One schemaEvents, profiles, messaging and analytics read the same taxonomy. No mapping layer between vendors.
Identity stitchingAnonymous sessions attach to the known profile the moment someone identifies. The first visit is not lost.
One event shape across SDKsClient, server and cross-platform SDKs write the same taxonomy. A mobile event and a backend event agree without a mapping step.

Learn more about Data Hub

Publish events to a Kafka cluster you own. Your infrastructure.

Topic routing rules, partition keys and your choice of JSON or Avro. Events land in your cluster, on your topics, in the shape your consumers already expect.

Routing rulesOrdered topic rules, first match wins, edited in the console. Change a destination without a deploy.
Declared destinations onlyPublishes to declared topics and buckets, checks consent before a send, and fails loudly rather than creating infrastructure.
Partition key and format you chooseSet the partition key, pick JSON or Avro. Existing consumers read it unchanged.

Learn more about Activation

The CRM is already deployed. Not a roadmap item.

A pipeline vendor hands you clean events and stops. Accounts, contacts, deals, lifecycle stages, tasks, meetings, scheduling and catalogs are live in the console today, on the same profiles the pipeline resolves, with every change available as an event.

Accounts, contacts and deals includedLifecycle objects ship with the CDP. No third tool to buy and wire back.
Seats and volume price separatelyVolume prices the CDP, seats price the applications. Neither gates the other, so a pipeline needs no seat.
Field changes are eventsA stage move emits an event. A workflow can act on it the same second.

Learn more about AI CRM

Workflows publishing events to Kafka and exporting to S3

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.

Server-side

Send events your client never sees. Payments, jobs, webhooks.

Cross-platform

One integration for both app stores.

React Native

No cap on sources at any tier, including free. Instrument everything.

Intempt vs the customer data platforms

Segment has the larger destination catalogue. The rows below are about whether the data does anything once it arrives.

CapabilityIntemptSegmentcompareTwilio Engagecompare

Event collection

SDKs and sources feeding the profile

Included

400+ connectors

Via Segment

Identity resolution

Anonymous to known to account

Included

Business tier

Via Segment Unify

Audience building

Segments from traits and behaviour

Included

Business tier

Included

Sends a message

The CDP itself reaching the customer

Included

Not offered

SendGrid plus Twilio

Channel coverage

Email, SMS, push, in-app, web personalization

All five native

None

Across three vendors

Product analytics

Funnels and retention on the same events

Included

Not offered

Delivery metrics only

Experiments

Testing on the audience you just built

Included

Not offered

Revenue attribution

Tying the routed event to closed revenue

Included

Routes the data only

Out of scope

Who operates it

Who has to be on staff to change a destination

A marketer

Engineering

Data portability

Warehouse sync, raw export, API

Included

Best in class

Segment grade

Pricing model

How the bill moves as you grow

On demand, no overage

Per tracked user, with a floor

Three meters

Every claim above is argued in full, with what they do better, on the linked pages.

Wired into the toolsyour team already opens.

Slack, Stripe, Twilio, SendGrid, Gmail, Google Calendar, Firebase, Apache Kafka, AWS. Blu Agent operates them for you without a browser tab.

See the full list

In the words of50+ live tenants.

“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

“Intempt helped us turn real browsing and purchase signals into personalized experiences that drive repeat buying. We finally have one system that sees the whole customer journey.”

Eric Gardner

COO, FieldsUSA

“With Intempt, we built a signal-led pipeline driven by real behaviors. Follow-ups are triggered by intent signals instead of timelines, so we only focus on users who are truly engaging.”

Tadas Kertenis

Co-founder, Hoperfy

Frequently askedquestions.

Everything you need to know about the Intempt CDP.

01 / 07

We're stitching HubSpot free plus Mailchimp plus Calendly plus GA4 with duct tape. Does this help?

That is the stack this is built for. Four tools, three seams, and no single view of ad click to signup to trial to paid, because none of the seams carry an identity. One snippet collects the events here, one profile per person resolves out of them, and events, profiles and custom objects share one taxonomy - so an audience gets filtered where it already lives instead of exported to a second tool to be useful. Nothing in front of that needs a data scientist or an analyst on staff: RFM, likelihood, ICP fit and next best product calculate on their own once a source is connected, keeping them current is a standing skill the Data Analyst agent runs, and most teams see live profiles in the same session they start setup.

That is the stack this is built for. Four tools, three seams, and no single view of ad click to signup to trial to paid, because none of the seams carry an identity. One snippet collects the events here, one profile per person resolves out of them, and events, profiles and custom objects share one taxonomy - so an audience gets filtered where it already lives instead of exported to a second tool to be useful. Nothing in front of that needs a data scientist or an analyst on staff: RFM, likelihood, ICP fit and next best product calculate on their own once a source is connected, keeping them current is a standing skill the Data Analyst agent runs, and most teams see live profiles in the same session they start setup.

Intempt Data

Your pipeline. Your cloud. Your data.

Collect events from every source, resolve one profile per person, and let anyone describe an audience without writing SQL or waiting on an analyst. Free to start, with no cap on sources or destinations.

Start for free