01
Create your account
Create an account and your organisation.
The first organisation member becomes an administrator and can invite the rest of the team.
Settings → Organisation holds your company name, billing email and address. Settings → Brand is where you set the logo and colours your clients see on shared dashboards and embeds.

02
Define your data
Create an event bucket from a sample event or define its fields yourself.
Specify timestamps, dimensions and metrics.
Event Horizon uses that structure to make the data queryable.
An event bucket defines both what you send and how you analyse it. Paste one sample event and the columns are proposed for you, typed and classified, with the reason for each; you confirm or correct them. Nothing is created until you do. You can also declare them by hand, choosing what each one is:
| timestamp_key | When the event happened. Required, and it is what every time filter reads. |
| dimension | What you group and filter by: country, campaign, subscription plan. It is stored as it was when the event happened, so what a company was called in 2020 still reads 2020. |
| metric | What you add up or average: revenue, duration, quantity. |
Declare the time zone your data comes from. Everything is stored in UTC, and an undeclared zone is assumed to be UTC. A misread hour cannot be corrected afterwards.
Timestamps can be an ISO-8601 string, or a plain epoch number in either seconds or milliseconds. We read the unit from the magnitude, so `1787232000` and `1787232000000` are the same instant. A number that arrives as a string is read the same way.
03
Connect a source
Send data through a webhook, database change stream, API workflow or another supported ingestion method.
Start the workflow. Event Horizon handles the ingestion path.
The shortest path is a webhook, and a new workflow already opens with one wired to a Loader. If your data comes from somewhere else, the bar above the canvas swaps it for another common shape: a database we follow as it changes, or an API we call on a schedule. Save it, and the address is generated for you and cannot be edited, because it is derived from your organisation and that node so it can never collide or be forged.
In the node inspector, choose Manage secret → Generate. The key is shown once and stored only as a hash, and not even we can recover it. Lose it and you generate another. Then post to the address shown in the node's URL field:
curl -X POST "https://ingest.eventhorizondata.com/webhooks/<org>/<node>" \
-H "Authorization: Bearer <key>" \
-H "Content-Type: application/json" \
-d '{"event_id":"evt-1","value":42}' Note the ingest. host. Ingestion has its own entrance, separate from the application, and a request sent to the app domain will be refused.
Start the workflow. A webhook node only accepts traffic while its workflow is running.
Send an `event_id` in the body, or an `Idempotency-Key` header, and a repeat of the same identifier inside five minutes is discarded rather than stored twice. Send neither and every request is accepted as new, because we would rather not guess at what makes two of your events the same one.
A 401 means one of two things: no Authorization header, or a key that does not match. A node whose key has never been generated refuses everything, by design.
04
Look at your data
Open Explore and choose:
- What happened?
- Metric.
- To whom or where?
- Dimension.
- When?
- Time range.
Then build the query visually. No SQL required.
The query explorer needs no SQL: pick an event bucket, a metric, something to group by and a period. You can also type the question in plain words and press Ask, and the draft comes back filled in, with a note saying what it covered and what it left out. Nothing runs until you have looked at it. Dashboards are built the same way, and can be shared by link or embedded in your own product carrying your brand.
05
Build the dashboard
Turn the questions you care about into dashboard widgets. Filter and drill into the results.
Share the dashboard or embed it into your own product.
06
Control access
Invite your team. Assign roles. Use row scopes when someone should only see part of the data.
Settings → Team to invite people, Roles to design what they can do, and row scopes to limit someone to part of the data, such as a client of yours who should only ever see their own region.