Data Sharing

Abstract

This document defines the data sharing requirements for Publisher Partners collaborating with Cardlytics to deliver a seamless offers and cash-back experience. It covers the types of data feeds, data scope, and specific fields needed for both historical and daily transaction data, along with customer and account data when such information isn’t sourced through other providers (e.g., Plaid).

Overview

Purpose of Data Sharing

Cardlytics requires Publisher Partners to share customer, account, and transaction data to enable personalized and effective cashback offers for customers.

Types of Data Feeds

1. Historical Data Feeds: A 12-month "look-back" dataset is required before the program launch to target customers based on past behavior.
2. Daily Data Feeds: Continuous data updates are necessary to support ongoing operations.

Data Scope

• Data pertains to current eligible customers and open accounts only.

Key Data Requirements

1. Customer and Account Data:
   • Unique customer and account identifiers (e.g., sourceCustomerId, sourceAccountId).
   • Additional attributes such as postal code, country, and portfolio ID to maintain accurate customer profiles.
   • Customer data is designed to protect consumer privacy by avoiding direct exposure of actual customer numbers.
2. Transaction Data:
   • Detailed transaction information (e.g., transactionId, transactionType, authorizationAmount).
   • Merchant-related fields such as category codes, merchant name, city, and postal code.
   • Timestamp fields to record transaction occurrence and posting times.
   • Currency and transaction amounts are standardized for consistency.

Summary of Requirements

• All required fields are clearly defined with examples and formatting instructions.
• Privacy considerations are emphasized, ensuring unique identifiers are used without exposing sensitive customer or account information.

Types of Data Feeds

Two primary types of data feeds are utilized:

• Historical or “look-back” data: This data is loaded prior to the "Go Live" date and enables the targeting of customers with relevant offers based on their past spending behavior.
• Daily data feeds: These feeds support the continuous operation of the Cardlytics system.

Historical Transaction Data

An initial export of 12 months of historical transaction data is necessary to enable effective targeting at program launch for all eligible customers.

Customer/Account/Card

• https://platform.cardlytics.com/publisher-integrations/reference/create-customers

Transaction

• API Reference Transaction Notification.