Connect Google Analytics 4 (GA4) to Rubii to report on the website traffic, engagement and conversions your campaigns drive, next to your media data in Tracker and dashboards. You connect GA4 once in Data Sources, then map a GA4 property to each placement you want to report on.
What you can report on
Rubii imports these GA4 figures for the properties you connect:
- Traffic and engagement – Users, New Users, Sessions, Engaged Sessions, Bounce Rate, Session Duration, Avg Session Duration and Pages Per Session.
- Ecommerce – Transactions, Revenue, Items Purchased, Item Revenue, and GA ROAS (as a percentage and as a value).
- Conversions – the conversion (key) events you map as goals, with their completions, values and conversion rate.
Each traffic metric comes in two versions:
- Placement metrics (for example Sessions) count only the traffic that matches the traffic sources mapped to that placement.
- Overall metrics (for example Overall Sessions) show the property's total, whatever the traffic source.
See Placement metrics and Overall metrics for why the two can differ.
Connect GA4
- In Rubii, go to Data Sources.
- Click the Google Analytics 4 card.
- Sign in with the Google account that has access to your GA4 properties, and grant Rubii access.
- Choose which accounts and properties to import.
Rubii starts pulling data straight after you connect, including the last 30 days of history. After that, GA4 data refreshes every morning.
Note: Google says GA4 can take 24–48 hours to finish processing a day's data, so the most recent days may still change.
Link the GA4 account to your advertiser
- Go to Advertisers and open the advertiser.
- On the Mapping tab, click the GA4 account in the list on the left to link it.
Until the advertiser is linked, no GA4 properties appear when you map a placement.
Map GA4 to a placement
GA4 is mapped placement by placement. Mapping one placement doesn't carry over to others in the campaign, or to new placements you add later, so map each one you want GA4 figures for.
- In Tracker, click the mapping icon on the placement's row. The campaign must be approved before mapping opens.
- Open the ANALYTICS tab, then GA PROPERTY & VIEW, and map the GA4 property. In GA4 the property acts as the view.
- Open GA TRAFFIC SOURCES and add the traffic sources that belong to this placement: click Add Rows, or Bulk Add to paste many at once. See Traffic sources.
- To report conversions, open GOALS and map the GA4 conversion events for this placement. See Goals.
Tip: To use the same property or goals on every placement in the campaign, use Apply to All on the mapping screen.
Traffic sources
A traffic source tells Rubii which GA4 traffic belongs to a placement. Each one can use any combination of these five fields. Fill in only the ones that match how the campaign was tagged, and leave the rest blank:
| Field | Matches | Example |
|---|---|---|
| Source (utm_source) | Where the traffic came from | google, facebook, newsletter |
| Medium (utm_medium) | The type of traffic | cpc, social, email |
| Campaign (utm_campaign) | The marketing campaign | spring_sale |
| Content (utm_content) | Which link or ad version was clicked | header_link, footer_ad |
| Term (utm_term) | The paid search keyword | running_shoes |
Rubii matches on the values GA4 recorded, and the matching isn't case-sensitive. You don't always need UTM tags. For example, Google Ads traffic with auto-tagging turned on arrives in GA4 as source google, medium cpc, with the Google Ads campaign name as the campaign.
Important: If a placement has a GA4 property mapped but no traffic sources, its placement metrics (Sessions, Transactions and so on) show 0. The Overall metrics still show the property's totals.
Rubii can't attribute traffic by landing page or page URL. Traffic sources only use source, medium, campaign, content and term.
Overlapping traffic sources
The same GA4 traffic can't be counted on two placements. When placements share a GA4 property and their dates overlap, Rubii blocks a traffic source that is the same as, or broader than, one already used on another placement. For example, source = google clashes with source = google, medium = cpc. The error tells you which placement already uses it.
Two traffic sources don't clash if they have different values in the same field, for example source = google and source = bing.
Search placements are mapped automatically
When you map Google Ads, Microsoft Advertising (Bing) or SA360 campaigns to a Search placement, Rubii automatically creates a traffic source from each campaign's name. For example, a Google Ads campaign called "Spring Sale" creates source = google, campaign = Spring Sale.
Note: If two Search placements share a GA4 property, have overlapping dates, and are mapped to platform campaigns with the same name, their automatic traffic sources are identical and clash. Only one of those placements can then be mapped to that GA4 property. To avoid this, give the platform campaigns different names.
Goals
Goals connect your GA4 conversion (key) events to a placement.
- Map a GA4 property to the placement first. Only conversion events from mapped properties are listed.
- You can mark goals as primary. When a placement has several goals, only the primary ones count toward Overall GA Conversions.
- GA4 conversions are reported separately from each ad platform's own conversions. Marking a GA4 goal primary doesn't change or replace a platform's conversions.
- If you rename an event in GA4, check that it's still marked as a key event. If it isn't, its conversions drop to zero in Rubii and in GA4.
To remove a mapped property, first unmap the goals that use it.
Placement metrics and Overall metrics
- Placement metrics (Sessions, Users, Revenue …) count only traffic that matches the placement's traffic sources.
- Overall metrics (Overall Sessions, Overall Users, Overall Revenue …) are the whole property's totals. They're reported at campaign level.
If your Rubii figures don't match GA4, first check which of the two you're using.
Note: Overall metrics are calculated separately for each campaign. If several campaigns use the same GA4 property and you report on them together, the Overall figures are added up across those campaigns, so the property's traffic is counted more than once. If a placement has more than one GA4 property mapped, its figures combine all of them. There's no filter for a single property in reports.
GA4 audience breakdowns
You can break down GA4 data by Age (GA4), Gender (GA4), Region (GA4), Country (GA4), Device (GA4), Browser (GA4) and OS (GA4), and by GA4 channel groups (Default Channel Group, Primary Channel Group, and their session and first-user versions). These breakdowns have some limits:
- They only work with the Month date type.
- They only work with Overall metrics.
- They can only be combined with campaign-level dimensions (Campaign, IO Number).
- They can't be combined with ad platform audience breakdowns (for example Facebook age or gender).
- Channel groups can't be used with Overall New Users, Overall Session Duration, Overall Pages per Session, Overall Avg Session Duration, Overall Transactions, Overall Items Purchased or Overall Item Revenue.
View your GA4 data
- Tracker – open a placement and switch to Analytics using the Platform / Adserver / Analytics selector.
- Dashboards – go to Reports → Dashboards, open a dashboard and add widgets that use GA4 metrics.