How it is wired

There is no console for your team to learn and no migration to sit through. We sit over the platform you already run, and this page is the whole of it.

Technology

Five stages between a segment and a deposit

Stage three is the one worth reading twice. Everything else is plumbing; the consent gate is what keeps a programme alive past its second quarter.

  1. Stage 01

    Segment

    Audiences are resolved at send time from your platform, so a list is never older than the campaign it is used for.

  2. Stage 02

    Consent gate

    Every destination is checked against the consent record, the frequency cap and the self-exclusion register before it is queued.

  3. Stage 03

    Route

    Traffic is placed on the route cleared for that market and sender identity, with a second route held as failover.

  4. Stage 04

    Send

    Waves go out in sequence rather than all at once, so early delivery data can stop a bad campaign before the bulk of it lands.

  5. Stage 05

    Attribute

    Deposit events come back from your platform and are reconciled against the signed link that produced them.

What the consent gate actually refuses

Written out in full, because this is the part an operator's compliance team will want to read before anything else.

  • Frequency capped per player per week, across every campaign rather than per campaign
  • Self-exclusion and cool-off state re-checked at send time, never cached from an overnight export
  • Quiet hours evaluated from the destination number's own country, not from our timezone
  • A send that would breach a market rule is refused before it leaves, not filtered downstream
  • Consent source and timestamp stored against every send, and exportable on demand
  • A lapsed segment rests automatically after three unanswered touches

What we connect to on your side

Connects to your platformWe read segments and take deposit events back through whatever your operation already runs. No migration, no second console for your team to learn.
Your sender, your domainCampaigns go out under your registered sender identity and your own short domain, so the player sees your brand and the goodwill stays yours.
Local clock, not oursQuiet hours and send windows are evaluated from the player's own number, and a message caught by a closed window waits rather than being dropped.
Numbers you can auditEvery figure on a report can be traced to raw events, and we will hand over the export without being asked twice.

GrowthMessenger Ltd does not hold a gaming licence and does not need one. Traffic runs under the operator's own licence and sender identity, and the operator remains the data controller for its player records throughout. Our role is the campaign, the split and the attribution.

Send it to your compliance team first

We would rather answer their questions before a commercial conversation than after one. Point them at this page and copy us in.

Messages sent today

407,891