Clarified on GA4 sessions tracking implementation #3943
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Proposed Changes Dividing the implementation information into 2 sub-headings: 1) tracking purely server side and it's limitations (not all user dimensions are available) 2) using gtag.js and GA4 destination (client & server-side). # Merge timing No rush! # Related issues (optional) Previous version implied that a pure server side implementation was not possible and you could only get sessions tracking/reports with gtag.js on the client side. A Slack thread with Kiara (https://twilio.slack.com/archives/CQ1F92KUG/p1670813658588399) clarified that it is possible to do a pure server side implementation of GA4 with the caveat that the customer will not have all sessions data available in reports. The hope is that the proposed changes will make the differentiation clearer.
|
This is awesome - very well written @050phy. Thank you! Looks good from my end. Will approve and let the docs team review grammar/style as well. Thanks again! |
kdaswani
approved these changes
Dec 13, 2022
stayseesong
approved these changes
Dec 14, 2022
stayseesong
added
the
content-update
stayseesong
deleted the
050phy-ga4-sessions-serverside-only-vs-with-clientside
branch
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Dividing the implementation information into 2 sub-headings:
Merge timing
No rush!
Related issues (optional)
Previous version implied that a pure server side implementation was not possible and you could only get sessions tracking/reports with gtag.js on the client side.
A Slack thread with Kiara (https://twilio.slack.com/archives/CQ1F92KUG/p1670813658588399) clarified that it is possible to do a pure server side implementation of GA4 with the caveat that the customer will not have all sessions data available in reports. The hope is that the proposed changes will make the differentiation clearer.