|
| 1 | +title: [integration_name] Destination |
| 2 | +(delete after reading) This template is meant for Actions-based destinations that do not have an existing Classic or non-Actions-based version. For Actions Destinations that are a new version of a classic destination, see the doc-template-update.md template. |
| 3 | + |
| 4 | +(delete after reading) In the section above, edit the title field. For example, Slack (Actions) Destination |
| 5 | + |
| 6 | +{% include content/plan-grid.md name="actions" %} |
| 7 | + |
| 8 | +(delete after reading) Include a 1-2 sentence introduction to your company and the value it provides to customers - updating the name and hyperlink. Please leave the utm string unchanged. |
| 9 | + |
| 10 | +<integration_name> provides self-serve predictive analytics for growth marketers, leveraging machine learning to automate audience insights and recommendations. |
| 11 | + |
| 12 | +(delete after reading) Update your company name and support email address. |
| 13 | + |
| 14 | +This destination is maintained by <integration_name>. For any issues with the destination, contact their Support team. |
| 15 | + |
| 16 | +(delete after reading) This include describes the requirement of A.js 2.0 or higher for Actions compatibility, and is required if your destination has a web component. |
| 17 | + |
| 18 | +{% include content/ajs-upgrade.md %} |
| 19 | + |
| 20 | +(delete after reading) The section below explains how to enable and configure the destination. Include any configuration steps not captured below. For example, obtaining an API key from your platform and any configuration steps required to connect to the destination. |
| 21 | + |
| 22 | +Getting started |
| 23 | +From the Segment web app, click Catalog, then click Destinations. |
| 24 | +Find the Destinations Actions item in the left navigation, and click it. |
| 25 | +Click Configure <desintation_name>. |
| 26 | +Select an existing Source to connect to <destination_name> (Actions). |
| 27 | +(delete after reading) The line below renders a table of connection settings (if applicable), Pre-built Mappings, and available actions. |
| 28 | + |
| 29 | +{% include components/actions-fields.html %} |
| 30 | + |
| 31 | +(delete after reading) Additional Context |
| 32 | + |
| 33 | +Include additional information that you think will be useful to the user here. For information that is specific to an individual mapping, please add that as a comment so that the Segment docs team can include it in the auto-generated content for that mapping. |
| 34 | + |
| 35 | +(delete after reading) Congratulations! 🎉 You’ve finished the documentation for your Segment integration. If there’s any additional information or nuance which did not fit in the above template and that you want to share with our mutual customers, feel free to include these as a separate section for us to review. If not, you may now submit this doc to our team. |
0 commit comments