Introducing FeedXChange

Introducing FeedXChange¶

The FeedXChange guides provide the definitive documentation for FeedXChange. They explain the purpose of each function, how to use it, and provide definitions for each field on the screens.

This documentation has four sections:

Tutorials walk you through creating components to configure FeedXChange.
Explanations describe the purpose of each component and the concepts for their use.
How-to Guides provide step-by-step instructions to configure the FeedXChange components.
References define each field and its limits, such as maximum length or value.

This documentation provides the basis for ReactorCX administrators to configure batch processing for systems that don't connect to RCX using the REST API.

About RCX and FeedXChange¶

The ReactorCX (RCX) platform runs loyalty programs to reward your repeat customers. Your front-end system connects with RCX using the ReactorCX REST API, ensuring loyalty-related data is updated in real time.

Some systems, such as a customer relationship management (CRM) system or some coalition partners, might not. In those cases, FeedXChange downloads data from those external systems in batches and processes partner accruals, enrollments, and bulk changes to members and reference data.

Figure 1. Overview of how FeedXChange fits into the RCX ecosystem

A back-end system (such as a CRM or partner system) processes segments or transactions.
Third-party or internal data are saved in an AWS bucket or on an SFTP-accessible server.
FeedXChange downloads the input file containing the data.
FeedXChange processes the file and sends the data to the RCX API.
FeedXChange receives the results from the API and generates a response file containing those results.
FeedXChange uploads the response file to the AWS bucket or SFTP-accessible server.

FeedXChange uses an intuitive interface to define file templates and validation criteria, response file generation rules, and other metadata describing how feed inputs and outputs work. You can also use it to schedule and run those integrations on a recurring basis.

One of the key principles of FeedXChange is that it adapts RCX to your existing file formats, rather than forcing your source system to convert data to a single format. This enables RCX implementations to be quicker and more efficient, because you don't have to redesign or convert existing file formats.

FeedXChange is also an operations manager tool, issuing alerts, providing dashboards for monitoring and reporting, and providing a user interface to investigate issues with individual batch process runs.

Why Use FeedXChange?¶

Format Flexibility¶

Flexible file format - FeedXChange accepts delimited and fixed length files
Multiple connection types - SFTP and S3 support
Rich validation - Comprehensive field validation and error reporting

Operational Excellence¶

Automated scheduling - Run integrations on your timeline
Comprehensive monitoring - Dashboard and run history tracking
Proactive alerting - Email notifications for successes and failures
Dependency management - Coordinate complex multi-integration workflows

Security & Reliability¶

Partner isolation - Each partner can only see their own data
Encrypted connections - Secure file transfer with GPG encryption support
File archiving - Automatic archival of processed files
Retry logic - Configurable retry mechanisms for failed operations

Quick Start¶

New to FeedXChange? Follow this path:

Start here: Getting Started Tutorial - Explore the dashboard and understand the workflow
Learn concepts: Core Concepts - Understand what each component does
Follow the tutorials: Complete the tutorial sequence to build a sample integration
Reference as needed: Use How-to Guides and References for specific tasks

Have existing integrations? Jump to How-to Guides for specific configuration tasks.

Core Concepts¶

FeedXChange uses four main components that work together in sequence:

1. Partners → 2. Connections & Templates → 3. Integrations

Partners (Create First)¶

A partner represents an organization in your loyalty program ecosystem, whether your own company or external partners like retailers, hotels, or service providers.

Key point: Every other component belongs to a specific partner.

Hosting partners can see all integrations across the program
Coalition partners can only see their own resources

Connections (Create After Partners)¶

A connection defines where FeedXChange can access files, whether an SFTP server or AWS S3 bucket. Each connection is partner-specific and stores authentication credentials.

Supported types: SFTP, S3 (Amazon Simple Storage Service)

Templates (Create After Partners)¶

A template is the blueprint that tells FeedXChange how to read and validate incoming files, and what response files to generate. Templates are associated with specific RCX processes.

FeedXChange supports the following types of processing within RCX:

Process Name	Description
Activity	Enables processing of bulk accruals (such as partner accrual feeds) and redemptions (such as point transfers or other expenditures coming from external sources).
Enrollments	Enables processing bulk enrollments of new members with optional duplicate matching by combinations of fields.
Member Segments	Enables bulk assignment of segments to members based on external segmentation sources.
Member Preferences	Enables bulk setting of member preferences and member-level loyalty feature flags. You can add preferences, but updating existing preferences isn't supported.
LoyaltyID	Enables adding a loyalty ID to members.
Profile Update	Enables updating member profile data.

Note

Any process based on RCX member activity can autoenroll the member with only their loyalty id and receive profile updates as they become available.

Integrations (Create Last)¶

An integration brings together a partner, connections, and template to create an automated workflow. It defines:

Which files to process (input path and file patterns)
Where to save results (response directory path and file patterns)
When to run (scheduling)
Who to notify (alerts)
Which integrations it depends on (dependencies)

Common Use Cases¶

Coalition Program Setup¶

Hosting partner: Your organization (manages the loyalty program)
Coalition partners: External partners (hotels, retailers, and so on)
File exchange: Partners submit transaction files, receive confirmation files