Platform · White-label

Choose how Claimr appears in your product

Use the Claimr Widget, embed selected components, deploy an approved branded portal or build a custom interface with the API and SDK.

View the Claimr Widget

Embedded

Claimr components inside your customer UI.

Portal

Complete white-label frontend on your domain.

Headless

API/SDK implementation, no Claimr UI.

The problem

Third-party quest platforms pull users off your product

Sending users to an external site to complete quests breaks the product experience, dilutes your brand and hands the user relationship to someone else's domain.

How Claimr solves it

Three ways to keep it native to your product

Embed Claimr's components directly in your existing UI, deploy a complete white-label frontend on your own domain, or implement everything yourself against a headless API — you choose the level of ownership.

Three implementation paths

  1. 01

    Embedded

    Drop Claimr components into your existing customer UI with your styling.

  2. 02

    Portal

    Deploy a complete white-label frontend on your own domain, fully branded.

  3. 03

    Headless

    Implement your own UI entirely, using only the API/SDK underneath.

  4. 04

    Your data throughout

    In every mode, the user relationship and data stay yours.

What white-label includes

Custom domain

Run the customer-facing experience on your own domain, not Claimr's.

Full branding control

Colors, typography and layout match your product, not a generic template.

Embeddable components

Drop in individual components — quest lists, progress, leaderboards — where you need them.

Headless API/SDK

Build a fully custom frontend against the same underlying platform.

Product-native UX

No redirect to a third-party destination breaks the user's flow.

Data ownership

User and activity data stay attributable to your product, not a shared platform.

Automation

The same automation engine, regardless of surface

Embedded, portal or headless — campaign rules and rewards work identically underneath.

Rule example
WHEN
Quest completed
(via embedded, portal, or headless UI)
THEN
+XP awarded
AND
Segment updated
AND
Webhook sent to your systems

Where teams use this

Product-native quests

Show quests and progress inside your existing app rather than a separate destination.

Branded loyalty portals

Launch a complete loyalty experience on a subdomain that looks like your product.

Custom frontend builds

Build a bespoke UI in your own stack against the headless API.

Multi-brand deployments

Run distinct branded experiences for different products or regions from one backend.

Integration

Pick your integration depth

Every deployment mode is built on the same API, SDK and webhook infrastructure.

REST APISDKWebhooksEmbeddable components
View documentation

Frequently asked questions

Yes — teams commonly start embedded for speed and move specific surfaces to a custom headless build over time.

RelatedAPI & SDKView the Claimr Widget

Your domain. Your branding. Your users. Your data

View the Claimr Widget