Pointillist Destination
Pointillist quick info
Pointillist accepts Track, and Identify calls. If you reference it in the Integrations object, call it “Pointillist”.
Pointillist accepts cloud-mode data from all Segment source types. It does not offer device-mode connections.
Getting Started
Once the Segment library is integrated with your server code, site or app, toggle Pointillist ON in the Segment dashboard, and add your Pointillist API key.
To set up your Pointillist account and receive your API key, click on this link and follow the instructions on the screen. For any additional questions, get in touch with a Pointillist customer representative at customer-success@pointillist.com.
Note: Pointillist accepts server-side, client-side as well as mobile app-data, so you can use either or all of Segment’s libraries (browser, mobile and server) to send data to Pointillist.
Identify
When you call identify, we’ll log an identify event with Pointillist and set userId and anonymousId as Actor Identifiers. Pointillist will then automatically associate all events tagged previously with the anonymousId to the provided userId. We will also associate any special traits that you provide such as name, email, and other custom traits with Labels and Numbers so that you can filter or create metrics.
Track
When you call track, we’ll log an event with Pointillist with userId and / or anonymousId as Actor Identifier and set event as Event Type. The table below shows mappings for other attributes. You’ll pass the key on the left into Segment and we will transform it to the key on the right in Pointillist.
| Segment Parameter | Pointillist Parameter |
|---|---|
anonymousID |
Actor Identifier |
userId |
Actor Identifier |
timestamp |
Event Time |
event |
Event Type |
location |
Attributes Labels |
campaign |
Attributes Labels |
| user traits | Labels |
| device attributes | Labels |
API Key
To get your API key, contact the Pointillist customer success team
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.
Supported Sources and Connection Modes
Before you start, make sure Pointillist 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 | ✅ | ✅ | ✅ |
Segment offers an optional Device-based Connection Mode for Mobile data going to Pointillist, so that you can use Pointillist features that collect data directly from the mobile device. To do this, you must package the Segment-Pointillist mobile SDK with the Segment mobile library.
Settings
Segment lets you change these destination settings from the Segment app without having to touch any code.
API Token
To get your API Token please get in touch with a Pointillist customer representative via customer-success@pointillist.com
This page was last modified: 14 Jul 2020
Need support?
Questions? Problems? Need more info? Contact us, and we can help!