Add userId is required for audiences/computed traits #1199
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.