User Profile

After integration with Reteno, the system automatically creates the user profile for each person who downloads your app, fills out forms on your website, etc. Here you can collect all user information, preferences, behaviors and use these data for personalization or segmentation.

To see a full contact profile, click on any blank space in the corresponding contact line in the Contacts → All contacts tab.

The information in the profile is divided into two tabs: Contact information and Contact activity.

Contact Information

This tab contains:

• User identifiers — email, phone number, applications, mobile and push tokens.
• Personal data contains name, age, gender, address, regional settings (time zone/language), etc. Also, you can add specific to your business custom fields.
• Subscription categories for campaign segmentation.
• Additional information — contact ID, created date, last edit date, source (import, subscription form, order, API, etc.)

📘

Note

One contact can hold several mobile and Web Push tokens and several device identifiers at the same time. Group statistics count contacts, not tokens, so the number of contacts in a group and the number of tokens they own can legitimately differ.

📘

Note

A change history for the contact's email address isn't stored. The profile shows only the current address. You can trace previous addresses indirectly — through the sending activities on the Contact activity tab or in campaign reports, where each message is recorded with the address it was sent to.

Also, here you can find information on the email address status. If the contact is blacklisted, the system automatically records the date and reason (for example, inactive email address) in the contact profile.

The system automatically records the date and reason in the contact profile if the contact has reported on spam or unsubscribed.

Checking Whether a Contact Allowed Push Notifications

A mobile push token in the contact card means the user granted permission for push notifications, so a segment or workflow condition that checks for the token tells you whether the contact can receive pushes at all.

A contact that has an application token and a device ID but no mobile push token installed the app without allowing notifications.

When the user turns notifications off, the token disappears from the card and the contact stops receiving pushes. After the app is uninstalled the token stays in the card until a send attempt returns an error from APNs or FCM — see Error Codes for Mobile Push Notifications.

Passing your own field for the same purpose, such as pushNotificationsEnabled, duplicates what the token already shows. Such a field is written by the app and updates only in a new session, so it drifts out of date: you get contacts that hold a token while the field still says notifications are off.

Contact Activity

This tab contains a history of user actions in your app, messages, or website. You can find the number of contact activities, channel, the sent message's name, date, and its status here.

📘

Attention

A widget can be displayed more times than allowed by the display frequency. This can happen when a customer visits the website in incognito mode or after clearing their cache, cookies, and local data on their device.

Apart from Delivered, Read and Clicked, the status field can also contain the Undelivered and Unsubscribed statuses.

Expand the menu and select the desired period to view the contact's actions for that specific period.

Each activity contains the following information:

• Sent message, date, and status – Campaigns category.
• Event names and assigned workflows – Events category.