CDP in ResultFly

CDP stands for Customer Data Platform.

In plain terms, a CDP is the place where a company gathers customer data from many systems and turns it into one usable customer view. It stores not only who the customer is, but also what happened in the customer’s relationship with the business over time.

Without a CDP, each system usually knows only its own fragment:

a CRM knows the customer’s name and status
a loyalty system knows points, tiers, and rewards
a POS or ecommerce system knows purchases
an app or website knows clicks, sessions, and form submissions
a support or ticketing system knows service history

A CDP connects those fragments. It helps answer questions like:

“Is this email address, phone number, loyalty ID, and app user the same person?”
“What has this person done recently?”
“Which channels can we use to contact them?”
“Which audience should they belong to right now?”

The important idea is that a CDP is not just a contact list and not just an analytics dashboard. It is a customer-data layer: it collects data, links it to the right person, keeps reusable customer facts, preserves the history of customer events over time, and makes those facts available for segmentation, reporting, personalization, and export.

For example, instead of asking every campaign to separately check purchase history, loyalty status, consent, and app activity, the CDP can keep those facts in one consistent model. Campaigns and downstream tools can then work with audiences such as “active loyalty members in Berlin who bought in the last 30 days and allowed email communication.”

For the business, this turns customer data into practical operating value:

customer understanding: teams see the real picture of customer interests, behavior, and history
accurate segments: audiences are built from actions and interests instead of guesses
personal communications: teams send the right message through the right channel at the right time
more engagement: relevant offers increase response and loyalty
revenue growth: better audience work can increase purchases, visits, and loyalty program participation
clean and reliable data: fewer duplicates and errors create more trust in the data

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
profile attributes
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:

A customer profile stores core customer facts such as name, city, loyalty status, or balance-related fields.
Identifiers link data from different systems to the same person.
Communication channels store where the customer can be reached and what consent status is currently known.
Incoming events describe things that happened around the customer, such as purchases, tier changes, or service interactions.
Profile attributes turn customer data into reusable facts such as total spend, last purchase date, or current tier.
Segments turn all of the above into saved audience rules.
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.