Skip to main content

Cake API Connector

Updated over a week ago
CAKE by Accelerize Upgrades Tracking, Attribution and ...

Overview

CAKE (by Impact) is an affiliate and performance marketing tracking platform used to manage partners, offers, conversions, attribution, payouts, and traffic. The CAKE API provides programmatic access to offer configuration, partner data, conversion tracking, click and event reporting, and various metadata tables and automates the ingestion of three distinct data sets from the Cake platform Campaign Summary, Event Conversions, and Clicks to capture end‑to‑end affiliate performance.

The CAKE API exposes performance marketing and affiliate tracking data across:

Affiliate & Offer Configuration

  • Affiliates / Partners

  • Offers

  • Offer contracts & terms

  • Landing pages / creatives

  • Pixels & postback URLs

  • Traffic caps, budget caps, status

  • Campaigns (affiliate + offer combinations)

Click, Event & Conversion Data

  • Clicks

  • Conversions (approved, pending, rejected)

  • Events / goals (custom events)

  • Payouts & revenue

  • Attribution type (first-touch, last-touch, multi-touch depending on setup)

Financial & Payout Data

  • Affiliate payout amounts and statuses

  • Advertiser revenue

  • Adjustments (manual and automated)

  • Billing periods

Metadata & Reference Data

  • Verticals

  • Countries / GEOs

  • Device types

  • Offer categories

  • Sub ID & tracking parameter mappings

  • Currency and account metadata

Granularity:

This integration retrieves data at: Advertiser, Affiliate / Partner, Offer, Campaign, Creative and Tracking link/ Landing page level.

Purpose

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).

Update Modes:

Append (for data table), Refresh (for metadata)

For more information on the Cake integration please follow this link.


Connection Setup

Key

Description

Required

Type

Size

cake_host

Base URL of your Cake instance (e.g., https://mycake.com)

Text

255

cake_api_key

API key generated in Cake UI

Text

Notehost, 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

cake_data_campaign

CampaignSummary

7 days

03:00

24 h

Cake Events Import

cake_data_events

EventConversions

60 days

04:00

24 h

Cake Clicks Import

cake_data_clicks

Clicks

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

bright_custom_date

Date (YYYY‑MM‑DD)

campaign_id

Campaign ID

campaign_name

Campaign name

brand_advertiser_name

Advertiser / brand

source_affiliate_name

Traffic source

views

Impression count

clicks

Click count

macro_event_conversions

Macro conversions

micro_events

Micro events (lower‑funnel actions)

paid

Paid conversions

sellable

Sellable actions

cost

Cost amount (network cost)

revenue

Revenue amount

pending / approved / rejected / returned

Conversion dispositions

order_total

Order value

total_paid

Total amount paid

2. cake_data_events (Conversion‑event detail)

Field

Description

event_id

Event ID

event_datetime

Timestamp

disposition_name

Pending / Approved / Rejected

brand_advertiser_name

Advertiser name

source_affiliate_name

Traffic source

creative_name

Creative asset

views

Event‑level impressions

3. cake_data_clicks (Raw click log)

Field

Description

click_id

Unique click identifier

click_datetime

Timestamp

brand_advertiser_name

Advertiser name

source_affiliate_name

Traffic source

creative_name

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]

brand_advertiser_name in campaigns, clicks, and events

Campaign [Cake]

campaign_name (campaign table)

Site [Cake]

source_affiliate_name in campaigns, clicks, and events

Creative [Cake]

creative_name in clicks & events


Base Metrics

Metric Name

Formula / Logic (across tables)

Round

Prefix

Views [Cake]

SUM(cake_data_events.views) + SUM(cake_data_campaign.views)

2

£

Clicks [Cake]

COUNT(DISTINCT cake_data_clicks.click_id) + SUM(cake_data_campaign.clicks)

0

Macro Event Conversions

SUM(cake_data_campaign.macro_event_conversions)

0

Paid [Cake]

SUM(cake_data_campaign.paid)

0

Sellable [Cake]

SUM(cake_data_campaign.sellable)

0

Micro Events [Cake]

SUM(cake_data_campaign.micro_events)

0

Cost [Cake]

SUM(cake_data_campaign.cost)

0

Revenue [Cake]

SUM(cake_data_campaign.revenue)

0

Pending [Cake]

SUM(cake_data_campaign.pending) + SUM(IF(cake_data_events.disposition_name = "Pending", 1, 0))

0

Rejected [Cake]

SUM(cake_data_campaign.rejected) + SUM(IF(cake_data_events.disposition_name LIKE '%Rejected%', 1, 0))

0

Approved [Cake]

SUM(cake_data_campaign.approved) + SUM(IF(cake_data_events.disposition_name LIKE '%Approved%', 1, 0))

0

Returned [Cake]

SUM(cake_data_campaign.returned) + SUM(cake_data_events.returned)

0

Order Total [Cake]

SUM(cake_data_campaign.order_total)

0

Total Paid [Cake]

SUM(cake_data_campaign.total_paid)

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]

Approved / (Rejected + Pending + Approved) * 100

2

%

Conversion Rate [Cake]

(Approved + Rejected + Pending) / Clicks * 100

2

%

Did this answer your question?