The Card Based Segmentation approach streamlines operations, improves the efficiency of loyalty programs, and generates valuable data that enables merchants to learn more about purchasing behavior in their businesses.
⚠️ Note: Limited availability. This feature is strictly available for Heartland merchants using Heartland/Global Payments Processing.
📋 Table of Contents
How It Works
1. Collect Card Linking Consent: Before card linking begins, member consent must be collected across onboarding or profile management channels. Permission updates and consent states are securely logged to the member's audit history.
2. First Transaction: When a member makes their first identified transaction (using phone number, email, or another identifier available in the loyalty program) and uses a credit card for payment, Como automatically links that specific card to their profile.
3. Ongoing Transactions: From then on, all transactions made with that card are automatically attributed to the member's profile - even if they didn't explicitly identify themselves with their loyalty account during checkout.
4. Multiple Cards: If a member uses multiple cards, any new card used in an identified purchase will also be linked to the same profile to ensure all points accumulate correctly.
ℹ️ Note: In cases where another member uses the same token previously linked to a different member, the token will be re-linked to the most recent member who made an identified purchase with it.
5. Data-Driven Insights: The program continuously analyzes transaction data to offer tailored promotions and rewards, enhancing the member experience while driving engagement.
To setup Card-Based Loyalty
1. Ensure you are using Heartland or Global Payments processing.
2. Configure Card Linking Consent via registration forms, import files, or Campaign Center rule actions.
3. Go to POS & Connectivity > API Keys.
4. Under API Keys, enable the token features:
-
Enable All Payment Token Features: Enables all payment token collection and linking functionality at once.
Alternatively, you can toggle individual flags as needed:
| Setting Flag | Description |
|---|---|
| Allow Payment Token Collection | Enables collection of payment tokens for segmentation purposes. |
| Allow Payment Token Linking for Loyalty Identification | Enables member identification based on payment tokens linked to their profile. |
| Show Card Link Status (Optional) | Allows third parties to view whether a member has a card linked to their profile. |
Consent & Onboarding Options
Merchants can capture and manage card-linking consent flexibly across multiple channels:
-
Registration Form Checkbox: Merchants can add a dedicated, optional
AllowCardLinkingcheckbox directly to custom Registration Form layouts or mobile/portal views. -
Mobile App & Portal Legal Notice: Whenever the
AllowCardLinkingfield is deployed on the Mobile App or Customer Portal, it automatically displays a system-controlled, multi-language legal description ("I want my payment card to be linked to my account...") that cannot be edited or removed. -
Member Import Files: Consent states can be captured via an optional
AllowCardLinkingschema field during file imports. -
Rule Engine Action: Under Campaign Center rules, an Allow Card Linking selection is available under the Update Member Preferences action. This selection is strictly restricted to Joins the Program or External Event Submitted triggers and carries a mandatory legal sensitivity notice.
- Migration & Existing Members: Existing businesses can either acknowledge consent for current members or require a new opt-in during profile updates.
ℹ️ Technical Notes
- Cross-Location Functionality: Card-based segmentation works across all locations; the same token is generated at each location.
- Card Limit: Users can link as many cards as they want to their account, but they must identify themselves at least once per new card to link it.
-
Audit History: Every consent state, source, and action change is fully tracked in the member's audit log.
Steps to Access the Member's Audit Log:Log in to the Como Sense Hub and search for the relevant member using their Phone Number, Email, Member ID, or Name in the Find Member search bar.
Click on the member's record in the search results to open their profile details.
View the Activities tab to view the complete chronological history of changes and events.
Card-Based Segmentation Dashboard
A dedicated dashboard under All Dashboards allows merchants to measure the impact of using card segmentation tokens. Merchants can filter metrics by Member/Non-Member status, date, member status (Active or Deleted), purchase status (Completed or Canceled), and whether an identification token is included in the purchase.
| Field | Description |
|---|---|
| Buying Tokens | Number of distinct tokens that made a purchase. |
| New Tokens | Newly registered tokens. |
| Tokens - Avg. Spend per Visit | Average amount spent per purchase using a token. |
| Tokens per Member | Total number of tokens (including unidentified) divided by purchasing members. |
| Identified Tokens per Member | Average identified tokens per member. |
| Tokens - Sales | Total sales linked to tokens. |
| Tokens - Visits | Total visits linked to tokens. |
| Visits per Token | Average visits by a token (purchases divided by distinct tokens). |
| Sales by Location | Breakdown of total token sales by location. |
| Monthly Trend - Sales / Avg. | Token sales and average trends broken down by month. |
| Monthly Trend - Sales | Token sales breakdown by month. |
| Monthly Trend - Avg. Spend Per Visit | Token Avg. Spend per Visit breakdown by month. |
| Monthly Trend - Visits | Token visits breakdown by month. |
| Monthly Trend - Distinct Tokens | Unique token breakdown by month. |
| Monthly Trend - New Tokens | New tokens breakdown by month. |
| Monthly Trend - Visits Per Token | Average visit breakdown by month. |