Reach & Retarget for Google Analytics 4
Reach & Retarget allows you to connect your Google Analytics 4 account. With Wistia analytics in Google, you can “retarget” audiences based on media engagement.
To connect to Google Analytics 4 (GA4), head to Account > Integrations. On the Integrations page, scroll down to the “Reach & Retarget Integrations” section.
Once you click “Connect,” you’ll be prompted to log into Google and select your Google account that has access to your GA4 instance.
Once authenticated, you will see a form with three fields to complete:
- Analytics Account: select from your GA4 compatible Analytics Accounts in the dropdown menu.
- Web Property: select a GA4 compatible Web Property from the dropdown menu.
- Web Data Stream: there is one data stream for each Web Property.
All three must be set up in Google Analytics prior to setting up the integration with Wistia. You can find resources on setting these up from Google here.
Once connected, the integration will be listed in the “Configured” section of your Integrations page.
Once the integration is connected, Wistia will start to send event data to the GA4 account that you’ve selected. The following events will be tracked:
- wistia_50_percent_played (and 25, 75, 95)
- wistia_clicked_link_https_wistia_com (the URL will be what you define)
- wistia_eventbrite_conversion_12345678 (event id)
Event data in GA4 comes with a few different properties - Event Name and event parameters (which contain Event Category, Event Label). Event Names are the events that occurred and Labels are always the name of the media where the action occurred.
If a media is embedded by itself as a standalone video embed, its events will have a category of “Video." If it’s embedded as a standalone audio embed, the category will be “Audio.”
If the media being played is part of a Channel embed, the category will be “Channel: [Name].” This will make it easier for you to attribute and measure activity to specific Channels embedded on your website, as well as differentiate where events are coming from.
Navigate to Reports > Engagement > Events. This page shows all of your collected events. It includes:
- Event name
- Event count
- Total users
- Event count per user
Depending on how many types of events you have in your installation, you may see a lot of things here. A standalone embed will use the “Video” or “Audio” type, and Channel embeds will have the “Channel” type.
Here, you’ll see a list of the events available to you, which is what we push using the categories we covered earlier. There are some defaults included, but this is where your custom events would also appear if you configured any. The default events are: wistia_play, wistia_50_percent_played (and 25, 75, 95) and wistia_conversion.
In order to create and retarget audiences through the GA4 integration, you’ll need to create audiences directly within GA4. This is because Google does not currently have an API for audience data in GA4.
Once audiences are manually set up in Google, this data can be passed from Wistia. You can find steps on how to manually set up audiences in GA4 here. To get started, head to Configure > Audiences.
Existing audiences in Universal Analytics are not compatible with GA4. You will need to set up audiences in GA4.
Yes! Wistia will send events to each platform when both integrations are enabled. In fact, Google recommends this.
While the Wistia integration with GA4 does not currently have this option, you will still need to link your GA4 account to your Google Ads account in order to use GA4 audiences to retarget in Google Ads. The instructions on how to do so can be found from Google here.
At this time, we don’t have a solution for converting a UA web property to GA4. This requires manually mapping each event label, category, and action. You can read more about mapping web properties here.
You need to have two Event scoped Custom Dimensions available in order to connect the integration (the maximum number you can have is 50). Remove two Custom Dimensions in order to connect the integration.