Quick Start Guide

Hello and Welcome to Reltio! The following information will help you get started on your journey to Be Right Faster.

By now, you must have received the Reltio Asset Sheet listing the Reltio assets provisioned for you.

What comes with your Subscription

With the license, you have a Base Package of three pre-configured tenants:
  • Production-ready PROD tenant
  • DEV tenant
  • TEST tenant

Use your Asset Sheet to understand what has been provisioned for you, and get started on your way to value with the Reltio Connected Data Platform.

Customer Account ID

This is the internal identifier for your account. Please use this ID or a specific tenant ID when submitting support tickets.

Geographic Region of Tenants

This is the geographic region within which your Reltio tenants have been provisioned and where your organization’s data will reside.

Reltio Solution Applied to your Tenants

Your DEV, TEST and PROD Master Data Management (MDM) tenants and their accompanying Reference Data Management (RDM) tenants are pre-configured to closely support your business requirements. The Reltio Platform is configured for your industry-specific entity types, relationship types, reference data and match rules. This strategy serves as an accelerator to deliver greater value faster.

Your MDM DEV tenant is prepopulated with a small set of sample records that help demonstrate the use of the platform’s model. You can choose to delete them.

Note: For some accelerators such as Account 360 solution, your license may include additional accessories such as the "Dun and Bradstreet connector" and the "Salesforce connector". Additional information is available about the Information Model and Solution Accelerators.

Countries for Address Cleanse

Reltio provides address cleansing as an intrinsic capability. The actual geographies for which cleansing is enabled is part of your license contract and specified here. The Address Cleanser uses the Default Country if an address passed to the cleanser fails to provide a country. For any changes needed, contact your Customer Success Manager.

Connectors Installed

Reltio provides connectors to 3rd party applications to accelerate the integration and value of Reltio with other applications. If you licensed any connectors from Reltio, they are listed here.

Dun & Bradstreet Connector

If you licensed Reltio’s Dun & Bradstreet connector, you can manually get real-time matches and enrichment from Dun & Bradstreet for individual account records. You can also automatically send batches of records to Dun & Bradstreet for enrichment and matching. Both modes of operation will provide the “corporate upward linkage” the Parent/HQ, the Domestic Ultimate and the Global Ultimate organizations will be returned from Dun & Bradstreet and will be linked to the original record sent for enrichment.

Salesforce Connector

Salesforce (salesforce.com, or SFDC) is a CRM platform used for customer relationship management solutions. Salesforce Connector provides integration between Reltio Platform and Salesforce-based solutions such as Veeva leveraging the capabilities of the Salesforce platform.

The major use cases for utilizing Salesforce Connector are:

  • Bi-directional Synchronization
    • Seamlessly synchronize Add, Update, Delete, Merge, and Unmerge between MDM and Salesforce to improve consistency of data
    • Manage affiliations/relationship Add, Update, and Delete across MDM and Salesforce
  • Search Before Create
    • Powerful three-step search process embedded directly in Salesforce to improve productivity and reduce the introduction of duplicates

Data Tenants Subscribed

Data Tenants are pre-configured and pre-populated to provide popular industry-specific, 3rd party data for enrichment to your tenants. If you licensed any Data Tenants, your DEV, TEST and PROD tenants are already subscribed to them. See Data as a Service for additional information about Data Tenants and Data Tenant Subscription Service (DTSS).

Customer Administrator

With the provisioning of your assets, one or more persons from your organization have been given the role of Customer Administrator for the Subscription ID listed. It is typically their job to then create business users and/or Tenant Admins. The Customer Admin can also create additional Customer Admins.
  • A business user is a user that your Customer Admin will create and give certain business-oriented roles to, depending on how you plan to use the Reltio solution.
  • A Tenant Admin is a user the Customer Admin will create and then give the role of ROLE_ADMIN_TENANT. The Tenant Admin has access to the configuration API, and can make configuration changes using the Reltio Console as can the Customer Admin. These individuals can also use the configuration API to make configuration changes.
  • A Customer Admin can log into any of the tenants registered to your Customer Account. Locate the URL of any of these tenants, enter it into your browser, enter the username and password listed. Alternatively, you can log into Console, see your registered tenants and click the link to log directly into a tenant.

See Setting Up Additional Users for detailed instructions.

Console URL

The Reltio Console is used by the Customer Administrators and Tenant Administrators. It is typically used for activities such as managing your platform’s configuration, environment, and performing exports, creating Workflows and checking the operational health of your tenants.

At the prompt, enter the tenant ID of your DEV, TEST or PROD MDM tenants. For example, “QyqSCp5r8gMwFYL” found in the URL of the tenant.

The Reference Data Management tenants are managed from a separate RDM console. See RDM URL for more information.

See Console for more information.

Data Science Information

If you have licensed Data Science, the following assets are included:

Qubole Account Link

Reltio partners with Qubole to manage the computing resources used by Reltio IQ. An account with Qubole has been provisioned for you. Use the Qubole account link provided to log in and perform the following activities:

  1. Define, Manage, and Maintain your Analytic models
  2. Define Scala-based notebooks
  3. Track and manage your Analytic node hour usage

Data Science URL

Much of the work you do with Reltio IQ will be performed within a Qubole Notebook or through Reltio IQ APIs. You must specify the Reltio Insights URL listed here to interact with Reltio IQ APIs. The use of a Qubole Notebook and Reltio IQ APIs is covered in more depth in the Reltio IQ topic, and in the Reltio IQ training course.

Data Science Usage

Through the Console you can track the node hours and storage usage related to the Reltio IQ Connector. Additionally, through the Qubole UI you can track the Analytic Hour usage (Spark Hours) and Analytic users.

MDM - Tenant Info

Most customers are provisioned three tenants:
  • DEV tenant where you will develop/modify new configurations
  • TEST tenant where you will test your configuration will a volume of data and various accessories (for example, integrations) that mimic your production tenant
  • PROD tenant where you will deploy the configuration.

This section of your Assets Sheet provides the details of each tenant, the tenant’s associated queue, and RDM tenant.

Often during development cycles you will find it necessary to copy your PROD tenant to your TEST tenant, then apply a new configuration from your DEV tenant to your TEST tenant. Performing this copy is part of your entitlement and can be accomplished by filing a support ticket. Typical entitlement for this service is one copy per month. Only the Customer Admin can request this service.

Name for Tenant

Your new tenant is given a default name which appears in the top right corner of the HUB after you log into the tenant. You can easily modify the tenant name via an API call. See Set tenant name section of the Reltio API documentation.

Record Capacity for Tenant

You are entitled to a capacity of 200,000 records in your DEV tenant. Your TEST tenants are entitled to the same volume as your PROD tenant.

MDM Tenant URLs

MDM Tenant UI URL - This is the MDM tenant’s primary URL. Business users will use the URL provided in the section associated with your PROD tenant. Customer Admins and Tenant Admins will often additionally log into the MDM DEV and MDM TEST tenants for various purposes. (“MDM” is used to distinguish these tenants from your RDM tenant, described below).

If you have access to the Console (see section on Console), then you can also log into your tenants via the console by clicking on the hyperlinked tenant URL in a drop down box.

MDM Tenant API URL - When accessing your tenant programmatically from a calling application, use the API version of the tenant’s URL.

MDM tenant auth URL - When a calling application wishes to make an API call to the tenant, it must obtain a token using the auth URL shown. Refer to the Authentication API documentation for more information.

MDM Tenant SQS Queue Info

Your tenant may have been provisioned with an AWS SQS queue, or a GCP Pub/Sub queue. If the former then the following information has been provided in your Asset Sheet. It provides the details of the queue that has been provisioned and linked to the tenant listed in the same section. To access the queue, a calling application or client needs only the queue name and set of keys.

The SQS queues are disabled at the time you receive this information. To enable a queue, contact your Customer Success Manager, or submit a support ticket.

MDM Tenant SQS Queue Name - Provides the name of the queue

MDM Tenant SQS Queue URL - Provides the URL of the queue

AWS Access Key and AWS Secret Key - Provides the keys for the queue

MDM Tenant, GCP Pub/Sub Info

Your tenant may have been provisioned with an AWS SQS queue, or a GCP Pub/Sub queue. If the latter then the following information has been provided in your Asset Sheet. It provides the details of the Pub/Sub component provisioned and linked to the tenant listed in the same section. To access the Pub/Sub, a calling application or client needs only the Project ID, Subscription Name and Private key ID JSON file.

The Pub/Sub queues are disabled at the time you receive this information. To enable a Pub/Sub queue, contact your Customer Success Manager, or submit a support ticket to Reltio Support.

MDM Tenant Pub/Sub Project ID - Provides the Pub/Sub Project ID

MDM Tenant Pub/Sub Subscription Name - Provides the Pub/Sub Subscription Name

Google Private key ID - Provides the Pub/Sub Private key. Example: "d91………………………………...z77"

Reference Data Management Tenant Information

Each of the MDM tenants provisioned for you has been linked to a supporting Reference Data Management tenant which has been prepopulated with industry specific reference data supportive of the Reltio Platform used to preconfigure your MDM tenants. If you wish to modify these associations, know that the association of an MDM tenant with an RDM tenant has been performed via the L3 configuration of the MDM tenant. Using this approach the MDM tenant can reference one and only one RDM tenant, but multiple MDM tenants can reference and thus be associated with the same RDM tenant. If you require your MDM tenant to utilize more than one RDM tenant simultaneously, you must remove the RDM reference from your L3 configuration, and instead file a ticket with Reltio Support. k

Additional Reference Data Management information can be found at: Reference Data Management (RDM)

Reference Data Management Tenant ID - This is the unique identifier for the RDM tenant. When logging into the RDM Console at RDM UI URL (see below), use this identifier at the prompt.

Reference Data Management UI URL - Use this URL to access the RDM Tenant Console. Typically rdm.reltio.com

Reference Data Management tenant Auth URL - When a calling application wishes to make an API call to the RDM tenant, it must obtain a token using the RDM tenant auth URL shown. Refer to the Authentication API documentation for more information.

Reference Data Management API URL - API endpoint, for applications wishing to make API calls to the Reference Data Management tenant.

Setting up Additional Users

Only a person given the role of Customer Admin has the permission to create additional users. Typically it will be important to create one or more Tenant Admins and a collection of business users. The Tenant Admin role can perform tenant configuration. The business user role will be utilized by data stewards and people within the business units that need to access/edit/enter data. If you intend to create numerous user accounts then it probably makes sense to define a Group with the proper roles in it, then add that Group to each User Account you create.

Log into Console and navigate to the User Management application. Follow the guidance provided in the Reltio Documentation portal. For either type of user, plan to add the following 3 roles: ROLE_USER, ROLE_API, ROLE_UI_ALL.

If creating a Tenant Admin, you must additionally add the following role to the User Account: ROLE_ADMIN_TENANT.

Setting up a User Profile to Represent a Process

Note: If you are inventing a user profile for use by a process (rather than a human user), feel free to invent a process-styled username that does not have an “@” symbol or domain.

An example of an acceptable username for this is “sys-admin-process100”. For the email field, you will need a classically formatted email address however and email addresses must be unique to each profile. A common strategy for complying with this and enabling a human user to receive email notifications triggered potentially by an action taken by the logged-in process, is to create an enumerated email address for a real user and instantiating that email address in your corporate email server as an alias of the human user’s real email address. For example, if John Smith should receive email notifications on behalf of the process “sys-admin-process1”, then the email address given to the profile for sys-admin-process1 could be john.smith1@acme.com. And the email administrator of your company must set up john.smith1@acme.com as an alias for john.smith@acme.com. Example below:

It is recommended that you have more than one Customer Admin established for backup purposes as Reltio’s best practice is for the customer to control all user access.

Engaging with Reltio

This section provides resources for engaging with Reltio as you become familiar with your licensed assets and the Reltio platform.

Reltio Documentation - Many questions can be answered from our documentation at https://docs.reltio.com.

How to use Reltio Technical Support

Our Technical Support organization supports the following request types:
  • Report an Issue
  • Ask a Question
  • Request a Technical Task
  • Suggest a new feature or Enhancement
  • Contribute Content

There are generally two ways to file a support request as follows:

From HUB - If you are using the Reltio Connected Customer 360, you will see a button in the bottom right corner of the screen called Send Feedback. This is the easiest way to file a support ticket and is particularly efficient when Reporting an Issue because all of the relevant info about your current circumstance is included automatically in the ticket.

Log into Reltio Support - The Customer Admin or designated contacts can visit Reltio Support and use their tenant credentials to log in and submit a ticket.

Designated Contacts

Designated Contacts are the persons within your organization designated as Customer Admin and/or Break/Fix contacts. At the time your Assets was created, Reltio received a set of names your organization identified for these roles, and they have been documented within our system as the designated contacts. Only designated contacts within your organization must be submitting support requests to Reltio. Either a Customer Admin or a Break/Fix contact can submit a ticket that reports a bug or trouble with a feature. However, if you wish something invasive to be done to your tenants (For example, “copy my prod tenant to my test tenant”), then we will perform that invasive action ONLY if submitted by a Customer Admin.

Your support plan with Reltio indicates how many designated contacts you are entitled. Feel free to identify others whom you wish to designate up to the level of your support plan. Make Reltio Support aware of the names and email addresses of those individuals by submitting a support ticket with that information. Your Designated Contacts is the sum of your Customer Admins and Break/Fix persons and may not exceed the numbers shown below.

Table 1. Plan and Designated Contacts Details
Support Plan Number of Designated Contacts
Standard 2
Premier 6
Concierge 12

Outage and Security Contacts

In addition to the Designated Contacts which are used for support purposes, Reltio also keeps on file the names of persons for the following purposes:

Outage Contact: These are the persons Reltio may contact proactively if your system becomes inactive or encounters any other problematic behavior.

Security Contact: These are the persons Reltio will contact proactively if Reltio Cloud experiences a security breach.

How to log into Reltio Support

As the Customer Admin and/or Break/Fix contact named in the Asset Sheet sent to you, you must be able to log into Reltio Support using the same credentials (username and password) as you would use when logging into a Reltio tenant. Once completed, you must plan to use the Reltio Login page to change your password. In this configuration of your solution wherein SSO is not being utilized, your Reltio tenant credentials will continue to serve as the credentials you use for logging into Reltio Support.

More information can be found at http://www.reltio.com/support

Logging into Reltio Support with SSO (Single Sign-on)

If you are a Customer Admin or Break/Fix contact, and during implementation of your Reltio solution your organization has elected to utilize SSO for logging into Reltio tenants, then the credentials you last used for logging into Reltio Support (see previous section) will continue to work, even though it is likely that your credentials for logging into a tenant will change due to the SSO implementation. Plan to store both sets of credentials and use them accordingly.

Changes to your Designated Contacts

As mentioned, your support plan articulates how many Designated Contacts you may have for your subscription. You may change who these people are as long as the number of Designated Contacts doesn’t exceed your entitlement. To make a change to the identified persons for these roles, a current Customer Admin must submit a ticket to Reltio Support notifying us of the change.

If your implementation is not SSO-enabled, Reltio support will make the change which generally means that the person will be given a user account in the Reltio Cloud and sent a set of credentials. The person can then access the Reltio Support site, Reltio Documentation portal, and can be given access to tenants by the Customer Admin.

If your implementation is SSO-enabled, Reltio support will make the change which generally means that the person will be given a set of credentials for logging into the Reltio Support site and the Reltio Documentation portal. Any access the person needs to actual tenants will be managed through the SSO system within your solution.

Providing Access to the Reltio Documentation Portal

If your implementation is not SSO-enabled, then anyone who has a log in to a Reltio tenant automatically can access the Reltio Documentation portal. If your implementation is SSO-enabled, then tenant login credentials are stored in your authentication system and are not known to Reltio’s internal systems. In order for those users to gain access to the Reltio Documentation Portal, you must submit a support ticket to Reltio Support asking for that access and providing to us the name and email address of the person or persons.

Your Customer Success Manager

Reltio has a dedicated Customer Success Team to ensure our customers are consistently realizing measurable value with a superior customer experience.

Customer Success team will be involved throughout your customer lifecycle, working as your advocate and trusted advisor. Your Customer Success Manager may have already reached out and introduced himself.

Your Account Executive

Your Account Executive works closely with you and the Customer Success team throughout your customer lifecycle managing the ongoing business and commercial relationship between you and Reltio.

We hope this information is helpful in getting you started quickly with Reltio Connected Data Platform. Please contact the Reltio Support or your Customer Service Manager or designated contact for any queries.