-
Notifications
You must be signed in to change notification settings - Fork 347
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
Setup guide for StackAdapt audience destination #7221
base: develop
Are you sure you want to change the base?
Setup guide for StackAdapt audience destination #7221
Conversation
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
@@ -3,15 +3,14 @@ title: StackAdapt Destination | |||
hide-boilerplate: true |
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.
All changes in this files are result of auto-linter on save
hide-boilerplate: true | ||
hide-dossier: true | ||
beta: true | ||
# id: 61d8859be4f795335d5c677c |
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.
Not sure what this ID should be 🤔
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.
That's OK the Docs team will fix that.
|
||
If you do not have an API key, reach out to the StackAdapt team for help. | ||
|
||
### Setting up the StackAdapt Audience destination in Segment Engage |
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.
Note for Docs team reviewer.
This Destination has 2 Actions.
- Forward Profile - this is basically a Connections Action which sends user profile data to Stackadapt. This Action can be used with Connections Source.
- Forward Audience Event - this syncs Engage Audiences to Stackadapt. This Action can only be used with Engage Audiences.
I'm thinking that might need some specific wording to explain that this Destination the different use-cases for each of these Actions, the different Sources for each (Connections Vs Engage Audience), and the different setup steps for each.
Is this something you can edit into this PR? Or would you like assistance from me or @Vanessa-SSY ?
Atlantis commands can't be run on fork pull requests. To enable, set --allow-fork-prs or, to disable this message, set --silence-fork-pr-errors |
|
Proposed changes
Adding setup guide for StackAdapt audience destination
Merge timing
Related issues (optional)