Profile Keys and Keyspaces

Profile Keys are string values that identify a Profile.

Profile data comes from many different sources: mobile applications, websites, CRM systems. Some data can be verified or assumed to come from a trusted source, and some can not.

To simplify managing data from different sources, Profile Keys are separated into different Keyspaces.

Keyspaces exist to manage user permissions: access and visibility. You can read more about Keyspaces and permissions once you're familiar with the basic concepts.

To fetch Keyspaces, use this API.

We'll create a Profile for an individual who we identify with their email address: andy.demo@apsis.com. This email address string will be our Profile Key. Since it is an email address, we will use the standard email Keyspace that exists by default in all APSIS One accounts.


Profile Attributes

Profile Attributes are data fields in Profiles used for names, addresses, and other demographic data.

They can be used in APSIS One to create Segments for email or SMS campaigns, as well as to create dynamic personalised content thats tailored for each Profile.

In this example well keep it simple with the default Attribute First Name, and "Andy" as value.


Sections

Sections separate data in APSIS One Profiles as a comprehensive method of managing user permissions and preserving personal data.

Admin users set up Section permissions for regular uses from their Account Settings.

Both Admin Users and regular Users that have permissions to all Sections can see all data collected from every Section in one specific Profile.

Meanwhile, regular users who have limited Section permissions only have access to the Profile data that corresponds with the Sections they have permissions for.

Instead of having separate Profiles for each Section, the Data Sections divide the data so that access is easily controlled within the account.

To fetch the sections on your account, use this API.

Sections can be used to differentiate Profile data between different brands or business units. A common example would be a retail company with two brands, a budget brand and a premium brand. This account would use a different Section for each of them.

When this company invites its members into APSIS One, they can set different user permissions so that access to one or another Section is individual, always keeping Profile data on the right hands.

Did this answer your question?