Google Analytics 4 integration in Zweigen
The Google Analytics 4 integration transfers your GA4 data automatically into Zweigen. Authentication uses OAuth2.
The connection runs in this order:
- Authorize your Google account through OAuth in Zweigen.
- Select the required GA4 property.
- Background processing starts only after you select the property.
If a dashboard widget says that a GA4 property must be selected, your Google account is not necessarily disconnected. Open Integrations, choose the required property for Google Analytics 4, and wait until data preparation is complete. Only messages such as Update permissions mean that you need to authorize Google again.
Prerequisites
- You have access to the relevant GA4 property.
- You authorize with the account that has the required permissions.
These metrics and dimensions are currently available in the Google Analytics 4 integration in Zweigen
| Category | Metrics | Show all |
|---|---|---|
| Users | 14 | |
| Behavior | 14 | |
| Events | 7 | |
| Advertising (non-commerce) | 8 | |
| E-commerce advertising | 10 | |
| E-commerce | 14 | |
| E-commerce revenue | 8 | |
| E-commerce items | 11 | |
| Total | 86 |
| Category | Dimensions | Show all |
|---|---|---|
| Time | 27 | |
| Traffic | 54 | |
| Content | 24 | |
| Devices & Tech | 14 | |
| Geography | 7 | |
| Audiences (Demographics/Interests) | 8 | |
| App & Screens | 8 | |
| E‑commerce | 23 | |
| Events (details) | 11 | |
| Internal/Technical | 2 | |
| Google Ads | 33 | |
| Search Ads 360 | 45 | |
| Display & Video 360 | 54 | |
| Campaign Manager 360 | 63 | |
| Total | 373 |
How to use events and key events correctly
Events capture user behavior, for example page_view, scroll, or form_submit. Key Events mark the events that matter for your business, such as lead submission, purchase, or appointment booking. First define 3 to 5 business-relevant Key Events, verify their triggering in GA4 through real-time and debug views, and then begin the analysis in Zweigen with keyEvents and sessionKeyEventRate.
Recommended starter metrics and why they matter
Use only a few readable core metrics at the beginning. Expand later depending on the question.
| Metric | What it describes | Recommendation for use |
|---|---|---|
| Active users | Number of active users | How is your reach developing? |
| Sessions | Number of started sessions | Compare with active users to understand depth of use |
| Engaged sessions | How many sessions include real interaction | Use it as an early indicator for content quality |
| Engagement rate | Share of engaged sessions | If it drops while users grow, page-fit is often off |
| Key Events | How many important goals are reached | Use this to see whether traffic turns into outcomes |
| Key Event rate per session | Shows efficiency per session | Compare channels by quality, not only by volume |
| Total revenue | The monetary result | Direct outcome evaluation |
| Average revenue per user | Average result per user | Helps evaluate traffic quality |
Recommended dimensions for root-cause analysis
These dimensions help you narrow down drivers and causes in a structured way.
| Dimension | Use in analysis |
|---|---|
| Session default channel group | Separate development by channel |
| Session source / first user source | Show concrete origin of sessions and first contacts |
| Session medium / first user medium | Evaluate traffic quality by medium type |
| Session manual campaign name | Connect outcome data with campaign steering |
| Landing page / landing page with query string | Analyze behavior by entry pages |
| Device category | Check differences by device type |
| Country / region / city | Supports geographic prioritization in campaigns |
Related topics
- Data Connections Overview - Compare all connection types
- Connection Status - What to do when connections fail
- Data Management - Manage integrations, data sources, and imports
All Data. One system.
Contact
We are happy to help and advise. Send us an email at hi@zweigen.cloud or visit our socials.