> ## Documentation Index
> Fetch the complete documentation index at: https://docs-xcor.paloaltonetworks.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Send Statsig events to Cortex XCOR

> Create a webhook to send your Statsig feature flag events to Palo Alto Networks Cortex XCOR as change events.

export const MyTenant = () => <>
    Replace <em><code>TENANT</code></em> with the name of your Cortex XCOR tenant.
  </>;

To send Statsig events to Palo Alto Networks Cortex XCOR, configure an
[outgoing webhook](https://docs.statsig.com/integrations/event_webhook#outgoing)
in Statsig and provide its signing secret to Cortex XCOR for
signature verification.

Cortex XCOR ingests only `statsig::config_change` events and silently
ignores other Statsig event types, such as `statsig::gate_exposure` and
`statsig::experiment_exposure`.

## Configure a Statsig outgoing webhook

To configure Statsig to send events to Cortex XCOR:

1. In Statsig, go to **Project Settings** and click the **Integrations** tab.

2. Find **Generic Webhook** and click **Enable**.

3. In the **URL** field, enter:

   ```text /TENANT/ theme={null}
   https://TENANT.chronosphere.io/api/v1/data/events/receiver/statsig
   ```

   <MyTenant />

4. Click **Event Filtering** to configure which event types Statsig sends.
   Cortex XCOR ingests only config change events and silently
   ignores exposure events if sent. Select only **Config Changes** and
   clear **Exposures**.

5. Save the webhook configuration.

6. From the **Generic Webhook** integration card, copy the **Signing Secret**.
   The secret is required to configure the integration in
   Cortex XCOR.

## Configure the Statsig integration in Cortex XCOR

Contact [Cortex XCOR Support](/support) to configure your Statsig integration and
provide the signing secret you copied from Statsig.

## Map Statsig events to Cortex XCOR events

After configuring the integration, Cortex XCOR automatically maps incoming
config change events from Statsig to change events in Cortex XCOR.
You can't customize how the payload maps to change events in Cortex XCOR.
To request modifications to the Statsig payload's mapping, contact
[Cortex XCOR Support](/support).

The following table describes how Statsig event fields map to Cortex XCOR
change events:

| Field | Value |
| - | - |
| `category` | `feature_flags` |
| `type` | `TYPE_ACTION` |
| `source` | `statsig` |
| `happened_at` | `TIMESTAMP` |
| `title` | `NAME ACTION` |

Replace the following:

* *`TYPE`*: The Statsig config type in lowercase, such as `gate` or `experiment`.
* *`ACTION`*: The action that occurred, such as `created` or `updated`.
  Combined with *`TYPE`*, this produces values like `gate_updated` or
  `experiment_created`.
* *`TIMESTAMP`*: The time the config change occurred, taken from the event's
  `timestamp` field.
* *`NAME`*: The name of the Statsig feature flag or experiment that changed.

Cortex XCOR also attaches the following labels to each event from the
Statsig payload:

| Label | Value |
| - | - |
| `type` | The Statsig config type, such as `Gate` or `Experiment`. |
| `name` | The name of the feature flag or experiment that changed. |
| `action` | The action that occurred, such as `updated` or `created`. |
| `description` | The description of the change, if provided by Statsig. |


## Related topics

- [Send third-party events to Cortex XCOR](/ingest/third-party.md)
- [Integrate with Cortex XCOR](/integrate.md)
- [Send Amazon EventBridge events to Cortex XCOR](/ingest/third-party/aws-eventbridge.md)
- [Send Buildkite events to Cortex XCOR](/ingest/third-party/buildkite.md)
- [Send Harness events to Cortex XCOR](/ingest/third-party/harness.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.