Ignition
An attribution machine — not a gamification toolkit

Attribution you can put on an invoice.

Ignition runs private-domain gamified growth — spin-to-win, claim codes, referrals — and stitches every reward back to a deterministic, auditable conversion. The wheel earns attention; the attribution path and the append-only ledger earn trust.

Deterministic billing · Double-entry ledger · Per-tenant isolation

100%
deterministic billing basis
Append-only
double-entry ledger
Versioned
public attribution policy

Positioning

Not a gamification toolkit — an attribution machine.

The spin wheel is acquisition theatre. The attribution path and the ledger are the product, and every engineering priority follows that judgement — because revenue correctness is not a feature you bolt on later.

  • Probabilistic conversions can inform dashboards — they never reach an invoice.
  • A platform fee, not a cut of inflated numbers, keeps incentives honest.
  • Every billable event freezes the policy version and evidence that produced it.

Capabilities

Built so the invoice is never a guess

Six things that make attribution defensible from the first tap all the way to the ledger.

Deterministic attribution only

Billing depends on confirmable events — claim-code redemption, not probabilistic device matching. If we can't verify it ourselves, it never bills.

Append-only double-entry ledger

Refunds and chargebacks post reversing entries; originals are never mutated. An unbalanced transaction is unrepresentable at the type level.

Versioned, public policy

Attribution rules are published to customers and KOLs. Every record freezes its deciding policy version and an evidence snapshot — appeal-ready by design.

Gamified acquisition

A server-authoritative spin wheel inside a Telegram Mini App: weighted draws, atomic stock, idempotent plays. The client only animates the outcome.

Per-tenant isolation

Row-level security scopes every query to its tenant; secrets are encrypted at rest with envelope encryption. Fail-closed by default.

Caps that don't stop service

Over-cap conversions still attribute and still credit the KOL — they're simply marked free. Better UX, and a natural upsell.

How it works

One path, end to end

From a tap in the Mini App to a line on a double-entry ledger — every hop is a fact we can reproduce.

  1. 01

    Play

    A user opens the Telegram Mini App and spins. The server draws the outcome and issues a single claim code.

  2. 02

    Redeem

    The code is redeemed inside the customer's app. Telegram identity and app identity bind here — in one locked transaction, the sole stitch point of the whole path.

  3. 03

    Attribute

    A deterministic attribution and its billable event are written together, stamped with the policy version and an evidence snapshot.

  4. 04

    Settle

    At month-end, unsettled events are invoiced against the tenant cap and a draft is pushed to the payment gateway.

  5. 05

    Ledger & audit

    Every charge posts balanced double-entry lines; a daily audit re-checks the invariants and alerts on any drift.

Why you can trust the number

Four constraints we don't bend

Most of the system only makes sense against these. They're the reason the invoice holds up.

C1

Billing rides on deterministic attribution

Probabilistic matches may appear on dashboards; they never appear on invoices. One exhaustive check enforces it — forgetting can't silently bill.

C2

No conflict of interest

A platform fee means we don't earn more by inflating numbers. Rules are versioned and public; every record keeps its evidence.

C3

The ledger is append-only

Refunds and fraud findings write reverse entries; the basis of an issued invoice stays frozen. The database itself revokes update and delete.

C4

Capabilities are data-driven

No scattered plan checks. Entitlements come from data, so a promise like “Discord free for now” is recorded, not hard-coded.

Pricing

Priced on confirmed conversions

A platform fee keeps incentives aligned; performance billing only ever counts events we can verify.

Starter

Platform fee

For a first private-domain campaign

  • Gamified Mini App wheel
  • Deterministic attribution
  • Public attribution policy
  • Monthly cap included
Most popular

Growth

Fee + performance

For teams billing KOLs on results

  • Everything in Starter
  • Performance billing on redemptions
  • Double-entry ledger & daily audit
  • Per-tenant isolation & encrypted secrets
  • Attribution query API

Enterprise

Let's talk

For regulated, multi-brand growth

  • Everything in Growth
  • Cloud KMS & Stripe adapters
  • Appeal channel & evidence export
  • Dedicated onboarding & SLA

FAQ

Questions, answered

Ready to make attribution invoice-grade?

See the full path — play, redeem, attribute, settle, ledger — running on your own campaign.