Apps: Profile View
Profile Cloud generates by default a random cookie and unique cookie ID for any visitor on your website. The ID has this format: “dloo1ox9vhq3kqu9j6dfdfewcymwh7a0T” and is by default the profile ID. Profile Cloud identifies your visitors on your website by this ID and it can also be found in the “profile overview” app in the interface.
In order to tie your users' behaviour across devices and web sessions (if cookies are erased), a cookie ID is not enough as there are no ways to be able to identify the same user on different devices if there is no identification on each device. The identification is in most cases a login but can also be a registration, email sign up, click on an email sent from your organization or any other identification process. By defining another unique ID such as email address, customer ID or any other ID that your organization are using makes it possible to tie behaviour on all your channels on different devices to a single profile. Use the same ID to connect offline data and data that you have in other systems.
There are numerous of benefits by setting a new profile ID.
- Connect offline and online data to one single profile.
- Track user behaviour on different devices and channels.
- More qualitative data on your customer’s behaviour.
- More qualitative re-targeting by communicating with the same message through all your channels.
Set a new profile ID in Web data collection
Define a new profile ID, for example, an email address, customer ID or any other ID that are unique to your users.
- Go to the web data collection app and create a new event definition.
- Create a data value that is picking up or receiving the ID (How the ID is collected is depending on your website and the specific case)
- Connect it to building block “Set profile ID”. “Set profile ID” should be set under event data.
- When the event is triggered Profile Cloud will now automatically set this ID as the profile ID and it can be viewed and searched on in the profile overview app.
The trigger “Profile cloud data present” executes after data has been sent from profile cloud. Generally, Web data collection-data is stored in the user´s browser. In some occasions, information from the profile cloud has to be available to serve the purpose of the event. Example of that can be geo-location data or attributes that may come from other data sources and has not yet been synced with the user´s browser.
If your event needs information to be present that is not stored locally in user´s browser, this trigger will make your event execute right after the reception of these data.
In order to create sustainable, usable and structured profiles, the profile data is categorised into different areas. Profile attributes is one area. Profile attribute refers to a set of data of your customers that is in most cases not based on the behavior or browser sessions. Data that is tied to the customer himself. Example of profile attributes can be email address, home address, gender, age, interests, relationship status, previous purchases, Customer vs prospect etc.
It is important to mention that APSIS does not consider the data you categorise as a profile attribute, meaning it is possible to use other kinds of data as profile attributes. It is completely up to each account to decide what data and what category to use. Below image shows some examples of profile attributes.
The trigger “Profile cloud data present” executes after that data has been sent from profile cloud. Generally, Web data collection-data is stored in the user´s browser, but in some occasions, information from the profile cloud has to be available to serve the purpose of the event. Example of that can be geo-location data or attributes that may come from other data sources than the web. If your event needs information that is not stored locally in user’s browser, to be present, this trigger will make your event execute right after the reception of these data.