The Datasource described on this page is an illustrative example. The actual fields, structure, and naming will vary based on your brand’s specific data model and integration. Use this as a reference for the type of data needed, not as an exact specification.
Overview
The Purchases Datasource contains the detailed transaction history for each customer: what they bought, when, how much they spent, and through which channel. This powers recommendation exclusion logic (never recommend what was already bought), frequency analysis, and category affinity calculations.
Key Fields
| Field | Type | Description | Example values |
|---|
transaction_id | String | Unique order identifier | "ORD-2024-847291" |
customer_id | String | Customer who made the purchase | "C-2847391" |
purchase_date | Date | Date of transaction | 2024-11-15 |
products | Array | List of products purchased | [{product_id: "SKU-12345", quantity: 1, price: €129}] |
total_amount | Currency | Order total | €247.00 |
channel | Enum | Purchase channel | "web", "store", "app" |
store_id | String | Store (if in-store purchase) | "STR-PARIS-MARAIS" |
Connected Use Cases
| Use Case | How Purchases is used |
|---|
| Enriched Product Recommendation | Exclusion logic + category affinity calculation |
| Customer Value Block | Total spend, frequency, last purchase context |
Data Requirements
| Requirement | Details |
|---|
| Update frequency | Real-time or daily (after each transaction) |
| Minimum fields | transaction_id, customer_id, purchase_date, total_amount |
| Recommended fields | All listed above for full recommendation quality |
| Format | JSON via Datasources API |
| Volume | Full transaction history (or last 24 months minimum) |
Integration Notes
Purchases are sourced from the brand’s OMS (Order Management System) or e-commerce platform. Both online and offline transactions should be included for complete behavioural analysis.
The distinction between Purchases (transaction-level detail) and CRM 360 (aggregated customer metrics) is important: CRM 360 provides the summary (total spend, frequency); Purchases provides the detail (individual orders, products, categories).
