Skip to Content
CDPCDP Overview

CDP in ResultFly

ResultFly includes a built-in CDP layer for collecting customer data, linking it to the right person, and turning it into usable audiences for campaigns and operations.

For marketing teams, this means one place to work with:

  • customer profiles
  • incoming customer events
  • communication channels and consent
  • derived customer facts
  • dynamic segments
  • audience export

For developers, this means ResultFly exposes a stable ingest contract with API keys, idempotent event delivery, and deterministic profile matching.

What the CDP Does

The CDP helps ResultFly answer a practical question: “what do we know about this customer right now, and which audience do they belong to?”

The answer is built from several layers:

  1. A customer profile stores core customer facts such as name, city, loyalty status, or balance-related fields.
  2. Identifiers link data from different systems to the same person.
  3. Communication channels store where the customer can be reached and what consent status is currently known.
  4. Incoming events describe things that happened around the customer, such as purchases, tier changes, or service interactions.
  5. Derived attributes turn event history into reusable facts such as total spend, last purchase date, or current tier.
  6. Segments turn all of the above into saved audience rules.
  7. Audience export lets teams send those audiences to downstream tools.

What the CDP Is For

  • Building audiences from real customer behavior, not only from campaign clicks.
  • Connecting loyalty, CRM, POS, ticketing, app, or service data to ResultFly.
  • Understanding a person across multiple identifiers and channels.
  • Reusing the same customer logic across many campaigns.
  • Exporting vetted audiences for analytics, communications, or activation.

What the CDP Is Not

  • It is not a campaign builder.
  • It is not an outbound messaging system by itself.
  • It is not a replacement for the brand’s CRM or loyalty platform.
  • It is not the same thing as campaign runtime variables.

Campaign variables still exist in ResultFly and are useful for flow logic inside campaigns. But they are a runtime mechanism, not the main customer-data model. Use the CDP when the goal is to understand people, events, channels, and audiences across the organization.

Start Here

If you are integrating your own backend, continue with Developers → CDP Integration and API Reference → Event Ingestion.

NodesCustomer Profiles