Update information about the Airship destination and source #2025
Conversation
borys-belinsky
requested review from
stayseesong
and removed request for
a team
markzegarelli
requested review from
markzegarelli
and removed request for
stayseesong
markzegarelli
added
content
|
|
||
| Custom Events and Tags sent from Segment are automatically populated within Airship Performance Analytics reporting dashboards. | ||
| When you call `group`, Segment sends a custom attribute to Airship with the name `airship_segment_group_<groupId>`, where `<groupId>` is the group's ID passed as one of its parameters. For example, if the group's ID is `1234` then the custom attribute name is `airship_segment_group_1234`. The value of the custom attribute is `true`. |
There was a problem hiding this comment.
The Airship attribute key uses the Segment attribute ids not the group id. From the example group call an attribute would be airship_segment_group_industry with the value Technology. See this example for more information.
| To use the Segment Destination integration, you must implement Named Users in Airship. The Segment UserID must match the Named User ID in Airship. | ||
|
|
||
| If your `named_user_id` and `UserID` do not match, Airship will not be able to associate Identify or Track events to the proper user in Airship. This would prevent you from effectively issuing automated messages or attaching user attributes from Segment within Airship | ||
| To use the Segment Destination integration, you must implement `Named Users` in Airship. The Segment UserID must match the Named User ID in Airship. If your `named_user_id` and `UserID` do not match, Airship will not be able to associate `identify` or `track` events to the proper user in Airship. You will not be able to issue automated messages or to attach user attributes from Segment within Airship. |
There was a problem hiding this comment.
Add group call type: Airship will not be able to associate identify, track, or group events to the proper user in Airship.
|
|
||
| There is a maximum limit of 20 properties for track events. A custom event will not be created for a `track` event whose properties count exceeds the limit. | ||
| Note that a custom event will not be created for a `track` event which has more than 20 properties. |
There was a problem hiding this comment.
This is no longer a limitation and can be removed.
| Airship gives brands the data, channels, orchestration and services they need to deliver push notifications, emails, SMS, in-app messages, and more to the right person in the right moment — building trust, boosting engagement, driving action and growing value. | ||
| Airship gives brands the data, channels, orchestration and services they need to deliver push notifications, emails, SMS, in-app messages, and more to the right person at the right moment — building trust, boosting engagement, driving action, and growing value. | ||
|
|
||
| [Airship Cloud-mode Destination integration](https://docs.airship.com/partners/segment/#destination) enables users to set Airship Tags and Custom Events through Segment's `identify`, `track`, and `group` API calls. |
There was a problem hiding this comment.
Add Attributes: enables users to set Airship Tags, Attributes, and Custom Events through Segment's identify, track, and group API calls.
| "segment-integration-group": ["hiring"] | ||
| }, | ||
| "remove": { | ||
| "segment_integration-group": ["has-remote-employees"] |
There was a problem hiding this comment.
Typo in group name, should be segment-integration-group
|
✔️ Deploy Preview for segment-docs ready! 🔨 Explore the source changes: b31852b 🔍 Inspect the deploy log: https://app.netlify.com/sites/segment-docs/deploys/616dd67d8525c700077b75ed 😎 Browse the preview: https://deploy-preview-2025--segment-docs.netlify.app |
|
Thanks for the PR @borys-belinsky and for the review @annarbecker! I've removed the Page call from the quick info box on the destination, and will deploy these changes today. |
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
Update information about the Airship destination and source based on Airship documentation
Merge timing