About profiles and devices

While in Actito, a profile is associated with only one e-mail address, it is a bit different with push notifications.

Indeed, a single profile may own different devices (a smartphone, a tablet, a desktop computer with different browsers,…). The profile may interact with your website/app with all these devices and opt-in (or not) to receive push notifications on each of these devices.

The end-customer Id must be unique in Actito, while in WonderPush several devices may be associated to the same end-customer Id, because they belong to the same profile.

• _{In this example, 1 person = 3 devices}

• _{To be contactable, the profile has to allow notifications on the app/browser of a device.}

About the end-customer id

The end-customer Id will be defined by your system (ex: your CRM).

The assignation of the end-customer Id to a device will occur in WonderPush when a profile opts in for push notifications and is known to your system (ex: logged into your site/app).

The same end-customer Id must be available in the Actito profile table, to be able to connect the profiles across the 3 systems.

Therefore, to choose the proper end-customer Id:

• The data must be available as a key in Actito thanks to the data synchronization between your system and Actito.

• The data must be available on your website or on your mobile app.

Please use an attribute which is already defined as unique on your Actito profile table.

About data synchronization

Data synchronization is required between your system and Actito to push the profiles (identified by the end-customer id). As these profiles must be authenticated on your website or your app, they should be known by your system and pushed into your normal data flows in any case.

The synchronization of the optins of these profile is automatically done between WonderPush and Actito. When a profile subscribes to push notification on your website or your app, an opted-in device will be recorded on WonderPush and automatically synchronized with Actito: a specific subscription will be updated on the profile matching the end-customer id of the subscriber.

Indeed, as part of the integration, specific subscriptions for the Push channel are defined: a Web subscription and/or an App subscription (depending on your set-up).

These subscriptions will be automatically updated in real-time when a profile (known by his end-customer id) gives or removes his authorization to be contacted on your app/ your website, depending on the type of device they are using.

A profile can subscribe to push notifications on multiple devices/multiple browsers. As long as they remain opted-in on one browser, their Web subscription value will be True. As long as they remain opted-in to the app on one mobile device, their App subscription will be True.

Example: a profile opts in on Firefox and opts out on Chrome. Their Web subscription remains True. If the profile opts out on both Firefox and Chrome, their Web subscription will be automatically updated to False.

Viewing your integrations

Your integrations will be visible when you create Push campaigns.

You can view the definition of the integration by clicking on View details.

Apart from the name of the integration, the important parameters are:

• The Actito Database to which the Integration is linked (and the entity on which it is stored).

• The profile attribute defined as end-customer id, which is the key for the synchronizations between your profiles and their devices.

• The name of the Web and App subscriptions, which are automatically synchronized when a profile opts in to push notification on your website/app.