Tracking Users

NVECTA starts to detect users right after you integrate your web platform through our SDK's. Hereafter, you can identify users by passing a unique identifier object (e.g., email, mobile) to merge and track them across sessions.

nv('user', USER_IDENTIFIERS, USER_ATTRIBUTES);

Benefits

• You can add more information to your NVECTA User Profile and create a user segment for different category of people with specific profile property predefined by you.
• You can build new campaigns to engage your users for each segment that you create.
• Secondly, by adding more info to your NVECTA User Profile you can personalize your messaging for the campaigns with related information.
• The third benefit includes personalizing your app created from information from the specific users NVECTA User Profile.

User Identifiers

You can pass a unique identifier object (e.g., userID, email, or mobile) to identify and merge users across different devices and sessions.

📘

Must Read:

We recommend that you must get familiar with all the concepts that are related with Events and Users before you proceed to track users. It will help you to get a better grasp of this section.

As soon as you integrate your platform through our SDKs - which may be a website or an app, NVECTA begins to detect users immediately. You can identify each user by passing a unique identifier object (such as email or mobile) to merge and track them across sessions. Every time a user visits your site, the SDK at NVECTA creates a unique identity (NV_UID) for the visitor. We are able to record users with the generated ID and also create a secret anonymous profile. The user's behavioral data and along with it the session data is stored under the secret profile. The session data includes information like:

• Custom Events
• System Events

👍

Note:

You can identify a user using any of the following: userID, email, or mobile.

You can identify the user at any of the following instances :

• When User signs up
• When User logs in
• When user views pages where the ID becomes known
• On change of User context

When a Unique Identifier has been assigned to a User:

• The user is now identified and falls in the known user category
• Automatically, a fresh Profile for the known User Profile is created, containing all their data
• All of their previous anonymous profiles get merged at this point to help you view a combined profile under the known User Profile

The User API allows you to track the activity of users' as they switch from device to device and keep adding attributes to the profiles.

For details on how profiles are merged when a user is identified, refer to the user identification and profile merging doc.

Guidelines

• All APIs related to users are a part of NVECTA's user object of the Web SDK
• You cannot change your assigned user ID
• Maximum number of characters allowed in making your user ID have to be under 100 characters
• User ID cannot be changed further once established. Unique ID means having a distinctive user identity.

User Attributes

User Attributes are Attributes related to the user profile as following: User's name, Email address, Location.

There are two types of User Attributes: System User Attributes and Custom User Attributes. Both attributes are tracked for known users and anonymous users.

System User Attributes

System user attributes are the attributes which are passed by you and recognized by NVECTA system.

Guidelines

• NVECTA allows professionals to assign values to all attributes for your website users.
• You can use the attributes to configure personalised messages.
• Record details using User attributes as they do not change and their details are the same throughout one session.

Setting System Attribute

Name, Email, and Mobile

nv('user',{'email':'[email protected]','mobile':'9999999999','userID':'XYZ4410'},{name:'test'});

📘

Phone numbers must be in international format with a leading "+" and country dial code (e.g., +919876543210, +551155256325). To learn how numbers are normalised and stored, see International Mobile Number Normalisation.

Birth Date (in YYYY-MM-DD format)

nv('user',{'email':'[email protected]','mobile':'9999999999','userID':'XYZ4410'}, {birth_date:'1986-08-19'});

Opt In Status
Set subscription preference of your users for SMS, Email, and WhatsApp. Use the following methods:

nv('user', {'email':'[email protected]', 'mobile':'9999999999','userID':'XYZ4410'}, {whatsapp_opt_in:1, email_opt_in:1, sms_opt_in:1});

• Those users who have shared their phone number and email address are automatically opted in to SMS and Email respectively.
• By default the WhatsApp opt-in setting is false. When the users decide to opt-in to a channel you would have to set it to true.
• If the Users happen to opt-out of a channel, they will stop receiving communications through that specific channel.

Learn more about subscription status for Email, SMS, and WhatsApp.

Custom Attributes

Custom attributes are the additional details passed by you for users. You can pass the user system attributes like name, email, mobile and whatsapp_opt_in, and custom attributes like user_score, plan_type etc as given below:

nv('user',{'email':'[email protected]','mobile':'9999999999','userID':'XYZ4410'},{name:'test', whatsapp_opt_in:1, user_score:'340', plan_type:3});

Important Points:

• Values of an attribute can have only one of the following data types: String (including String Array), Integer (Number), Boolean, Date (including Timestamp), Object, and Nested Object. The maximum number of custom attributes allowed per data type is as follows:
  • String: up to 200 attributes
  • Number: up to 100 attributes
  • Boolean: up to 20 attributes
  • Date (including Timestamp): up to 20 attributes
  • Object: up to 20 attributes
  • Array of Objects: up to 5 attributes
• The maximum length of a String data type for an attribute is 1000 characters.
• The maximum length of an attribute Key is 50 characters.
• Attribute Names should contain only alpha-numeric, white spaces or "_"; No other special characters are allowed. Recommended names should be - 'first name', 'last_name'.

Complex Attributes

Your user details may have more complex info like Array and objects:

nv('user',{'email':'[email protected]','mobile':'9999999999','userID':'XYZ4410'},{name:'test', user_score:'340',
whatsapp_opt_in:1, plan_type:3, Address:{
  "Flat" : "h-3/94",
  "Building Number" : "B2",
  "Locality" : "Bengali Road",
  "City" : "Palam",
  "State" : "Delhi",
  "PIN" : "110045"
}
});