Dashboards are good for noticing. Exports are good for comparing, reconciling and preserving a decision trail. If several people review promotions—or if finance wants to see whether discount spend produced enough revenue—an exported campaign report gives everyone the same frozen snapshot.

Smart Cycle Discounts Pro can export analytics as CSV or JSON. That is separate from exporting campaign configurations for backup or transfer, and separate again from exporting generated coupon codes. This guide covers performance data: what happened during a selected reporting window.

What the analytics export contains

The export service supports three practical scopes. An overview produces store-wide summary metrics for the chosen range, optionally filtered to one campaign. A campaigns report produces one row per campaign. A product report can focus on one product or return the top products by attributed revenue.

A campaign row includes the campaign ID and name, operational status, impressions, clicks, conversions, attributed revenue, discount given, click-through rate, average order value and ROI. These are campaign-level measurements, not a dump of individual customer identities or raw order records.

That distinction matters. A campaign export answers questions such as “Which promotion generated the most attributed revenue?” or “Which campaign used a lot of discount budget but converted poorly?” It does not by itself prove incrementality. For that, compare equivalent periods, margin context and a sensible baseline. Our guide to Campaign Intelligence metrics explains what each signal can and cannot tell you.

CSV or JSON: which format should you choose?

Choose CSV when a person will open the file. Smart Cycle Discounts adds report metadata and readable headers before the data rows. Choose JSON when software will consume the file or when you want a structured snapshot that keeps the export field names intact.

Neither format is inherently “more accurate.” They contain the same selected dataset represented differently. The important choices are scope, campaign filter and date range.

A reliable export workflow

1. Write down the decision first. “Choose next month’s promotion” needs a campaign comparison. “Reconcile one campaign’s numbers” needs a filtered report. Do not export everything by habit.
2. Confirm the reporting range. Use a window that includes the full promotion and enough surrounding context. A seven-day campaign inside a 30-day report can be compared only if the dates are understood.
3. Choose overview, campaigns or product. Start broad only when you are genuinely exploring. For a defined question, narrow the scope.
4. Apply the campaign filter if needed. Confirm both the campaign name and ID, especially when names have been reused.
5. Generate CSV or JSON. Open the result immediately and verify the report type, generation time, currency and first few rows.
6. Save an untouched original. Make calculations in a copy. This preserves an audit snapshot if formulas or columns are later changed.
7. Record the decision. Add a short note: what was reviewed, what changed and when the result will be checked again.

How to read the campaign fields

Impressions and clicks describe exposure and interaction. A high click-through rate with weak conversions may indicate a message–offer mismatch, checkout friction or traffic that was curious but not qualified.

Conversions, revenue and average order value describe attributed commercial activity. Read them together. High revenue from a few unusually large orders is different from repeatable volume across many orders.

Discount given is the cost side of the promotion before cost of goods, fees, shipping subsidies and returns. ROI is useful as a directional campaign metric, but it is not a replacement for contribution margin. A finance review should bring in costs the plugin cannot infer.

Status fields explain whether the campaign was active, scheduled, paused or completed when represented by the performance pipeline. Do not treat status as performance. A completed campaign can be excellent; an active one can be leaking margin.

Common export mistakes

Comparing unequal windows

A weekend flash sale and a month-long evergreen campaign should not be ranked on total revenue alone. Normalize by active days, eligible traffic or another fair denominator.

Mixing attributed revenue with incremental revenue

Attribution connects an order to campaign activity. Incrementality asks whether that order would have happened without the promotion. The second question needs a baseline, holdout or careful period comparison.

Editing the only copy

Sorting is harmless; overwriting cells and adding formulas can quietly turn a source file into an interpretation. Keep the generated original read-only and work in a duplicate.

Ignoring campaign identity

Names can be reused. IDs are safer for reconciliation. Include both in a report or decision note.

Treating a download as an automation

A manual export is a snapshot. Scheduled reports are a separate Pro workflow. If recurring oversight is the goal, define recipients, cadence and what threshold should trigger a response instead of accumulating unread files.

Storage, privacy and retention

Generated files are written to a protected wsscd-exports directory under WordPress uploads. The plugin creates directory-listing protection and adds a random token to the filename. Export capability is also permission-gated.

Those controls reduce accidental exposure; they do not replace operational hygiene. Download only to approved devices, avoid forwarding reports through personal email, remove stale copies and include exports in your retention policy. Product and campaign analytics may still reveal commercially sensitive performance even without customer-level data.

Frequently asked questions

The useful export ends with a decision

Exporting more data is not analysis. Start with one question, select the smallest defensible scope, verify the file, and leave a short decision record. That turns a download into a repeatable campaign review rather than another forgotten attachment.

Webstepper

WordPress & WooCommerce Plugin Studio

We build WooCommerce plugins and publish practical guides grounded in the behavior of the actual product code.