Skip to Content
OverviewUser Identity & Identification

User Identity & Identification in ResultFly

1. Introduction: What is a User in ResultFly

ResultFly operates alongside the brand’s CRM, POS, and loyalty platforms. A user in ResultFly is an internal record that captures someone’s participation in campaigns rather than a copy of the CRM profile. Users can even be created before a person ever opens a campaign—or when they never plan to enter one—so the brand can preload rewards, statuses, or entitlements.

  • A single ResultFly user can reference multiple records in the client’s systems.
  • Campaigns need stable identifiers, even when the brand chooses not to pass personal data.
  • The user record can be born in ResultFly first and later linked to marketing or CRM data.

2. Identity vs User: Key Concept

User is the unified record where progress, achievements, prize rights, and other campaign states are stored.

Identity is the way ResultFly recognizes that a visit or transaction belongs to that user. Identities may come from a brand app, a loyalty program, an offline receipt, or a ResultFly form.

One user may have several identities. This connects activity across mobile apps, offline receipts, and web campaigns without duplicating information or sharing unnecessary personal details.

3. Why Identity Mapping Matters

  • Offline to online. An in-store purchase can grant points in a digital game as long as the receipt carries an identity already known to ResultFly.
  • Loyalty to campaign. The loyalty program sends a participant ID; ResultFly uses it to continue progress in a campaign instead of starting from scratch.
  • Cross-channel experience. The same person opens a push notification, joins a promo on the site, and receives an SMS. Identity mapping keeps it as one story rather than three separate sessions.
[Web / App / POS event] -> [Identity recognized] -> [ResultFly user] -> [Points, statuses, prizes]

4. Identity Management Modes

Mode A: Client-Managed Identity (Privacy-First)

  • The client identifies the person and passes ResultFly a pseudonym, token, or hash—any durable string that only the brand’s systems understand.
  • ResultFly stores the internal user record and never sees the email or phone.
  • Ideal when the brand enforces strict privacy controls, works inside owned apps, or follows enterprise security standards.

Mode B: ResultFly-Managed Identity

  • ResultFly requests the email or phone directly and verifies it with a one-time code.
  • The platform confirms that the participant is real and reports a verified presence in the campaign.
  • Useful for standalone campaigns, lead-generation, or quick launches without deep IT involvement.

Both modes are peers: campaigns track progress in exactly the same way, and the choice only depends on business context.

5. Hybrid Scenarios

Hybrid scenarios are possible, but the exact mechanics and rollout details are still being defined. Please contact your ResultFly platform manager for the latest guidance and availability.

6. What Data ResultFly Sees (and Does Not See)

Required data

  • ResultFly internal user ID (created automatically, including for pre-provisioned users).
  • The identity chosen by the client (pseudonym, token, email, or phone depending on the mode).

Optional data

  • Name, city, segment, or any additional attributes the brand is comfortable sharing.
  • Event or transaction parameters that do not contain personal data (for example purchase value, category, or channel).

What may be absent altogether

  • Email and phone when the client prefers the privacy-first mode.
  • CRM personal fields that are irrelevant to campaigns.

Personal data (PII) is governed by the brand: the client decides what to send and how long to keep it, and ResultFly follows the policy—up to working solely with pseudonyms.

7. Choosing the Right Identity Strategy

  • If you have your own app and strict security policies, lean on the client-managed mode with tokens or hashes.
  • If you are launching a campaign without IT support and need fast lead capture, use the ResultFly-managed identity mode.
  • If you want to start privacy-first but later add email for communications, begin with Mode A and enable ResultFly verification for the same users when the brand is ready.
  • If offline transactions drive the mechanic, align on the identity that the POS or ERP already provides before the campaign starts.

8. How This Affects Campaigns & Games

  • Points accumulate on the user. Once the identity is matched, scores from different channels immediately add up—even for users who have not visited the experience yet.
  • Attempts, limits, and access to levels are tied to the user record, so participants keep their progress even when they switch devices.
  • Leaderboards show users rather than isolated sessions. Reliable identification boosts trust in rankings.
  • Prizes and fulfillment connect to a confirmed user, making it easier to control distribution and prevent abuse.

ResultFly remains a transparent link between the brand and the participant: the platform helps agree on identity, does not force a single method, and never asks for unnecessary data.

Last updated on
NodesExternal Events