Campaigns¶
Campaigns is the traffic layer. A campaign ties together the what (an offer), the where (a landing page), and the how (creative), and tracks its spend and revenue.
Key fields¶
| Field | Meaning |
|---|---|
name |
Campaign name. |
launch_product |
The target offer (productId, BV_Product). |
launch_landing |
The destination landing page. |
launch_creative |
The creative shown in the campaign. |
status |
Campaign lifecycle state (enum). |
budget_daily |
Daily budget (USD). |
pause_type |
How the budget/pause is enforced. |
metrics |
Recorded metric rows. |
metric |
The aggregate metric definition. |
ad_spend |
The aggregate spend definition. |
campaign_dollar_score |
Spend-based performance score. |
convertibility_score |
Predicted conversion potential. |
Metric definitions¶
Campaign metrics are deterministic aggregates over the workspace, matching the dashboard's shared definitions:
| Metric | Definition |
|---|---|
net_revenue |
revenue − refunds − chargebacks − fees. |
profit |
net_revenue − ad_spend − opex. |
roas |
revenue / ad_spend. |
net_roas |
net_revenue / ad_spend. |
conversions |
Successful orders. |
ad_spend is the spend definition used across campaigns and the finance dashboard.
Interaction¶
- View campaigns — browse campaigns for an offer/landing page/creative.
- Write campaigns — create and configure traffic runs.
- Record campaigns — attach metric rows (
metrics, enum) as the network reports them.
Plausible integration¶
For traffic attribution, the platform supports Plausible: campain URL → landing page slug, with analytics available by public IP (only), by campaign, by referral, by browser, by OS, and by country.