Xplenty quick info
If you reference Xplenty in the Integrations object, call it “Xplenty”.
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
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.
Supported Sources and Connection Modes
Segment offers an optional Device-based Connection Mode for Mobile data going to Xplenty, so that you can use Xplenty features that collect data directly from the mobile device. To do this, you must package the Segment-Xplenty mobile SDK with the Segment mobile library.
Segment lets you change these destination settings from the Segment app without having to touch any code.
The connection name
Your SQL read-only user password, so that Xplenty can connect to the database.
Your SQL username, so that Xplenty can connect to the database.
Your workspace’s slug
This page was last modified: 25 Nov 2019
Questions? Problems? Need more info? Contact us, and we can help!