Resolution levels

Overview

This document explains how resolution levels work within Redpoint Interaction (RPI) and when to use each of the pre-defined resolutions. A standard selection rule’s resolution level defines the data warehouse or auxiliary database table from, and the key level at which, records are to be counted when the rule is run. It is set using a dropdown.

The list contains resolution levels that have been set up within the current RPI installation. A new standard selection rule’s resolution level defaults to the value defined as default within the resolution level's configuration interface.

Within the RPI configuration there are two types of resolutions:

• Standard resolutions are used for the majority of selection rules within RPI. These contain all of the data points needed to select groups of records throughout the process. For example, if you want to select all customers/individuals who have made a purchase within the last 30 days, standard resolutions will allow you to do this.

• PII resolutions are used to select customers/individuals based on Personally Identifiable Information (PII) information that is housed in a different database. For example, if you want to suppress a list of records based on an email address, you’d do this using the PII resolutions.

The resolution levels that have been set up within RPI have been set up at the individual business unit record level.

Standard resolutions

Golden Record Summary

Using the Golden Record Summary resolution level allows you to select records based on the Individual Business Unit ID. If there are multiple business units associated with a customer, then RPI will see each of those brands as unique records due to this combination.

Golden Record Summary resolution use cases

1. Personalized Marketing: Utilizing the detailed customer profile from the golden record to send highly targeted and personalized marketing emails.

2. Customer Retention: Sending retention-focused emails that address the customer’s specific needs and preferences, as identified in the golden record.

3. Feedback Collection (reviews): Requesting feedback on products or services that the customer has used, based on the history stored in the golden record.

When using this resolution, you are selecting unique records based on Individual ID and Business Unit, since an individual can belong to multiple business units. This allows a single communication to be sent based on different brands in the database. You can dedupe records based on the Household ID for the selected records.

Customer Account Summary

Using the Customer Account Summary resolution level allows you to select records based on the Customer Account ID. If you want to send to all customers and all of their potential accounts, this is the correct resolution level to use.

Customer Account Summary resolution use cases

1. Welcome Emails: Greet new customers and provide them with useful information about their account and your services.

2. Anniversary or Birthday Rewards: Celebrating milestones in the customer’s relationship with the brand by offering special rewards or recognition.

3. Educational Content (newsletter): Provide valuable content that helps customers get the most out of your products or services.

4. Anniversary or Birthday Rewards: Celebrating milestones in the customer’s relationship with the brand by offering special rewards or recognition.

A customer could have multiple Accounts within the Customer Account Summary Table, which would allow duplicate messages to be sent to a given customer.

Loyalty Account Summary

Using the Loyalty Account Summary resolution level allows you to select records based on the Loyalty ID. If you want to send to all the loyalty accounts that are available on the database, then the Loyalty Account Summary resolution is the correct resolution level to use.

Loyalty Account Summary resolution use cases

1. Monthly Statement: Informing customers of their current point balance.

2. Points Redemption Emails: Informing customers when they’ve earned enough points to redeem them for rewards or discounts.

3. Bonus Points Campaigns: Running special events where customers can earn extra points for a limited time.

4. VIP Exclusive Rewards: Sending targeted emails to VIP members with special offers, early access to sales, or exclusive content.

5. Tier Advancement Notifications: Congratulating customers when they move up to a higher tier within the loyalty program and explaining the new benefits they’ve unlocked.

A customer can have multiple loyalty accounts associated to their record within the database, which would send duplicate messages to a single customer across all their accounts.

Email BU Summary

Using the Email Summary resolution level allows you to select records based on the Email ID. If you want to send to all the Email addresses that are available on the database, then the Email Summary resolution is the correct resolution level to use.

Email BU Summary resolution use cases

1. Re-engagement Campaigns: Reach out to customers who haven’t interacted with your brand in a while to rekindle their interest.

2. Product Updates and Announcements: Keep customers informed about new products, services, or features that may interest them.

A customer/Individual can have multiple email addresses associated to their record within the database, which would send duplicate messages to a single individual across all their email accounts.

PII resolutions

Golden Record Summary PII

This resolution allows you to segment or select records based on certain PII data, such as name, email address, or location information. These fields can be used within selection rules to target specific records to be used for suppressions. You cannot see the PII data, due to PII security policies set up within the RPI SaaS configuration, along with the database design, but you can see the available attributes to use within selection rules.

This will pull unique records based on the Individual Business Unit ID within the database similar to the Standard Golden Record Summary resolution. Any targeting that is done at the Golden Record Summary resolution will need to use the Golden Record Summary PII resolution to target PII specific information.

Party Profile PII

This resolution level pulls all records that have a Party Profile ID and allows you to segment or select records based on certain PII data, such as name, email address, or location information. These fields can be used within selection rules to target specific records to be used for suppressions. You cannot see the PII data, due to PII security policies set up within the RPI SaaS configuration, along with the database design, but you can see the available attributes to use within selection rules.

The Party Profile ID is used to join to the Customer Account Summary and Loyalty Account Summary tables. Any targeting that is done at those resolutions will need to use the Party Profile PII resolution to target PII specific information.