Configure the destination
- Open your Google Analytics destination in Masivo’s CDP connections.
- Configure at least one complete stream. Web uses its
G-...Measurement ID and API Secret. Android and iOS each use their Firebase App ID and the API Secret from the corresponding GA4 app data stream. - Enable Sync events and/or Sync purchases. Include the event names you need when restricting the allowed-events list.
- Use Test connection to validate sample payloads. This checks formatting, not credentials or actual collection; verify receipt in the real stream.
Connect client context
Your website/app captures the real analytics identity and session and supplies an optionalga4 object with events. For purchases, pass that context through
your checkout backend, which sends the protected PURCHASE event to Masivo.
Web uses the Google tag’s client_id; Android/iOS use Firebase’s
app_instance_id. Set session_id from the same session. Masivo does not
collect these values automatically or replace the Google/Firebase SDK.
Events without a real identity continue using the previous customer-ID
fallback on the web stream. They cannot be used to confirm that session
attribution is fixed. An app with an identity but an unconfigured stream
produces a configuration error instead of being rerouted.