About Profiles

Follow
Our Profile API gives your users on app or website the ability to enhance their experience by selecting their preferences and proactively sharing data. This is done through a simple interface, similar to that of Settings in iOS; which can contain on/off, numerical, date range, and more inputs.
 
A few examples:
 
Fashion/Retail: Asking the user their gender, sizes (shoes, shirt, trousers, jacket), style preferences. So every time an individual goes into the app, the items available to their preferences always appear first.
 
Sports: Sports fans are passionate and love content. But every fan is different. Asking the fan the type of content they would like to receive, at what frequency, ensures they kept up to date on the important issues in real time.
 
Publishers: In the digital world publishers need to drive up conversion rates to succeed. Why not ask the reader for their preference in topics? Use it to display that content first. Give them value, and they will willingly give you back data.

 

Technically speaking

From a more technical perspective, a profile is predefined set of named keys to which devices will eventually store matching data against each of these keys. Each element within the profile has a datatype definition. Some can contain limits to check if data to be added against this profile element is valid or not. Each key can also contain an “extra” attribute for the value to be inserted, typically to represent the unit of the value.

When a user adds the value for the key, a timestamp of the insertion time will be added together with the value automatically into system. Values for each key can only be one value for any given key; meaning the new value for this key from this user will overwrite the old value. If the profile element is defined as incremental, each key can contain multiple entries for this user and old values will remain for upcoming profiling purposes. Typically this incremental type of profile element is used when the profile is expected to gather all the events of a specified type, such as “User has finalised the payment on our online store”. Using these incremental profile elements enables the functionality to define more detailed target groups as an audience, while defining rules for the Beems and/or requesting analytics of a system.

Entries of the profile elements can be added from the host application, also by providing suitable fields for the user to add values for each defined profile element.

The profiles and the containers can be created and stored using Dashboard. An administrator inputs the required contents and data types in the user interface. The host application can access and update those profiles, providing the user with the necessary UI elements to fill their profile data.

 

Supported datatypes for profile elements

  • Boolean (true/false)
  • Number
  • Text
  • Timestamp
  • Numeric range (from-to validity for upcoming values)
  • Timestamp range (from-to validity for upcoming values)
  • Option list (single- or multiselect)

Example profile

  • Do you have a pet?
  • What is your favourite movie?
  • How old are you?
  • Have a guess; which day of the upcoming christmas will be the most profitable?
  • Did you buy a pizza?

Do you have a pet?

User has a pet or not. This is a boolean value (true/false) which will be set as true or false by an user.

What is your favourite movie?

Favourite movie of the user is text because you never can generate list of all available options of the movies available. Type for this key is text, where the user can enter the name of his/her favourite movie.

What is the age of the user?

Age is numeric representation (Number) of a user’s age which will be defined as “Number”. The “extra” field for this profile element could be defined as “years”, expecting that age is always defined as years.

Which day of the upcoming christmas will be the most profitable?

Best representation of the date is timestamp. To be more precise with this upcoming christmas the valid timestamp range should be defined by using the type for this key as TimestampRange with proper from and to values. “From” value could be defined as 2014-12-15 and “to” value of this could be set to 2014-12-26. When user is adding value for this profile element it will only allow values between the given timestamp range. Any other given value will be invalid and cannot be set.

Did you buy a pizza?

When something has occured – in this case a pizza has been bought by the user – the host application will send the message to Beemray SDK’s profiling for this. It is just a Boolean element on this profile because the question was all about when a pizza was bought. Occurence of each entry on profile will always contain also the timestamp which in this case enables analytics to combine query against the profile data about the pizza payments over time.

Have more questions? Submit a request

Comments