Release - #10
Merged
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
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 PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@stackmade/gtm-as-code@0.8.4
Patch Changes
9b75e49:
gtm-code verifyandgtm-code doctor, implementing ROADMAP.md milestone 0.8.gtm-code verify [--days <n>]queries the GA4 Data API for every declared event over the trailingN days (default 28) and reports which ones were never received — the check
plan/driftcan'tgive you, since config can match GTM/GA4 exactly while the site never actually fires an event. For
a received event it also checks whether each
dimension: trueparameter was ever recorded with avalue; parameters not registered as a custom dimension are reported as unverifiable rather than
silently skipped, since the Data API has no way to query an arbitrary event parameter.
gtm-code doctorchecks config validity, credentials, GTM/GA4 API reachability, and GA4 Data APIquota headroom, explaining what's missing instead of
plan/applyfailing mid-run with a rawGoogle error.
Both are live-verified against a real GA4 property.
doctor's quota check reads a realtokensPerDayfigure on a standard non-360 property, and it tells "API not enabled" apart from"permission denied", which Google reports under the same
PERMISSION_DENIEDstatus. One caveatverifynow states in its own output: the Data API's dimension schema is eventually consistent, soa parameter can be reported as not registered for a few minutes after
applycreated its customdimension.