Skip to content

Optimizely Data Platform - New docs #6314

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

Conversation

Romani-Ramzi
Copy link
Contributor

Proposed changes

Merge timing

Related issues (optional)

@Romani-Ramzi Romani-Ramzi requested a review from a team as a code owner March 28, 2024 23:09
@Romani-Ramzi Romani-Ramzi requested review from forstisabella and removed request for a team March 28, 2024 23:09
@forstisabella forstisabella added the new-integration Added a new source or destination label Apr 1, 2024
@forstisabella forstisabella requested a review from tcgilbert April 1, 2024 16:53
@joe-ayoub-segment joe-ayoub-segment changed the title create docs Optimizely Data Platform - New docs Apr 2, 2024
@forstisabella forstisabella self-requested a review April 2, 2024 15:35
Copy link
Contributor

@tcgilbert tcgilbert left a comment

Choose a reason for hiding this comment

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

just two changes for me. lmk if you have any questions!


Sync your Twilio Segment customer data to Optimizely Data Platform (ODP) for real-time segmentation, reporting, and to enrich customer profiles in ODP.

After you set up your Optimizely Data Platform destination, Segment syncs your customer data to ODP in near real-time.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
After you set up your Optimizely Data Platform destination, Segment syncs your customer data to ODP in near real-time.
After you set up your Optimizely Data Platform destination, Segment syncs your customer data to ODP in near real-time.
This destination is maintained by Optimizely. For any issues with the destination, [contact their Support team](mailto:support@<integration_name>.com).

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the mailto should be optimizely or segment?

Copy link
Contributor

Choose a reason for hiding this comment

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

It should be Optimizely, if you all are owning it!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

got it, I will update now

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If there is any issue or question when setting "action" in segment side, so customer still mail to optimizely and we forward to you?

Copy link
Contributor

Choose a reason for hiding this comment

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

Customers are usually well versed enough to differentiate where to send their support queries. If something is wrong within the Segment UI they will almost always reach out to us.

Additionally, our support team is always available to assist in customer queries if insight is needed from the Segment side of things. You can always reach out to [email protected] for help

Copy link
Contributor Author

Choose a reason for hiding this comment

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

perfect, we updated the required part, please check

@Romani-Ramzi
Copy link
Contributor Author

just two changes for me. lmk if you have any questions!

currently we would like to go with your suggestions, as you have more experience on what customers understand when reading through segment docs.

but our doc team will have to go through that as well, and raise what they think is good, hopefully they like your suggestions :).

@joe-ayoub-segment
Copy link
Contributor

hi @forstisabella - Romani and Alex are keen to get this doc pushed live. We're going to move the Integration to Public Beta today. Does anything else need to be changed in this PR before it can go live?

@forstisabella
Copy link
Contributor

nope! I was holding off on the merge because they mentioned that their tech writers wanted to review before we published it, but I am good to go on our side. Slack me when you move this integration into public beta and I'll merge the docs/catalog in a one-off deploy @joe-ayoub-segment

@Romani-Ramzi
Copy link
Contributor Author

@forstisabella, My mistake, I was not clear
our tech writers will review once we get word of mouth about this integration, they will get some feedback based on how easy or hard new users go through it.

from our side, we are good to go, I believe Joe already moved us to "public beta", but you may need to double check.

@forstisabella forstisabella changed the base branch from develop to optimizely-1-off April 5, 2024 15:40
@forstisabella
Copy link
Contributor

no worries, @Romani-Ramzi! I'm going to go ahead and merge this. Thanks for your collaboration on this! :)

@forstisabella forstisabella merged commit b674bf7 into segmentio:optimizely-1-off Apr 5, 2024
@Romani-Ramzi
Copy link
Contributor Author

Thanks alot @forstisabella, its was a pleasure going through all this with you and the team. :D

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-integration Added a new source or destination
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants