Request Data Adapter

The Request Data Adapter surfaces incoming parameter values, like Customer and Activity Attributes, from web URLs or API calls. It allows organizations to obtain data such as campaign codes or customer segments during interactions, which can be passed through URLs or Customer Event APIs. These attributes can be used in real-time for Eligibility Rules, ensuring personalized content is displayed to users redirected from search engines or other requests.

Example

A customer's online search for credit card deals leads them to a bank's promotional offer. By clicking the link, they're directed to a page with detailed offer information.

A mobile phone company leverages a campaign code from a click-through advertisement to present the most relevant offer to the customer at the point of engagement.

Create a Request Data Adapter

  1. In MXO, navigate to Collect and select External Data.

  2. Click Create and specify Request as the adapter type.

  3. Provide a descriptive name and a brief summary for the adapter.

  4. Click Let's get started and enter the necessary configuration details.

  5. Test the configuration with Test configuration, then click Apply and Save.

Integrate the MXO-passed values from your Request Data Adapter by configuring Eligibility or Priority Rules. Use the Data Item Picker in the rule editor to find your adapter under Data Items>Data Adapters. Select it to access and set the attributes for decisioning, as illustrated below.

Choose a data item

Important Considerations

The Request Data Adapter allows you to access data on incoming interaction requests. It does not store the data. This is useful when a customer wants to use the data in decisioning but doesn't want Medallia to store it.

Data storage can be facilitated with Attribute Capture Points.

Historical Activity Attribute values are accessed through the Propositions Data Adapter but the "current context" values, for example those that came in as part of the API properties, can be accessed through the Request Data Adapter. This differs from Customer Attributes where we only surface the last captured values or, if new on the current request, through the Customer Metadata Adapter.