-
Notifications
You must be signed in to change notification settings - Fork 974
Integrate experiments with firebase analytics internal #9278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: web-experiment
Are you sure you want to change the base?
Conversation
|
Size Report 1Affected Products
Test Logs |
f4f7ce2
to
b210bbb
Compare
b210bbb
to
66b104b
Compare
Size Analysis Report 1This report is too large (2,214,516 characters) to be displayed here in a GitHub comment. Please use the below link to see the full report on Google Cloud Storage.Test Logs |
experimentId: string, | ||
variantId: string | null | ||
): Promise<void> { | ||
const analytics = await this.analyticsProvider.get(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there cases where the provider doesn't return a valid value which we should handle?
const customProperty = { | ||
[experimentId]: variantId | ||
}; | ||
analytics.setUserProperties({ properties: customProperty }); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this method allow setting multiple user properties in one shot? I'm wondering if it might be a better idea to instead set all properties in one call given each such call would hit their public endpoint over the network?
Maybe we could carve out setUserPropertiesInAnalytics
as a separate method where all properties updates could be bundled?
experimentId: string | ||
): Promise<void> { | ||
void this.addExperimentToAnalytics(experimentId, null); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This function seems redundant to me. If we're reusing addExperimentToAnalytics
, then we could directly call it in removeInactiveExperiments
instead.
This change is part of the feature to support Web Experiments in Remote Config. The change is split into 3 PRs where:
This is 3/3 mentioned above
Design doc (internal): go/experiments-web