Skip to main content
Members are the end consumers who earn and redeem points in your loyalty program. Loyalife gives administrators a unified view of every member — from their profile and linked accounts to their full transaction history and current tier standing.

​
What is a member?

A member is any individual enrolled in the loyalty program. Membership can be created:
  • Via API (your application calls the Create Member API at sign-up or onboarding)
  • Via file upload (bulk CSV import for existing customer bases)
  • Via the partner app (channel partners onboard retailers or customers directly; subject to approval if the Maker-Checker workflow is enabled)
Once created, a member receives a unique Relation Reference (the program’s own member identifier — CIF number, account number, or equivalent) that never changes and is used across all queries, reports, and reconciliations.

​
Accessing the Members module

Select Members from the left sidebar. The members list shows:
Manage Members screen listing enrolled members with Relation Reference, Member Name, Phone Number columns and a search bar with filter options
Use the search bar to find members by Relation Reference, name, phone, email, or card number. Use filters to narrow by status, tier, or registration date.

​
Member identifiers

Every member has a Relation Reference plus up to two product-linked identifiers:

​
Identifier rules

These rules apply to both API calls and file-based member imports.

​
Member statuses

Inactive members can still query their points balance, view transaction history, and access profile details via API. Redemption is blocked until the member becomes active again. This ensures members retain visibility of their account even during inactive periods.

​
What you can do

From the Members module you can:
  • Search, filter, and export members — find specific members or build segments for export
  • View member details — access a full profile including transaction history, linked accounts, and tier status
  • Perform bulk point adjustments via CSV upload
  • View and export linked accounts and card data

​
Permissions

Actions such as suspending, blocking, or cancelling a member may require Maker-Checker approval depending on your program’s configuration. Changes submitted without approval appear in the Approval Workflow queue until a checker acts on them.