Deep dive into Reltio for Individual Accounts
Learn about the components in Reltio for Individual Account.
This section details the Reltio industry-specific templates you'll use to manage individual account data. Dive in!
Reltio for Individual Accounts account administration
Administration enables you to manage users and provide access to API keys.
Using Administration, you can do the following:
- Invite users
For example, you want to invite your team mates to explore Reltio for Individual Accounts features. The Invite User functionality is available only for the administrators.
For more information, see Invite users.
- Manage Users
After inviting users into Reltio for Individual Accounts, you can edit user details, make users inactive, and delete users. You can also activate inactive users.
For more information, see Administer your Reltio free account.
- Access API keys
In Reltio, you need the API keys to obtain access tokens from the Reltio Auth server. You can use the tokens to use Reltio APIs through the Developer Portal. Using Administration, you can gain access to these API keys.
For more information, see Access the API Keys.
Administer your Reltio free account
Administration enables you to invite, edit, activate, and delete users.
Access Administration
- Click
The Users page is displayed. This page includes details such as the User Name, Full Name, Role, and Status.
.
Invite users
- In the Administration page, click Invite user. The Invite User page is displayed.
- Enter First name*.
This is a mandatory field.
For example, Alan.
- Enter Last name*.
This is a mandatory field.
For example, Kent.
- Enter Email address*.
This is a mandatory field and should be a valid email ID, which is made up of the email id and domain name.
- Select User.
The User role enables you to do all tasks, except User Management and Workflow Approval.
Or
Select Admin.
The Admin role enables you to do all tasks, including User Management and Workflow Approval.
- Click Invite User.
The user is added and listed in the Users page.
Edit a user
- In the Users page, hover over the user whose details have to be edited.
- Click Edit.
The Edit user page is displayed.
- Edit the required field: First name or Last
name. Note: You cannot edit the Email Address of the user.
- Edit the Role, if required.
- Click Save.
The updated user information is displayed in the Users page.
Activate a User
- In the Users page, hover over the inactive user.
- Click Activate.
The user is activated. The Status of the user changes from Inactive to Active.
Deactivate a User
- In the Users page, hover over the active user.
- Click Deactivate.
The user is activated. The Status of the user changes from Active to Inactive.
Delete a User
- In the Users page, hover over the user.
- Click Delete.
The user is deleted and no longer listed in the Users table.
Access the API Keys
- In the Administration page, click API
credentials.
The API credentials page is displayed. In this page, the Client ID, Client Secret, and Authorization details are displayed, which cannot be modified.
- Click Copy.
The Client ID, Client secret, and Authorization are copied. You can use these keys to send a request to the Reltio Auth server to obtain tokens to access your tenant.
For more information about obtaining token access, see Obtaining access tokens with client credentials grant type .
Exploring the Dashboard
The Reltio Dashboard consists of various facets that show the data in the form of charts.
The Dashboard helps you to analyze key information more quickly and thoroughly. It provides a graphical summary of information and you get a consolidated view of all the data in a single page.
You can view various charts on the Dashboard. These responsive charts show relevant data when you hover over on the various graphical portions of the chart. When you click any graphical portion, the drill down results are shown in the search page. For example, if you click on the Male bubble in the Individuals by Gender bubble chart, the Search page appears with the results of the selected Male segment as shown in the images below.
Various Dashboard Facets
Some samples of the dashboard charts are given below.
The chart given below displays the individuals based on their marital status. When you hover over each category, the associated number of results is visible.
This chart displays the number of individuals based on the state.
This chart displays the address verification status of individuals.
This chart displays the data based on the source system.
Understanding the Reltio free account Data Model
The rich Reltio for Individual Accounts free account data model provides a 360-degree view of an individual.
Use the Reltio free account to master personal data. Use your free account to integrate details about individuals that exist across various sources. With the out-of-the-box match rules, Reltio will remove duplicates and generate a golden copy of an individual’s data.
Check out the data model for Reltio free account - including individual profile and attributes.
Individual | Parameter Example |
---|---|
URI | configuration/entityTypes/Individual |
Label | Individual |
Description |
This entity type represents a person entity. |
Abstract | false |
Data Label Pattern | {LastName} {FirstName} |
Attribute Label | Name | Attribute Type | Sub-Attribute Name | Data Type | |
---|---|---|---|---|---|
Full Name | Name | Simple | String | ||
Prefix | Prefix | Simple | String | ||
First Name | FirstName | Simple | String | ||
Middle Name | MiddleName | Simple | String | ||
Last Name | LastName | Simple | String | ||
Suffix | SuffixName | Simple | String | ||
Preferred Name | PreferredName | Simple | String | ||
Title | Title | Simple | String | ||
Nickname | Nickname | Simple | String | ||
Devices Used | DevicesUsed | Simple | String | ||
Web Cookie ID | WebCookieID | Simple | String | ||
Device ID | DeviceID | Simple | String | ||
Alternate Name | AlternateName | Nested | |||
Type Code | Type | String | |||
Type Description | Description | String | |||
First Name | FirstName | String | |||
Last Name | LastName | String | |||
Middle Name | MiddleName | String | |||
Prefix | Prefix | String | |||
Suffix | Suffix | String | |||
Gender | Gender | Simple | String | ||
Role Type | roleType | Enumerated | String | ||
Ethnicity | Ethnicity | Simple | String | ||
Social Media | SocialMedia | Nested | |||
Channel Name | ChannelName | String | |||
Identifier | Identifier | String | |||
Join Date | JoinDate | Date | |||
Active Status | ActiveStatus | String | |||
Policy Consent | PolicyConsent | Nested | |||
Type | Type | String | |||
Effective From | EffectiveFrom | Date | |||
Expiry Date | ExpiryDate | Date | |||
Policy Version | PolicyVersion | String | |||
Time Stamp | TimeStamp | TimeStamp | |||
User/Application | UserApplication | String | |||
Source IP | SourceIP | String | |||
Device ID | DeviceID | String | |||
Cookie ID | CookieID | String | |||
Phone | Phone | Nested | |||
Type | Type | String | |||
Number | Number | String | |||
Country Code | CountryCode | String | |||
Extension | Extension | String | |||
Formatted Number | FormattedNumber | String | |||
Rank | Rank | Int | |||
Area Code | AreaCode | String | |||
Local Number | LocalNumber | String | |||
Validation Status | ValidationStatus | String | |||
Line Type | LineType | String | |||
Format Mask | FormatMask | String | |||
Digit Count | DigitCount | Int | |||
Geo Area | GeoArea | String | |||
Geo Country | GeoCountry | String | |||
Suppress | Suppress | String | |||
Exception | Exception | String | |||
Active Status | Active | Boolean | |||
MultiChannelCommunicationConsent | Nested (within nested) | Nested (Within nested) | |||
Privacy Consent Status | PrivacyConsentStatus | String | |||
Source Type | SourceType | String | |||
Source | Source | String | |||
Effective From | EffectiveFrom | Date | |||
Expiry Date | ExpiryDate | Date | |||
Communication Type | CommunicationType | String | |||
Communication Frequency | CommunicationFrequency | String | |||
Source IP | SourceIP | String | |||
Device ID | DeviceID | String | |||
Cookie ID | CookieID | String | |||
Phone Opt Out | PhoneOptOut | Boolean | |||
Text Message Opt Out | TextMessageOptOut | Boolean | |||
Address | Addresses | Nested | |||
Address Type | AddressType | String | |||
Address Input | AddressInput | Blob | |||
Address Line 1 | AddressLine1 | String | |||
Address Line 2 | AddressLine2 | String | |||
City | City | String | |||
State | StateProvince | String | |||
Country | Country | String | |||
Zip5 | Zip5 | String | |||
Zip4 | Zip4 | String | |||
Verification Status | VerificationStatus | String | |||
Verification Status Details | VerificationStatusDetails | Blob | |||
AVC | AVC | String | |||
Latitude | Latitude | String | |||
Longitude | Longitude | String | |||
DPV Confirmed Indicator | DPVConfirmedIndicator | String | |||
Residential Delivery | ResidentialDelivery | String | |||
MultiChannelCommunicationConsent | Nested (within nested) | ||||
Privacy Consent Status | PrivacyConsentStatus | String | |||
Source Type | SourceType | String | |||
Source | Source | String | |||
Effective From | EffectiveFrom | Date | |||
Expiry Date | ExpiryDate | Date | |||
Communication Type | CommunicationType | String | |||
Communication Frequency | CommunicationFrequency | String | |||
Source IP | SourceIP | String | |||
Device ID | DeviceID | String | |||
Cookie ID | CookieID | String | |||
Email Opt Out | MailOptOut | Boolean | |||
Nested | |||||
Type | Type | Enumerated | |||
String | |||||
Domain | Domain | String | |||
Domain Type | DomainType | String | |||
Username | Username | String | |||
Rank | Rank | Int | |||
Validation Status | ValidationStatus | String | |||
Active | Active | Boolean | |||
Source CD | SourceCD | String | |||
MultiChannelCommunicationConsent | Nested (within nested) | ||||
Privacy Consent Status | PrivacyConsentStatus | String | |||
Source Type | SourceType | String | |||
Source | Source | String | |||
Effective From | EffectiveFrom | Date | |||
Expiry Date | ExpiryDate | Date | |||
Communication Type | CommunicationType | String | |||
Communication Frequency | CommunicationFrequency | String | |||
Source IP | SourceIP | String | |||
Device ID | DeviceID | String | |||
Cookie ID | CookieID | String | |||
Email Opt Out | MailOptOut | Boolean | |||
Status | Status | Simple | String | ||
Status Reason Code | StatusReasonCode | Simple | String | ||
Status Update Date | StatusUpdateDate | Simple | Date | ||
Education | Education | Nested | Education | ||
School Name | SchoolName | String | |||
Type | Type | String | |||
Degree | Degree | String | |||
GPA | GPA | Number | |||
Years in Program | YearsInProgram | Int | |||
Start Year | StartYear | Int | |||
End Year | EndYear | Int | |||
Field of Study | FieldofStudy | String | |||
Year of graduation | YearOfGraduation | Int | |||
Graduated | Graduated | Boolean | |||
Eligibility | Eligibility | String | |||
Type | EducationType | String | |||
Marital Status | MaritalStatus | Simple | String | ||
Privacy Preferences | PrivacyPreferences | Nested | |||
Do Not Process (GDPR) | DoNotProcess | Boolean | |||
Do Not Profile | DoNotProfile | Boolean | |||
Do Not Track | DoNotTrack | Boolean | |||
Do Not Market | DoNotMarket | Boolean | |||
Do not Export Individual Data | DoNotExportIndividualData | Boolean | |||
Ok to Store PII Data Elsewhere | OktoStorePIIDataElsewhere | Boolean | |||
Forget Individual | ForgetIndividual | Boolean | |||
Do No contact | DoNoContact | Boolean | |||
Identifiers | Identifiers | Nested | |||
Deactivation Reason Code | DeactivationReasonCode | String | |||
Deactivation Date | DeactivationDate | Date | |||
Reactivation Date | ReactivationDate | Date | |||
Type | Type | String | |||
ID | ID | String | |||
Status | Status | String | |||
Activation Date | ActivationDate | Date | |||
Date of Birth | DoB | Simple | Date | ||
Year of Birth | YoB | Simple | Int | ||
Date of Death | DoD | Simple | Date | ||
Year of Death | YoD | Simple | Int | ||
Presumed Dead | PresumedDead | Simple | Boolean | ||
Image Link | ImageLinks | Simple | Image URL | ||
Video Link | VideoLinks | Simple | URL | ||
Document Link | DocumentLinks | Simple | URL | ||
Website URL | WebsiteURL | Simple | URL | ||
Description | Description | Simple | Blob | ||
Account | Account | Simple | String | ||
Birth City | BirthCity | Simple | String | ||
Birth State | BirthState | Simple | String | ||
Birth Country | BirthCountry | Simple | String | ||
Delete Entity | DeleteEntity | Simple | Boolean |
Reltio Identity 360 Match Rules
Match rules are combinations of attributes that are used for matching the entities.
The following table lists the six out-of-the-box Match Rules defined for Reltio Identity 360:
Label | Name | Type | Scope |
---|---|---|---|
Rule1:Exact(first, last, addressline1, city, state);ExactOrNull(Middle, Suffix, Gender) |
Rule1 | Suspect for review | All |
Rule1:Exact(first, last, addressline1, city, state);ExactOrNull(Middle, Suffix, Gender) |
Rule2 | Automatic merge | All |
Rule3:Fuzzy(first, Last name);Exact (Identifier Id, Identifier Type) |
Rule3 | Automatic merge | All |
Rule4:Exact(first, last, Zip5);ExactOrNull(Middle, Email Id);Fuzzy(Addressline1) |
Rule4 | Suspect for review | All |
Rule5: Fuzzy (first, Last name);Fuzzy(email, phone)) |
Rule5 | Suspect for review | All |
Rule6:Fuzzy(first, Last name);Exact(Email, Phone) |
Rule6 | Suspect for review | All |
Reltio Identity 360 Relationship Types
Relationships are the links between the entities.
The following table lists the Relationship Types available for the Free and Premium editions of Reltio Identity 360:
Name | Entity Type | Direction | Attributes | Description |
---|---|---|---|---|
Friend | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between Individuals, representing the Friend relationship type. |
Relative | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Relative relationship type. |
Assistant | Individual-to-Individual | Unidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Assistant relationship type. |
Manager | Individual-to-Individual | Unidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Manager relationship type. |
Affiliated with | Individual-to-Organization | Unidirectional | 4: Commenters (String), Title (String), PrefOrActive (String), Rank (Int) | Type of relationship between Individual and Organization, representing the Affiliation with an organization. |
ReferredBy | Individual-to-Individual | Unidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Referred By relationship type. |
Parent | Individual-to-Individual | Unidirectional | 1: Commenters (String) | Type of relationship between Individuals, representing the Parent relationship type. |
Spouse | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Spouse relationship type. |
Sibling | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Sibling relationship type. |
Domestic Partner | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Domestic Partner relationship type. |
Family | Individual-to-Individual | Bidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Family relationship type. |
Influencer | Individual-to-Individual | Unidirectional | 1: Commenters (String) | Type of relationship between individuals, representing the Influencer relationship type. |
Reltio Identity 360 Data Sources
Data may come to the Reltio platform from multiple sources.
The Sources page in the Data Modeler application lists the details of the sources available for your tenant.
The data sources for Reltio Identity 360 are given below.
Source Name | Description | Abbreviation |
---|---|---|
Salesforce CRM | Salesforce CRM - Sales & Service Cloud | SFCRM |
Microsoft Dynamics | Microsoft Dynamics CRM | MSD |
Hubspot | Hubspot CRM and Marketing Automation | HUB |
Marketo | Marketing Automation | MARK |
Abode Marketing | Marketing Automation | |
Salesforce Pardot | Marketing Automation | SFPAR |
Salesforce Marketing Cloud | Marketing Automation | SFMC |
Constant Contact | Marketing Automation | CC |
MailChimp | Marketing Automation | |
Twilio | Communications | TWIL |
PagerDuty | Communications | PAGE |
Zoom | Video and Web Conferencing | ZOOM |
Webex | Video and Web Conferencing | WEBX |
Segment | Customer Data Platform | SEG |
Tealium | Customer Data Platform | TEA |
Lytics | Customer Data Platform | LYT |
ActionIQ | Customer Data Platform | AIQ |
Okta | Identity and access management | OKTA |
OneLogin | Identity and access management | ONEL |
ForgeRock | Identity and access management | FORGE |
SAP Customer Data Cloud (Gigya) | Identity and access management | SAPCDC |
ServiceNow | Customer service & Support | SERNOW |
Zendesk | Customer service & Support | ZEN |
Salesforce Service Cloud | Customer service & Support | SFSC |
Freshdesk | Customer service & Support | FRESH |
Liveramp | Identity Third Party Data | LIVE |
Acxiom | Identity Third Party Data | ACX |
Experian | Identity Third Party Data | EXP |
Infutor | Identity Third Party Data | INFU |
Discover.org | Identity Third Party Data | DISC |
ZoomInfo | Identity Third Party Data | ZINFO |
Qualtrics | Customer Experience | QUAL |
Medallia | Customer Experience | MEDA |
Gainsight | Customer Success | GAIN |
Survey Monkey | Survey | SURV |
Drift | Online Chat | DRIFT |
Hootsuite | Social Engagement | HOOT |
Sprinklr | Social Engagement | SPRINK |
Website | Web form | WEB |
Contact Data File | Contact Data File | CDF |
Reltio Identity 360 Interactions Perspective
Interactions Perspective enables you to manage interactions or events for a profile.
An Interaction is an event that occurs at a particular moment, such as, making a retail purchase, opening an email, opening a support case, or, visiting a website. You can define different types of interactions and their taxonomies in the Business Model.
Interactions can be associated with multiple entities, have an interaction type, and have associated attributes. For more information, see Interaction perspective for Reltio 360 Data Products.
The following table lists the Interactions Types available out-of-the-box for the Free and Premium tiers of Reltio Identity 360:
Name | Attribute | Attribute Type | Description |
---|---|---|---|
Email Opened First Time | Timestamp | The date and time when the user opened the email for the first time. For example, 05/11/2021 9:15:01 PM. | |
Email Opened Last Time | Timestamp | The date and time when the user opened the email the last time. For example, 05/11/2021 9:15:01 PM. | |
Email Sent Time | Timestamp | The date and time when the user sent the email. For example, 05/11/2021 9:15:01 PM. | |
Email Link Clicked First Time | Timestamp | The date and time when the user clicked the email link the first time. For example, 05/11/2021 9:15:01 PM. | |
Email Link Clicked Last Time | Timestamp | The date and time when the user clicked the email link the last time. For example, 05/11/2021 9:15:01 PM. | |
Email link | URL | The Universal Resource Locator (URL) link of the email. For example, test@gmail.com. | |
Product Viewed | Product ID | String | The ID of the product viewed by the user. For example, TR643RYV. |
Product Description | String | The product description. For example, Handmade Special Forces rucksack. | |
Time | Timestamp | The date and time when the user viewed the product. For example, 05/11/2021 9:15:01 PM. | |
Product Link Clicked | Product ID | String | The ID of the product, whose link was clicked by the user. For example, JW892IM. |
Product Description | String | The description of the product link clicked by the user. For example, XX smart phone. | |
Product Link | URL | The URL link of the product. For example, https://aaaa.com/xx-smart-phone/. | |
Time | Timestamp | The date and time when the user clicked the product link. For example, 05/11/2021 9:15:01 PM. | |
Product Shared | Product ID | String | The ID of the product, whose link was shared by the user. For example, JW892IM. |
Product Description | String | The description of the product shared by the user. For example, XX smart phone. | |
Sharing Medium | String | The medium through which the product was shared. | |
Time | Timestamp | The date and time when the user shared the product. For example, 05/11/2021 9:15:01 PM. | |
Product Added to Cart | Product ID | String | The ID of the product added to the cart by the user. For example, JW892IM. |
Product Description | String | The description of the product added to the cart by the user. For example, XX smart phone. | |
Time | Timestamp | The date and time when the user added the product to the cart. For example, 05/11/2021 9:15:01 PM. | |
Product Removed from cart | Product ID | String | The ID of the product, removed from the cart by the user. For example, JW892IM. |
Product Description | String | The description of the product removed from the cart by the user. For example, XX smart phone. | |
Time | Timestamp | The date and time when the user removed the product from the cart. For example, 05/11/2021 9:15:01 PM. | |
Product Searched | Product Search Term | String | The term used to search for the product. For example, handmade rucksack. |
Time | Timestamp | The date and time when the user searched for the product. For example, 05/11/2021 9:15:01 PM. | |
Search URL | URL | The URL link where the product was searched. For example, https://inaaa.com/fashion/handmade-rucksacks.html. | |
Checkout Started | Cart ID | String | The Cart ID when starting the checkout process. For example, 3. |
Time | Timestamp | The date and time when the checkout started. For example, 05/11/2021 9:15:01 PM. | |
Cart Value | String | The value of the cart when checkout started. For example, $62.10. | |
Checkout Complete | Cart ID | String | The Cart ID when completing the chckout process. For example, 3. |
Time | Timestamp | The date and time when the checkout process was completed. For example, 05/11/2021 9:15:01 PM. | |
Cart Value | String | The value of the cart at the time of checkout. For example, $62.10. | |
Form Filled | Form Link | URL | The URL link of the form filled by the customer. For example, https://inaaaa.com/filling-a-form/xj33. |
Time | Timestamp | The date and time when the user filled the form. For example, 05/11/2021 9:15:01 PM. | |
Asset Downloaded | Asset ID | String | The ID of the asset downloaded by the user. For example, TR345TY. |
Time | Timestamp | The date and time when the user downloaded the asset. For example, 05/11/2021 9:15:01 PM. | |
Page Viewed | Page URL | URL | The URL link viewed by the customer. For example, https://aaa.com/rucksack.html. |
Time | Timestamp | The date and time when the user viewed the page. For example, 05/11/2021 9:15:01 PM. | |
Subscribe | Time | Timestamp | The date and time when the user subscribed to the service. For example, 05/11/2021 9:15:01 PM. |
Unsubscribe | Time | Timestamp | The date and time when the user unsubscribed from the service. For example, 05/11/2021 9:15:01 PM. |
Unsubscribe Reason | String | The reason for unsubscribing from the service. For example, Did not sign up for this service. | |
Order | Order ID | String | The ID of the order generated after the user places the order. For example, 820932. |
Order Value | String | The value of the order placed by the user. For example, $92.32. | |
Time | Timestamp | The date and time of the order placed by the user. For example, 05/11/2021 9:15:01 PM. | |
Store Visit | Store ID | String | The ID of the store where the user has placed the order. For example, 293832. |
Store City | String | The city where the store is located. For example, San Franscisco. | |
Store Address | String | The address of the store where the user has placed the order. For example, 123, 1st Avenue. | |
Store Zip | String | The Zipcode of the city where the store is located. For example, 92112. | |
Time | Timestamp | The date and time of the order placed by the user. For example, 05/11/2021 9:15:01 PM. | |
Ad-click | Type of Ad | String | The type of advertisement viewed by the customer. For example, Banner or Video. |
Channel | String | The channel where the advertisement was viewed. For example, email. | |
Time | Timestamp | The date and time the user viewed the advertisement. For example, 05/11/2021 9:15:01 PM. | |
Campaign | Campaign ID | String | The campaign ID followed by the user. For example, 1054. |
Campaign Name | String | The campaign name. For example, Clients Newsletter. | |
Campaign Source | String | The source of the campaign. For example, your email newsletter. | |
Campaign Medium | String | The medium of the campaign. For example, any social media. | |
Campaign Term | String | The term of the campaign. For example, 2 weeks. | |
Campaign Content | String | The content of the campaign. For example, |
Overview of Profiles
A profile is a collection of all the data associated with an entity.
An entity is a customer, supplier, or an employee who form the core of your business. In order to maintian seamless business operations, you must make sure that all entity details are available in your system.
Reltio Identity 360 enables you to create and maintain your entities using profiles. These profiles can be created in the following ways:
- Loading profiles into Reltio
You can use the Data Loader application in Console to load profiles into Reltio Identity 360. For more information, see Get started with Reltio Identity 360 .
- Creating a new profile
You can create new profiles in Reltio Identity 360 using the Profile page in Hub. This page includes various attributes and facets, such as Address, Identifiers, Contact, Relationship, and Privacy Preferences. For more information, see Creating Profiles in Reltio Identity 360.
Creating Profiles in Reltio Identity 360
The Profile page enables you to create and maintain your profiles.
To create a new profile:
Privacy and Consent Preferences
Reltio Identity 360 enables you to specify the privacy and consent preferences of your customers.
When dealing with personal data of customers, utmost care must be exercised since there are laws to protect the privacy of these data. In accordance with the data protection law of the land, it is crucial to obtain legal consent or permission from individuals to process their personal data.
In Reltio Identity 360, consent for customer data can be configured for the following:
- Profile/Entity
You can specify privacy preferences for a customer. For example, whether the individual can be tracked or profiled, or whether their data can be processed in third party systems.
- Policy Consent
When users interact with websites or services, they consent and accept policies such as Privacy Policies or Terms of Services. These policies are tracked within Reltio Identity 360 along with the dates of acceptance and versions.
- Multi-channel communication consent
Multi-channel consent refers to the consent or permissions that customers or individuals have given to organizations. Through consent, a customer agrees to be contacted through different channels of communication. The channel of communication can be Email, Short Message Service (SMS), in-person, or over a phone call. Individuals consent or agree a particular channel to be contacted. For example, some individuals do not want to be contacted through Email or in-person. Instead, they prefer only SMS or phone calls.
Configuring Privacy and Consent Attributes
Configure privacy and consent preferences of the customers.
Configuring Privacy Preferences
- In Reltio Identity 360, select the profile to configure privacy and consent preferences.
- Select Editing.
The profile is displayed in the Editing mode.
- Click Privacy Preferences.
- Select Yes or No for Do Not Process (GDPR) to indicate whether the customer is GDPR compliant. For more information about GDPR, see GDPR compliance in the Reltio Platform.
- Select Yes or No for Do Not Profile to indicate whether the customer can be profiled.
- Select Yes or No for Do Not Track to indicate whether the customer can be tracked.
- Select Yes or No for Do Not Market to indicate whether customer data can be shared with others for advertising purposes.
- Select Yes or No for Do Not Export Individual Data to indicate whether customer data can be exported.
- Select Yes or No for Ok to Store PII Data Elsewhere to indicate whether the customer's Personally Identifiable Information (such as social security details or contact information) can be stored elsewhere.
- Select Yes or No for Forget Individual to specify whether the system needs to forget the user's details.
- Select Yes or No for Do Not Contact to indicate whether the customer can be contacted for notifying information such as new product launch, or updates to existing products.
Configuring Policy Consent
- In the profile, select Policy consent.
- Expand Data Processing.
- Select Type.
This denotes the type of policy being accepted by the user.
- Click the Calendar icon.
- Select Effective From date.
This denotes the date from which the policy is applicable.
- Click the Calendar icon.
- Select Expiry
Date.
This denotes the date till which the policy is applicable.
Configuring Multi Channel Consent Attributes
- In the Contact attributes facet of the profile, click Phone.
- Expand Multi Channel Communication Consent.
- Select Privacy Consent Status.
- Not Seen (NS) - If the customer is not interested in being contacted using the communication type being selected.
- Opt In - If the customer wants to opt for the communication type being selected.
- Opt Out - If the customer wants to opt out of the communication type being selected.
- Seen - If the customer is interested in being contacted using the communication type being selected.
- Select Source Type.
- Enter Source based on the Source Type selected.
- Enter Effective date.
This denotes the date from which the privacy consent status is applicable.
- Enter Expiry date.
This denotes the date till which the privacy consent status is applicable.
- Select Communication Type, which can be Marketing(M), Newsletters(N), or Promotions(P).
- Select Communication Frequency, which can be Daily (D), Monthly(M), Other(O), or Weekly(W).
- Enter Source IP.
This is an alphanumeric field.
- Enter Device ID.
This is an alphanumeric field.
- Enter Cookie ID.
This is an alphanumeric field.
- Select Yes or No for Phone Opt Out to indicate whether the customer agrees to be contacted through phone.
- Select Yes or No for Text Message Opt out to indicate whether the customer agrees to be contacted through SMS.
Data Validation Function for Identity 360
The Data Validation Function (DVF) is now enabled for Identity 360.
By now, you have either loaded data into Reltio Identity 360 using Data Loader or created data using Profiles. This data has to be validated for its accuracy. We have enabled Data Validation Function (DVF) for Reltio Identity 360 to validate the accuracy of the data.
DVF enables you to validate data against a set of validation functions. For more information, see Data validation function.
For Identity 360, the following DVFs have been enabled:
- Social Security Number (SSN)
If the Identifier Type for the profile is SSN, and the format is not as per the recommended format, then a warning message indicating that the SSN is invalid is displayed.
- Email
- The Email address of the entity should follow standards set in RFC-5322. In other words, the email should have an email ID, the symbol @, and a domain name. If this standard is not followed, a warning message is displayed.
- The Email address is mandatory for a profile. A warning message is displayed if the Email address is not entered, or is missing for an entity.
- First name
The First Name of the entity should contain only alphabets. If you enter numbers or special characters, a warning message is displayed.
- Middle name
The Middle Name of the entity should contain only alphabets. If you enter numbers or special characters, a warning message is displayed.
- Last name
The Last Name of the entity should contain only alphabets. If there are numbers or special characters, a warning message is displayed.
- Date of Birth
The year in the Date of Birth specified for the entity must be after the year 1921. A warning message is displayed if the year is before the year 1921.
- Date of Death
The year in the Date of Death specified for the entity must be after the year 1921. A warning message is displayed if the year is before the year 1921.
Reltio Identity 360 - FAQ
Find the answers to Frequently Asked Questions (FAQs) about Reltio Identity 360.
- The Console offers so many applications. Which applications can I access while
using the FREE edition?
The FREE edition of Reltio Identity 360 provides access to UI Modeler, Data Modeler, Tenant Management, Data Loader, Export, External Match, and User Management applications.
- I would like to upgrade from the Reltio Identity 360 FREE edition. What should I do?
To move to a higher edition of Reltio Identity 360, click the UPGRADE button on Hub or Console and we will get back to you to discuss your requirement and take it forward.
- Can I invite my team members to explore the same Reltio Identity 360 FREE edition?
Yes, you can invite your team members to explore the FREE edition of Reltio Identity 360. For more information, see Add more Users.