Customer data

Know the person behind the purchase.

Connect customers, purchases and accounts. Give maxinja the context to recommend a message that fits.

Halden Coffee example

The same catalog. A different next coffee.

CContact

Sarah Bell

Brewer: V60 pour-over
Likes: Bright, fruity coffee
Preference: Try a lighter roast

Preferences that explain the choice.

Bought by SarahOOrder object

House Espresso

Product from the last order

Available in the example catalogPProduct object

Ethiopia Yirgacheffe

Light roast
Citrus and jasmine

OEventOrder completedSarah bought House Espresso.

Person + purchase + product context.
A lighter roast for bright, fruity pour-over coffee.

V60 pour-overTry a lighter roast

The message this context makes possible

Halden

Your next cup starts here.

Hi Sarah,

Try Ethiopia Yirgacheffe for your V60 pour-over. Its light roast and citrus and jasmine notes suit the bright, fruity coffee you enjoy, while giving you the lighter roast you’d like to explore after House Espresso.

Find your next coffee

One business. Every customer’s context.

Connect people to orders, products, accounts and subscriptions. Keep shared business records separate from each person’s activity.

Facts you store. Answers you calculate.

Store known details, such as a brewing preference. Evaluated attributes find related records and calculate answers from the data you maintain.

Stored fieldBrewing preference

V60 pour-over

A fact supplied with Sarah’s customer record.

Evaluated attributeLatest order

House Espresso

A related order found by a saved definition.

Explore evaluated attributes

Remember the event. Check the present.

An event records what happened. Your journey can wait, check current records and stop a follow-up that no longer fits.

Explore customer events

The momentOrder completed

Keep the original purchase details.

The later checkA newer order?

Query the maintained customer records.

The decisionFollow up if still relevant

Use the condition in your configured journey.

Find the next reason to write.

Find repeat buyers who have gone quiet. Use their last order to make the return invitation personal.

Explore audience building

Native Halden audience definition: at least two recorded orders and a most recent order at least 14 days ago.

Returning regularsSaved Halden audience definition

Customers with at least two recorded orders whose latest order was at least 14 days ago.

Bring records through REST or CSV and keep the source current. Explore data connections

Start with the customers you want to reach.

We’ll connect the customer, purchase history and product details behind it.

Book a demo