Google Analytics 4

1. Navigate to your GA4 Property and choose

   Admin > Data collection and modification > Data streams.

2. If you do not have a data stream yet, you should click Add stream > Web. If you do have a data stream already, you should click on the datastream.  

3. Copy the Measurement ID from the top right corner. You will need it later.  

4. Click on Measurement Protocol API secrets on the same page.

   If you do not see the Measurement Protocol API secrets option, this means that you do not have Edit permissions for this GA4 Property.

5. Click on Create to generate a new secret, and give it the name Converge. After creating, copy the Secret value.  

6. In your Converge dashboard, under Connections, click

   Create New Connection and fill in your Measurement ID and API Secret. After that click Create Connection.  

Google Analytics 4 does not natively deduplicate events that are being sent from both the server and the browser.

As such, the Converge connection will automatically not forward the server copy of the event and only send the browser copy of the event.

These server-side copies will show up with a Skipped status in the Connection Log. However, the event will still arrive in GA4 through the browser-side copy.

If you see that there is a discrepancy, check off the following:

1. Make sure that your GA4 property and your Converge dashboard are in the same timezone. There might be a difference due to a timezone misalignment.
2. Verify that you have no active Filters
   that are filtering out certain purchases. You can check this in the Connection Logs
   .
3. Make sure that you configured the connection type for this connection to be sGTM or server-side. If you are only tracking client-side, then your purchases might not get tracked due to Ad blockers and tag-loading issues.
4. Verify that you have disabled “Collect automatically detected user-provided data”under
   Admin >
   Data collection.
5. If your cookiebanner informs Converge that the user has given no consent, then Converge will pass this denied-consent parameter to GA4 and GA4 will drop this purchase. You can verify whether this is the case by inspecting the GA4 Connection Logs for the Placed Order-events. If you find a denied consent parameter under the profile properties then it means that your cookiebanner passed a deniedstatus for these purchases.
   

If your customer journey goes through multiple domains (e.g. landing pages or checkout on a different domain), it is important to configure this in GA4 to avoid broken customer journey reports.

You can configure cross-domain tracking through the following steps:

1. Go to
   Admin > Data collection and modification > Data streams.
2. Select your data stream > Configure tag settings > Configure your domains.
3. You have now arrived in the Cross-domain Linking Configuration. In some cases, GA4 will already provide you with some suggestions. If not, then you can add your domains by adding a condition. When setting up a condition, make sure that you use the Contains match type.
4. Save your changes.