Feeds Overview
ES Loyalty
Feeds Overview
Feeds are structured, file-based data interfaces that move information into and out of ES Loyalty™. They are the primary integration mechanism for clients that require batch processing, bulk data operations, or scheduled data exchange between their systems and the ES Loyalty platform.
What are feeds?
Every core loyalty operation depends on feeds: member enrollment, transaction processing, point awards, redemptions, tier management, program configuration, and data warehouse synchronization. Feeds give both sides of the integration a defined, versioned, and auditable contract with fixed field specifications, strict naming conventions, PGP encryption, and sequenced delivery via SFTP or AWS S3.
ES Loyalty supports two integration models: real-time API and file-based feeds. Most enterprise implementations use both, with the API handling consumer-facing earn and redemption flows, and feeds covering bulk operations, configuration management, and downstream analytics.
Inbound and outbound
Feeds run in both directions.
Client to ES Loyalty
Keeps the platform synchronized with the client's systems by loading member records, submitting purchase transactions and activity events, applying rewards and redemptions, and maintaining program configuration such as product catalogs, store locations, partner programs, and tier structures.
ES Loyalty to client
Carries processed loyalty data back to the client. Operational outbound feeds return validation results and reject records from inbound processing. Data warehouse outbound feeds, delivered via Snowflake data sharing, surface member accounts, transactions, redemptions, promotion attribution, fulfillment records, and targeted offer assignments — the primary data source for analytics, reporting, and business intelligence.
Key value for technical teams
Feeds are designed to integrate cleanly with existing enterprise data infrastructure.
Defined contracts
Each feed has a fixed schema, field types, required and optional designations, and validation rules.
Sequenced delivery
File naming encodes sequence numbers, enabling ordered processing and gap detection.
Reject and audit trail
Records that fail validation are returned in reject feeds with error codes, giving engineering teams a clear path to diagnosis and resubmission.
Encryption
Inbound files containing sensitive member data are PGP-encrypted in transit.
Flexible scheduling
Feed frequency is configured per client, from real-time near-batch to daily or weekly cycles depending on operational requirements.