Google Analytics 4
Connect GA4 so Meerkats has sessions, traffic sources, landing pages, events and conversions for your site.
The GA4 connection imports sessions, users, traffic sources, landing pages, events and conversions from the properties you choose. It fills the gap between ad clicks and orders: how much traffic each campaign sent, what it did on site, and where it dropped off.
| How it connects | Sign in and approve |
| Reads | Sessions and users, Events and conversions, Ecommerce events, Property settings |
| Can change | Create an audience in GA4; Create a custom dimension or key event |
| Refresh | On your plan's schedule, plus Resync anytime |
Before you start#
- A Google account with Viewer access or higher on the GA4 property.
- The property ID (Admin › Property settings).
Permissions#
Google Analytics 4 asks you to approve these permissions. Each one is listed with why Meerkats needs it.
| Permission | Why Meerkats needs it |
|---|---|
https://www.googleapis.com/auth/analytics.readonly | Read reports and property settings |
https://www.googleapis.com/auth/analytics.edit | Create audiences and custom definitions when you approve (optional) |
Connect#
1. Connect GA4#
- Open Integrations
In the sidebar, select Integrations, find GA4 and select Connect.
- Sign in with Google and allow access
Pick the Google account with access to the property.
- Choose properties
Tick the GA4 properties to sync, then run Resync in Data Hub › Bronze Layer.
What syncs#
| Google Analytics 4 | In Meerkats |
|---|---|
| Sessions and users | By day, with source, medium, campaign, landing page, device, country |
| Events and conversions | Event counts and key events (conversions) with parameters |
| Ecommerce events | view_item, add_to_cart, begin_checkout, purchase with item and value |
| Property settings | Time zone, currency, key events, custom dimensions |
Raw data lands in Data Hub › Bronze Layer. Modelled tables, with metrics defined once, are in Data Hub › Gold Layer. Every number in a report or an agent’s answer comes from a query on these tables, never from the model’s own arithmetic.
Metrics you get#
The metrics people ask for most, named as Google Analytics 4 names them. The full list, with each definition, is in the metric catalog.
SessionsUsersNew usersEngagement rateSessions by source and mediumLanding page conversion rateAdd-to-cart rateCheckout ratePurchasesRevenue
How often it syncs#
Meerkats syncs on your plan's schedule: daily on Free, hourly on the $49 plan, every 30 minutes on $149 and every 15 minutes on $399. You can run a sync at any time with Resync in Data Hub › Bronze Layer.
- GA4 data is final after about 48 hours; earlier numbers can shift. Each sync re-imports the last three days.
- GA4 uses data-driven attribution by default; corrected ROAS uses your orders instead.
What Meerkats can change#
In every connected tool, Meerkats can create, read, update and delete records, within the permissions you grant and the permissions the tool allows. These are the changes it proposes for Google Analytics 4, and the limit that applies to each.
| Change | Limit |
|---|---|
| Create an audience in GA4 | Proposed for approval; needs the edit scope |
| Create a custom dimension or key event | Proposed for approval; needs the edit scope |
How every change is governed
Every change starts as a proposal in your Inbox. Nothing changes in the connected tool until a person approves it, unless you set that rule to act on its own.
Before it runs an approved change, Meerkats re-reads the live value. If the value moved since the proposal, it asks again instead of acting on stale data.
Meerkats stores the value it replaced, so every change can be undone from Agents run history.
Anything Meerkats creates starts paused. Switching it on is a second, separate approval.
Troubleshooting#
The property isn't listed
Your Google account needs at least Viewer on the property. Ask the GA4 admin.
Sessions don't match ad clicks
Clicks and sessions never match exactly: bounced, blocked and duplicate clicks don't start sessions. Treat a gap over 30% as a tracking problem.