Setting up Google Analytics 4

Connect Google Analytics to measure visits and checkout activity in a Google Analytics 4 property. Enter a web stream's Measurement ID for browser tracking. You can also add an API secret for server-side purchase events through Measurement Protocol.

Before you start

• Sign in as the store owner, or use a staff account with access to manage Apps and integration settings.
• Have a GA4 property with a Web data stream for your storefront. Use a separate test property or stream when preparing your setup.
• Have permission to view the stream's Measurement ID and create an API secret if you need server events.
• Check whether the same GA4 stream is already installed through Google Tag Manager or a theme script. Avoid adding a second independent installation that counts the same activity again.

This guide uses GA4. Use a Measurement ID beginning with G-; a GTM- container ID, an AW- Ads ID, or a retired Universal Analytics UA- ID is not the value to use for this setup.

Install or open Google Analytics

1. In Nevuto Admin, open Settings > Apps.
2. Click Explore apps, find Google Analytics 4, and start its installation for the intended store.
3. Review the Install Google Analytics 4? dialog and click Install app.
4. If it is already installed, open its app details in Settings > Apps and click Open app.

The app installation confirmation. Installing the app does not replace choosing a GA4 stream and enabling its settings. Select an image to open it at full size.

Copy and save your Measurement ID

In Google Analytics, select the intended property. Open Admin > Data streams, choose the Web stream for your website, and copy its Measurement ID. See Google's Measurement ID guide.

In Nevuto's Google Analytics configuration:

1. Enter the G- Measurement ID in the field labeled Google Analytics.
2. Turn on Enable Google Analytics.
3. Leave the advanced API Secret empty if you want browser tracking only.
4. Click Save. Resolve any error, then reopen the configuration to confirm the saved ID and enabled setting.

Initial configuration with no ID or API secret entered and tracking disabled. Save is disabled until a setting changes. Saving checks the input format; it does not confirm that Google has received data.

Add optional Measurement Protocol purchases

To supplement browser tracking with server purchase events, create a Measurement Protocol API secret for the same Web stream whose Measurement ID you entered. In GA4, open that stream under Admin > Data streams, choose Measurement Protocol API secrets, and create a secret. Copy its secret value, not its display name. See Google's Measurement Protocol setup.

In Nevuto:

1. Expand Measurement Protocol (Advanced).
2. Paste the secret value into API Secret.
3. Keep Debug Mode off when you want server events recorded in your GA4 property.
4. Check Enable Google Analytics and click Save.

The advanced settings expanded with an empty secret and both toggles off. No secret was saved or purchase event sent for this screenshot. Keep your API secret private.

Understand the current Debug Mode behavior

In the current Nevuto integration, Debug Mode sends server events to Google's validation service. Those events are not recorded in GA4 reports. This control does not enable browser debugging or send server purchases into GA4 DebugView, even though the on-screen description mentions DebugView. Google's event validation guide explains the distinction.

Leave Debug Mode off for normal server purchase reporting. If you use validation while setting up, switch it off and Save before verifying recorded purchases. Browser debugging with Google Tag Assistant is a separate workflow.

Verify browser and purchase events

After saving your own test configuration:

1. Open your storefront in a separate browser tab. Grant analytics consent if your store's privacy settings request it.
2. Open Realtime in the matching GA4 property and confirm activity from your visit. For browser-tag diagnosis, follow Google's verification guide.
3. Complete a test checkout using a payment provider's test environment and return to the store after successful payment.
4. Compare the paid Nevuto order with the GA4 purchase event, its transaction reference, currency, and value. For example, a test order of 50.00 USD should report that currency and the intended purchase value.
5. If you configured API Secret, verify server purchase delivery with Debug Mode off. Server delivery also depends on the store's background processing and consent settings.
6. Check that a cancelled or failed checkout is not reported as a paid purchase. If browser and server purchase events both arrive, confirm that they refer to the same transaction rather than increasing the order count twice.

Allow for report processing; saving a setting or seeing browser activity alone does not establish that a server purchase arrived. These are instructions for your own test account, not a claim that the screenshots demonstrate successful GA4 delivery.

Browser purchase events reflect reaching the order-completed screen; a manual-payment order may still be awaiting payment then. Server purchases follow the order being marked paid. Use the payment status in Nevuto when reconciling the two sources.

Use your production property

When testing is complete, enter the intended production stream's Measurement ID and, if used, the API Secret created for that same stream. Keep Debug Mode off, turn on Enable Google Analytics, and click Save. Reopen the form to confirm the settings, then verify fresh storefront activity and purchases in the production property.

There is no separate sandbox toggle for this integration. Changing a payment provider to live mode does not change the GA4 property receiving your analytics.

Edit or disable analytics

Open Settings > Apps > Google Analytics 4 > Open app to update the ID or secret. Turn off Enable Google Analytics and click Save to disable this integration's browser and server collection. Data already recorded in Google remains there. Other tracking installed through a theme or Tag Manager must be managed separately.

Troubleshooting

• The configuration is unavailable: Confirm the app is installed in this store and your staff role can manage its settings.
• The ID is rejected: Copy the complete G- Measurement ID from the Web stream, without spaces or a tracking script.
• Save is disabled: There are no unsaved changes on the form.
• No visits appear: Check the property/stream, enabled setting, consent choice, and browser blocking. Test the storefront rather than an admin page.
• Browser activity arrives but server purchases do not: Confirm the API secret is from the same stream, the order is paid, and Debug Mode is off. Contact support with a non-secret order reference and test time if delivery is still missing.
• Counts are higher than expected: Check whether the same GA4 property is also installed through Tag Manager or custom scripts before adding or duplicating tags.