Ingest users from Segment

Connect Segment via webhook to import user data.

View as Markdown

Krenalis connects with Segment through webhooks to receive user data via real-time events. Once connected, Krenalis automatically stores users in your workspace's data warehouse for unification and activation.

How it works

  1. Set up a webhook. Set up a webhook on Segment.
  2. Filter events. Choose what events to collect.
  3. Map the data. Match each event property to your Customer Model using Visual Mapping, JavaScript, or Python.
  4. Ingest users. Krenalis automatically stores your users in the workspace's data warehouse, ready for unification and activation.

Steps

1. Connect Krenalis with Segment

  1. In your Krenalis workspace, open the Sources page.
  2. Click Add a new source ⊕, then select the Segment card.
  3. Click Add source....
  4. Click Add to complete the connection.
  5. On the connection page, click Settings → Event write keys and copy the event write key and the endpoint URL

2. Add a webhook on Segment dashboard

Then proceed to create a webhook destination in Segment:

  1. From the Segment dashboard, go to Connections → Destinations.

  2. Click Add destination, search for Webhook, then select it.

  3. Click Add destination on the webhook page.

  4. Choose the data sources to send to Krenalis, and enter a destination name and click Next.

  5. Enter a name for the destination and click Create destination.

  6. In Mappings, click New Mapping, select Send, and set:

    Field Value
    URL The endpoint copied earlier.
    Method POST
    Batch Size 500
    Headers Click Add Mapping Field, enter Authorization as the header name, and Bearer EVENT_WRITE_KEY as the value, where EVENT_WRITE_KEY is the write key you copied earlier.
    Enable Batching Yes

    Refer to the following screen:

    How to fill out the form

  7. Save and enable the pipeline.

3. Debug the events

Use the Event debugger in your source connection in the Krenalis Admin console to verify that events are received correctly.

  1. In Krenalis, open your source connection.

  2. Go to the Event debugger tab.

    Event debugger

    It shows a live sample of the most recent events received for this source connection. Use it whenever you need to quickly confirm that events are arriving as expected and to inspect their contents in real time.

  3. Generate an identify event in Segment. The event should appear within a few seconds:

    Event debugger

  4. Click the event in the list to view its JSON payload and confirm the data sent from your app.

    {
    "anonymousId": "b27c5d9f-92a7-4d30-b21a-4df21a6872c2",
    "context": {
        "browser": {
            "name": "Safari",
            "version": "17.2.1"
        },
        "ip": "172.91.24.57",
        "library": {
            "name": "krenalis.js",
            "version": "1.0.0"
        },
        "locale": "en-US",
        "os": {
            "name": "macOS",
            "version": "14.5"
        },
        "page": {
            "path": "/dashboard",
            "title": "User Dashboard",
            "url": "https://app.example.com/dashboard"
        },
        "screen": {
            "width": 3024,
            "height": 1964,
            "density": 2
        },
        "session": {
            "id": "1766272512048"
        },
        "timezone": "America/Los_Angeles",
        "userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 14_5) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/17.2.1 Safari/605.1.15"
    },
    "messageId": "f9189a52-b37b-4d7d-9f2d-08b91d85fa9c",
    "receivedAt": "2025-10-20T16:15:24.340Z",
    "sentAt": "2025-10-20T16:15:24.327Z",
    "originalTimestamp": "2025-10-20T16:15:23.992Z",
    "timestamp": "2025-10-20T16:15:24.010Z",
    "traits": {
        "email": "emily.johnson@example.com",
        "plan": "Enterprise",
        "company": "Acme Corp",
        "jobTitle": "Product Manager",
        "country": "United States"
    },
    "type": "identify",
    "userId": "703991475"
}

    If no event appears after a few seconds:

    • Check your application logs for errors.
    • Ensure your event write key and endpoint are correct.

💡 See the Event spec for full details on the event schema.

4. Add a pipeline to import user data

  1. Click on the Pipelines tab of the connection for Segment.
  2. Next to the Import users into warehouse pipeline, click Add pipeline....
Import users into warehouse

This is an "Import users" pipeline type, which transfers identified user profiles from events received from Segment into your warehouse.

Each pipeline defines how and when user data flows from Segment into the warehouse. You can add multiple pipelines per connection to handle different data segments or destinations.

5. Filter events

The filter selects which users to import based on the collected events:

Filter events

It is preset to import user data only if the event is of type identify—with or without traits—or if it is not an identify event but includes traits. For now, you can leave it as configured. Adjust this filter only after gaining experience with event handling.

6. Transformation

The Transformation section lets you populate your Customer Model properties using user traits from collected events. You can choose between a Visual Mapping interface or advanced transformations written in JavaScript or Python.

You have full control over which properties to map—assign only those relevant to your business context and leave others unassigned when no matching values are available.

Visual Mapping

For complete details on how transformations work for harmonization, see how to harmonize data.

7. Save your changes

When you're done, click Add (or Save if you're editing an existing pipeline).

The new pipeline will appear in your source connection and can be edited or disabled at any time.

Pipelines

Once saved, the new pipeline appears in the pipelines list for Segment. From here, you can monitor imports, adjust filters, and manage transformations. Each pipeline defines how and when users flow from Segment into your warehouse.

Pipeline to import user data
Column Description
Pipeline Name and description of the pipeline.
Filter Condition that determines which events are processed. If not set, all events are included.
Enable Switch to activate or deactivate the pipeline. When disabled, no events are processed.
Manage Edit settings such as filter and transformation.
⋮ (More) Additional options, such as deleting the pipeline.