How long until a new event shows up?

Seconds. Events are available for analysis within seconds of arriving, so there is no nightly job and no separate real-time tier to buy.

What happens if I send the same event twice?

Nothing bad. Every event carries a unique ID and a second arrival with that ID is dropped rather than counted, so a retry never inflates a number.

Do you validate events against a schema I define?

Not per event. The fields that describe every event are checked on arrival, so a malformed call is caught before it is stored. If you need each custom event validated against its own authored schema before it is allowed in, that is a different model and Snowplow does it. What you get instead is seeing the event as it lands, which catches most of what a schema check would have caught, while you can still fix the code.

Do you have a Snowflake or BigQuery connector?

No, and no direct Databricks connector either. Events batch to an S3 bucket you own and your warehouse reads from there. One extra hop, and the storage stays yours.

Should I track client-side or server-side?

Both. Client SDKs capture more interaction detail. Server calls are more reliable, cannot be blocked by an ad blocker, and are the right place for anything tied to money.

A clam holding a glowing pearl as streams of bubbles flow into it.

Know your events arrived before you leave the code.

Watch events arrive in real time as you test, then stream the same data to your own topic or bucket.

Start for free

0.0on G2

10B+events

500M+users

7+years profitable

50+enterprises

Send events from the systems you already use.

Client SDKs, server SDKs, an HTTP endpoint and the platforms you already pay for all reach the same place.

Install a client SDK for web, iOS, Android or React Native
Call a server SDK from Node, Python or PHP, or post to the HTTP API
Pull from Shopify, Stripe, HubSpot or a scheduled feed

Send events from the systems you already use

Keep every customer event consistent.

The fields that describe an event are checked when it arrives, not on a job that runs overnight.

Name the event, stamp the time and identify who did it
Group a visit with a session ID and a company with an account ID
Get the check on arrival

Know your tracking works before you ship.

A live feed shows events arriving in real time, so you confirm the call in the moment.

Pause, resume or clear a live feed of raw events
Open any event and read the payload it actually sent
Turn a live row into a saved event with its properties mapped

Know your tracking works before you ship

Keep failed events from becoming lost data.

Every event carries an ID, so a retry does not become a second conversion.

Deduplicate on event ID with nothing to build
Skip writing your own batching, ordering and retry logic
Replay a failed request without inflating a number

Keep failed events from becoming lost data

Use events soon after they arrive.

Recent events stay fast to read and history stays fast to scan.

Analyse an event within seconds of it arriving
Trigger a journey as the event lands
Skip the nightly job and the separate real-time tier

Move events when your team needs them.

The same enriched record goes to a topic as it happens, or to a bucket on a window.

Publish each event to a Kafka topic your systems already watch
Write the same events to a bucket your warehouse reads
Pick the mode per destination, so you pay for speed once

Use cases built for the metrics that matter.

Three outcomes data teams measure from day one.

Events streamed to a Kafka topic, with delivery and replay on failure

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 every integration

Teams love it

They stopped stitching tools andhired one system.

Jim Stromberg, CEO at StockInvest — “Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

“Acquisition and retention finally feel like one connected motion instead of two separate problems.”
Jim Stromberg
CEO, StockInvest

Eric Gardner, COO at FieldsUSA — “We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

“We finally have one system that sees the whole customer journey.”
Eric Gardner
COO, FieldsUSA

Tadas Kertenis, Co-founder at Hoperfy — “With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

“With Intempt, we built a signal-led pipeline driven by real behaviors.”
Tadas Kertenis
Co-founder, Hoperfy

Frequently askedquestions.

01 / 06

How do I find out my tracking broke?

You watch it. Usually a client opens a dashboard and asks why a number looks wrong, which is a bad way to learn. The live feed means you can click through the flow yourself and see which call never fires, and connection status shows you a source that stopped sending.

Intempt Data

Confirm your first event in one session.

Pick a source and install it. Send autotracked events, then add your own. Watch the live feed to confirm they arrive. Point the stream at a topic, a bucket, or both.