Skip to content

Doc 68 customerio personas #1200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
markzegarelli merged 5 commits into from
Nov 5, 2020
Merged

Doc 68 customerio personas #1200

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e50ead2
DOC-68 break out personas block
markzegarelli Nov 5, 2020
ed3e5bb
Add userId is required for audiences/computed traits
segment-sv Nov 5, 2020
8d5f01d
active voice / move to a note
Nov 5, 2020
6d1805a
Merge pull request #1199 from segmentio/segment-sv-patch-1
Nov 5, 2020
eb941c6
needs a space there
Nov 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 13 additions & 0 deletions src/connections/destinations/catalog/customer-io/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,7 @@
title: Customer.io Destination
rewrite: true
redirect_from: "/connections/destinations/catalog/customer.io/"
hide-personas-partial: true
---

[Customer.io](https://customer.io/) lets you send automated email, push, SMS, letters, and webhooks based on your customer's activities in your app or product. It makes conversion tracking, optimization and remarketing easier than ever. The `analytics.js` Customer.io Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-customerio).
Expand Down Expand Up @@ -223,3 +224,15 @@ Remember that before we can send events to Customer.io from client-side Javascri

### Page events not being associated with user
Page events will only be associated to a user if the user has been previously identified in Customer.io. If you identify a user after making Page calls, the previous page events will not be associated to the user in Customer.io.


## Personas

You can send computed traits and audiences generated using [Segment Personas](/docs/personas) to this destination as a **user property**. To learn more about Personas, contact us for a [demo](https://segment.com/contact/demo).

For user-property destinations, an [identify](/docs/connections/spec/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`.

> note ""
> Customer.io requires you to pass a `userId` value when you sync Audiences or Computed Traits.

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.