Insider

Insider is an AI-driven cross-channel personalisation platform covering web, app, email, SMS, push, WhatsApp, and on-site experiences powered by predictive segments.

Why route Insider through Datafly Signal

Profiles are updated from the server, not the browser. Events reach Insider even when a tracker blocker or a failed page unload would have dropped a client-side call, so the profile reflects what actually happened.
Delivery is batched, rate-limited, and retried. Signal buffers to Kafka, respects the Insider rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination. Insider is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

Prerequisites

Complete these steps in Insider before configuring Signal.

Access your Insider panel

Find your Partner Name

Navigate to Settings > Account. Your Partner Name is the short slug identifying your Insider tenant (e.g. myco). It appears in the API path: https://unification.useinsider.com/api/user/v1/upsert.

Generate an API key

Go to Integration Hub > Authentication > API Keys and click Generate. Configure:

Name: e.g. “Datafly Signal”.
Scopes: select Unification API (user upsert + event tracking).
Click Generate and copy the API Key immediately.

Decide on UUID source

Insider users are keyed by a uuid you control. Common choices:

Datafly user_id for authenticated visitors.
Datafly anonymous identifier for pre-login activity (will need to be merged once the visitor authenticates).

Configuration

Field	Type	Required	Description
`api_key`	secret	Yes	Insider Unification API key.
`partner_name`	string	Yes	Your Insider partner slug (e.g. `myco`).

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Insider under the Marketing Automation category.
Click Install, and fill in the required fields.
Click Install Integration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/insider/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Insider",
    "variant": "default",
    "config": {
      "api_key": "xxxxxxxxxxxxxxxxxxxx",
      "partner_name": "myco"
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Datafly Event	Insider Concept	Notes
`page`	`page_view` event	Sent via Unification API events array.
`Product Viewed`	`product_detail_page_view`	Includes product ID and name.
`Order Completed`	`confirmation_page_view`	Mapped to Insider’s purchase event with `total`, `currency`.
`identify`	User upsert	Identifiers + attributes sent to `/api/user/v1/upsert`.

Identity

Insider keys users on a uuid you control. Signal forwards:

Field	Source	Notes
`uuid`	`user_id` from `datafly.identify()`	Your stable customer ID. Used to key the Insider user.
`email`	`traits.email`	Stored in `identifiers.email`. Used for cross-channel resolution.
`phone_number`	`traits.phone`	E.164 format. Stored in `identifiers.phone_number`.
`custom.*`	`traits.*`	Additional traits are mapped to Insider custom attributes.

Call datafly.identify() whenever the user logs in:

datafly.identify("user-123", {
  email: "jane@example.com",
  phone: "+447700900123"
});

Insider events should be sent under the marketing consent category. Insider has its own opt-in records per channel (email, SMS, push, WhatsApp) — Signal forwards CMP consent state so server-side workflows can suppress messaging where appropriate.

Verify it’s working

Trigger a test event from your website.
In the Insider panel, navigate to Audience > Users and search for the test user by uuid or email.
Click the user to view recent events and custom attributes.
In Signal, check Live Events to confirm delivery with a 200 response status.

Troubleshooting

Symptom	Possible Cause	Resolution
`401 Unauthorized`	Invalid API key or wrong scopes	Regenerate the key with Unification API scope.
`400 partner_name invalid`	Slug doesn’t match account	Confirm the partner name in Settings > Account.
User not appearing	Missing `uuid`	Insider requires a non-empty `uuid` on every event.
Predictive segments not updating	Event name not in Insider’s taxonomy	Use Insider’s standard event names (`product_detail_page_view`, `confirmation_page_view`) for full segmentation support.

Visit Insider InOne developer documentation for full reference.