Skip to content
IForevents Docs
IForevents Docs
HomeDashboardGitHubPrivacyTermsSecurityIntroduction
Support and SLA

Connectors

What each destination needs and how events map

DestinationCredentialsEndpoint usedMapping
Mixpanelproject token, project API secret, region (us or eu)/importevent = name, distinct_id = your user id, $insert_id = event uuid, properties as sent; identify becomes $identify with $-prefixed traits
AmplitudeAPI key, region/2/httpapiuser_id, event_type, event_properties, insert_id; identify becomes $identify with user_properties
CleverTapaccount id, passcode, region (us1, eu1, in1, sg1, aps3, mec1)/1/uploadevents as evtName / evtData keyed by identity; identify becomes a profile push (Name, Email)
Google Analytics 4measurement id, Measurement Protocol API secret/mp/collectone request per user, up to 25 events; names normalised to GA4 rules; page_view keeps page_location; identify is skipped
BrazeREST endpoint, REST API key/users/trackevents keyed by external_id; identify becomes attributes
Slackincoming webhook URLthe webhookone line per event with up to three properties; use filters to pick what reaches the channel
WebhookURL, optional signing secretyour endpointthe event spec

All connectors batch (Mixpanel and Amplitude up to 2,000 events per request, CleverTap 1,000, Braze 75, GA4 25 per user, webhooks 100) and use the event uuid as the idempotency key where the tool supports one, so a retry never double-counts.

Filters

Every destination can restrict what it receives:

  • Event types: track, page_view, identify.
  • Only these events / Never these events: exact event names.
  • Property predicates (API): eq, neq, exists, missing, contains, prefix on a property key.

Filtered events are not deliveries and are not logged.

On this page

Filters