Subscriber Data

A subscriber is the user of a mobile app that contains our SDK. Pushologies has two categories of subscriber data

Detailed Notification Events

These are the specific events we process related to a subscriber's interaction with our notifications and your app. The events that we record are listed below.

Pending - Notification has left the Pushologies infrastructure and is awaiting delivery to the device. Applicable to all notifications.
Received - Notification has been received on the target device. Applicable to all notifications.
Downloaded - The SDK has downloaded the requested content and a notification has been displayed to the user. Applicable only to content related notifications.
Download failed - The SDK failed to download the requested content. The notification without the content will be displayed. Applicable only to content related notifications.
Opened - Notification has been opened by the user on the target device. Applicable to all notification.
Viewed - The content has been completely viewed, or the notification has no content and has been opened. Applicable to all notifications.
Link opened - An interactive link has been tapped. Applicable to all notification and a subscriber may record multiple Link opened events per notification if the notification has multiple interaction options.
Session Times - The exact times and durations a user opens the app. Not linked to a specific notification.

Aggregated Subscriber Notification Events

These are the cumulative totals we attribute to each subscriber record of the total number of each of the detailed notification events. This allows you to understand the overall engagement of a specific subscriber with your app.

Retention Periods

Detailed Notification Events - Retained for 30 days

Aggregated Notification Events - Retained indefinitely for an active subscriber

In plain terms, you will only be able to build segments and target users based on actions a subscriber has taken in the last 30 days, unless those actions have resulted in the assignment of a tag against the subscriber record.

Platform Users

Pushologies equips Administrators with the ability to remove the identifying characteristics of a platform user in a self service manner.

It is entirely the responsibility of the Pushologies Client to remove access and/or the identifying characteristics of their users if they no longer wish that individual to have access to the platform. Pushologies do not routinely remove accounts, even if they have remained inactive for a period.

Platform Tenants

A Tenant is the entire customer environment, which includes notification history, aggregated results, subscriber data and platform user profiles.

Pushologies will remove the entire tenant after six months following the end of the relationship, unless otherwise instructed to remove it sooner.