Lytics

Lytics Audience Trigger Webhook Setup

Pushly integrates with Lytics using an Audience Trigger Webhook.

For the step-by-step webhook configuration flow in Lytics, follow Lytics’ documentation while applying the Pushly-specific requirements below.

Prerequisites

Before you begin, make sure you have:

1. A Pushly API key: Generate one using Pushly’s API Access Management documentation.

2. A Pushly webhook URL: Your Pushly account manager will provide this.

3. A matching user identifier selected from your Lytics profile schema This identifier must be:

   • unique per user

   • stable over time

   • privacy-safe

   • the same identifier Pushly will use for matching

Important: before the integration can function, you must confirm with Pushly which Lytics profile field will be used for matching. If you are unsure which field to use in Lytics, contact your Lytics account manager.

Pushly-Specific Configuration

Authorization Header

Configure the webhook to send this header:

X-API-KEY: <your Pushly API key>

Webhook URL

Use the Pushly webhook URL provided by your Pushly account manager.

Trigger Type

In Lytics, configure the webhook as an Audience Trigger Webhook and select the audience event types you want Pushly to receive:

• Enter

• Exit

You can also enable Existing Users if you want Lytics to backfill users who are already in the selected audience. Lytics sends those as entered events.

Do not enable Existing Users until you have performed a test against an internal user profile to ensure the integration is working as expected.

Export Fields

When you configure Export Fields in Lytics, include:

• your selected matching identifier field

• segment_events

This is critical. Lytics only sends the fields you select in Export Fields. Do not leave Export Fields empty.

Optional Settings

Lytics also supports Fields to Trigger, which sends webhook events when selected user fields change. This is optional and is separate from audience entry and exit events. For a standard Pushly audience-trigger integration, this usually does not need to be configured.

Validation

After setup, validate the integration by triggering a real audience event in Lytics.

You can do this by:

• adding or updating a test user so they enter an audience

• removing or updating that user so they exit an audience

Before You Finish

Please provide Pushly with the exact Lytics field that will be used as the matching identifier before the integration is activated.