Tessera DocsConnecting sources
0%

Getting started

3 min read

Send your first event

Track an action, attach properties and confirm delivery in the debugger.

An event is a single thing a user did, like signing up or finishing checkout. Start with one event that matters to your team and add more once the first one is flowing.

Name events in past tense

Use Object + Verb in past tense, such as Invoice Paid or Project Created. Consistent names make dashboards far easier to read six months from now.

Check the debugger

Open Debugger in the sidebar. Each incoming event shows its properties, the source it came from and any destinations it was forwarded to.

Was this page helpful?

Most searched

The three articles developers open most. Start here if you're stuck on auth, webhooks or keys.

Support

Docs answer most questions. For everything else, the engineers who built the API are one message away.

MK

Maya · Northwind

Our webhooks stopped at 14:02 UTC. Request ID req_8f2a91.

PS

Priya · Tessera engineer

Found it. Your endpoint returned 502 for 3 minutes. We replayed 214 events, all delivered.

Priya is typing

CAN’T FIND IT?

Ask the people who build the API. Send a request ID

or a failing payload and we’ll trace it on our side.

Replies in under 4 hours on weekdays

Answered by engineers, not a script

Full logs checked for every request ID

Quire Template

from

$79

Quire template preview

Create a free website with Framer, the website builder loved by startups, designers and agencies.