Integrations / Database

Google Bigtable logo

Google Bigtable

Event delivery to Google Cloud Bigtable.

Datafly Signal delivers first-party events to Google Bigtable server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Bigtable expects.

Why route Google Bigtable through Datafly Signal

The data lands in infrastructure you own

Signal writes to your Google Bigtable directly from your own deployment. Datafly operates no intermediary and never holds a copy of your event data.

Client IP and user agent are recorded as event context

Both come from the original visitor request rather than from your server, so geography and device analysis reflects the actual visitor.

One consent decision governs every destination

Google Bigtable 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_checkoutpagepurchaserefundremove_from_cartsearchselect_promotionview_cartview_itemview_item_list

Vertical presets

Retail, General. 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 Bigtable documentation.

Frequently asked questions

Does Datafly Signal integrate with Google Bigtable?

Yes. Datafly Signal delivers first-party events to Google Bigtable server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Google Bigtable expects. The integration is included in every deployment at no additional cost.

How is server-side Google Bigtable tracking different from the Google Bigtable tag?

The Google Bigtable 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 Bigtable from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Google Bigtable?

The blueprint ships with mappings for add_to_cart, begin_checkout, page, purchase, refund, remove_from_cart, search, select_promotion, and more. Any event in your schema can be mapped to Google Bigtable through pipeline configuration without a code change.

Do I need to keep the Google Bigtable tag on my site?

No. Signal delivers to Google Bigtable from the server, so no client-side Google Bigtable script is required on your site.

Ready to move Google Bigtable server-side?

See how Datafly Signal delivers first-party events to Google Bigtable from infrastructure you control, with hashed identity and consent enforcement built in.