Introduction
For merchants in partner sales, precise, role-based reporting determines efficiency and controllability. Without standardized KPIs, blind spots arise: partners with poor conversion remain unnoticed, payouts become confusing, and campaigns cannot be compared. This article provides practical reporting templates and dashboard configurations that merchants can use directly in Affilentra or import via CSV/SQL. Goal: faster decisions, clear responsibilities, and immediate access to the metrics that drive revenue and profitability.
What does a merchant dashboard really need?
A merchant dashboard must meet three requirements: clarity (unambiguous definition of KPIs), role separation (segregate data by merchant, partner, software operator) and actionability (from overview to detailed analysis in at most two clicks). Concrete KPIs that should be reported regularly:
- Conversion rate by partner (conversions / clicks)
- Earnings per Click (EPC = revenue / clicks)
- Return rate (returns or cancelled orders / orders)
- Payout costs (sum of direct commission payments + administrative fees)
Prebuilt KPI sets: Definitions and calculations
Below you will find precise KPI definitions that should be used consistently in any report. These definitions are suitable for direct display in widgets or as calculations after CSV/SQL import.
1. Conversion rate by partner
Definition: Share of conversions in clicks, grouped per partner.
- Formula: Conversion rate = conversions / clicks (expressed as %)
- Important fields: partner_id, partner_name, clicks, conversions, period_start, period_end
- Benefit: Identifies top performers and partners with high reach but low efficiency.
2. EPC (Earnings per Click)
Definition: Average revenue or commission value per click.
- Formula: EPC = revenue / clicks (currency unit per click)
- Important fields: partner_id, revenue, clicks, currency
- Benefit: Measures monetization efficiency across partners and channels.
3. Return rate
Definition: Share of orders that were cancelled or returned.
- Formula: Return rate = returns_or_cancellations / orders (expressed as %)
- Important fields: order_id, order_value, is_returned, return_date, partner_id
- Benefit: Visibility into quality risks and partners that generate disproportionate cancellations.
4. Payout costs
Definition: Sum of all payout amounts to partners including transaction and administrative fees for a billing period.
- Formula: Payout costs = SUM(payout_amount + payout_fees + admin_fees)
- Important fields: payout_id, partner_id, payout_amount, payout_fees, admin_fees, payout_date
- Benefit: Transparency about the real costs of partner programs and a basis for budget decisions.
Dashboard configurations for Affilentra
Below are four prebuilt dashboard widget sets that can be mapped directly into Affilentra or imported via CSV/SQL. Each set contains the necessary data fields, display options and suggested filters.
1. Partner Performance Overview (Widget Set)
- Display: Partner rankings by conversion rate, EPC and revenue.
- Fields: partner_id, partner_name, clicks, conversions, conversion_rate, revenue, EPC, period
- Filters: Time range, Country, Campaign, Traffic source
- Visualization: Tables with sparklines, Top-10 bar chart
2. Conversion Funnel by Partner
- Display: Clicks → Sessions → Orders → Conversions → Returns
- Fields: partner_id, clicks, sessions, orders, conversions, returns
- Filters: Partner, Product category, Landing page
- Visualization: Stacked funnel, conversion rate per stage
3. Cost and Payout View
- Display: Payout costs by partner and overall summary
- Fields: payout_id, partner_id, payout_amount, payout_fees, admin_fees, payout_status
- Filters: Billing period, Payment status
- Visualization: Time series, cost distribution cake
4. Returns Analysis and Quality Control
- Display: Return rate by partner, product and campaign
- Fields: order_id, partner_id, product_id, order_value, is_returned, return_reason
- Filters: Product group, Return reason, Time range
- Visualization: Heatmap by product & partner
CSV and SQL templates (Practical templates for import)
The following templates are intended as direct import templates for Affilentra or for adaptation to your data warehouse. Each CSV header line describes the required columns; SQL schemas show the minimal fields for relational integration.
CSV: partner_performance.csv
Header line (example):
partner_id,partner_name,period_start,period_end,clicks,conversions,revenue
CSV: payouts.csv
Header line:
payout_id,partner_id,payout_date,payout_amount,payout_fees,admin_fees,payout_status
SQL: Minimal schema for partner performance
CREATE TABLE partner_performance ( partner_id INT, partner_name VARCHAR(255), period_start DATE, period_end DATE, clicks INT, conversions INT, revenue DECIMAL(12,2) );
SQL: Minimal schema for payouts
CREATE TABLE payouts ( payout_id INT PRIMARY KEY, partner_id INT, payout_date DATE, payout_amount DECIMAL(12,2), payout_fees DECIMAL(12,2), admin_fees DECIMAL(12,2), payout_status VARCHAR(50) );
How to implement the templates in Affilentra
- Prepare export: Extract the raw data from your shop/tracking into the CSV structure of the template.
- Column check: Ensure that naming conventions and data types (date, decimal numbers) match.
- Import: Upload the CSV into Affilentra or connect the SQL schema to your reporting layer within the platform.
- Mapping & validation: After import, verify that all fields are mapped correctly (especially partner_id and time periods).
- Create dashboard: Use the predefined widgets (partner performance, funnel, payouts, returns) and arrange the filters.
- Operational routine: Schedule daily or weekly imports and define alerts for thresholds (e.g., conversion rate < X or return rate > Y).
Practical examples of action scenarios
Concrete use cases that enable quick decisions:
- Partner with high click volume but low conversion: arrange a meeting, review the landing page, replace creatives.
- Rising return rate for certain products: cluster return reasons, review partner promotions, pause campaigns.
- Payout costs rising above budget: review payout rules, reduce administrative fees or adjust flat rates.
Conclusion and next step
With standardized KPI sets and importable CSV/SQL templates, merchants reduce setup time and increase measurability. Affilentra combines tracking, commission calculation and payout in a role-based, self-hosted platform—ideal for operating the described dashboards productively. Use the templates as a starting point, adjust filters and thresholds to your business goals, and establish regular reports as a management instrument.
Ready to deploy? Choose how to get started: Choose how to get started
Next step
Try Affilentra yourself
A unified platform that transparently brings together product provisioning, tracking, conversion validation, commission calculation and payout across clearly separated roles; option for self-hosted installation with a perpetual license without revenue sharing; merchants retain control over products, terms and creatives; partners receive personal tracking links and a transparent payout history.