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 XCOR:- In Statsig, go to Project Settings and click the Integrations tab.
- Find Generic Webhook and click Enable.
-
In the URL field, enter:
Replace
TENANTwith the name of your Cortex XCOR tenant. - Click Event Filtering to configure which event types Statsig sends. XCOR ingests only config change events and silently ignores exposure events if sent. Select only Config Changes and clear Exposures.
- Save the webhook configuration.
- From the Generic Webhook integration card, copy the Signing Secret. The secret is required to configure the integration in XCOR.
Configure the Statsig integration in Cortex XCOR
Contact XCOR 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, XCOR automatically maps incoming config change events from Statsig to change events in XCOR. You can’t customize how the payload maps to change events in XCOR. To request modifications to the Statsig payload’s mapping, contact XCOR Support. The following table describes how Statsig event fields map to XCOR change events:
Replace the following:
TYPE: The Statsig config type in lowercase, such asgateorexperiment.ACTION: The action that occurred, such ascreatedorupdated. Combined withTYPE, this produces values likegate_updatedorexperiment_created.TIMESTAMP: The time the config change occurred, taken from the event’stimestampfield.NAME: The name of the Statsig feature flag or experiment that changed.