Genesys destination

Prerequisites for setting up Genesys Loader

1. The first step is to set up the loader within Meiro Integration by following the instructions given in this article.
   

After you finalize the first step, you can proceed with the following:

2. Set up the loader as a destination in CDP. This step is described below in this article.

3. Export segmented customer profiles to the destination. Read here.

Destination ID (required, not editable)

"The Destination ID" is a numeric value that analysts will refer to within the Meiro Integrations environment. After you choose the ID, it will not be possible to change it later on.

Find the right workspace in Meiro Integrations, with  the CDP component responsible for the data load:

Check Destination ID in Meiro Integrations:

Insert Destination ID in the Meiro Business Explorer.

Name (required)

The name will be visible across the Meiro Business Explorer for the users (Data Library/ Destination tab, segment detail)

Description (optional)

It is possible to add a description to the destination. The description will be displayed for use in the Data Library/ Destination tab.

Icon (required)

The icon will be visible across the Meiro Business Explorer for the users (insights, Data Library/  Attributes, Sources and Destinations tabs,  segments, and customer profiles).

Exported & Mandatory   attributes

(required)

"Exported attributes" - values of exported attributes will be sent to the dedicated Meiro Integrations workspace, then to the destination.

"Mandatory attributes" all customers in the export must have those attributes' values known.

For this destination, both "exported attribute" and "mandatory attribute" are:

Exported Attributes: Phone number is required. Other attributes are optional, depending on the use case (e.g. Name, Product Recommendations, Consent). 

Mandatory Attributes: Phone number

Meiro Integrations

(required)

"MI workspace" refers to the workspace in Meiro Integration which will be executed when the segment is exported.

To run exports you need to know the name of the workspace. You should get the name of the respective workspace from the Meiro data analyst.

Meiro data analyst takes care of the Meiro Integration's workspace preparation, and data transformation for a specific destination (e.g. Facebook, Twitter, Google Analytics). Each destination requires a different (very specific) data structure.

Parameters: one of list-name or list-id is required

Meiro Integration key: one of list-name or list-id is required

• If list-id is provided the component will expect the list already exists and will update the contacts in it

• If list-name is provided the component will create the list with the given name and populate it

If both list-id and list-name are provided the component will update the contacts, however, will NOT rename the list in case a different name is provided

User Input: ticked

This field is required to be filled in order to Genesys.

Exportable

Exportable shows how many customer profiles will be exported to your destination.

This number is defined by the conditions you choose to segment the audience but also by mandatory attributes that have been set up by the administrator (that must be present to export to your destination).

For example, if you segment 1000 profiles but only 10 profiles have mandatory attributes present, only those 10 will be exported to your destination.

Mandatory attributes are visible in the Data Library/ Destinations tab.

For exports to Genesys, the mandatory attribute are:

Phone Number

Parameters

One of  list-name or list-id is required

• If list-id is provided the component will expect the list already exists and will update the contacts in it

• If list-name is provided the component will create the list with the given name and populate it

If both list-id and list-name are provided the component will update the contacts, however, will NOT rename the list in case a different name is provided

Data Requirements

Input file structure

• Component expects CSV input file

Example:

{
     "upload_contacts": {
      "enabled": true,
      "clear_contact_list_before_upload": false,
      "file_name": "upload_contacts.csv",
      "id_column": "id",
      "callable_column": "callable",
      "contact_list_id": "contact",
      "contact_list_name": "meiro_test",
      "column_names": [
        "id",
        "first_name",
        "phone_number",
        "callable"
      ],
      "phone_columns": [
        {
          "column_name": "phone_number",
          "type": "home"
        }
      ]
    },
 }

Does export create a new audience or update an existing one?

If list-name is provided the component creates a new Contact List

If list-id is provided the component updates contacts in the Contact List. 

The Contact List must exist in this case or the component will fail.

Can I add a new contact list?

Yes. When you provide a list-name but no list-id the component created a new Contact List.

Can I update the existing contact list with new customer profiles?

Yes. Provide an existing list-id, and the component will add or update the contacts in the list. Contacts are never deleted from the list.

Are there any limits for exports?

There are no (known) limits on the number of contacts.

What data is exported to Genesys?

In the most simple use case, only emails will be exported to Genesys. However, additional attributes can be exported as well, including nested JSON objects.