Operator guideEN

Bonus Map / Form

Shared create-and-edit wizard for Bonus Map drafts: general content, visuals, render layout, tracking, bonus generation config, generated-day review, confirmation, and publish.

How to use this guide

Start with the main guide

Follow the explanation and examples first. Extra definitions and formulas are available below when you need them.

What this page does

This is the shared wizard used both to create a new Bonus Map and to edit an existing one. The create screen can only save the first step and create the saved draft. The edit screen then unlocks the full wizard.

The wizard has six steps:

General Draft Creation: name, key, source text, claim URLs, and period dates
Day Visual Settings: desktop/mobile backgrounds, island images, connection styling, and past-day styling
Render Settings: desktop layout and mobile vertical/swipe layout numbers
Tracking: the optional MKT value shown in the list
Bonus Configuration: prize-type weights, EUR range rules, free-spins categories, source CMS copy, and JSON generation editor
Generate Days & Review: day generation, generated reward cards, card translation, period confirmation, fallback confirmation, and publish

What operators capture here

Bonus Map name: the campaign name
Internal key: a unique key for the map
title, subtitle, and claim-button text translations per language
Claim URL (logged-in) and Claim URL (guest), when the claim CTA should route different player states differently
Period start date and Period end date
visual assets for desktop, mobile, past/current/future islands, and custom connection graphics
render/layout numbers for desktop and mobile map drawing
MKT marketing tracking value
bonus generation settings: prize weights, ranges, free-spins game categories, and source CMS content
generated-day state, period card readiness, confirmation state, and publish state

How create and edit differ

On create, saving the first step builds a saved draft and then sends the operator straight to the edit screen for that new map.
On edit, each wizard step saves a partial patch to the same Bonus Map row.
A saved draft is not a completed launch. It becomes publishable only after days are generated and every generation period is confirmed.
After generated days exist, the period fields are locked on the page and the save flow rejects period changes.
Bonus Configuration is locked after publish and after generated days exist. The save flow rejects bonusConfig changes in those states.
The Generate step creates day rows first, then generates/resumes linked bonuses for claimable days. Bonus generation can partially fail and is retryable.
The Confirm period action activates generated bonuses and enables linked promo pages for the confirmed period. Publish only marks the Bonus Map published after all generated periods are confirmed.

How prize weights work

A missing configuration starts at 33% Deposit Match, 33% FS for Deposit, and 34% Match + FS.
The three weights must total 100% before the configuration can be saved.
A weight of 0% disables that prize type. It is removed from random selection and its type-specific generation fields are no longer required.
Positive weights are probabilities, not quotas. A 50% weight does not guarantee that exactly half of a short period will use that prize.

How reward amounts are generated

Configured money ranges are EUR baselines.
Each generated value is selected from its configured minimum/maximum range.
Minimum deposit rounds upward to a whole unit.
Maximum deposit, maximum bonus, and fixed maximum win round downward to a whole unit.
Other generated numeric currency fields round to two decimals.
Maximum Deposit = Maximum Bonus Amount / (Bonus Percent / 100).
Fixed Maximum Win = Maximum Deposit * Maximum-Win Deposit Multiplier.
Active non-EUR currencies are expanded using their current marketing ratio when generation runs. A missing, invalid, zero, or negative ratio falls back to 1.
This marketing ratio is configuration scaling, not an accounting FX rate. Already-generated bonuses are not proven to update automatically when the ratio changes later.

How to read Generate Days & Review

The summary chips show loaded day count, generated-period count, and draft/published state.
Each period shows total, successful, failed, processing, and pending day counts.
Card chips count ready, failed, and source-fallback deposit/free-spins content legs.
Retry period appears when failures exist; Generate period bonuses appears when the period still has pending days.
The generated-day table shows Date, Period, Confirmed, Prize type, Promotion Title, deposit bonus/content, free-spins bonus/content, generation Status, and Generation error.
Use the period tabs to select a monthly window and the locale tabs to preview promotion titles in another language.
source fallback means the source-language title is being shown because the selected locale has no usable title.
preview warning means the title still contains unresolved template content or another rendering warning.
A retry can remain partial. Review the status and error for every day before translating or confirming the period.
The live map preview is an operator aid; it does not prove that the player-facing placement has been published or is visible.

Confirmation and publish

Translate cards prepares the configured languages for generated promotion cards and pages.
Normal confirmation requires all generated days to succeed and their required content to be ready.
Confirm with source fallback accepts source-language content for missing or failed translations; it is not a translation retry.
Confirming a period activates that period's generated bonuses and enables its linked promo pages.
Publishing is a separate final state change for the Bonus Map after every generated period is confirmed.
After both steps, verify the intended player-facing placement and campaign dates in the target environment.

Why operators open this screen

start a new daily-prize campaign
rename a map or fix its translations
adjust the campaign period before days are generated
tune the player-facing map look and mobile behavior
configure which reward types can be generated and their EUR baseline ranges
prepare and translate generated reward cards before confirming a period
publish a fully generated and confirmed map

Known caveats

A new map is created as a draft. Do not treat it as launched until all periods are confirmed, the map is published, and the intended player-facing placement has been checked.
Bonus Map name, Internal key, at least one title translation, and valid period dates are required. Saving with a duplicate key or invalid period is rejected with an error.
Period dates are date-only and inclusive. Source validation rejects invalid dates, start-after-end periods, and periods longer than 366 days.
The Bonus Configuration content tab writes source copy under the platform's primary content language. If that language cannot be resolved during generation, generation falls back to en.
Enabled prize types require source-language Promotion Title; the other card/page content fields are optional. This title is card/page copy and is separate from the generated bonus record's own title.
Money values in Bonus Configuration are EUR baselines. Generation expands them to active currencies when generated bonuses are created.
Card translation requires the platform translation service. If translation fails, operators can retry Translate cards or explicitly confirm with source fallback.
JSON mode edits generation settings only. Content, visuals, and period are not part of that JSON editor.
Editing requires BonusMap update permission and creating requires BonusMap create permission; without it the page shows a no-permission notice.

More details

Definitions and formulas

Open only the section you need. The relevant section opens automatically when you request help for a specific item on screen.

Calculations14 topicsOpen details

Default prize-type weights

A new or incomplete configuration starts with all three prize families enabled and a total weight of 100%.

Inputs: saved prize-weight configuration
Formula: Missing weight configuration is normalized to Deposit Match 33%, FS for Deposit 33%, and Match + FS 34%.

Zero-weight prize type

Set a prize type to `0%` when it must never be generated. Its type-specific generation requirements are then not enforced.

Inputs: saved prize-weight configuration
Formula: Prize types with weight less than or equal to zero are removed from the weighted-selection pool.

Normalized generation range

Saved ranges are normalized before generation; review the saved values rather than relying on the order originally typed.

Inputs: saved generation ranges
Formula: Missing range boundaries copy the available boundary, negative values become zero, and reversed minimum/maximum values are swapped.

Weighted prize selection

Weights control probability across generated days; they do not guarantee an exact count of each prize type in a period.

Inputs: saved positive prize weights
Formula: Choose a random threshold from zero up to the sum of positive weights, then select the prize type whose cumulative weight contains that threshold.
Zero Rule: Returns no prize type when every weight is zero.

Random value inside a configured range

A range describes possible generated values, not one fixed reward amount.

Inputs: saved minimum and maximum range
Formula: Numeric boundaries are reordered low-to-high. Integer ranges select a whole number from the inclusive integer interval; generic decimal ranges select a random value and round it to the requested precision.

Generated amount rounding

Generated values can differ from the exact mathematical result at the configured rounding boundary.

Inputs: generated numeric value, generated field type
Formula: Minimum deposit is rounded upward to a whole unit. Maximum deposit, maximum bonus, and fixed maximum win are rounded downward to a whole unit. Other generated numeric currency fields are rounded to two decimals.
Rounding Boundary: Rounding is applied when the generated EUR values are built and again when each currency is expanded by its marketing ratio.

Computed maximum deposit

This is the deposit amount at which the percentage reward reaches the configured maximum bonus cap.

Inputs: max_bonus_amount, bonus_percent
Formula: Maximum Deposit = Maximum Bonus Amount / (Bonus Percent / 100).
Zero Rule: Returns zero when the inputs are invalid or Bonus Percent is not positive.
Rounding Rule: The result is rounded downward to a whole currency unit.

Computed fixed maximum win

This creates the generated bonus's fixed win cap from the calculated deposit cap and multiplier.

Inputs: max_deposit_amount, deposit_multiplier_max_win_amount
Formula: Fixed Maximum Win = Maximum Deposit * Maximum-Win Deposit Multiplier.
Zero Rule: Returns zero when an input is invalid or not positive.
Rounding Rule: The result is rounded downward to a whole currency unit.

EUR baseline expansion to active currencies

Review active-currency marketing ratios before generation; changing a ratio later does not prove that already-generated bonuses were recalculated.

Inputs: EUR baseline generation values, active currency code, active currency marketing ratio
Formula: For each active non-EUR currency, multiply eligible EUR baseline fields by that currency's marketing ratio. Percentages, multipliers, and NGR thresholds are copied without scaling.
Currency Basis: EUR is the configuration baseline. Generated bonus definitions contain EUR plus every active currency loaded during generation.
Exchange Rate Basis: Uses the configured currency `marketingRatio`; this is a marketing scaling ratio, not a market or accounting FX rate.
Exchange Rate Timestamp: The active currency rows and their current marketing ratios are read when bonus generation runs. No historical rate timestamp is stored with the generated mapping.
Rounding Rule: Each scaled field uses the same field-specific whole-unit or two-decimal rounding rule as the EUR baseline.
Missing Rate Behavior: A missing, non-finite, zero, or negative marketing ratio falls back to `1`.
Refund Reversal Handling: Not applicable. This calculation creates bonus configuration values and does not aggregate transactions, refunds, or reversals.

Generated day coupon code

Coupon construction is deterministic for each map, day, and reward leg.

Inputs: generated day date, Bonus Map id
Formula: Deposit coupon is DDMM + BN + map id. A free-spins leg appends FREESPINS. Existing stored coupon values are reused.
Caveats: The code contains day and month but not year; the map id separates maps.

Day creation and bonus generation boundary

A successful day-slot step does not guarantee that every reward was generated. Review the per-day status and retry incomplete periods.

Inputs: generated day records, per-day generation status
Formula: Missing day slots are created in a transaction. Bonus creation runs afterward per day and can leave a mixture of successful, failed, processing, or pending rows.

Period summary state

Use the period status together with the count chips; one failed day is enough to mark the whole period failed.

Inputs: per-day generation status, per-day confirmation time
Formula: A period is confirmed only when every day has a confirmation timestamp. Otherwise failed outranks processing, all-success becomes ready to review, and every other combination remains pending.

Promotion-title preview fallback

Source fallback in preview means the source-language text is being shown; it does not mean translation was retried successfully.

Inputs: selected-locale promotion title, source-locale promotion title
Formula: Prefer the selected locale title. When it is missing, show the source-locale title and mark source fallback. Unresolved template tokens or title-rendering issues produce preview warnings.

Publish readiness

Confirmation activates period rewards and pages; Publish separately marks the Bonus Map itself as published.

Inputs: map publish state, generated day count, per-day confirmation time
Formula: Publish is enabled only after at least one generated day exists, every generated day belongs to a confirmed period, and the map is not already published.

Fields78 topicsOpen details

Bonus Map name

Campaign name for the map; required by the page and save flows.

Step: general_draft_creation
Data Type: string
Editable: true
Required: true

Internal key

Unique saved identifier for the map; duplicate keys are rejected with `internalKey must be unique`.

Step: general_draft_creation
Data Type: string
Editable: true
Required: true

Title translations

Per-language player-facing map title; the page requires at least one non-empty title translation before save.

Step: general_draft_creation
Data Type: translations-map
Editable: true
Required: true

Subtitle translations

Optional per-language subtitle shown with the map.

Step: general_draft_creation
Data Type: translations-map
Editable: true
Required: false

Claim button text translations

Per-language claim CTA label for the button players press.

Step: general_draft_creation
Data Type: translations-map
Editable: true
Required: false

Claim URL (logged-in)

Optional target URL for authorized players who press the claim button; saved as null when blank.

Step: general_draft_creation
Data Type: url
Editable: true
Required: false

Claim URL (guest)

Optional target URL for non-authorized players who press the claim button; saved as null when blank.

Step: general_draft_creation
Data Type: url
Editable: true
Required: false

Period start date

First campaign date in `YYYY-MM-DD`; source validation checks date-only format, real calendar date, start <= end, and maximum 366 days.

Step: general_draft_creation
Data Type: date
Editable: true
Required: true
Lock Rule: Disabled by the page and rejected by the save flow after generated day rows exist.

Period end date

Last campaign date in `YYYY-MM-DD`; the period is inclusive on both ends.

Step: general_draft_creation
Data Type: date
Editable: true
Required: true
Lock Rule: Disabled by the page and rejected by the save flow after generated day rows exist.

Desktop background asset

Desktop background image used by the player-facing map.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Mobile background asset

Mobile background image used by the player-facing map.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Past island image

Island image for days that are already past.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Current island image

Island image for the current day.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Future island image

Island image for days that are not yet available.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Connection dotted color

Color used for the dotted connection trail when no custom connection asset is selected.

Step: day_visual_settings
Data Type: color
Editable: true
Required: false

Custom connection SVG/image asset

Optional custom image/SVG for the connection between islands.

Step: day_visual_settings
Data Type: asset-reference
Editable: true
Required: false

Past day opacity

Opacity for the disabled/past-day visual state; the input allows 0 to 1 with 0.05 step.

Step: day_visual_settings
Data Type: decimal
Editable: true
Required: false

Apply grayscale to past disabled days

Applies grayscale styling to past disabled days when enabled.

Step: day_visual_settings
Data Type: boolean
Editable: true
Required: false

Mobile mode

Chooses whether mobile renders as a vertical horizon column or a horizontal swipe strip.

Step: render_settings
Data Type: enum
Editable: true
Required: true
Allowed Values: vertical, swipe

Desktop island size

Diameter in pixels of each desktop day island.

Step: render_settings
Data Type: number
Editable: true
Required: true

Desktop island gap X

Horizontal distance in pixels between desktop islands.

Step: render_settings
Data Type: number
Editable: true
Required: true

Desktop canvas padding

Empty padding around the desktop map canvas.

Step: render_settings
Data Type: number
Editable: true
Required: true

Desktop wave offset

Vertical wave amplitude that makes the desktop strip less linear.

Step: render_settings
Data Type: number
Editable: true
Required: true

Desktop background scale

Desktop background zoom; `1` means cover, lower values reveal more image, higher values zoom in.

Step: render_settings
Data Type: decimal
Editable: true
Required: true

Desktop connection dash array

SVG dash pattern for the desktop island trail.

Step: render_settings
Data Type: string
Editable: true
Required: true

Mobile vertical island size

Diameter in pixels of each island in vertical mobile mode.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical island full height

Full vertical space reserved per island including labels and reward card.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical island gap Y

Normal vertical gap between islands in vertical mobile mode.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical first island gap Y

Extra vertical gap after day 1.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical last island gap Y

Extra vertical gap before the top-most day near the horizon.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical top pad

Top padding above the top-most island.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical bottom pad

Bottom padding below day 1.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical zigzag offset

Horizontal left/right offset for the vertical zigzag.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical zigzag side pad

Minimum side padding that keeps zigzag islands away from screen edges.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile vertical top island scale

Scale applied to horizon/top islands; values below 1 shrink distant islands.

Step: render_settings
Data Type: decimal
Editable: true
Required: true

Mobile vertical initial current day anchor

Initial viewport anchor for the current day, expressed as a 0-1 frame-height fraction.

Step: render_settings
Data Type: decimal
Editable: true
Required: true

Mobile vertical background scale

Background zoom for vertical mobile mode.

Step: render_settings
Data Type: decimal
Editable: true
Required: true

Mobile vertical connection dash array

SVG dash pattern for normal vertical mobile trail segments.

Step: render_settings
Data Type: string
Editable: true
Required: true

Mobile vertical first connection dash array

SVG dash pattern for the trail segment leading to the first day.

Step: render_settings
Data Type: string
Editable: true
Required: true

Mobile swipe island size

Diameter in pixels of each island in swipe mode.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile swipe island full height

Full height reserved for each swipe-mode island.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile swipe island gap X

Horizontal distance between islands in swipe mode.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile swipe side pad

Left/right padding at the ends of the swipe strip.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile swipe zigzag offset

Zigzag offset for islands in horizontal swipe mode.

Step: render_settings
Data Type: number
Editable: true
Required: true

Mobile swipe background scale

Background zoom for horizontal swipe mode.

Step: render_settings
Data Type: decimal
Editable: true
Required: true

Mobile swipe connection dash array

SVG dash pattern for swipe-mode trail segments.

Step: render_settings
Data Type: string
Editable: true
Required: true

MKT

Optional marketing tracking value shown in the list as the `MKT` chip.

Step: tracking
Data Type: string
Editable: true
Required: false

Prize-type weights

Distribution across `Deposit Match`, `FS for Deposit`, and `Match + FS`; the page and save flow require the three weights to sum to 100.

Step: bonus_configuration
Data Type: percentage-distribution
Editable: true
Required: true
Lock Rule: Disabled after publish, after `daysGeneratedAt`, after `periodLockedAt`, or when day rows exist; the save flow also rejects bonusConfig changes after publish or generated days.
Caveats: Missing configuration starts from `33% / 33% / 34%`., A weight of `0` disables that prize type from random selection and removes its generation-readiness requirements.

Deposit Match ranges

Range min/max values used when generated day bonuses pick the `deposit_match` prize type.

Step: bonus_configuration
Data Type: range-group
Editable: true
Required: conditional
Fields: Bonus %, Min Deposit (EUR), Max Bonus Amount (EUR), Wagering Multiplier, Max Win Deposit Multiplier, Max Bet (EUR)
Required When: Deposit Match weight is greater than 0; `Bonus %`, `Min Deposit (EUR)`, and `Max Bonus Amount (EUR)` must have positive max values before generation can run.

FS for Deposit ranges

Range min/max values used when generated day bonuses pick the `fs_for_deposit` prize type.

Step: bonus_configuration
Data Type: range-group
Editable: true
Required: conditional
Fields: Min Deposit (EUR), Free Spins Count, Bet Level, Wagering Multiplier, Max Bet (EUR), Fixed Max Win (EUR)
Required When: FS for Deposit weight is greater than 0; min deposit, free-spins count, and game category are required before generation can run.

FS for Deposit / Free Spins game category

Master game subcategory used for generated free-spins bonuses when `FS for Deposit` has weight.

Step: bonus_configuration
Data Type: foreign-key
Editable: true
Required: conditional

Match + FS / Deposit Match fields

Deposit-match part of the combined deposit-plus-free-spins prize type.

Step: bonus_configuration
Data Type: range-group
Editable: true
Required: conditional
Fields: Bonus %, Min Deposit (EUR), Max Bonus Amount (EUR), Wagering Multiplier, Max Win Deposit Multiplier, Max Bet (EUR)
Required When: Match + FS weight is greater than 0; `Bonus %`, `Min Deposit (EUR)`, and `Max Bonus Amount (EUR)` must have positive max values.

Match + FS / Free Spins fields

Free-spins part of the combined deposit-plus-free-spins prize type.

Step: bonus_configuration
Data Type: range-group
Editable: true
Required: conditional
Fields: Free Spins Count, Bet Level, Wagering Multiplier, Max Bet (EUR), Fixed Max Win (EUR)
Required When: Match + FS weight is greater than 0; free-spins count and game category are required.

Match + FS / Free Spins game category

Master game subcategory used for the free-spins leg of `Match + FS`.

Step: bonus_configuration
Data Type: foreign-key
Editable: true
Required: conditional

Bonus Configuration content

Source-locale CMS copy used when generating the linked bonus banner and page for each enabled prize-type leg.

Step: bonus_configuration
Data Type: localized-content-block
Editable: true
Required: conditional
Fields: Promotion Title, Text Bonus Type, Text Bonus Description, Banner image, Description, Terms And Conditions, Promotions image
Required When: Enabled prize-type legs require non-empty `Promotion Title`; other content fields are optional.
Caveat: `Promotion Title` is the generated promotion-card and page copy; it is separate from the generated bonus record's own title field.

Bonus Configuration JSON

Admin JSON editor for generation settings only; content, visuals, and period are intentionally excluded.

Step: bonus_configuration
Data Type: json
Editable: true
Required: false
Lock Rule: Disabled when the bonus configuration is locked.

Generated days count

Number of generated day rows currently loaded for the map.

Step: generate_review
Data Type: count
Editable: false

Period count

Number of generated monthly periods represented by the generated day rows.

Step: generate_review
Data Type: count
Editable: false

Published / draft chip

Shows whether the map is still draft or already published.

Step: generate_review
Data Type: status-chip
Editable: false

Period cards

Per-day generated reward cards with bonus ids, coupons, content status, CMS keys, source content, translated locales, and preview warnings.

Step: generate_review
Data Type: review-table
Editable: false

Generated period selector

Selects which generated monthly period is shown in the review table and used by period actions.

Step: generate_review
Data Type: tabs
Editable: true

Promotion-title preview locale

Selects the language used to preview generated promotion titles; the source language is labelled separately.

Step: generate_review
Data Type: tabs
Editable: true

Period generation state

Shows whether the period is pending, processing, partially failed, generated, or confirmed.

Step: generate_review
Data Type: status-chip
Editable: false

Bonuses active / inactive

Shows bonuses active after period confirmation and inactive before confirmation.

Step: generate_review
Data Type: status-chip
Editable: false

Period content readiness

Summarizes ready, failed, pending, and source-fallback card content across the period.

Step: generate_review
Data Type: status-chip
Editable: false

Read-only

Marks a confirmed period whose generation and content actions are no longer offered.

Step: generate_review
Data Type: status-chip
Editable: false

Date

Calendar date represented by the generated reward row.

Step: generate_review
Data Type: date
Editable: false

Period

Monthly generation key assigned to the day.

Step: generate_review
Data Type: string
Editable: false

Confirmed

Shows whether the day belongs to a confirmed period.

Step: generate_review
Data Type: status-chip
Editable: false

Prize type

Reward family randomly selected for that day from the enabled weighted types.

Step: generate_review
Data Type: enum
Editable: false

Promotion Title

Preview of the generated deposit and free-spins promotion titles for the selected locale.

Step: generate_review
Data Type: localized-preview
Editable: false
Caveats: A `source fallback` chip means the selected locale has no title and the source-language title is displayed., A `preview warning` chip means unresolved template content or another title-rendering warning was detected.

Deposit bonus

Linked generated deposit-bonus id, shown as a link when available.

Step: generate_review
Data Type: relation-link
Editable: false

Deposit content

Preparation and translation readiness of the deposit reward card.

Step: generate_review
Data Type: status-chip
Editable: false

Free spins bonus

Linked generated free-spins bonus id, shown when the selected prize type includes free spins.

Step: generate_review
Data Type: relation-link
Editable: false

Free spins content

Preparation and translation readiness of the free-spins reward card; a dash is shown when the prize has no free-spins leg.

Step: generate_review
Data Type: status-chip
Editable: false

Status

Current bonus-generation state for the day.

Step: generate_review
Data Type: string
Editable: false

Generation error

Last generation error for the day; a dash is shown when no error is stored.

Step: generate_review
Data Type: string
Editable: false

Live map preview

Desktop or mobile preview built from the current map visuals, layout settings, generated-day state, and selected preview context.

Step: generate_review
Data Type: visual-preview
Editable: false
Caveats: Preview is an operator aid and does not prove that the player-facing placement is published or visible.

Metrics10 topicsOpen details

Days

Number of generated day rows currently loaded for the map.

Formula: count of loaded generated day rows

Period(s)

Number of distinct monthly generation keys represented by the loaded day rows.

Formula: count distinct generation period key

Days

Total generated day rows in the selected period.

Formula: count of rows in the period group

Success

Days in the selected period whose generation status equals success.

Formula: count where generation status is success

Failed

Days in the selected period whose generation status equals failed.

Formula: count where generation status is failed

Processing

Days in the selected period whose generation status equals processing.

Formula: count where generation status is processing

Pending

Days in the selected period with no generation status value.

Formula: count where generation status is empty

Cards ready

Deposit and required free-spins card legs whose content status is ready.

Formula: count qualifying card legs where content status is ready

Cards failed

Deposit and required free-spins card legs whose content status is failed.

Formula: count qualifying card legs where content status is failed

Fallback

Card legs confirmed to use source-language content because translated content was not ready.

Formula: count qualifying card legs where content status is fallback

More help

Bonus Map

Operator guide for building retention Bonus Map campaigns, a draft-first calendar of generated daily rewards that players claim across a fixed period.

Bonus Map / List

Grid of all Bonus Map campaigns with derived lifecycle status, period, generated-day progress, and create, edit, and delete controls.

Affiliate Deals / Form

Create and edit form for affiliate deals, including PID, date window, commercial terms, and responsible person.

Affiliate Payment Settings / Form

Create and edit form for one affiliate payment-setting record, with visible PID targeting, minimum deposit threshold, and active-state control.

Auto Tags Manager / Create

Full rule-builder for a new automatic tagging rule, including priority, tag actions, coupon actions, KPI field selection, and draft impact estimation.

Automatic Withdrawal / Form

Create and edit form for one automatic-withdrawal rule, including thresholds, KYC, countries, methods, tags, and per-currency limits.