Skip to content
IForevents Docs
IForevents Docs
HomeDashboardGitHubPrivacyTermsSecurityIntroduction
Support and SLA

Destinations

Forward every event to the tools your team uses (Cloud)

A destination is a place IForevents Cloud forwards a project's events to: Mixpanel, Amplitude, CleverTap, Google Analytics 4, Braze, Slack, or your own HTTPS endpoint. You track once, with any SDK, and every tool gets the same event within seconds. Destinations exist only on IForevents Cloud; the self-hosted edition is analytics only.

Not available yet

Destinations are not enabled yet. This page describes how they will work when they ship.

Set one up

  1. Settings → Destinations → Add destination. Pick the project, the kind and a name, and paste the credentials the tool gave you. They are encrypted at rest and never shown again.
  2. Optionally restrict what is forwarded: event types (track, page_view, identify), only some event names, or never some names.
  3. Send test event. The dashboard reports the HTTP status the tool answered. Fix the credentials until it succeeds; real traffic starts as soon as the destination is enabled.

What is sent

The event spec: the event's id, type and name, the user (your own id from identify / X-User-Id, plus the IForevents user id), the timestamp, the properties, the traits from identify, and the request context (address, user agent, SDK). Each connector maps that onto the tool's own batch API; the exact mapping is on Connectors.

Delivery, retries, log

  • Every event sent to a destination is one delivery. Deliveries are batched per destination (up to 100 events or 2 seconds) and rate-limited per destination so one noisy project cannot get another one throttled.
  • A tool answering 429, 5xx or timing out is retried after 30 s, 5 min, 1 h, 6 h and 24 h. Other 4xx answers are final. After the last retry the event is parked and can be replayed.
  • A destination failing five times in a row is paused for five minutes; the other destinations of the organization are unaffected.
  • The delivery log (Settings → Destinations → Delivery log) shows every attempt with its status, HTTP code, latency and error, for the plan's retention (3 days on Free, up to a year).

Plans

Free includes one destination and 100,000 deliveries a month, hard-capped. Paid plans include the whole catalog with a monthly volume of deliveries and per-plan overage; see Plans & Pricing.

On this page

Set one upWhat is sentDelivery, retries, logPlans