ProsperStack Destination

1. Log in to the ProsperStack dashboard.
2. Navigate to Settings > Manage integrations.
3. Click Configure in the Segment integration section.
4. Click Connect Segment.
5. Select a Segment workspace and source to send to the ProsperStack Destination.

To add additional sources, click Connect a source.

1. In the Segment app, go to Connections and click Add Destination.
2. Search for "ProsperStack" in the Destinations Catalog, and select the ProsperStack destination.
3. Click Configure ProsperStack and choose the source you want to connect the destination to.
4. Create a new API key from the ProsperStack API keys settings screen.
5. Enter the API Key in the ProsperStack destination Settings tab in Segment.

ProsperStack supports the following methods, as specified in the Segment Spec.

Send Identify calls to ProsperStack to update subscriber custom properties in ProsperStack. For example:

1
analytics.identify("userId123", {
2
  email: "john.doe@example.com",
3
  traits: {
4
    "Number of contacts": 5800,
5
    "Is professional": true,
6
    "Last contacted": "2021-05-04",
7
    "Preferred name": "Johnny",
8
  },
9
});

Segment sends Identify calls to ProsperStack as an identify event.

Custom traits specified in an Identify call update custom properties for a corresponding subscriber in ProsperStack. You must specify an email in an Identify call in order for a ProsperStack subscriber to match with the Identify call.

Custom properties in ProsperStack that match the exact key of a trait update automatically. You can configure additional trait mappings in the ProsperStack configuration dashboard.

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule 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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Segment lets you change these destination settings from the Segment app without having to touch any code.