Skip to content
ClickMaster
SegmentsSegment · iGaming

From the ad click to the first deposit, on the same record.

Track the source, convert the sign-up, read the profile, measure the risk and decide when the bonus goes out — without switching tools between one step and the next.

Player lifecycle

Six stages, a single history.

Every stage writes to the same contact: how they arrived, what they did, how much they deposited and what they have already received from you.

  1. 01

    Visit

    The ad, affiliate, link or campaign that brought the session — with the parameter preserved.

  2. 02

    Sign-up

    Form completed, data captured and the contact created in the base.

  3. 03

    Verification

    The identity check that happens before the account is released.

  4. 04

    First deposit

    The event that separates a sign-up from a customer — and closes the attribution.

  5. 05

    Recurrence

    Frequency, interval and trend of the deposits that follow.

  6. 06

    Reactivation

    Who stopped, how long ago, and which channel they still answer on.

When a stage stalls you can see exactly which one — and act on that stage instead of raising the top-of-funnel budget in the dark.

Tracking and pixel

Know which ad brought the deposit, not just the click.

Pixel on the page, event from the server and the same identifier end to end: a conversion that happens days later is still tied to the campaign that produced it.

  • Your own pixel

    A script of yours on the capture pages, writing source and behaviour straight to the contact.

  • Server-side events

    The event leaves the server, not the browser: blockers, closed tabs and device switches do not erase the conversion.

  • Postbacks and offline conversions

    Send the deposit back to the media source that produced it, with the click identifier it arrived on.

  • Campaign and affiliate parameters

    UTMs, click id and affiliate code preserved from the first session through to the conversion.

  • Deduplication

    The same event arriving from the browser and from the server is counted once.

  • Journey attribution

    First touch, last touch and the whole path between them, on the same record.

The deposit usually happens after the session that produced the sign-up. That is why the source is stored on the contact, not only in the browser that opened the page.

Lead conversion

Between the sign-up and the first deposit there is a conversation.

Pages, forms and automated messages carry the sign-up to the next action, on the channel where they answer.

  • Capture pages

    Landing pages and quizzes published without a developer, with the pixel already in place.

  • Forms and qualification

    Sign-up answers land as fields on the contact, ready to segment on.

  • WhatsApp, email and Instagram

    Talk on the channel the sign-up replied on, from the same history.

  • First-deposit sequence

    An automation carries the contact from a completed sign-up to the first action that matters.

  • Stalled sign-up recovery

    Whoever signed up and went no further enters a flow of its own, with a different argument.

  • Hand-off to the team

    The highest-value contact reaches a human with the whole history attached.

Player profiling

Not every sign-up is worth the same.

Source, behaviour, value and lifecycle stage make up the profile — and the profile is what decides the offer, the channel and the incentive.

  • SourceCampaign, creative, affiliate and page that brought the sign-up in.
  • BehaviourWhat the contact opened, answered, clicked and left half-finished.
  • Declared dataWhat they told you themselves, in the form, the quiz or the conversation.
  • ValueRecorded deposits, frequency and how both move over time.
  • Preferred channelWhere they actually reply, and the time of day they tend to reply.
  • Lifecycle stageWhich stage they are in right now, and how long they have been stuck there.

The six dimensions become dynamic segments: a contact joins and leaves the group on its own as the behaviour changes, with no list exported by hand.

Risk analysis

Tell the player with potential from the one who came for the bonus.

Abuse, duplication and unusual behaviour show up on the same profile, before the incentive goes out.

  • Bonus abuse

    A contact that only shows up while an incentive is running and disappears once it is spent.

  • Duplicate accounts

    Repeated data, the same source and the same sign-up pattern in series.

  • Payment pattern

    Deposit, withdrawal and chargeback outside the behaviour recorded so far.

  • Velocity and volume

    Many actions in little time, coming from the same place or the same campaign.

  • Data inconsistency

    What was declared at sign-up does not match what the history shows.

  • Signs of problem gambling

    Frequency and intensity that call for human review and a limit — not another incentive.

No rule decides on its own. The system flags the contact, records the reason and shows the signal next to the profile; approving, holding or refusing stays with your operation.

Bonuses

When and how to release — by rule, not by impulse.

Eligibility, trigger, budget cap and expiry set up front; return measured afterwards, in the same place.

When to release

  • Sign-up with no first depositThe contact finished signing up and stopped. The incentive goes out as a nudge, on a short clock.
  • Right after the first depositThe moment of highest attention — and the best chance of turning it into a habit.
  • Drop in frequencyThe interval between deposits has grown. The signal shows up before the contact goes quiet.
  • ReactivationA contact dormant long enough that the incentive is worth more than the message alone.
  • High-potential profileBehaviour and value above the group's average, with risk inside the accepted range.
  • Never with risk openAn open abuse, duplication or problem-gambling signal suspends the release.

How to release

  • Eligibility ruleWho qualifies is defined by segment, not picked by hand from a spreadsheet.
  • Risk gateThe automation reads the profile's signals before releasing, and stops if one is lit.
  • Budget capA limit per contact, per campaign and per period, set before the rule runs.
  • Term and expiryEvery incentive is born with an expiry date, and the date goes in the message.
  • Human approvalAbove a threshold the flow pauses for someone to approve — and the record stays on the contact.
  • Return measurementWho received it, what they did next and how much came back, against those who did not receive it.

A bonus rule is an automation like any other: trigger, condition, action and record. The difference is that the condition reads the profile and the risk before it spends.

Segment dashboard

Your market's metrics, under the names you use.

Sign-up, verification, first deposit, recurrence and reactivation side by side, fed by the same event the funnel records.

Segment metrics

  • Sign-ups
  • Verified sign-ups
  • First deposit
  • Time to first deposit
  • Repeat deposit
  • Reactivated contacts
  • Bonuses released
  • Flagged contacts
  • Cost per sign-up

The names above are the metrics the dashboard assembles from your events. No figure on this page is a result of ours or of a customer — yours appear once the account starts recording.

Compliance · content pending

Nothing here counts as regulatory guidance

Licensing, identity verification, advertising and responsible-gaming requirements differ by country and are not described on this page. The platform records events, flags signals and keeps the history of every decision; reading the applicable rule and answering for it stays with your operation. This section gets its reviewed text once that text exists.

Connectors · content pending

No name before it exists and is tested

Segment integrations join this list one at a time, after they exist and have been tested. Until then, connecting a gaming platform, a payment provider or an affiliate programme is done through the API and webhooks.

Start now

Run your iGaming operation on one platform.

Create your account and connect acquisition, profiling, risk and bonuses on the same database.