Google Analytics Setup
Recommended configuration for your Google Analytics 4 property when using DATA Reshape server-side tracking.
These are our recommendations for optimal tracking accuracy. Your setup may vary based on your specific requirements.
This guide assumes you already have a GA4 property created. If not, create one first at analytics.google.com.
Reporting Identity
Admin → Data display → Reporting identity
Select Blended. This combines User-ID, Google Signals, device ID, and modeling to provide the most complete view of your users across sessions and devices.
Google Signals
Admin → Data collection and modification → Data collection → Google signals data collection
Turn On. Google Signals enables cross-device reporting, remarketing audiences, and demographics data in your reports.
User-ID and User-Provided Data
Admin → Data collection and modification → Data collection → User-ID and user-provided data collection
Enable both settings:
- User-ID collection → On
- User-provided data collection → On
Then set:
- Collect automatically-detected user-provided data → Off
User data (email, phone, etc.) is collected and hashed by DATA Reshape before being sent to GA4. Automatic detection by GA4 is not needed and may cause duplicates or collect data without proper consent.
User Data Collection Acknowledgement
Admin → Data collection and modification → Data collection → User Data Collection Acknowledgement
Click I acknowledge. This is required by Google to confirm that you have appropriate consent mechanisms in place for collecting user data.
Referral Exclusions
Admin → Data collection and modification → Data streams → [your stream] → Configure tag settings → List unwanted referrals
Add your payment processors to prevent them from appearing as traffic sources and breaking attribution. Common examples:
| Payment Processor | Domain(s) to exclude |
|---|---|
| PayPal | paypal.com |
| Stripe | stripe.com |
| Netopia | netopia-payments.com |
| euPlatesc | euplatesc.ro |
| Mobilpay | mobilpay.ro |
| 3D Secure pages | Your bank's 3DS domain |
Add any other payment gateway domains that redirect users during checkout. Without these exclusions, returning users are attributed to the payment processor instead of the original traffic source.