-
Notifications
You must be signed in to change notification settings - Fork 380
Release 22.50.2 #3963
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Release 22.50.2 #3963
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.
…e-only-vs-with-clientside Clarified on GA4 sessions tracking implementation
* add commandbar destination docs commandbar destination doc commandbar destination doc commandbar destination doc * Edits and private beta actions info * edits Co-authored-by: Lucas Howard <lucas@commandbar.com> Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
Co-authored-by: stayseesong <83784848+stayseesong@users.noreply.github.com>
* Update S3 Source to be EU compatible * Update src/connections/sources/catalog/cloud-apps/amazon-s3/index.md * Update src/connections/sources/catalog/cloud-apps/amazon-s3/index.md * Update src/connections/sources/catalog/cloud-apps/amazon-s3/index.md * Update src/connections/sources/catalog/cloud-apps/amazon-s3/index.md
Removed stray backslash
catalog update
Ripe destination docs
…update Update import statement to explicitly call segment.analytics
markzegarelli
approved these changes
Dec 15, 2022
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.
Release 22.50.2