Insider One

Datafly Signal sends product, cart and purchase events and profile attributes to Insider One through the Upsert User Data API, for identified users.

Why route Insider One through Datafly Signal

• Events arrive when the browser cannot send them. Server-side delivery is not stopped by ad blockers, tracking prevention or a page unload.
• One consent decision governs every destination. The integration is gated by the same consent state as the rest of your stack.

Prerequisites

• Your Insider One partner name (lower case) and a UCD API token.
• Email, phone and uuid enabled as identifiers in Insider’s Identity Resolution settings.

Configuration

Configure in Signal

API Endpoint

POST https://unification.useinsider.com/api/user/v1/upsert
X-PARTNER-NAME: partner
X-REQUEST-TOKEN: TOKEN
Content-Type: application/json

{"users": [...]}, batched up to 500 users per request (Insider accepts 1,000 and 5 MB).

Identity Signals

Event Mapping

Ecommerce / Retail preset (ecommerce)

Server-side Upsert User Data for Insider One’s Unified Customer Database: product views, add to cart, remove from cart, cart views and purchases as Insider’s default events (product_detail_page_view, item_added_to_cart, item_removed_from_cart, cart_page_view, purchase) with event_params per item (shipping_cost on the order’s first line only), and identify traits as profile attributes (gender, city, country, language; no name or birthday, which earlier versions never sent). Each user object carries the identifiers the event has: uuid (the Signal user_id), email (trimmed, lower-cased) and phone_number (E.164). Insider matches profiles on the identifier values themselves and messages users by email, SMS and WhatsApp, so email and phone are sent in plain text, as the Upsert API requires; they must be enabled as identifiers in Insider’s Identity Resolution settings. Events from anonymous visitors (no user_id, email or phone) are not sent. Page and listing views are off by default because the Insider tag records them.

To customise, edit the integration’s Field Mappings in the Management UI.

Example: a purchase

What Signal sends (rendered from the preset):

POST https://unification.useinsider.com/api/user/v1/upsert

{
  "users": [
    {
      "events": [
        {
          "event_name": "purchase",
          "event_params": {
            "currency": "GBP",
            "event_group_id": "T-1001",
            "name": "Parka Jacket",
            "product_id": "SKU-1",
            "quantity": 2,
            "shipping_cost": "4.95",
            "taxonomy": [
              "Jackets"
            ],
            "unit_price": 139.99,
            "unit_sale_price": 129.99,
            "url": "https://www.example.co.uk/shop/jackets?utm_source=google"
          },
          "timestamp": "2025-09-22T00:13:20.123Z"
        },
        {
          "event_name": "purchase",
          "event_params": {
            "currency": "GBP",
            "event_group_id": "T-1001",
            "name": "Wool Hat",
            "product_id": "SKU-2",
            "quantity": 1,
            "taxonomy": [
              "Hats"
            ],
            "unit_price": 20,
            "unit_sale_price": 20,
            "url": "https://www.example.co.uk/shop/jackets?utm_source=google"
          },
          "timestamp": "2025-09-22T00:13:20.123Z"
        }
      ],
      "identifiers": {
        "email": "neill@example.com",
        "phone_number": "+447700900123",
        "uuid": "crm-user-7"
      }
    }
  ]
}

Testing

Troubleshooting

Limitations

• Anonymous visitors are not sent: Insider needs an identifier.
• Page and listing views are off by default: the Insider tag records them.