ePrivacy and GPDR Cookie Consent by Cookie Consent Skip to main content

Setup guide: integrate Genesys loader into CDP

Setup guide is for setting up Meiro Business Explorer, usually it is done by the Meiro team.

PrerequisitePrerequisites for setting up Genesys Loader

  1. GenesysThe destinationfirst needsstep is to beset setup the loader within theMeiro Administration/Entities/Integration Destinationsby tab.

    The prerequisite is thatfollowing the exportinstructions destinationgiven needsin tothis bearticle.

    2. first
  2. Set created byup the Meiroloader team and within the Meiro Integrations.

    Learn more: about how to setas a Genesys destination in MeiroCDP. Integrations.Read here. 

After you finalize all previous steps, you can proceed with exporting segmented customer profiles to the destination. Refer to this article.

Set

Setting up

 Genesys in CDP

DestinationThe destination can be set in the Meiro Business Explorer in the Administration/Entities/DestinationsDestination tab.

The setup is usually done by the Meiro technical consultant.

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:

workspace.png

Check Destination ID in Meiro Integrations:

destination ID MI.png

Insert Destination ID in the Meiro Business Explorer.

image.png

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.




Back to top