Canonical Terms
iGaming Suite Glossary
Canonical public definitions for iGaming Suite terms including synthetic casino data, btag/VTag, click_id, FTD, GGR, NGR, postback, operator data batch and treatment/control testing.
Definitions are aligned with the iGaming Suite context model and help future public pages use consistent product language.
Who it is for Search engines, AI agents, developers, operators, affiliates and agencies.
What it does
- Tracking and attribution language
- Casino economics terminology
- Synthetic data and proof terminology
- CRM experiment terminology
Inside the Suite
A real product view
Definition governance
The glossary is the canonical public vocabulary for iGaming Suite. It exists so every product page, research page, documentation page and future social post uses the same terms for tracking, casino economics, synthetic data, market intelligence and CRM experimentation.
- Use product-accurate definitions instead of broad casino-marketing language.
- Keep accounting, legal and regulatory terms limited to product context unless reviewed sources support a wider claim.
- Link important terms back to the product pages where they are operationally used.
How the terms connect products
Horus Lab owns synthetic run lineage, source paths, wallet and gameplay data. Horus Intelligence owns attribution, postback, accepted-batch reporting and commission language. Oracle Network owns reviewed market and directory terms. Viper owns treatment/control, lift and CRM experiment vocabulary.
- Synthetic data terms should point toward Horus Lab and Developer Sandbox docs.
- Attribution and revenue terms should point toward Horus Intelligence.
- Directory and registration terms should point toward Oracle Network.
- Incrementality and CRM terms should point toward Viper.
Product surfaces
These are the product names, modules and data objects used inside iGaming Suite today.
- btag / VTag: affiliate tracking token
- click_id: immutable click identifier
- FTD: first-time deposit
- NGR: net gaming revenue
- operator_data_delivery_batch.v1: accepted casino-source package
- treatment/control: experiment assignment groups
Definitions
Synthetic casino data
Real-shaped, non-real-player data generated to test casino integrations, reporting contracts, BI pipelines and AI-agent behavior.
Horus Lab run lineage
The run ID, scenario, tenant/workspace scope and generated-row relationship that makes synthetic data auditable and cleanup-safe.
Source path
The acquisition or origin path assigned to a synthetic or real player journey, such as organic, affiliate, agency, campaign or tracked link origin.
btag / VTag
The affiliate tracking token class that ties traffic to operator, affiliate, campaign, source and commercial context.
click_id
An immutable click identifier used to bind a traffic event to later registration, deposit, player and reporting events.
S2S postback
A server-to-server notification used to report registration, deposit, revenue or other conversion events without relying on browser pixels.
Postback dispatch
The queued outbound delivery of a normalized postback event to a configured endpoint with idempotency and reconciliation context.
FTD
First-time deposit, counted only inside the correct attribution, event-time and reporting-window rules.
GGR
Gross gaming revenue before deductions such as bonuses, fees, taxes, adjustments or chargebacks, depending on the reporting contract.
NGR
Net gaming revenue after the deductions required by the operator or affiliate reporting contract.
CPA
Cost per acquisition, a commercial agreement model where a qualified player event can trigger a fixed commission.
RevShare
Revenue share, a commercial agreement model where commission is calculated as a percentage of eligible revenue such as NGR.
Hybrid deal
A commercial agreement that combines fixed acquisition logic with revenue-share logic under defined qualification rules.
Operator data batch
A reviewed package of casino-source data that Horus Intelligence can accept as reporting proof.
operator_data_delivery_batch.v1
The explicit accepted-batch contract name for casino-source data entering Horus Intelligence reporting.
Products Report
A casino-source reporting view that groups product or vertical activity such as casino and future sportsbook lines.
Players Report
A casino-source reporting view that lists player-level activity, economics and source context for reconciliation.
Cleanup proof
A confirmation that generated synthetic rows for a run were removed without deleting shared setup, credentials or manually created test data.
Oracle Network
The iGaming Suite market and directory intelligence layer for reviewed regulation, operator, agency and affiliate discovery workflows.
Pending review
A status for candidate directory or registration data that must be reviewed before becoming public, trusted or operational.
Treatment/control
Experiment groups used by Viper to estimate incremental CRM or VIP intervention effects.
Lift
The estimated incremental change between treatment and control groups after an intervention, measured under explicit assumptions and data-quality checks.
OLS diagnostics
Ordinary least squares regression checks used by Viper to inspect modeled relationships, residuals and fit quality in synthetic or reviewed data.
Casino CRM adapter
The future real-casino integration boundary for player sync, event ingestion, consent records and reviewed CRM delivery attempts.
FAQ
Why does iGaming Suite need its own glossary?
Because the product spans synthetic casino data, affiliate tracking, directories, CRM and BI. A shared vocabulary helps humans, search engines and AI agents understand the entity map.
Are these definitions legal or accounting advice?
No. They are product definitions for iGaming Suite. Legal, tax, regulatory and accounting decisions need reviewed specialist sources.
Which terms matter most for discoverability?
Synthetic casino data, btag/VTag, click_id, postback, FTD, GGR, NGR, operator_data_delivery_batch.v1, Oracle Network and treatment/control are priority entity terms.