Integrations / Analytics
Woopra
Server-side product and customer-journey analytics via the Woopra HTTP Tracking API. Delivers events and visitor traits over the GET /track/ce endpoint, authenticated by project domain (no API key), stitched to browser sessions through the Woopra visitor cookie. Event properties are prefixed ce_, visitor properties cv_.
Datafly Signal delivers first-party events to Woopra server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Woopra expects.
Why route Woopra 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 Woopra receives the complete event stream.
Client IP and user agent are preserved
Server-to-server delivery normally loses both, which weakens matching. Signal forwards the genuine visitor values as request headers so Woopra attributes the event to the right session.
One consent decision governs every destination
Woopra 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_checkoutgenerate_leadloginpageplan_viewedpurchasesearchsign_upsubscription_startedview_itemVertical presets
Default. 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 Woopra documentation.
Frequently asked questions
Does Datafly Signal integrate with Woopra?
Yes. Datafly Signal delivers first-party events to Woopra server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Woopra expects. The integration is included in every deployment at no additional cost.
How is server-side Woopra tracking different from the Woopra tag?
The Woopra 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 Woopra from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Woopra?
The blueprint ships with mappings for add_to_cart, begin_checkout, generate_lead, login, page, plan_viewed, purchase, search, and more. Any event in your schema can be mapped to Woopra through pipeline configuration without a code change.
Do I need to keep the Woopra tag on my site?
No. Signal delivers to Woopra from the server, so no client-side Woopra script is required on your site.
Other analytics integrations
Ready to move Woopra server-side?
See how Datafly Signal delivers first-party events to Woopra from infrastructure you control, with hashed identity and consent enforcement built in.