Search results for "{{ search.query }}"

No results found for "{{search.query}}". 
View All Results

Tracking users

All user related APIs are part of WebEngage iOS SDK's WEGUser object. You get an instance of WebEngage WEGUser object as follows:

WEGUser* weUser = [WebEngage sharedInstance].user;

Identifying users

WebEngage SDK automatically creates a unique ID (LUID) which the WebEngage backend uses to uniquely identify users. These are “anonymous” profiles to which you can assign unique User IDs (CUID). Assigning a CUID helps collect the user's activity and information across systems in a single unified profile.

A user profile's ID once assigned, cannot be changed. Although ID can be any NSString that uniquely identifies users in your system, we recommend using system generated user IDs from your database instead of information that can change over time such as email addresses, usernames or phone numbers.

The usual places to assign IDs are

  • On user signups
  • On user logins
  • On screen or page views where user identity becomes known
  • When the user context changes

Constraint:
An ID can be of maximum 100 characters.

You can assign an ID by calling the login method. All attributes, events and session information accumulated before this API has been called get associated to an anonymous user created by default. Once login is called, all of this stored information is attributed to this identified user.

[weUser login:@"9SBOkLVMWvPX"];

Make sure you call login as soon as the user logs in to your application, or whenever earliest you are able to identify the user.

//Available >= 3.4.12
[weUser logout];

//Deprecated >= 3.4.12, use login instead
[weUser loggedout];

Make sure you call logout when the logged-in user logs out, or you do not want to attach any future event, session or user data with this user, until login is called again.

User attributes

There is often additional identifying information, such as name and email address, associated with user profiles. WebEngage provides setters for assigning these attributes to users. These attributes can be used to segment users and target campaigns to a specific group. Additionally, they can be referred to personalize campaign messages to each user.

Attributes can be set on “anonymous” profiles as well.

Each session has its own user attributes, but they get copied from one session to the next. This is in contrast to event parameters, which may take on different values per event. For this reason, you generally use user attributes for things that do not change much within the session, or with which you want the entire session associated.

Setting system user attributes

Constraint:

  • NSString type attribute values must be less than 1000 characters long. Any characters beyond that will be truncated.

Email

[weUser setEmail:@"john@doe.com"];

Hashed Email

If you are averse to passing your users' personally identifiable information, WebEngage enables you to pass hashed email IDs and to set up private Email Service Provider API endpoints at your end.

//(Available >= 3.4.2)
[weUser setHashedEmail:@"144e0424883546e07dcd727057fd3b62"];

Birth Date

//(Available >= 3.4.14, use setBirthDate for < 3.4.14)

NSDateComponents *comps = [[NSDateComponents alloc] init];
[comps setDay:19];
[comps setMonth:08];
[comps setYear:1996];
NSDate *date = [[NSCalendar currentCalendar] dateFromComponents:comps];

[weUser setBirthDate:date];

Birth Date in yyyy-mm-dd format

[weUser setBirthDateString:@"1986-08-19"]; //yyyy-mm-dd

Phone Number

[weUser setPhone:@"+551155256325"];

The NSString phone must be in E.164 format, eg. +551155256325, +917850009678.

Hashed Phone Number

If you are averse to passing your users' personally identifiable information, WebEngage enables you to pass phone numbers and to set up private SMS Service Provider API endpoints at your end.

//(Available >= 3.4.2)
[weUser setHashedPhone:@"e0ec043b3f9e198ec09041687e4d4e8d"];

Gender

[weUser setGender:@"male"];

First Name

[weUser setFirstName:@"John"];

Last Name

[weUser setLastName:@"Doe"];

Company

[weUser setCompany:@"Alphabet Inc."];

Opt In Status

To set the subscription preference of your users (for Push, In-app, SMS and Email) use setOptInStatusForChannel. Users who are opted out of a particular channel will not receive any communication on that channel. Users are by default opted into all channels.

[weUser setOptInStatusForChannel:WEGEngagementChannelPush status:YES];

WEGEngagementChannel is an enum and can have four values: WEGEngagementChannelPush, WEGEngagementChannelInApp, WEGEngagementChannelSMS, WEGEngagementChannelEmail. Setting setOptInStatusForChannel to false for a particular channel opts the user out of that channel.

Deleting system user attributes

WebEngage allows you to delete any system attributes that you had created previously if you no longer need them.

-(void) deleteAttributeType:(WEGUserProfileAttribute)attributeName;

WEGUserProfileAttribute is an enum and can have following values:

User Profile Attribute
Description

WEGUserProfileAttributeEmail

Email

WEGUserProfileAttributeBirthDate

Date of birth

WEGUserProfileAttributeGender

Gender

WEGUserProfileAttributeFirstName

First name

WEGUserProfileAttributeLastName

Last name

WEGUserProfileAttributeCompany

Organization

Setting custom user attributes

Use these APIs to attach custom attributes to the user. These data types are allowed for below APIs: NSString, NSNumber, NSDate, NSArray, NSDictionary. NSArray can contain one of these data types.

Constraints:

  • Attribute names must be less than 50 characters long. NSString type attribute values must be less than 1000 characters long. Any characters beyond that will be truncated.
  • In addition to the system attributes, you can create at most 25 user attributes of each data type.
  • You cannot start your attribute names with we_.
  • If attribute value is NSArray or NSDictionary, it cannot be used to create user segments. It can only be used to personalize campaigns.

NSString attribute

[weUser setAttribute:@"Twitter username" withStringValue:@"@origjohndoe86"];

NSNumber attribute

[weUser setAttribute:@"Points earned" withValue:[NSNumber numberWithInteger:78732]];

NSDate attribute

NSDateComponents *comps = [[NSDateComponents alloc] init];
        [comps setDay:19];
        [comps setMonth:8];
        [comps setYear:1996];
        NSDate *date = [[NSCalendar currentCalendar] dateFromComponents:comps];
        [weUser setAttribute:@"Last order date" withDateValue:date];

NSArray attribute

The NSArray value must not contain any data type other than ones specified above.

[weUser setAttribute:@"Brand affinity" withArrayValue:@[@"Hugo Boss",@"Armani Exchange", @"GAS", @"Brooks Brothers"]];

1. User attribute names are case sensitive.
2. attributeName must not start with we_. Attribute names starting with we_ are reserved for WebEngage's internal use, and will be ignored if used for custom attributes.
3. For custom user attributes, the first datapoint synced to WebEngage defines the data type for that attribute in WebEngage. Therefore, data types must be consistent with the data that you want to store for the attribute. If you change the data type later, attribute data will stop flowing to WebEngage.

You can define multiple user attributes in one go using NSDictionary. The keys of this NSDictionary will be attribute names and values will be respective attribute values. These attribute values must be one of the above specified data types or NSDictionary.

//(Available >= 3.4.14)
NSDictionary *custumAttributes=@{@"Age":@31,@"Twitter username":@"@origjohndoe86",@"Subscribed to email":@YES,@"Dollars spent":@461.93,@"Points earned":@78732,@"Brand affinity":@[@"Hugo Boss", @"Armani Exchange", @"GAS", @"Brooks Brothers"]};
        [weUser setAttribute:@"User details" withDictionaryValue:custumAttributes];

Deleting custom user attributes

WebEngage allows you to delete any custom attributes that you had created previously if you no longer need them.

[weUser deleteAttribute:@"Points earned"];
[weUser deleteAttributes:@[@"Twitter username", @"Subscribed to email", @"Points earned"]];

What's Next

Tracking events

Tracking users