Skip to content

Conversation

@segment-sv
Copy link
Contributor

Received request from Solutions Architect extraordinaire Joe Ayoub:

Hi friends@ team,

A customer of ours noticed that the Customer.io Destination requires users in a Personas Audience to have userIds. If the users don't have userIds then the user will not be synced to Customer.io (as part of a Personas Audience).

There is no mention of this requirement in the Personas documentation.
It essentially means that it is not possible to sync anonymous Audiences to Customer.io, even if all the users have email addresses. This is important information for our customers to have.

Would it be possible to update the Destination docs to state that a userId is required when syncing an Audience or Computed Trait? Obviously, an email address is important when syncing Audiences to Customer.io (but I don't know if email is actually required...)

Thanks,
Joe

This can be added to the doc ASAP, no intended timeline.

Received request from Solutions Architect extraordinaire Joe Ayoub:

Hi friends@ team, 

A customer of ours noticed that the Customer.io Destination requires users in a Personas Audience to have userIds. If the users don't have userIds then the user will not be synced to Customer.io (as part of a Personas Audience). 

There is no mention of this requirement in the Personas documentation. 
It essentially means that it is not possible to sync anonymous Audiences to Customer.io, even if all the users have email addresses. This is important information for our customers to have. 

Would it be possible to update the Destination docs to state that a userId is required when syncing an Audience or Computed Trait? Obviously, an email address is important when syncing Audiences to Customer.io (but I don't know if email is actually required...)

Thanks,
Joe
@markzegarelli markzegarelli merged commit 6d1805a into DOC-68_customerio-personas Nov 5, 2020
@markzegarelli markzegarelli deleted the segment-sv-patch-1 branch November 5, 2020 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants