Skip to main content

Customer data platform

One event-driven profile for every customer

Capture what users do across your app, website and campaigns as timestamped events, keep persistent attributes on each profile, and use both to segment, automate and personalize.

Read the docs

Reviewed:

Overview

AppBoost CDP is the event-driven customer data layer for marketing managers, product managers and data teams. It records system events automatically and custom events you define, stores persistent attributes such as LTV, last seen and platform on each user profile, and makes that data available for segments, automation journeys and personalized messaging.

Key facts

Event types
System events (auto-captured) and custom events
Event structure
Event name, userId, timestamp, properties
Attribute types
System and custom user attributes
Profile identifiers
userId, advertising ID (madid), devices
Custom data sources
App, website, POS through the SDKs
SDK setup time
5-10 minutes for most mobile SDKs

The problem

User data lives in separate systems

Installs, campaign opens and purchases are logged in different tools, so nobody can see one user across them. A CDP records each action as an event against a single user and keeps the attributes that describe that user.

Capabilities

What Customer Data Platform includes

  • Automatic system events

    Events such as appInstalled, appOpen, purchase, appPush open, email opened and landing page open are captured after SDK integration, with no tagging work.

  • Custom events

    Track events specific to your business, such as product_viewed, add_to_cart, checkout_started or loan_application_submitted, logged through the SDKs.

  • Structured event records

    Every event carries an event name, the userId, an exact timestamp and properties such as order ID, amount, currency and items, so events can be filtered and joined.

  • System user attributes

    Profiles fill automatically with attributes such as platform, country, city, app version, usagecounter, installationAt, lastSeenAt and ltv.

  • Custom user attributes

    Add your own attributes per platform, such as app, website or POS, and set them through the SDK so profiles reflect your business model.

  • Identity and devices

    Users are identified by the userId your app sets, the advertising ID and the list of devices, with reinstall count and the Smart Link that acquired them on the profile.

  • Campaign and automation events

    Email, SMS, push, web push and automation messages log received, open and conversion events, tying channel results to the same user profile.

  • Ready for activation

    Events and attributes feed segments, automation journeys and personalization variables, so the data is used directly in campaigns instead of sitting in a report.

How it works

How Customer Data Platform works

  1. 1

    Install the SDK

    Add the AppBoost SDK to your app or website. Users are detected and system events start recording automatically.

  2. 2

    Plan your custom events

    Choose the business events worth tracking, for example add_to_cart or subscription_started. Your account manager recommends a set during integration.

  3. 3

    Set custom attributes

    Send attributes that describe each user, using the Set Custom User Attributes section in each SDK guide.

  4. 4

    Verify on the profile

    Open a user profile to confirm events, attributes, LTV and timeline look correct before building on them.

  5. 5

    Activate the data

    Create segments, start automation journeys and personalize messages from the events and attributes you now capture.

Who it is for

Who uses Customer Data Platform

For marketing managers

Get customer data you can act on without asking for a report, from behavior and purchase history to channel engagement.

  • Segment on purchases, opens and inactivity
  • Trigger journeys from real events
  • Use lifetime value and order counts in targeting
  • See campaign engagement on the user record

For product managers

Define a clean event model once and reuse it across analytics, segmentation and automation.

  • Named events with userId, timestamp and properties
  • System events captured without extra code
  • Custom events and attributes set through the SDK
  • Consistent identifiers across app and campaigns

Use cases

Customer Data Platform use cases

  • 01

    E-commerce cart recovery

    Capture add_to_cart and cart abandonment events, remind users by push and email, and segment by ordersNum to treat repeat buyers differently.

  • 02

    Fintech application follow-up

    Track loan_application_submitted and loan_application_completed, then retarget users who abandon an application using pushEnabled and ltv.

  • 03

    SaaS trial conversion

    Track subscription_started and trial_expired, remind users before a trial ends, and use appOpen frequency to find engaged users.

  • 04

    Acquisition source analysis

    Use the Smart Link recorded on each profile to compare users who came from different links.

Frequently asked questions

Customer Data Platform FAQ

What is the difference between system and custom events?
System events are predefined by AppBoost and recorded automatically after integration, such as appInstalled, appOpen and purchase. Custom events are defined by you, such as add_to_cart, and logged through the SDKs. Your account manager usually recommends a set of custom events during integration.
What is stored on a user profile?
A profile holds system attributes such as userId, platform, country, city, appversion, usagecounter, installationAt, lastSeenAt and ltv, plus any custom attributes you define. Events are recorded against the same user through the userId.
How do users get identified?
The userId is set by your app, and the SDK captures the advertising ID (madid) and the list of devices automatically. Name, email and phone come from the user object your app sends, and attribution fields such as smartlink_id are stored on matching.
How much effort does integration take?
Installing the AppBoost SDK takes 5-10 minutes for most mobile platforms, and system events and attributes start recording after that. Custom events and attributes need a small amount of code where you call the SDK.
How does the CDP fit with Audiences and automation?
The CDP holds events and attributes, Audiences turns them into segments, and Marketing Automation and Omni-channel Messaging use those segments and events to send messages. The three share one user profile.
Can the data cover more than the mobile app?
Yes. Events and attributes are defined per platform, including app, website and POS, and are logged through the respective SDKs. There are SDKs for Android, iOS, Flutter and the web.

Give every customer one profile your team can use

Review your event model with the AppBoost team and decide which events and attributes to track first.

See pricing