Using first-party data in GA4 for better attribution

This article explains how to enable tracking for hashed first-party data in Google Analytics 4.

Google's user-provided data collectionarrow-up-right enables your Google Analytics property to receive and process hashed first-party customer data.

circle-info

This feature is part of an open beta - it is subject to change, and may have no immediate effect on attribution.

This brings benefits similar to Enhanced Conversions for Google Ads:

  • Better user identification using consenting Google signed-in users' data

  • Cross-device attribution - e.g. user visited on Android phone and then purchased using Chrome (logged in)

  • Less reliance on cookies - bypassing 7 day GA cookie limit set by Safari / iOS

  • Demographic / interest reporting based on first-party data

How to track first-party data in GA4

There are 2 steps to track first-party data in Google Analytics 4.

  1. Open the Littledata app and go to the Google Analytics 4 destination settings. Under the Data customisation tab, turn on Send user data.

  2. In your GA4 property, open Data collection and enable User-provided data collection.

After you complete these steps, Littledata will start sending hashed first-party data to your GA4 property. The data is hashed using the SHA-256 algorithm.

How it works?

When you turn on the setting inside your Littledata account, conversion events sent to your Analytics property will be enriched with hashed first-party data.

If the user-provided data collection setting inside your Analytics property is not enabled, the conversion will be processed but the first-party data and user_id will not.

circle-check

This is an example of the data we send to Google Analytics:

Last updated

Was this helpful?