Module · Promotion

Promotion: statistics, requests and revenue

This page explains what the module counts (impressions, clicks, booking requests from paid cards), where specialists and the team see the numbers, the admin revenue screen with its CSV files, and the read-only check of paid places. Options are described in Settings.

Impressions and clicks

  • Impression: a paid card was shown on a public page. The count is reported by the page that actually displays the block, so a card that the theme did not render is not counted.
  • Click: a visitor opened the profile or service page from a paid card.

Not counted: admin pages, background requests, scheduled tasks, visits without a browser identification and visits whose browser identification matches Bot user agents (lines).

By default every display and every click counts. To count repeated views or clicks of the same visitor once, set Impression deduplication (per browser session or per visitor per day) and Click deduplication (minutes). Both use a technical cookie, ep_promo_vid.

Counts are collected in a buffer and written to the statistics by a scheduled task, so new impressions and clicks can take up to about an hour to appear.

Statistics are kept per campaign and per day. They are shown:

  • to the specialist on the Promotion tab: totals ("120 impressions · 8 clicks"), the click rate ("6.7% of impressions") and Impressions by day;
  • to the team on the campaign page (Impressions / clicks by day) and in the CSV files below.

How long daily statistics are kept is set in the core Data retention settings (Promotion impressions and clicks, kept forever by default).

Booking requests from paid cards

When a visitor clicks a paid card, the module remembers the click in the ep_promo_lead cookie for Lead attribution window (days) (7 by default). If the same visitor then sends a booking request within that window, the request is counted for the campaign:

  • after a click on a profile card: a request for any service of that specialist;
  • after a click on a service card: a request for that service.

When the booking is later paid, it is also counted as a paid request, even if the payment arrives through a delayed provider notification without the visitor's browser. The counters appear as "Requests 3, paid 1" for the specialist and on the campaign page for the team.

  • Setting the window to 0 turns this counting off; no attribution cookie is set.
  • Counting does not change the booking, its price or any commission. It is information for the specialist and the team.
  • Old records are removed according to the core Data retention entries Promotion click snapshots (90 days by default) and Promotion campaign requests (kept forever by default). A click snapshot removed before the booking is paid means that payment no longer counts as a paid request of the campaign.

Reports

Where: ExpertPress → Promotion → Reports (Звіти). Needs the Reports / CSV permission (money access by default); others see "Reports require the MONEY permission."

Choose From and To (local dates; by default the last 30 days) and click Show.

Revenue

The Revenue (Виручка) table shows, per currency, Payments, Refund and Net for promotion sales. Revenue is counted by the date the money was recorded in the ledger, the same basis as the payment module's money journal, so the two can be compared for the same dates.

Under the table:

  • reconciled: the promotion records and the ledger agree for the period;
  • mismatch: check the period and refund statuses: they do not agree, for example because a refund is still waiting for the provider's confirmation.

If the data cannot be read, the screen says "Report data is unavailable (read error). Do not treat zeros as reconciled."

By plan (За тарифами) splits the same numbers by plan, type and number of days.

CSV files

CSV: revenue (CSV: виручка) on the Reports tab downloads the revenue data. The classic Promotion page (Classic Promotion button) also shows Placement occupancy (Заповнюваність місць) and offers more files:

File Ukrainian label Contents
CSV: revenue CSV: виручка Totals per currency; ledger revenue and refunds; rows per plan, per type and per payment method (paid, refunded, net).
CSV: occupancy CSV: заповнюваність Per place: concurrent seats (M), days, seat-days, occupied days and fill percentage.
CSV: impressions/clicks CSV: покази/кліки Per place: impressions and clicks for the period.
CSV: auctions CSV: аукціони Per currency: revenue of sold seats, refunds, net and paid seats; closed auctions, total seats, fill percentage; attributed requests and paid requests.

Amounts in CSV files are in minor units of the currency (for example cents). The separator and the byte-order mark are set in Rules → Impressions, clicks and CSV. If the data cannot be read, no file is created and you see "Report unavailable" instead of a file with zeros.

Where: ExpertPress → Promotion → Paid places reconciliation (Звірка платних місць). Open to staff who can edit places or who have money access.

A read-only check of every place. Nothing is stopped, cancelled or refunded from this screen. For each place it shows:

Column Meaning
Placement The place, whether it is on, and its mode.
Public display Whether a public page currently displays the place.
Paid running, Paid scheduled, Paid paused Campaigns in each state.
Seats in use / paid seats Running campaigns of any source against the place's paid capacity (the smaller of M and paid slots).
Peak ahead The largest number of campaigns that will overlap at one moment in the future.
Findings Problems found, or "No mismatches found in the records read."

Possible findings:

  • "Paid campaigns hold this place, but no public page displays it." Check your theme or the catalog page.
  • "Unpaid reservations (checkouts awaiting payment or auction wins) hold this place, but no public page displays it."
  • "More paid campaigns are running than the place has paid seats." Usually after lowering seats; let campaigns end or terminate some.
  • "Seat holders overlap beyond the paid seats."
  • "Campaigns could not be read; the place was not checked." and similar read errors. Values that could not be read show as unavailable, never as zero.

Use it after changing places, modes or the theme, and before telling a specialist their promotion is visible.

Admin overview and setup checks

  • The core admin overview lists Campaigns needing a decision with an Open queue link when paused campaigns wait for the team.
  • The core setup checks include a Paid promotion line. It explains what blocks selling, for example a missing payment module, a place without public display, a fixed-price place without an active plan, paused sales, or no place with paid seats.