Xplenty Destination
Destination Info
- Refer to it as Xplenty in the Integrations object
Personas
You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.
When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Note that real-time audience syncs to Xplenty may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
| Setting | Description |
|---|---|
| Name (required) |
string, defaults to Segment SQL . The connection name |
| Password (Read-Only) (required) |
string. Your SQL read-only user password, so that Xplenty can connect to the database. |
| User name (required) |
string, defaults to readonly . Your SQL username, so that Xplenty can connect to the database. |
| Workspace Slug (required) |
string, defaults to segment . Your workspace’s slug |
This page was last modified: 08 Mar 2022
Need support?
Questions? Problems? Need more info? Contact Segment Support for assistance!