To make an identify call successfully, either the email or userId is required.
The following table lists the RudderStack attributes and their mappings with the Refiner properties:
userId Required, if email is absent.
properties.email Required, if userId is absent.
The track call lets you capture user events and send them to Refiner as trackEvent events. If a track event contains a userId, then Refiner updates the corresponding user’s information. Otherwise, it creates a new user.
Refiner does not store any additional properties sent with the track event.
The following table lists the RudderStack properties and their mappings with the Refiner properties:
The group call lets you link an identified user with a group, such as a company, organization, or an account. Note that Refiner associates all group traits with the account object associated with the user.
cookies, the cookies that are categorized as necessary are stored on your browser as they are as
for the working of basic functionalities of the website. We also use third-party cookies that
analyze and understand how you use this website. These cookies will be stored in your browser
consent. You also have the option to opt-out of these cookies. But opting out of some of these
have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This
category only includes cookies that ensures basic functionalities and security
features of the website. These cookies do not store any personal information.
learn more about cookies and why we use them, visit our cookie
policy. We'll assume you're ok with this, but you can opt-out if you wish Cookie Settings.