Repeated Events and Counts
An event that reaches Zeotap more than once is counted once. This page explains when that holds, when a repeat can still count, the hourly limit on counted events, and what to send support when a count looks wrong.
Why an event arrives more than once
Repeats are a normal part of moving events reliably, not a sign of a fault:
- Your side retries. A browser or mobile SDK that does not hear back in time sends the same batch again, and a partner webhook re-sends a batch it could not confirm.
- Our side retries. Delivery inside Zeotap is built so that an event is never lost, which means one can occasionally be handed to the realtime plane a second time — after a restart, a deploy or a brief storage error.
In each case the repeat carries the same event, and Zeotap recognises it.
What is counted once
When the same event is received again, Zeotap recognises it and does not count it again. This applies to everything a repeat could change:
| Value | Repeat counted again? |
|---|---|
| Counts — performed at least 3 times, a count attribute | No |
| Sums and averages | No |
| Latest value, minimum, maximum | No — a repeat never changes these |
This holds for realtime audience conditions, realtime attributes, what the Membership API and Sites serve, and what realtime syncs send. A repeat is recognised per person and per event source: the same event sent for two different people, or through two different event sources, counts for each.
When a repeat can still count
- Repeats more than 24 hours apart. An event is recognised as a repeat for 24 hours after it was first counted. A copy that arrives later, for example a partner re-sending a batch that is more than a day old, is counted again.
Hourly limit on counted events
Each person is counted for at most 1,000 events an hour. This covers every event that adds to a realtime count or sum for that person, however many audiences and attributes it feeds. A person means one identifier: one user id or one anonymous id.
- Events past the limit in an hour are not counted. Nothing they carry is recorded, latest values included, and they do not change audience membership. Counting starts again at the next hour.
- A repeat of an event already counted is still recognised as a repeat, and is never counted against the limit twice.
- A visitor this busy is almost always a bot, a load test or a shared device, whose counts would not be reliable anyway.
When a count looks wrong
Contact support with:
- the workspace;
- the person’s identifier, for example their user id or anonymous id;
- the realtime event, audience or attribute involved;
- the
messageIdof each event in question, if you have it; - roughly when the events were sent.
Next Steps
- Realtime Attributes — live per-person counts, sums and values.
- Membership — reading realtime audience membership.
- Realtime Syncs — pushing a person’s change to a destination.
- Sites — sharing audiences and attributes with your website.