Moved Tinybird tracker token to the analytics service#13
Merged
Conversation
jloh
approved these changes
Jul 9, 2025
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.
This moves the
TINYBIRD_TRACKER_TOKENenvironment variable out of Ghost's configuration, and passes it directly to the analytics service.The Tinybird
trackertoken grants write access to theanalytics_eventsdatasource in Tinybird. Before we had the analytics service sitting between Ghost and Tinybird, Ghost needed to send this token with each tracking event request, or else Tinybird would return a 401 error. This isn't very secure, since thetrackertoken is exposed in plain text in the network tab whenever visiting a Ghost site's frontend.Now that we have the analytics service sitting between Ghost and Tinybird, we can add the token to each request there, which means Ghost no longer needs to pass the token with each request, and in fact doesn't need to use the
trackertoken at all.