Segment Event Field | Required? | Description |
---|---|---|
userId | Required | Maps to the id of a user in Kana. This is the external identifier of your user. |
traits.name | Optional | Maps to the name of a user in Kana. |
traits.email | Optional | Maps to the email of a user in Kana. |
traits.billingUserId | Optional | Maps to the billingId of a user in Kana. Must be the customer id for either Stripe or Chargebee as valid billing providers. |
userId
and email
to determine when to create, update or merge a user. The userId
takes precedence as the canonical identifier. Kana allows for multiple users to have the same email
.
userId
: We will create a new user if that userId
cannot be matched.
userId
and email
: The following examples illustrate when a user will be created, updated or merged in Kana based on (1) what is sent in the Segment event payload, and (2) what users & which details are present in Kana:
userId
but could have an email
. Segment identify events will always have a userId
. Therefore, duplicate users could occur.
Kana will also try update or merge these users when Segment events come in with an email
which matches (as can be seen in the diagram above). However, in some cases we will not merge users. The likelihood is that the payload contains the same email as multiple users and one of these was a Stripe import which has no userId
.
In both these cases, we will flag these users to you in the dashboard. You will be able to review and then merge these users in case it’s necessary. You can see more on this in the Errors section below.
billingId
, and (2) calling out users which have the same email
.
billingId
. If it is necessary for them to have one, or you suspect they might be duplicates, then you can import a CSV with the correct details for each user to resolve this. You can click ‘View Users’ to see all those users and import the CSV (under ‘Import CSV’).