Your questions about Claimr

Yes, when you want a ready-made interface you can customize. Choose the modules and appearance, then connect the Widget to your product. Use the API when you need your own interface, with supported SDK methods where relevant.

Yes. You can use the Widget for the customer-facing experience and server-side API calls for connected data and operations. Plan account linking so both refer to the same user.

Quests, challenges, achievements, competitions, XP, points, tiers, streaks, leaderboards, seasons, rewards, referrals, polls and quizzes. Choose the combination that fits your program and implementation.

No. Eligible actions can earn achievements or XP before registration. Your integration identifies the visitor and records the activity using the configured identity and consent model.

Your signup integration links the visitor identity to the new account using Claimr's supported account-linking flow. Set up and test that connection so earned progress carries over.

Before signup, recognizing a returning visitor depends on your identity and storage setup. On this website, progress relies on storage in the same browser and preference consent. Clearing storage or changing browsers can break that connection. Progress does not automatically follow visitors across devices before account linking.

Yes. You define the qualifying actions, completion conditions, and whether each activity can be earned once or repeated. Use one-time achievements for milestones and repeatable challenges where they fit your program.

The Widget gives you a ready-made interface for tasks and progress. You can also use Claimr's API and SDK to build the experience into your own interface.

Not for every journey. Start with product and campaign activity, then add wallet or social connections where the experience needs them. Decide which signals are required for each campaign.

The profile holds the connected activity. A score summarizes aspects of that activity. A segment groups users who match the conditions you choose, so you can use that group in a campaign or personalized experience.

No. Linking supported product, wallet and social accounts provides campaign context. It is not identity verification and does not prove that every linked account belongs to a unique person.

Yes. Use the supported integration and tag-based visibility to show relevant quests and groups. Display settings are separate from eligibility checks for actions and rewards.

No. The previews use fictional participants and sample conditions to explain the experience. They do not calculate Claimr scores, update a real profile or award rewards.

You choose the relevant conditions, such as an activation event, later participation or a contribution threshold. Registration alone does not have to earn a reward. Connect the required events and define the qualification window.

Yes. Claimr supports referral relationships beyond a direct invite. Agree eligible levels and reward allocation as part of the program rules.

Referral Score reflects downstream contribution using tracked activation, retention and revenue signals, rather than only the number of invitations. Its usefulness depends on the data connected to your implementation.

No. A contribution score is not proof of identity or a guarantee against abuse. Use appropriate eligibility checks, program limits and review procedures alongside scoring.

Choose the reward, who supplies it, the qualifying action, and any limits or deadlines. Agree how delivery and failed claims will be handled. For rewards fulfilled by your own systems, include that delivery flow in your integration and test it before launch.

A rule combines tracked events, profile conditions and configured actions. Connected product, wallet, social and referral signals can inform eligibility. Actions can include progress, rewards, segment changes and webhooks.

Campaign rules can be configured without code once the relevant signals are connected. Developers may still be needed for product events, account linking, custom integrations and downstream reward fulfillment.

Confirm duplicate-event handling for the tasks and endpoints you use, including how a repeated event is identified and whether it can award progress or rewards again. Use stable event identifiers and appropriate checks in connected systems. Test retries and reward frequency before launch; do not assume every integration ignores repeated events.

Yes. Webhooks can notify connected systems about relevant events. Configure the receiving service and plan authentication, retries, monitoring and duplicate handling as part of the integration.

Custom-domain portals are part of the white-label offering. Agree domain setup, Claimr branding visibility, and customization scope with the team for your chosen setup.

The Widget lets you customize its theme, content, modules, and placement. A portal is configured to an agreed scope. With a custom interface, your team builds the frontend against Claimr's API. The examples on this page show design directions, not identical controls available in every option.

With the Widget, your team embeds and configures an existing interface. A portal is scoped with Claimr, including branding, domain setup, and authentication. For a custom interface, your team owns the frontend and API integration. Timing depends on those requirements.

No. Use the REST API for backend operations without adding the Widget SDK. Add the SDK when the frontend needs supported Widget methods or callbacks.

The organization API token authorizes backend requests and must remain private. A user token links a particular account to Claimr and is passed to that user's Widget. Your backend should authenticate the user before requesting or returning their token.

Use the authentication and credential storage supported by your MCP client or trusted integration. Keep secrets out of frontend code, shared prompts and public repositories.

Yes. Creation and update tools can write to a campaign. Ask for a plan first, confirm the campaign being changed, and approve the actions you want the assistant to take. A drafted suggestion does not make a change by itself.

Browse the task catalog, inspect campaigns, create groups, quests and tasks, and manage supported settings such as referrals, tiers, rewards and presentation. Ask the assistant to inspect the available tools before proposing a change.

Yes. Claimr MCP is publicly available for compatible MCP clients. Contact the team for connection details and the account access required for your organization. Available tools depend on your connection and its permissions. Get MCP setup help

Use the security information request on the Security page to discuss your evaluation requirements with the Claimr team.

The Security page describes access control, credential isolation, request validation, traceability, and data export and deletion controls. Ask the team how these apply to your integration.

The public subprocessor page is currently a draft and does not yet list vendors. Contact Claimr for the current provider details needed for your review.