Skip to main content

Intro

The Content Manager is a powerful headless CMS system that allows you to create and manage dynamic content for your loyalty applications. It provides a centralized way to control promotional banners, seasonal campaigns, coupon displays, and other content that needs to be updated frequently without code deployments.

Key Features​

  • Collections: Organize related content into collections with configurable schemas
  • Documents: Create rich content items with custom attributes, images, and links
  • Publishing Workflow: Draft and publish content with granular control
  • Scheduled Publishing: Set specific date ranges for when content should appear
  • Multi-locale Support: Manage content in multiple languages for international audiences
  • Audience Targeting: Show different content to specific user segments or tiers
  • Full-text Search: Built-in search capabilities with faceted filtering
  • API-First: Consume content from any platform (mobile, web, or custom)

Use Cases​

The Content Manager is ideal for:

  • Promotional Banners: Showcase sales, new products, or special offers on your app's home screen
  • Seasonal Campaigns: Holiday-themed content that automatically appears and disappears based on dates
  • Coupon Displays: Curate and display available coupons from your coupon books system
  • Announcements: Important messages, updates, or news for your users
  • Featured Content: Highlight specific products, services, or experiences
  • Tier-Specific Promotions: Show exclusive content to premium or VIP members

Content Lifecycle​

Architecture​

The Content Manager is built on a multi-tenant architecture:

  • Collections define the structure and contain multiple documents
  • Documents are individual content items with custom attributes stored as JSON
  • Organization Isolation ensures your content is private to your organization
  • Read-Optimized database queries with separate read/write connections for performance

All content is managed through the CMS API (/cms/* endpoints) and can be consumed by any client that can make HTTP requests with proper authentication.