Platform SLAs and Operational Support

This section outlines Cardlytics platform service levels, availability targets, incident response expectations, customer support commitments, partner data requirements, and maintenance windows for publisher integrations.

Platform Service Levels

Cardlytics targets the following platform service levels for publisher integrations.

Service LevelTarget
Server-side API latencyp99 latency of 300ms or better for end-user-facing API calls
Platform availability99.9% or greater in each calendar month

Platform functionality is considered available when:

  1. End users are able to access and use the platform.
  2. The partner is able to send and receive program information through publisher interfaces.

Availability is measured as a percentage of total time in a calendar month during which the platform is available.

The following are included in uptime calculations:

  1. Planned maintenance communicated to the partner in advance.
  2. Planned maintenance by the partner communicated to Cardlytics in advance.
  3. Force majeure events that result in the platform not being available.
  4. Instances where the partner platform is unavailable for reasons not attributable to Cardlytics platform functionality.

Cardlytics will provide a monthly availability report to the partner within 5 business days after the end of each month.

Availability Target

SLADescriptionCalculationTarget
Platform availabilityPlatform availability is measured on a 24/7/365 basis, including planned or agreed downtime and scheduled maintenance, and excluding unplanned or emergency downtime.Supplier Platform Availability / Total Number of Hours * 100>= 99.9%

Incident Response Times

Cardlytics responds to incidents based on severity and business impact.

PriorityDescriptionResponse TimePermanent Resolution or Workaround
Priority 1: ShowstopperSevere degradation of service levels, an outage affecting end-user-facing services, offers not serving, profile page unavailable, or a service that is down or cannot be used by the majority of customers with no workaround available.30 minutes8 hours
Priority 2: MajorFull functionality is not available, or the service is only working to a limited extent and impacting some customers.2 hours48 hours
Priority 3: MinorA non-critical process or function is impacted. A minority of customers are affected, and a workaround may be available. The issue may become a higher priority if not resolved within a defined time.1 business day5 business days
Priority 4: TrivialA routine issue with minimal or minor business impact that is tolerable for an extended period.1 business day10 business days

Customer Support and CSA Support

The partner provides first-line support to its customers.

When the partner requests second-line support from Cardlytics for a program customer issue through the Customer Service Application, Cardlytics will provide:

  1. An initial response within 2 business days.
  2. A path to resolution within 5 business days.

These timelines apply unless additional information is required from the partner to resolve the issue.

Critical Partner SLAs

Partners must provide required data to support optimal program processing, functionality, and user experience.

DeliverableDescriptionHow UsedSLA
Customer dataRequired customer data fields as provided in Cardlytics integration documentationCustomer profileDaily
Account dataRequired account data fields as provided in Cardlytics integration documentationCustomer profileDaily
Auth transaction dataRequired auth transaction data fields as provided in Cardlytics integration documentationReal-time messaging, targeting, and merchant budget managementReal-time
Posted transaction dataRequired posted transaction data fields as provided in Cardlytics integration documentationRedemptionsDaily

Platform Maintenance and Release Schedule

Planned maintenance is performed during regional maintenance windows.

RegionMaintenance Window
USSunday, 12:00 AM to 4:00 AM Eastern Time
UKSunday, 12:00 AM to 4:00 AM British Summer Time

Daily releases with no downtime or major end-user impact may be performed on the platform.