Marketing performance
Open Journal -> Advanced analytics -> Marketing performance. The same report is available under Marketing -> Overview. It groups players by source, medium and campaign, then measures their subsequent payments.
Report fields
| Field | Purpose |
|---|---|
| Project | All accessible projects or one project. The same player in different projects is counted separately. |
| Game server | All servers or one server of the selected project. Selecting a server requires both registration on that server and payments to it. Registrations without a recorded server remain in the overall report. |
| Period | A calendar preset, year or custom registration dates. |
| Registered from / Registered through | Inclusive UTC registration dates. Defaults to the last 30 days. |
| Payments through | Inclusive UTC observation date, covering the registration period and no later than today. Today includes only the elapsed part of the day. |
| Source | An exact source label, such as newsletter. An empty field does not filter the source. |
| Medium | An exact medium label, such as email. |
| Campaign | An exact campaign label, such as summer-return. |
| Attribution | All registrations, with campaign tags, or without tags. Any recorded source, medium or campaign qualifies as tagged. |
| Receipt currency | One currency and precision. Automatic selection uses the first available currency/precision in code order. Currencies are not added together or converted. |
| Rows per page | 1, 10, 30, 50 or 100. This does not limit the total group count. |
Apply edited fields with the refresh button. Filters stay in the page address; reopening starts on the first page. Reset restores the last 30 days, observation through today, all projects, empty labels and automatic currency selection.
Measures
| Measure | Calculation |
|---|---|
| Registrations | Players first registered in the selected projects and dates, after applying the filters. |
| Paying players | Registered players with a qualifying payment in the selected currency by the observation date. |
| Payments | Distinct payments by those players. Multiple partial receipts of one payment do not increase this count. |
| Payer conversion | Paying players / registrations × 100%. |
| Gross receipts | Received payment amounts in the selected currency. |
| Receipts per registration | Gross receipts / registrations. |
Cards and rows use the same rules. Below the cards are registrations with tags, without tags, and without payments in this currency. Conversion and the average are unavailable when there are no registrations. Zero receipts never hide registered players.
Labels belong to the recorded registration. Later visits do not replace them. A missing label says “not recorded”, not “direct traffic”.
One campaign
Labels are exact and case-sensitive; populated fields are combined. Selecting newsletter + email + summer-return leaves a group of four players.
Observation date
Registration dates define the cohort; the payment observation date defines how long to follow it. Compare receipts through June or September without changing who belongs to the June cohort.
Missing campaign tags
Players without tags are included. A missing label does not prove there was no advertising; attribution may simply not have been recorded.
“With campaign tags” keeps every registration with at least one of the three labels. All three do not have to be present.
Currencies and no payments
A player can pay in more than one currency. Switching currencies keeps the registration cohort but recalculates payers, payments, conversion and amounts. USD and EUR receipts are not one combined monetary total.
An explicitly selected currency without matching receipts leaves the registrations visible, with zero payers, payments and amounts. If there are no receipt currencies at all and selection is automatic, amounts are unavailable because no currency is known.
Every group
Groups are ordered by receipts descending, then registrations descending, followed by source, medium and campaign. Next and Previous traverse the whole list without changing the overall totals.
After editing filters, refresh before paging. New data or an expired page prompts a refresh rather than continuing an inconsistent list.
One server
Select the project before its server. Registrations without a recorded server are not automatically assigned to it. A payment by the same player to a different server does not count for the selected one.
History and empty results
Whole years and custom historical periods are supported, not just recent months. Registration dates start at 1900; actual coverage depends on recorded history, with no arbitrary ten-year cutoff.
No matching registrations produces zero counts and an empty-result message. This differs from existing registrations that have not paid.
Calculation limits and access
Only positive live customer receipts after registration and through observation qualify. Replayed receipts are not counted twice. Guest payments without an identified registered player, test payments and administrative credits are excluded.
Gross receipts are not profit or net revenue: refunds, fees and advertising costs are not deducted. This report does not calculate ROI or prove that a campaign caused a payment. Inspect individual operations in the payment journal.
Only recorded events form the history. Late data can update an earlier period; missing historical labels are not inferred.
The journal requires Advanced analytics permission. The same report in Marketing requires Marketing view permission; one does not grant the other. No email, credentials or individual payment details appear here. Address exports remain a separate marketing action requiring Export permission.
An unavailable report shows an error and clears previous results, not fabricated zero counts or an empty-cohort message. For an oversized query, select a project, server or narrower registration period.