Skip to content

Getting Started with FeedXChange

Getting Started with FeedXChange

This tutorial guides you through configuring FeedXChange to integrate ReactorCX (RCX) with external systems (such as partner systems or a customer relationship management (CRM) tool). It uses a fictitious retail chain called Acme Pet Shop and a fictitious partner, a pet resort and spa called PAWs Resorts.

Example

Acme Pet Shop creates a loyalty program in RCX called Acme Pet Loyalty Rewards. Through a partnership agreement with PAWs Resorts, program members who board their pets at the resort earn points they can spend at Acme Pet Shop.

Because PAWs Resorts doesn't connect directly to the ReactorCX API, the resort periodically saves the relevant data to a file in an AWS bucket. FeedXChange connects to that bucket and downloads the new files on a schedule. FeedXChange then processes the files and sends the updates to RCX for all Acme Pet Loyalty Rewards members who boarded their pets at the resort. This enables the members to receive rewards for using the Acme Pet Shop partner.

Logging In to FeedXChange

Your customer success manager provides the address and login credentials specific to your account.

Exploring the Dashboard

The FeedXChange dashboard displays a summary of all the integrations that have run in the system recently:

FeedXChange dashboard showing navigation menu on the left with options Dashboard, Partners, Connections, Templates, Integrations, and Run History. The main area displays summary cards for Failed Runs, Success Runs, Failed Integrations, and Success Integrations, each with counts and trend indicators. A Recent Operations section lists failed and succeeded integration runs with columns for Run ID, Name, Status, Start, End, and Duration.
Figure 1. FeedXChange Dashboard

The dashboard shows integration runs for:

  • The past day
  • The past week
  • The past month

It provides basic metrics and trends for the integration runs. The dashboard also provides a list of the integrations that have most recently succeeded or failed, or are currently running.

An integration is a process that you can run once or on a recurring basis. It's defined by a set of rules and criteria that determine when the process runs, what types of files FeedXChange accepts, and what types of files it produces.

A run is a single execution of an integration.

You can click the Run Id for an integration to open the Run History view where you can view the details of the run.

Exploring the Run History

After you create and run an integration, you can monitor the results from the Run History view.

The Run History view displays a list of all integration runs. You can filter them by status, run ID, integration name, and for a date range. You can also search for a run by the integration name or the run ID.

FeedXChange Run History screen showing a table of integration runs with columns for Integration Name, Run ID, RCX Process, Status, Start, End, Duration, Succeeded, Failed, and Actions. The table lists five runs with statuses such as Failed, Processing, and Succeeded. Above the table are filters for Integration Name, Run ID, date range, and a search bar. Tabs enable switching between All, Failed, and Succeeded runs.
Figure 2. FeedXChange Run History view

The icons in the Actions column enable you to view run logs or run details:

  • The Logs () provide detailed information about the run, which can be used to troubleshoot any issues that may have occurred.
    • To find a particular log entry, use the search option in the dialog box. If the search yields more than one result, press <Enter> to cycle through them.
    • To download the log file to view with other tools, click Download Log.

  • The run Details () give you easy access to the input and response files for the run. The Integration Details dialog box displays:

    • Name: The name of the integration
    • Run ID: A unique identifier for the integration run
    • Input File Name: The filename of the input file, fetched from the source server, on which the integration ran
    • Response File Name: The filename of the response file FeedXChange generated after the integration run

    Icons enable you to copy () the text displayed for the associated field and download () the input and response files.

Before you can create and run integrations, you must create:

  1. One or more partners
  2. One or more connections
  3. One or more templates

See also: