Abstract

This document presents integration options for brands seeking to implement Cardlytics-powered user experiences within their digital platforms. Two primary approaches are detailed:

Publisher-Built User Experience: The publisher uses the Cardlytics API to build and host a fully customized user experience within their own app or website. This method offers maximum control and flexibility but requires more development effort, especially when adopting new features. The estimated time to market is 4 weeks.
Cardlytics-Built User Experience: The publisher integrates a pre-built, white-labeled Cardlytics experience via SDK/Hosted, embedding it within their app or site. This approach delivers an out-of-the-box solution with minimal development work required for new features, enabling a faster launch (2-4 weeks), though with less customization.

Comparison tables highlight key features, integration mechanisms, user experience control, development timelines, maintenance needs, and resource requirements for each option, helping organizations select the integration strategy that best fits their technical capabilities and business needs.

Integration Options

Publisher-Built User Experience

How It Works

Publisher leverages the Cardlytics API to build and host the user experience within their app/site.

Maximizes control of user experience
Development work required for new feature adoption

Time to Market: 4 weeks

Publisher-Built User Experience

How It Works

Publisher integrates a pre-built, white-labeled user experience within their app/site via SDK/Hosted.

Out-of-the-box user experience
Minimal development work required for new feature adoption

Time to Market: 2-4 weeks

Integration Comparison: Brands

Feature	Publisher-Built	Cardlytics-Built (Embedded)	Cardlytics-Built (Hosted)
Auth Integration required	✅	✅	✅
Plaid Linking required	✅	✅	✅
Integration Mechanism	Cardlytics API	Cardlytics SDK/Hosted	Auth Integration
Location of Experience	Integrated into Publisher Site	Embedded into Publisher Site	External white labeled site
User Experience	Publisher controlled	Cardlytics controlled with Publisher header/footer if desired	Cardlytics controlled
Development Time to Market	4-8 weeks	2-4 weeks	2-4 weeks
Maintenance Required	Publisher	Limited	Limited
Auth Integration	Runs in existing publisher user session	Runs in existing publisher user session	Need to establish user session
Resourcing	Dev resources	Limited dev resources	Limited dev resources; more security/IT

Integration Comparison: Brands

Feature	Publisher-Built	Cardlytics-Built (Embedded)	Cardlytics-Built (Hosted)
Auth Integration required	✅	✅	✅
Plaid Linking required	✅	✅	✅
Integration Mechanism	Cardlytics API	Cardlytics SDK/Hosted	Auth Integration
Location of Experience	Integrated into Publisher Site	Embedded into Publisher Site	External white labeled site
User Experience	Publisher controlled	Cardlytics controlled with Publisher header/footer if desired	Cardlytics controlled
Development Time to Market	4 weeks	2-4 weeks	2-4 weeks
Maintenance Required	Publisher	Limited	Limited