Skip to main content
Network errors happen. A client cannot always know whether the collector stored a batch. ManaLens makes retries safe with the event’s message_id.

How it works

  • Every event has a message_id, a UUID.
  • Reports count each message_id once per project. So when a client sends the same event twice, page views, custom events and revenue count it once.
  • The SDKs make a new message_id for each event, and keep it when they retry a batch.

Retry a server event

When you send server events, set your own message_id, so that a retry has the same ID:
To make the ID stable across process restarts, derive it from your own record. For example, store a UUID with the webhook or job that the event describes.

Things to know

  • Deduplication happens in reports, not at the collector. A repeated event can be stored twice in raw_events. In SQL, count events with uniqExact(message_id). See SQL access.
  • A message_id must be unique in the project. Do not reuse one ID for different events.
  • Retry only 429 and 5xx responses. See errors.