Skip to content
Lamba
Sign In

Growth

Loyalty

Connect earn, spend, reversal, and retention activity to identity-linked loyalty context.

Before you start

Loyalty docs are Preview while dedicated loyalty API pages are completed. Use the Lamba console for program setup and visibility, then keep earn, spend, and reversal workflows tied to Lamba identity, Project scope, retention rules, and audit context.

What you build

Loyalty should stay attached to identity context:

  • Lamba User
  • Project membership
  • environment
  • source event
  • loyalty action
  • audit trace

Implementation steps

1) Configure the program in the console

Choose the Project, environment, earning rules, retention window, and plan-bound availability before showing loyalty features in your product.

2) Define the earning source

An earn event should point to the product action that produced it. Keep enough metadata to reconcile duplicates and explain support cases.

3) Define spend and reversal behavior

Spend and reversal actions should be idempotent. A reversal should reference the original loyalty action when possible.

4) Keep Project boundaries explicit

Do not let loyalty state from one Project silently apply to another unless your product has a documented cross-Project program.

5) Connect loyalty to events

Use webhook and audit events for downstream operations. Loyalty activity should not require a second customer identity graph.

API coverage note

Until a dedicated public Loyalty API reference is published, use console visibility, audit records, webhook delivery, and plan-limit responses as the integration boundary.

Security and operational notes

  • Treat loyalty balances and events as sensitive account data.
  • Log actor, Project, environment, event ID, and trace ID for manual adjustments.
  • Apply plan retention and usage limits before presenting long-range loyalty history.

Troubleshooting

If loyalty state looks wrong, check duplicate event handling, Project scope, reversal references, and whether sandbox events were mixed with production reporting.

  • Growth Workflows: /docs/growth/overview
  • Audit Events: /docs/reference/audit-events
  • Webhook Deliveries: /docs/reference/webhook-deliveries