- If accid is sent, then userid will be ignored – as all subsequent events will be tracked against the account.
- If userid is sent, then this will be taken as an identifier for the user across the site. Use this same identifier when the user logs in; makes an order; or in any offline orders that are submitted.
- If neither accid or userid is sent, then email will be used as the unique identifier for the user. This should be used whenever the user logs in; makes an order; or in any offline orders that are submitted.
- If accid or userid is set – and email is set as well – then the email address will just be stored against the user. It will be used if any Triggered Emails are sent.
- Best practice is to send the userid (or accid if using accounts). This is because it will remain unique to that user – email addresses may well be changed over time.
- The Id should match the Id sent in the user feed.
If you are passing groupid, then this must match one of the groups sent in the GroupPricing field in the Product Feed.
Properties
A unique ID for the user
The users email address
If the user is part of business account this value can be used to ensure customer specific account pricing, and personalization at the account level rather than the user level.
Optional user group. Used to support price banding (prices per user group)
First name of the user
Last name of the user
The prefix of the userExample:
Mr