Perkamo
The engine behind your customer program

Your experience.
Our loyalty engine.

Perkamo manages points, progress and earned benefits. Your developer connects customer actions and builds the interface; your team manages the program from a console.

Try it freeRead the quickstart

Free Test Space. No card required. Your app owns benefit fulfillment.

Perkamo AI · Beta

Describe the intent.
Keep the control.

Draft a Goal. Review your program's settings. Decide what goes live.

Explore Perkamo Intelligence

“Help learners complete three lessons.”

Learning momentumDraft

3 lessons · One-time · 0 points

Review in editor
Illustrative example, not a live AI session. Nothing is saved automatically.
Inside PerkamoConsole / Insights
Perkamo Insights console showing event activity, customers and webhook diagnostics in a Test Space
Actual console. Test Space with example data.
Choose what helps your customers

Start with one mechanic.
Add more when it earns its place.

Use just the pieces your program needs. A Goal can track progress without awarding points. A Perk can unlock without a redemption.

Make useful actions count

Earning rules turn trusted actions into points. Set eligibility, point caps and cooldowns to control how often points can be earned.

Give customers something to build on

Wallets keep the points balance and its history. Levels derive status from that balance, giving customers a clear threshold to reach next.

Make the next step visible

Goals count actions toward a target. Track a one-time or repeatable activity target, with optional points on completion.

Let customers use what they earn

Rewards let customers spend their points. Perkamo debits the wallet and returns an effect; your backend provides the discount, access or other benefit.

Recognize a goal reached

Perks automatically unlock a persistent benefit after a Goal, points threshold or another supported condition. Your app reads that eligibility and delivers the benefit.

From event to experience

One action, both sides.

Start with a three-lesson Goal, then try a different target or program. Watch progress and benefit eligibility change together. This is a local illustration; your developer builds the customer interface.

Program playgroundInteractive example
Your program

Small rule.
Visible progress.

When a customer doeslesson.completed
Actions to unlock the benefit
Unlock this PerkPractice library

Changing the target starts a fresh example. It does not rewrite a real customer’s progress.

What your customer could see
Practice library3 more actions to unlock

0 / 3 · Try the customer action

Why it happened

One action.
An explainable result.

  1. Waiting for an actionlesson.completed
  2. Track Goal progress0 of 3 qualifying actions
  3. Unlock the benefitAfter 3 actions

A stable transaction ID means a retry is not another action. This demo illustrates that behavior locally.

01 Set a target 02 Try an action 03 See the resultLocal demo · no data sent

Illustrative UI, not a hosted widget. Your app sends events, displays progress and provides the unlocked benefit.

Integration boundaries

We track the program.
You deliver the benefit.

Your backend sends trusted facts and fulfills discounts, emails or feature access. Perkamo maintains balances, progress and unlocks. Signed webhooks can notify your systems of supported changes.

Read the integration guide
Server keys stay on your backend
Browser integrations use short-lived client tokens with limited permissions.
Test and Live are separate
Validate your program with isolated customers and credentials before connecting production activity.
Program changes apply deliberately
Versioned configuration and event history help explain the rules behind customer results.
Built for the way you work now

Your stack.
Your AI tools.
One program.

Connect your AI client through MCP to inspect a program, validate changes and prepare supervised updates. Your app keeps using the API.

Connect an AI client

MCP access is in preview. Permissions follow your account; Live changes require explicit confirmation. It is not an end-user chatbot.

Perkamo MCPOAuth · Preview

Hosted MCP endpoint

https://api.perkamo.com/mcp

Inspect your programget_program
Validate a proposed changevalidate_program
Review before changing LiveWrite access + explicit approval

Example workflow, not a live connection or agent session.

Before you build

Is Perkamo right for our business?

It fits businesses with a website or app, identifiable customers and a repeat action worth encouraging. You need a developer or agency to connect the API and build the customer-facing experience. It is not a ready-made stamp card, Shopify plugin or no-code loyalty app.

What if we have enterprise requirements?

Share your integration, security and rollout requirements with us before launch. Your team can evaluate the API, separate Test and Live Spaces, and customer event history in a free Test Space. Dedicated infrastructure and custom SLAs are not included in the standard pay-as-you-go offer; discuss any additional requirements with us before committing.

What can I try before connecting my app?

Create a free account to get a separate Test Space. Configure a small program, send test events from the console and inspect a test customer’s progress. No payment card or production integration is needed for that test. The interactive examples on this page are illustrations, not hosted widgets.

Will this increase sales or retention?

That depends on the action, the benefit and how you present it. Perkamo runs the program; it does not guarantee business results. Start with one behavior, record a baseline in your own analytics and compare outcomes in a pilot. Progress and point awards are not proof of incremental revenue.

Could my developer build this instead?

Yes. For a simple one-off counter, building it yourself may be enough. Perkamo becomes useful when you need changing rules, persistent customer state, safe event retries and a console for investigating results. Your developer still builds the integration and customer interface.

What would moving away from Perkamo involve?

You keep your customer IDs, interface and benefit fulfillment in your own systems. Customer state is readable through the API. Replacing Perkamo still requires moving relevant state and rebuilding the rule logic; there is no one-click migration promise. Keep your source events and assess this dependency in a Test Space before launch.

One behavior. One benefit.
Start with a test customer.

Create your free account, configure a small program and send a test event from the console. See the result before connecting your app or adding a card.

Create a free Test Space