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

Update index.md #5515

Closed
wants to merge 5 commits into from
Closed

Update index.md #5515

wants to merge 5 commits into from

Conversation

lookerb10
Copy link

Add source doc

Proposed changes

Merge timing

Related issues (optional)

Add source doc
@lookerb10 lookerb10 requested a review from a team as a code owner October 10, 2023 17:49
@lookerb10 lookerb10 requested review from pwseg and removed request for a team October 10, 2023 17:49
@pwseg pwseg assigned tcgilbert and unassigned tcgilbert Oct 12, 2023
@pwseg pwseg requested a review from tcgilbert October 12, 2023 16:32
## Getting Started

1. **Set Up the Segment Block**: Begin by setting up the Segment block within Alloy. This will enable Alloy to forward data to Segment efficiently. If you're unfamiliar with how to do this, the Alloy documentation or support team can guide you through the process.
Copy link
Contributor

Choose a reason for hiding this comment

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

Can you provide a link for "the Alloy documentation"?

Copy link
Author

Choose a reason for hiding this comment

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

Comment on lines 16 to 18

2. **Contact the Alloy Team**: If you prefer a hands-off approach, you can request the Alloy team to set up the Segment integration on your behalf. They possess the expertise to ensure a smooth data flow from Alloy to Segment.
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
1. **Set Up the Segment Block**: Begin by setting up the Segment block within Alloy. This will enable Alloy to forward data to Segment efficiently. If you're unfamiliar with how to do this, the Alloy documentation or support team can guide you through the process.
2. **Contact the Alloy Team**: If you prefer a hands-off approach, you can request the Alloy team to set up the Segment integration on your behalf. They possess the expertise to ensure a smooth data flow from Alloy to Segment.
1. From your workspace's [Sources catalog page](https://app.segment.com/goto-my-workspace/sources/catalog){:target="_blank”} click **Add Source**.
2. Search for "Ally Automation" in the Sources Catalog, select it, and click **Add Source**.
3. Give the source a name, for example Alloy_Prod. The name is used in the Segment interface. Click add source to save your settings.
4. Copy the Write key from the Segment UI.
5. In Alloy, **Set Up the Segment Block**: This will enable Alloy to forward data to Segment efficiently. If you're unfamiliar with how to do this, the Alloy documentation or support team can guide you through the process.
6. **Contact the Alloy Team**: If you prefer a hands-off approach, you can request the Alloy team to set up the Segment integration on your behalf. They possess the expertise to ensure a smooth data flow from Alloy to Segment.

Copy link
Author

Choose a reason for hiding this comment

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

looks to be a typo in Alloy missing the o

2. **Contact the Alloy Team**: If you prefer a hands-off approach, you can request the Alloy team to set up the Segment integration on your behalf. They possess the expertise to ensure a smooth data flow from Alloy to Segment.

## Types of Calls to Segment
Copy link
Contributor

Choose a reason for hiding this comment

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

Are the events you send to Segment configured by the user? In other words, are there no events that alloy sends to segment b default?

If there are default events, you will need to create a table like so listing out the events that are sent.

Copy link
Author

Choose a reason for hiding this comment

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

There are no default events, the user must select which ones.


Using Segment, the interaction data captured can be sent directly to marketing, product, and analytics tools. The integration with Alloy means that this data can also be utilized to drive automation, ensuring consistent and personalized user interactions across all touchpoints.

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
This source is maintained by Alloy. For any issues with the source, [Contact the Alloy Support team](mailto:<add support email>)

Please provide a mailing address or link to support page^

Copy link
Author

Choose a reason for hiding this comment

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

@tcgilbert
Copy link
Contributor

Created new PR for edits: #5555

@tcgilbert tcgilbert closed this Oct 18, 2023
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