# Profiles & segments that update as users act

> Product · Data

Unify client and server events into live profiles. Build dynamic segments that enter and exit journeys automatically — no CSV exports, no overnight sync lag.

Canonical URL: https://tappd.io/product/profiles-segments

## The problem

Static lists go stale the hour you export them. Product events live in analytics, billing events in Stripe, and “who should get this message” becomes a spreadsheet argument. By the time the audience is “ready,” the moment has passed.

## How Tappd helps

Tappd keeps a real-time profile per user: attributes, devices, lifecycle stage, and the behaviors you stream from the SDK or Track API. Segments are queries on that stream — when someone matches, they can start a journey the same minute.

## At a glance

- **Live** — Segment membership
- **SDK + API** — Event sources
- **Auto** — Journey entry & exit

## Capabilities

### One profile across apps

Useful when you run more than one product — the same person can carry context across iOS, Android, and web without stitching IDs by hand every campaign.

### Dynamic segments, not lists

Combine attributes and behaviors: “trialing, invited teammates, never opened billing.” Membership updates as events arrive.

### Server-side truth via Track API

Send purchases, subscription changes, and backend milestones the client never sees — so messaging reflects revenue reality.

### Journey-native audiences

Drop any segment into a trigger or branch. No export to a CEP, no waiting for a warehouse sync to finish.

### Device & channel readiness

Know who can receive push, who has an active session, and who last opened — before you burn a send.

### Built for product events

Name the events your product already emits. Tappd doesn’t force a marketing taxonomy that fights your schema.

## Example: dormant power users

You want everyone who was highly engaged and then went quiet for 28 days — without maintaining a weekly CSV from analytics.

### 1. Stream the signals

SDK sends session and feature events; Track API sends plan and seat changes from billing.

### 2. Define dormancy

Segment: last_active > 28 days AND lifetime_sessions > 20 AND plan != churned.

### 3. Enter win-back

On segment entry, start a win-back journey with personalized offer steps.

### 4. Exit on return

Any new session removes them from the segment and stops the sequence.

## Who it’s for

- Data-informed growth teams tired of stale lists
- Engineers who want a clean event contract once
- CRM leads coordinating mobile + web without a CDP project

## FAQ

### Can I send events from my backend?

Yes — use the Track API for server-side events. Pair it with the SDK for client behavior and push/in-app delivery.

### How fast do segments update?

As events stream in. Users can enter and exit journeys based on live membership rather than a nightly rebuild.

### Do I need Segment or a CDP first?

No. Many teams start with the SDK + Track API. Segment is available if you already run it — see Integrations.

## Related

- [Integrations](https://tappd.io/product/integrations)
- [Journey builder](https://tappd.io/product/journeys)
- [Win-back solution](https://tappd.io/solutions/win-back)

---

[Get started](https://tappd.io/) · [Contact sales](https://tappd.io/sales) · [Docs](https://docs.tappd.io)