This preview of pull request 1639 is meant for internal use only.

PersistIQ Destination

PersistIQ quick info

PersistIQ is in beta, and accepts Identify calls. If you reference it in the Integrations object, call it “PersistIQ”.

PersistIQ accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.

PersistIQ is the easiest sales engagement software to use. Sales teams use PersistIQ to connect with more prospects using targeted emails, calls, and tasks.

This destination is maintained by PersistIQ. For any issues with the destination, contact the PersistIQ Support team.

This document is about a destination which is in beta

This means that the PersistIQ Destination is in active development, and some functionality may change before it becomes generally available.

Getting Started

Before you start, make sure PersistIQ supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode ⬜️ ⬜️ ⬜️
☁️ Cloud-mode
  1. From the Segment web app, click Catalog.
  2. Search for “PersistIQ” in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. Enter the “API Key” into your Segment Settings UI which you can find at the bottom of your PersistIQ Integrations page.

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

You can pass in an email and unsubscribed (with a value of true) in an identify call. If the email address matches an email present in PersistIQ, that prospect will be marked as opted out. Here is an example of how to do that:

analytics.identify('userId123', {
  email: 'john.doe@example.com',
  unsubscribed: true
});

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.

Settings

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

API Key

Click your initials in the bottom left of the page, click Integrations, and scroll to the bottom of the page.

This page was last modified: 20 Oct 2020



Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account