🔍 Overview
The Cake connector automates the ingestion of three distinct data sets from the Cake platform—CampaignSummary, EventConversions, and Clicks—to capture end‑to‑end affiliate performance.
Granularity
• CampaignSummary ➜ one row per campaign per day
• EventConversions ➜ one row per conversion event
• Clicks ➜ one row per individual clickPurpose – Combine spend, revenue, and conversion disposition data with click‑stream detail for full‑funnel analysis and reconciliation.
Refresh cadence – Each dataset is appended daily with its own look‑back window (Campaign 7 days, Events 60 days, Clicks 2 days).
For more information on the Cake integration please follow this link.
⚙️ Connection Setup
Key | Description | Required | Type | Size |
| Base URL of your Cake instance (e.g., | ✅ | Text | 255 |
| API key generated in Cake UI | ✅ | Text | — |
Note – host, token, secret, username, and password are unused (null) for this connector; authentication relies solely on the API key passed in query‑string.
🛠 Jobs & Schedules
Job Label | Target Table | Method (hidden) | Look‑back | First Run (UTC) | Poll Freq |
Cake Data Import |
|
| 7 days | 03:00 | 24 h |
Cake Events Import |
|
| 60 days | 04:00 | 24 h |
Cake Clicks Import |
|
| 2 days | 05:00 | 24 h |
All three jobs run daily. Each job appends fresh data and re‑requests the defined look‑back window to capture late‑arriving records or adjustments.
📚 Tables & Fields
1. cake_data_campaign (Campaign‑level performance)
Field | Description |
| Date (YYYY‑MM‑DD) |
| Campaign ID |
| Campaign name |
| Advertiser / brand |
| Traffic source |
| Impression count |
| Click count |
| Macro conversions |
| Micro events (lower‑funnel actions) |
| Paid conversions |
| Sellable actions |
| Cost amount (network cost) |
| Revenue amount |
| Conversion dispositions |
| Order value |
| Total amount paid |
2. cake_data_events (Conversion‑event detail)
Field | Description |
| Event ID |
| Timestamp |
| Pending / Approved / Rejected |
| Advertiser name |
| Traffic source |
| Creative asset |
| Event‑level impressions |
3. cake_data_clicks (Raw click log)
Field | Description |
| Unique click identifier |
| Timestamp |
| Advertiser name |
| Traffic source |
| Creative asset |
Exact schemas may include additional columns returned by Cake; all columns are captured and stored.
📐 Dimensions
Dimension | Mapped Fields (across tables) |
Advertiser [Cake] |
|
Campaign [Cake] |
|
Site [Cake] |
|
Creative [Cake] |
|
📊 Base Metrics
Metric Name | Formula / Logic (across tables) | Round | Prefix |
Views [Cake] |
| 2 | £ |
Clicks [Cake] |
| 0 |
|
Macro Event Conversions |
| 0 |
|
Paid [Cake] |
| 0 |
|
Sellable [Cake] |
| 0 |
|
Micro Events [Cake] |
| 0 |
|
Cost [Cake] |
| 0 |
|
Revenue [Cake] |
| 0 |
|
Pending [Cake] |
| 0 |
|
Rejected [Cake] |
| 0 |
|
Approved [Cake] |
| 0 |
|
Returned [Cake] |
| 0 |
|
Order Total [Cake] |
| 0 |
|
Total Paid [Cake] |
| 0 |
|
Currency fields are stored in the currency configured within Cake. Prefix/suffix can be adjusted per reporting tool.
⚖️ Composite Metrics
Name | Formula | Round | Suffix |
Conversion‑to‑Sale Rate [Cake] |
| 2 | % |
Conversion Rate [Cake] |
| 2 | % |
🔗 Joins
No explicit metadata lookup tables are defined; therefore joins are implicit via shared dimension values (campaign_id, brand_advertiser_name, etc.). All reporting joins are performed in the BI layer using these natural keys.
✅ Summary
The Cake connector captures campaign summaries (7‑day window), event‑level conversions (60‑day window), and click logs (2‑day window) on a daily cadence. It produces three append‑only fact tables rich with dimensions such as advertiser, campaign, site, and creative, and provides 14 base metrics plus 2 composite KPIs for performance analysis across the affiliate funnel.