Integrations / Analytics
June
Server-side product-analytics delivery to June (june.so) via its Segment-compatible HTTP ingestion API. Maps Signal page views and B2B/SaaS lifecycle events to June track/page calls with userId, anonymousId, identify traits, and event properties.
Datafly Signal delivers first-party events to June server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload June expects.
Why route June 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 June 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 June needs to attribute the event to the right session.
One consent decision governs every destination
June 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
feature_usedgenerate_leadidentifyloginpageplan_viewedsign_upsubscription_cancelledsubscription_startedtrial_startedVertical presets
B2B / SaaS. 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 June documentation.
Frequently asked questions
Does Datafly Signal integrate with June?
Yes. Datafly Signal delivers first-party events to June server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload June expects. The integration is included in every deployment at no additional cost.
How is server-side June tracking different from the June tag?
The June 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 June from your server, so delivery does not depend on browser conditions.
Which events can Signal send to June?
The blueprint ships with mappings for feature_used, generate_lead, identify, login, page, plan_viewed, sign_up, subscription_cancelled, and more. Any event in your schema can be mapped to June through pipeline configuration without a code change.
Do I need to keep the June tag on my site?
No. Signal delivers to June from the server, so no client-side June script is required on your site.
Other analytics integrations
Ready to move June server-side?
See how Datafly Signal delivers first-party events to June from infrastructure you control, with hashed identity and consent enforcement built in.