GA4 Traffic Source Attribution for Reserve with Google Sessions
When guests book through Reserve with Google (RwG), their Webstore sessions originate outside your owned channels β making accurate attribution in Google Analytics 4 (GA4) essential for understanding how RwG drives bookings. This article explains how to configure Google Tag Manager (GTM) dataLayer variables and GA4 event parameters so that RwG-originated sessions appear correctly in GA4 Acquisition reports.
Audience: Marketing administrators and analytics managers who configure GTM and GA4 for the Webstore.
On this page
- Before you begin
- How RwG session attribution works
- Steps
- Worked example
- Tips
- Troubleshooting
- Related articles
Before you begin
- Your organization must be enrolled in the Reserve with Google integration. RwG enrollment requires involvement from your Zenoti account team β it is not a self-service admin toggle.
- GTM must already be installed on your Webstore. Confirm that your GTM container ID is configured at Configuration > Online booking > Online booking settings > Webstore V2.
- Your GA4 property must be linked to the same GTM container.
- You need edit access to your GTM workspace and GA4 property.
- Confirm that your GA4 Measurement ID is set at the org level in the Webstore V2 template settings.
Note: Changes to Webstore template settings may take up to 30 minutes to propagate due to cache invalidation. Allow for this delay when testing configuration changes.
How RwG session attribution works
When a guest arrives at the Webstore from a Reserve with Google booking surface, the Webstore pushes three values to the GTM dataLayer on every page load of that session:
| dataLayer key | Value pushed | Purpose |
|---|---|---|
ws_booking_source |
booknow |
Identifies the booking source as RwG |
ws_booking_medium |
google |
Identifies the traffic medium |
ws_bookNow |
true |
Boolean flag confirming an active RwG session |
These values mirror the role that utm_source and utm_medium query parameters play for standard campaign traffic. By reading them in GTM and forwarding them to GA4 as Source/Medium dimensions, you ensure that GA4's Traffic Acquisition, User Acquisition, and Source/Medium reports attribute RwG sessions correctly β and that GA4's Default Channel Group rules apply automatically for the booknow / google source/medium pair.
The dataLayer push happens automatically for every RwG-originated session. No additional Webstore configuration is required to trigger the push itself. Your task is to configure GTM to read those values and pass them to GA4.
Steps
Step 1 β Create GTM dataLayer variables
Create three dataLayer variable definitions in GTM β one for each key the Webstore pushes.
- Sign in to your GTM workspace and open the container linked to your Webstore.
- In the left navigation, select Variables, then click New under User-Defined Variables.
- Configure the first variable:
- Variable Type β Select Data Layer Variable.
- Data Layer Variable Name β Enter
ws_booking_source. - Name (the GTM variable name) β Enter a descriptive label such as
DLV - ws_booking_source. - Click Save.
- Repeat step 3 for the second variable:
- Data Layer Variable Name β Enter
ws_booking_medium. - Name β Enter
DLV - ws_booking_medium. - Click Save.
- Data Layer Variable Name β Enter
- Repeat step 3 for the third variable:
- Data Layer Variable Name β Enter
ws_bookNow. - Name β Enter
DLV - ws_bookNow. - Click Save.
- Data Layer Variable Name β Enter
You now have three GTM variables that will read the RwG attribution values from the dataLayer on every Webstore page load.
Step 2 β Map variables to GA4 event parameters
Configure a GTM tag that sends the RwG source and medium values to GA4 as session-scoped traffic source parameters, populating the same Source/Medium dimension that UTM parameters would populate.
In GTM, select Tags, then click New.
Click Tag Configuration and select Google Analytics: GA4 Event.
Configure the tag:
- Measurement ID β Enter your GA4 Measurement ID, or reference the GTM variable you use for it.
- Event Name β Enter
page_view(or the event name your GA4 configuration uses for session attribution).
Under Event Parameters, add the following parameters:
Parameter name Value traffic_source{{DLV - ws_booking_source}}traffic_medium{{DLV - ws_booking_medium}}rwg_session{{DLV - ws_bookNow}}Note: To populate GA4's standard Source/Medium dimension β the same dimension populated by
utm_sourceandutm_mediumβ use thesession_traffic_source_detailevent parameter approach, or configure a GA4 configuration tag that setstraffic_sourceandtraffic_mediumat the session level. Consult the GA4 documentation for your property's session-scoping method, as the exact parameter names depend on your GA4 configuration tag setup.Under Triggering, click the trigger selector and choose All Pages (or the trigger you use for GA4 page-view events).
Name the tag (for example,
GA4 - RwG Attribution) and click Save.Click Submit in GTM to publish the container changes.
Important: Publish your GTM container before testing. Unpublished changes are visible only in GTM Preview mode and do not affect live Webstore sessions.
Step 3 β Verify attribution in GA4 Acquisition reports
After publishing the GTM container, verify that RwG-originated sessions appear correctly in GA4.
- Use GTM's Preview mode to simulate a Webstore session originating from an RwG link. Confirm that the dataLayer shows
ws_booking_source: "booknow",ws_booking_medium: "google", andws_bookNow: trueon page load. - In GA4, navigate to Reports > Acquisition > Traffic Acquisition.
- Filter or search for the source/medium pair
booknow / google. - Confirm that sessions attributed to this source/medium appear in the report.
- Check the Default Channel Group column. GA4 applies its Default Channel Group rules automatically based on the source and medium values. Verify that RwG sessions are grouped as expected (typically under Organic Search or a custom channel group you have defined for RwG traffic).
Tip: Allow 24β48 hours after publishing for GA4 to accumulate sufficient session data for the source/medium pair to appear in Acquisition reports. Real-time reports in GA4 can confirm that events are arriving sooner.
Worked example
Example: Your center runs a promotion and a guest discovers your business through Google Search and taps the Book Now button on your Google Business Profile via Reserve with Google. The guest lands on your Webstore. On that page load, the Webstore pushes
ws_booking_source: "booknow",ws_booking_medium: "google", andws_bookNow: trueto the GTM dataLayer.Your GTM tag reads
DLV - ws_booking_source(value:booknow) andDLV - ws_booking_medium(value:In the User Acquisition report, you can filter by First user source/medium = booknow / google to identify guests whose first-ever session came through RwG, giving you a clear picture of RwG's contribution to new guest acquisition.
Tips
- Test with GTM Preview before publishing. Use GTM's built-in Preview and Debug mode to confirm that all three dataLayer variables (
ws_booking_source,ws_booking_medium,ws_bookNow) are populated correctly before submitting the container to production. - Use a custom channel group for RwG in GA4. GA4's Default Channel Group rules may classify
booknow / googledifferently depending on your property configuration. Create a custom channel group in GA4 (Admin > Data display > Channel groups) with a rule matchingSource exactly matches booknowandMedium exactly matches googleto ensure consistent reporting across all Acquisition reports. - Coordinate with your Zenoti account team on RwG enrollment timing. The dataLayer push only fires for sessions that originate from an active RwG booking surface. If your RwG integration is not yet live, the variables will be undefined and no attribution data will flow to GA4.
- Avoid duplicating UTM parameters for RwG traffic. The
ws_booking_sourceandws_booking_mediumdataLayer values serve the same attribution purpose as UTM parameters for RwG sessions. Adding manual UTM parameters to RwG booking links may cause double-attribution or override the dataLayer values depending on your GA4 session-source precedence rules. - Review GA4 session-source precedence rules. GA4 gives precedence to UTM parameters over other session signals. If your RwG booking links include UTM parameters, those will take precedence over the dataLayer values. Remove UTM parameters from RwG links if you want the dataLayer attribution to apply.
Troubleshooting
The dataLayer variables are undefined in GTM Preview.
The Webstore only pushes ws_booking_source, ws_booking_medium, and ws_bookNow when the session originates from an active Reserve with Google booking surface. If you are testing by navigating directly to the Webstore URL, the values will not be present. To test, use an RwG booking link provided by your Zenoti account team, or confirm with your account team that your RwG integration is live and the booking surface is active.
GA4 Acquisition reports show no data for booknow / google.
First, confirm that your GTM container was published after you created the dataLayer variables and the GA4 tag. Unpublished GTM changes do not affect live sessions. Second, allow 24β48 hours for GA4 to process session data β the source/medium pair will not appear in standard Acquisition reports until GA4 has processed at least one session. Use GA4 Realtime reports to confirm events are arriving immediately after publishing.
The Default Channel Group in GA4 does not classify RwG sessions as expected.
GA4 evaluates Default Channel Group rules in order. If an earlier rule matches medium = google (for example, a broad Organic Search rule), RwG sessions may be grouped there instead of a custom RwG group. Review your channel group rule order in GA4 (Admin > Data display > Channel groups) and move your RwG-specific rule above any broader rules that could match the same source/medium pair.
The GA4 tag fires but Source/Medium shows (not set) for RwG sessions.
This typically means the traffic source parameters are not being applied at the session level. Verify that your GA4 configuration tag (not the event tag alone) is set to read the DLV - ws_booking_source and DLV - ws_booking_medium variables, and that the tag fires on the first page load of the session. Session-level source attribution in GA4 is determined by the first event in the session β if the configuration tag fires after the first page-view event, the source may not be captured.
Webstore template changes are not reflected in the live Webstore.
Template configuration changes at Configuration > Online booking > Online booking settings > Webstore V2 take up to 30 minutes to propagate. Wait for the cache to clear before re-testing.