Skip to content
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

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

katemacfarlane
Copy link
Contributor

A guide that goes through how to send DevCycle Feature data to external destinations such as CDPs, analytics providers, etc.

A guide that goes through wow to send DevCycle Feature data to external destinations such as CDPs, analytics providers, etc.
Copy link

vercel bot commented Jun 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
devcycle-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 2, 2024 10:02pm

Copy link

@sourcery-ai sourcery-ai bot left a 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.

@cdruxerman
Copy link
Contributor

@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.

@andrewdmaclean
Copy link
Contributor

@katemacfarlane do you need any support here?

@andrewdmaclean andrewdmaclean changed the title Sending Data to External Destinations Best Practices Guide Best Practices Guide: Sending Data to External Destinations Jun 18, 2024
Object.values(features).forEach((feature) => {
variations.push(`${feature.key}:${feature.variationName}`);
})
omtr.eVarNumber = variations.join(',');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

whats omtr?

@andrewdmaclean
Copy link
Contributor

@katemacfarlane where is this sitting right now?

@andrewdmaclean andrewdmaclean marked this pull request as draft July 2, 2024 22:15
@andrewdmaclean andrewdmaclean changed the title Best Practices Guide: Sending Data to External Destinations [Draft] Best Practices Guide: Sending Data to External Destinations Jul 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

4 participants