-
Notifications
You must be signed in to change notification settings - Fork 367
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
Optimizely Data Platform - New docs #6314
Conversation
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Outdated
Show resolved
Hide resolved
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
…latform/index.md Co-authored-by: forstisabella <[email protected]>
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.
just two changes for me. lmk if you have any questions!
src/connections/destinations/catalog/actions-optimizely-data-platform/index.md
Show resolved
Hide resolved
|
||
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. |
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.
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). |
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.
the mailto should be optimizely or segment?
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.
It should be Optimizely, if you all are owning it!
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.
got it, I will update 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.
If there is any issue or question when setting "action" in segment side, so customer still mail to optimizely and we forward to you?
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.
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
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.
perfect, we updated the required part, please check
…latform/index.md Co-authored-by: Thomas Gilbert <[email protected]>
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 :). |
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? |
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 |
@forstisabella, My mistake, I was not clear from our side, we are good to go, I believe Joe already moved us to "public beta", but you may need to double check. |
no worries, @Romani-Ramzi! I'm going to go ahead and merge this. Thanks for your collaboration on this! :) |
Thanks alot @forstisabella, its was a pleasure going through all this with you and the team. :D |
Proposed changes
Merge timing
Related issues (optional)