From customer activity
to a useful email.
Bring website context and confirmed product events into one customer view. Give your email rules facts to work with.
What Alex explored.
What Alex saved.
Alex
alex@example.test
Explore the example · Fictional brands and data · No emails sent
A saved project.
A reason to include Alex.
Use the source that can establish the fact. Browsing a pricing page does not establish a purchase.
Project created
The product’s server confirms that Alex saved a project.
Fits the segment
The saved-project rule includes Alex in the audience.
Has permission
Marketing permission is checked separately. Alex has opted in.
Ready to review
Alex is included in the campaign about the new preview.
Open the captured example ↗Explore the website context in Alex’s profile
Website activity can start a Play.
When pixel plays are enabled for your workspace, site activity can start approved marketing workflows. The person still needs to be identified and eligible.
Keep confirmed facts separate.
Your server establishes purchases and consent changes. Pixel observations also build the profile; they do not mean barua rewrites each email live.
A few useful details.
Is this a standalone CDP?
This customer data is built for barua’s email workflows and customer view. It is not a general-purpose warehouse or an audience sync service for other destinations.
Does pixel activity change each email’s wording?
No. Email workflows use approved rules and reusable wording. Pixel activity can start a Play when enabled and also supplies profile context. It does not cause a live rewrite of each email.
Put your customer facts to work.
Tell us what your product knows about a customer and which email should come next.