Connect Google Analytics 4 to Customer Spine
Site and app behaviour for visitors who have not identified themselves yet.
Where the data goes
Every teamspace gets one endpoint for all sources — the signature header each vendor sends tells us which integration delivered the event. You are given the real one when you sign in — the last segment is your teamspace id.
https://ingest.customerspine.com/ingest/<your-teamspace-id>Method POST · Header X-Ingest-Signature
How it authenticates
You forward events from your own collector, signing the body with the generated secret.
Steps
- 1Forward from your collectorGA4 cannot post to a third party directly. Send a copy of each event from your own server, or from a scheduled BigQuery export, to the URL above.
- 2Sign the bodySet X-Ingest-Signature to the hex HMAC-SHA256 of the exact request body, keyed with the generated secret. If you forward a custom wrapper shape rather than the GA4 event row itself, also set X-Ingest-Source: ga4 so the source is recognised.
Worth knowing
GA4 identifiers are the weakest we accept. A client_id is a browser, not a person, so it never merges two profiles on its own — it only ever adds detail to a profile something stronger already established.