Skip to content

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

Merged
merged 3 commits into from
Apr 9, 2020
Merged

Update index.md #673

merged 3 commits into from
Apr 9, 2020

Conversation

Danny-Driscoll
Copy link
Contributor

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)

@sanscontext
Copy link
Contributor

🎉 Welcome welcome! I'm going to review this now.

Copy link
Contributor

@sanscontext sanscontext left a 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.
Copy link
Contributor

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.

@sanscontext
Copy link
Contributor

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.

@sanscontext sanscontext self-requested a review March 3, 2020 22:38
@Danny-Driscoll
Copy link
Contributor Author

Can we get this merged in @sanscontext? I sent over the signed document

@sanscontext
Copy link
Contributor

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.

@sanscontext sanscontext merged commit 0c74161 into master Apr 9, 2020
@sanscontext sanscontext deleted the optimizely-edits-march branch April 9, 2020 20:46
bot-docsteam added a commit that referenced this pull request Nov 10, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants