-
Notifications
You must be signed in to change notification settings - Fork 12
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
[Draft] Best Practices Guide: Sending Data to External Destinations #694
base: main
Are you sure you want to change the base?
[Draft] Best Practices Guide: Sending Data to External Destinations #694
Conversation
A guide that goes through wow to send DevCycle Feature data to external destinations such as CDPs, analytics providers, etc.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
We have skipped reviewing this pull request. We don't currently review documentation changes - Let us know if you'd like us to change this.
@katemacfarlane what other details are you planning to add? I think there are some areas you can expand and some you can simplify. For example I don't think you need to show all the different languages for the same action, but I would show different options like setting experiments as a user property instead of as an event. |
@katemacfarlane do you need any support here? |
Object.values(features).forEach((feature) => { | ||
variations.push(`${feature.key}:${feature.variationName}`); | ||
}) | ||
omtr.eVarNumber = variations.join(','); |
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.
whats omtr?
@katemacfarlane where is this sitting right now? |
A guide that goes through how to send DevCycle Feature data to external destinations such as CDPs, analytics providers, etc.