-
Notifications
You must be signed in to change notification settings - Fork 363
Update index.md #673
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
Update index.md #673
Conversation
🎉 Welcome welcome! I'm going to review this now. |
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.
One request, which is to make sure folks who might be using the old one have some guidance here on what to do. :) Checking in with the Segment dev team to confirm as well.
|
||
This limitation requires that customers include a native Optimizely snippet or implementation before their Segment snippet or implementation on pages or in mobile apps where Optimizely experiments run. | ||
Although Segment maps `track`, and in some cases `page`, events to Optimizely's `track` method, customers must implement all Optimizely decision-based methods, such as `activate`, `isFeatureEnabled`, etc., natively. Segment's API does not include methods that correspond to decision-based methods. |
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.
Is there a link to a list of these "decsion-based methods"? Might be useful for readers to review.
I confirmed with the team that we don't have anyone still using the old version who might get stranded without additional instructions, so dismissing those threads. The last item is a nice-to have, but not required. |
Can we get this merged in @sanscontext? I sent over the signed document |
Hey @Danny-Driscoll sorry for the delay - I just saw your email with the signed doc. Having to rebuild to make sure it passes CI, then we're golden! Should take about ~10 minutes all told. |
Proposed changes
Removing references to Optimizely Classic from the Optimizely Web destination docs since the product has been fully sunsetted, and it had been pushing currently-relevant content further down the page.
Also added some context to the introduction section about why Optimizely libraries need to be implemented natively vs. pulled in by segment
Related issues (optional)