Product automation

Connect product events to the next action

When a user reaches a milestone, Claimr can update progress, unlock the next activity or deliver a configured reward. Connect the event, check eligibility and choose what happens next.

Explore API & SDK
  • Tracked signals
  • Clear conditions
  • Connected actions
Find a journey that fits
Test the logicInteractive example

One example rule

First project, first win

Choose the example inputs
Only reward this milestone onceNot yet granted

THEN - apply the eligible actions

100 XPConfigured rewardActivatedTarget segmentNotifyConnected system

Change the inputs, then run the example rule.

No live automation - exploration XP is separate

Try the example above - sample actions, no live campaign

How automation works

Choose the event, conditions and outcome

Combine a trigger, the conditions that matter and the actions to take. Keep the logic connected to the user's progress and profile.

Behavior-based triggers

Start a rule from tracked product, social, wallet or referral activity.

Example

A first project, completed quest or activated referral

Conditions & eligibility

Check available profile fields, scores or activity thresholds before an action becomes eligible.

Example

Onboarding complete and the milestone reward not yet granted

Progress & rewards

Award configured XP, points or rewards when a rule's conditions are met.

Example

An eligible milestone earns points and an achievement

Segments & next steps

Update campaign eligibility or a segment so the next experience reflects new activity.

Example

An activated user becomes eligible for a product challenge

Connected systems

Use webhooks to pass relevant events to the systems involved in your workflow.

Example

Notify a backend service about an eligible campaign event

Lifecycle journeys

Build rules around onboarding, repeat participation, loyalty and referral milestones.

Example

A new tier opens a different set of eligible activities

Choose the moment that matters

Useful rules for real product journeys

Start with one event and a clear outcome. These scenarios illustrate the logic you can plan with your team.

Illustrative SaaS journey

Turn the first project into a next step

Recognize activation while keeping the next useful feature in view.

  1. 01 / When

    First project published

    Your product sends the relevant event.

  2. 02 / If

    Onboarding is complete

    Check the connected account and reward eligibility.

  3. 03 / Then

    Recognize activation

    Grant configured progress and update the activation segment.

What to watch

Eligible activation events, actions applied and repeat feature use

SaaS example selected: Turn the first project into a next step

Customer story · Early depositor engine

Daily scoring across a complete points program

A custom listener and pricing service connected on-chain events to per-wallet points, bonus windows, referrals and leaderboards in one DeFi program.

Read the case study

Anonymous DeFi protocol · Phase-one deposits, July 2024-January 2025

Chains in the points program
2

Ethereum and an L2 connected to the same deposit, pricing and points infrastructure.

How it’s measured for chains in the points program
Depositing wallets
~5,700

Distinct addresses with at least one recorded phase-one deposit across the two chains.

How it’s measured for depositing wallets

Good automation starts with good inputs

Make the rule clear before it goes live

Define what should happen when conditions match, when they do not and when the same event arrives again. The interactive example shows those decisions locally.

  1. 01

    Connect reliable events

    Map product events to the right account and supply the fields the rule needs.

  2. 02

    Set conditions and limits

    Agree eligibility, reward frequency, duplicate handling and any review requirements.

  3. 03

    Test the outcomes

    Check matching, non-matching and repeated events, including downstream reward fulfillment or webhooks.

Put it inside your product

Show activities, progress and rewards in a Widget that fits the experience.

Explore the Claimr Widget

Connect the product signals

Use the API, supported SDK controls and webhooks where the journey needs them.

Explore API & SDK

Watch the rule and the result

Eligibility

Which tracked events meet the conditions, and which do not?

Execution

Were the intended actions applied without unwanted repeat rewards?

Delivery

Did downstream systems receive and handle the events as expected?

Define the relevant events, cohort and timeframe before comparing results.

Before the next move

A few things worth knowing

The mechanics, the setup and how the experience connects to your product.

Security & data handling
What can an automation rule connect?

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.

Is the interactive example a live campaign builder?

No. It is a local explanation of rule logic. It does not publish a campaign, grant campaign rewards or send a webhook. Website exploration XP is separate. The separate Campaign Sandbox is marked coming soon; contact the team to discuss an implementation.

Do we need to write code for every rule?

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.

What should we check before enabling event retries?

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.

How quickly do rules run?

Rules respond as relevant events are tracked and evaluated. Actual timing depends on the source, integration and downstream actions; confirm any latency requirements for your use case rather than assuming a fixed response time.

Can automation notify another system?

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.

Make the next move

Plan your first automation

Bring an event, a condition and an outcome. We'll help you connect them to a useful campaign experience.

Try the Claimr Widget