Integrations / Analytics
Google Firebase
Server-side event tracking to Google Firebase Analytics.
Datafly Signal delivers first-party events to Google Firebase server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Firebase expects.
Why route Google Firebase 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 Google Firebase 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 Google Firebase attributes the event to the right session.
Delivery is batched, rate-limited, and retried
Signal buffers to Kafka, respects the Google Firebase rate limit, and retries on 429 or transient failure rather than dropping the event.
One consent decision governs every destination
Google Firebase 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_cartpurchaseview_itemVertical presets
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 Google Firebase documentation.
Frequently asked questions
Does Datafly Signal integrate with Google Firebase?
Yes. Datafly Signal delivers first-party events to Google Firebase server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Firebase expects. The integration is included in every deployment at no additional cost.
How is server-side Google Firebase tracking different from the Google Firebase tag?
The Google Firebase 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 Google Firebase from your server, so delivery does not depend on browser conditions.
Which events can Signal send to Google Firebase?
The blueprint ships with mappings for add_to_cart, purchase, view_item. Any event in your schema can be mapped to Google Firebase through pipeline configuration without a code change.
Do I need to keep the Google Firebase tag on my site?
No. Signal delivers to Google Firebase from the server, so no client-side Google Firebase script is required on your site.
Other analytics integrations
Ready to move Google Firebase server-side?
See how Datafly Signal delivers first-party events to Google Firebase from infrastructure you control, with hashed identity and consent enforcement built in.