Skip to Content
CDPCustomer Profiles

Customer Profiles

A customer profile is the central record ResultFly uses to represent one person inside the CDP.

It is not meant to be a full copy of the brand’s CRM. Instead, it is the ResultFly view of the customer: the set of facts needed for segmentation, audience activation, support, and future campaign decisions.

What a Profile Contains

A profile can store business-relevant customer fields such as:

  • name fields
  • city
  • birth date
  • loyalty registration date
  • loyalty status
  • bonus balance
  • expiring bonus amount and expiry date

ResultFly can also show convenient top-level contact values such as email or phone on the profile card. These are useful for display and simple filtering, but they are not the full communication model.

Why Profiles Matter

Profiles give teams one customer-level view across many incoming systems.

That helps with:

  • seeing a customer’s current status before launching a campaign
  • building audiences from profile facts and behavior together
  • investigating support questions without searching several source systems
  • exporting audiences based on the latest customer view

Profiles Can Exist Before a Campaign Visit

ResultFly does not require the customer to open a campaign first.

A profile may appear because:

  • a backend system sent an event for that person
  • a loyalty or CRM import path provisioned the person ahead of time
  • the customer was identified through an app, site, or form flow

This makes it possible to prepare balances, tiers, or access rights before the customer ever opens a ResultFly experience.

Profile vs Campaign Variables

Profiles belong to the CDP and describe the person.

Campaign variables belong to runtime execution and describe how a specific campaign behaves for that person.

Examples:

  • “Loyalty status is Gold” belongs on the profile.
  • “User has 2 attempts left in this campaign” belongs in campaign variables.

If a value must be reused across segmentation, exports, and customer operations, it usually belongs in the profile or in derived attributes, not only in campaign runtime.