Integrations / Analytics
Statsig
Server-side product-analytics event delivery to Statsig's log_event HTTP API. Logs custom events with a Statsig user object (userID, email, IP, user agent, locale, custom attributes) and event metadata, joined to Statsig users for experimentation and feature-flag metric measurement.
Datafly Signal delivers first-party events to Statsig server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Statsig expects.
Why route Statsig through Datafly Signal
Your numbers stop depending on what the browser allows
Client-side analytics loses every visit where the tag is blocked or the page unloads early. Signal delivers from the server, so Statsig receives the complete event stream.
Client IP and user agent are carried in the payload
Both are taken from the original visitor request rather than your server, which is what Statsig needs to attribute the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Statsig rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Statsig is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.
What ships in the blueprint
Mapped events
add_to_cartbegin_checkoutloginpagepurchasesearchsign_upview_itemVertical presets
Default, Retail. Each preset starts from a working configuration for that vertical rather than a blank field map.
Full field mappings, configuration fields, and troubleshooting are in the Statsig documentation.
Frequently asked questions
Does Datafly Signal integrate with Statsig?
Yes. Datafly Signal delivers first-party events to Statsig server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Statsig expects. The integration is included in every deployment at no additional cost.
How is server-side Statsig tracking different from the Statsig tag?
The Statsig tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Statsig from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Statsig?
The blueprint ships with mappings for add_to_cart, begin_checkout, login, page, purchase, search, sign_up, view_item. Any event in your schema can be mapped to Statsig through pipeline configuration without a code change.
Do I need to keep the Statsig tag on my site?
No. Signal delivers to Statsig from the server, so no client-side Statsig script is required on your site.
Other analytics integrations
Ready to move Statsig server-side?
See how Datafly Signal delivers first-party events to Statsig from infrastructure you control, with hashed identity and consent enforcement built in.