Enhance Firebase Analytics Integration: screen() & identify() Support Parameters and Traits Mapping #174
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
This PR improves the Firebase Analytics integration by enriching both screen() and identify() tracking methods to support dynamic parameters and user traits through transformation and casting utilities.
Changes
1. screen() method enhancement
Before:
After:
Benefit: Allows sending contextual parameters along with screen view events for improved analytics segmentation and insight.
2. identify() method enhancement
Before:
After:
Benefit: Supports transformation and validation of user traits before passing them to Firebase, enabling cleaner, more structured analytics data.
Why This Matters
These enhancements make analytics events more meaningful and flexible by allowing structured data mapping. This helps downstream analysis, segmentation, and personalization in Firebase and related analytics tools.