[CSO-377] FAQs - Expand analytics section to clarify dashboard scope#543
Merged
Naledi-Civic merged 4 commits intomainfrom Feb 25, 2026
Merged
[CSO-377] FAQs - Expand analytics section to clarify dashboard scope#543Naledi-Civic merged 4 commits intomainfrom
Naledi-Civic merged 4 commits intomainfrom
Conversation
kevinhcolgan
approved these changes
Feb 25, 2026
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
2 participants
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.
Summary
Expands the existing "How can I monitor usage for Civic Auth?" FAQ entry to clearly describe what analytics Civic Auth provides and what it does not.
Changes
overview/faqs.mdx: Expanded "How can I monitor usage for Civic Auth?" accordion to list available events (login, wallet creation) and explicitly note that custom in-app analytics are not providedJira
CSO-377
Context
The support bot was conflating Civic's internal analytics tooling with what is exposed to customers. This update clarifies the scope and directs developers to third-party solutions for custom analytics.