Set up Google Analytics 4

Connecting Google Analytics 4 has two halves: a value you create in Google Analytics, and a value you paste into Vunda. You set up a GA4 property and data stream in Analytics, copy its Measurement ID, paste it into Vunda, and your app starts reporting events on its next build.

What you will need

• A Google Analytics account with a GA4 property you can edit.
• A few minutes inside Google Analytics to add a data stream and copy its ID.

Step 1: get your Measurement ID from Google Analytics

This step happens inside Google Analytics, not in Vunda, so the exact screens are owned by Google. Verify against their current guide before you rely on it.

In Google Analytics, create (or open) a GA4 property and add a data stream for your store. Then open the stream and copy its Measurement ID, the short code in the format G-XXXXXXXXXX. You will find it under Admin, then Data streams, by opening the stream and reading the ID at the top of the stream details. (Source: Set up Analytics for a website and/or app, and GA4 Measurement ID.)

Step 2: paste your Measurement ID into Vunda

In Vunda, open Integrations, choose the Google Analytics card, and turn on Enable Google Analytics. Paste the code you copied into the Measurement ID field. The field's own hint points you back to the same place in Analytics: Find this in GA4 under Admin > Data Streams > your app stream.

Then click Save. Vunda confirms the save and reminds you that analytics apply on your next app build.

Optional: add your Firebase project ID

Your GA4 property for an app is linked to a Firebase project, and the Firebase project ID (optional) field lets you record which one. Leave it blank if you are not sure; you can add it later. If you do fill it in, use only lowercase letters, numbers and hyphens. You will find the project ID in the Firebase console under Settings, then the General tab, where it is shown at the top of the page. (Source: Understand Firebase projects.)

After you connect

Publish a new version of your app from the Publish page. Once that build is live, your app reports its events (screen views, product views, add to cart and checkout) to your GA4 property. Because GA4 is wired in at build time, changing the ID later means publishing again before the change reaches shoppers' phones.

The events your app sends

The Google Analytics card on the Integrations page lists every event under Events your app sends, with when each one is sent and its parameters. The list is generated from the same catalogue the app sends from, so it is always the complete list.

• Your app sends nothing to GA4 until a shopper allows usage analytics in the app, and stops as soon as they turn it off.
• Events for a screen are sent only when your app has that screen. For example, video events such as video_start come only from clips and story videos, and select_content only from stories, journal articles and routines.
• Where Google Analytics has a recommended event, the app uses it, so GA4's standard reports work without custom setup. A product picked from a clip, a story or a routine is sent as select_item with that list, so GA4 can credit the product view and add to cart that follow.
• A group marked Not sent yet is built but switched off for every app, for example the loyalty events, which use names from GA4's games section and wait for a separate approval.

The video events use the names Google documents for web video measurement. Your app sends them as ordinary events, so they always appear in your event reports, but GA4's built-in video dimensions may not fill in for an app data stream. (Sources: GA4 recommended events, Enhanced measurement video events, and GA4 event limits.)

Connecting GA4 changes what you must declare in your store privacy forms; see Your privacy obligations.