Repository navigation
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
This branch was successfully deployed
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
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.
Why
docs.tablepro.app loads GA4 through the Mintlify integration with no consent step. One page view sets
_gaand_ga_GQYNPKSK83on.tablepro.app, the parent domain. tablepro.app's privacy policy says Google Analytics cookies are not set until the reader allows them, so that sentence was false for anyone who had opened the docs.Change
ga4integration fromdocs/docs.json.Verified
mint validatepasses. A headless load of the live docs before this change shows the two cookies and requests to googletagmanager.com, analytics.google.com and stats.g.doubleclick.net; nothing else on the page sets a cookie.Not in this PR