Question 1

Is the Claimr Widget the recommended way to integrate Claimr?

Accepted Answer

Yes. The Widget is the primary, fastest path to adding Claimr to a product. API/SDK is available when a team needs a fully custom frontend.

Question 2

Can we use Claimr with our own interface?

Accepted Answer

Yes — the Widget, API and SDK all read and write against the same underlying data, so you can render the Widget for most of the experience and use the API for anything custom.

Question 3

Which mechanics does Claimr support?

Accepted Answer

Progression, achievement, competition, growth, rewards and feedback mechanics — including XP, tiers, quests, streaks, leaderboards, seasons, referrals, rewards, raffles, polls and quizzes.

Question 4

Is any personal information stored in the anonymous identifier?

Accepted Answer

No. The visitor identifier is a random first-party token with no PII attached until the visitor voluntarily signs up.

Question 5

What happens if a visitor never signs up?

Accepted Answer

Their progress simply remains attached to the anonymous identity. Nothing is lost, and nothing requires an account to accrue.

Question 6

Can achievements be awarded twice by accident?

Accepted Answer

No — every achievement event carries an idempotency identifier so retries or duplicate triggers can't double-award progress.

Question 7

Can I see this working right now?

Accepted Answer

Yes — the checklist on this page and on the homepage is your own progress in a live Claimr campaign: the quests tick as you browse, and the XP shown is what the campaign granted you.

Question 8

How often are scores recalculated?

Accepted Answer

Scores update as new activity is tracked, so segment membership stays close to real-time rather than batch-refreshed.

Question 9

Do I need wallet or social tracking enabled to use this?

Accepted Answer

No — the User Score gracefully combines whichever signals are enabled. Product-only deployments still get a meaningful score.

Question 10

Are the scoring formulas published?

Accepted Answer

The underlying weights are proprietary, but the input dimensions and how they're used for segmentation are fully documented.

Question 11

Can I build my own segments beyond the built-in ones?

Accepted Answer

Yes — segments are rule-driven and configurable, combining any score, tag or product event.

Question 12

When should we use the Widget, API or SDK?

Accepted Answer

No — the REST API and SDK are independent. Use the API alone for backend integrations, or add the SDK when you also want to control the Widget from your own frontend.

Question 13

What does MCP create?

Accepted Answer

No — it's an additional, AI-native way to produce the same configuration the REST API and dashboard already use.

Question 14

Does an MCP-generated draft publish automatically?

Accepted Answer

No — generated configuration is a draft. Saving it into a live campaign is a separate, explicit step.

Question 15

How are credentials protected?

Accepted Answer

No — this site's own sandbox proxies generation requests through a server endpoint, and MCP credentials stay server-side.

Question 16

How can we request security information?

Accepted Answer

Use "Request security information" on the Security page (/security) to contact the Claimr team.

Question 17

What data-handling controls are available?

Accepted Answer

See the confirmed controls listed on the Security page (/security), including access control, encryption, data export and deletion.

Question 18

Which subprocessors are used?

Accepted Answer

See the current subprocessors list (/legal/subprocessors).

Claimr frequently asked questions

Platform

Identity and pre-signup

Intelligence

Developers

Security