Repository navigation
Add GA4 and Amplitude business event analytics - #4
Open
Sadturtleman wants to merge 5 commits into
Open
Sadturtleman wants to merge 5 commits into
Sadturtleman wants to merge 5 commits into
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.
Change
Business events now feed GA4 and Amplitude from one authenticated, typed event ledger. The admin dashboard shows each provider's configuration and delivery states. Redash provisioning is removed; existing internal SQL views remain intact.
Amplitude uses independent transactional delivery records, batches of ten, fixed regional endpoints, persisted payloads and insert IDs for retries, and a six-day retry cutoff. Migration 7 adds the queue without changing applied migration 6. No source code, email, inquiry body, or credentials enter analytics payloads.
Validation