​

Exports and Operational Checks

​

Export strategy

• workspace summaries
• campaign breakdowns
• link-level detail
• conversion/event/customer records
• affiliate commission and payout views

​

Export readiness checklist

1. Confirm workspace/campaign/link scope before export.
2. Confirm date range and timezone are final.
3. Confirm status filters are intentional.
4. Confirm reporting currency context.
5. Capture export filename with scope and timestamp.

​

Export format guidance

• CSV for spreadsheet analysis and finance workflows
• JSON for automation pipelines and scripted checks

• keep a shared naming convention with date range + scope
• version controlled reconciliation sheets for monthly close
• never compare exports generated with different filters/timezones

​

Reconciliation cadence

• daily: traffic and conversion sanity checks
• weekly: campaign economics and partner payout prep
• monthly: billing, retention, and access audit

​

Weekly operations dashboard checks

1. Validate top links and campaigns against expected traffic sources.
2. Validate conversion status distribution for unusual spikes.
3. Validate affiliate commission and payout queues.
4. Validate integration delivery health and retry spikes.
5. Validate budget and credit utilization trend.

​

High-value checks

• scope alignment (workspace vs campaign vs link)
• date/timezone consistency
• status-filter consistency
• currency and cost-model consistency
• partner payout status consistency

​

Practical runbooks

​

Runbook: “Revenue looks too high/low”

1. Export Conversions with target date range.
2. Export Events for same range and filter.
3. Confirm status mix (pending vs approved vs refunded/chargeback).
4. Confirm currency normalization in reporting context.
5. Re-check campaign/link scope filters.

​

Runbook: “Affiliate payout mismatch”

1. Export commissions by status.
2. Export payout batches and settlement states.
3. Confirm refunded/fraud/cancelled commission exclusions.
4. Confirm program/partner filters match payout batch scope.

​

Runbook: “Customer count lower than conversion count”

1. Export conversions and inspect identity fields.
2. Check missing customer email/external IDs.
3. Confirm dedupe/identity stitching expectations for the source.

​

Runbook: “Click numbers look right but analytics cards are sparse”

1. Confirm you are in the intended tab (Clicks/Leads/Sales/Funnel).
2. Confirm date window includes your test traffic period.
3. Confirm hidden status filters are not excluding records.
4. Confirm campaign/link scope is not overly narrowed.

​

Runbook: “Export does not match dashboard card exactly”

1. Confirm export and dashboard use identical scope and filters.
2. Confirm timezone settings match.
3. Confirm card uses summary behavior while export uses event rows.
4. Re-run export after a short refresh window for convergence.

​

Incident triage starter

1. capture current filters and scope
2. compare exported datasets
3. check recent configuration changes (rules, currency, plan, integrations)
4. re-run with a fixed date window

​

Evidence package for support/escalation

• screenshot of page with visible filters and date range.
• exported file used for reconciliation.
• workspace/campaign/link IDs involved.
• timestamp and timezone of observed issue.
• recent configuration changes in the affected module.

• /user-guides/manual/data/analytics-and-reporting
• /user-guides/manual/data/conversions-customers
• /user-guides/manual/ecosystem/affiliates-and-partners