A common problem / a joined result
We don't know who our repeat customers are
Recognise repeat buying across channels when the identity evidence supports it.
Talk through the sources behind your question.
Sound familiar?
The same person buys online, returns to a shop and uses a reward. Each system shows a separate record, so your team keeps treating a returning customer as new.
The pieces live apart.
Orders, receipts and loyalty activity use different keys. Counting repeat purchases needs a supported link between those records and a clear rule for what counts as a return.
Online store
The first paid order
POS
The later store purchase
Loyalty
The shared member ID
Each source has a piece. The join gives the pieces a shared meaning.
One rule. A useful result.
Example rule / events → tag
Online store: first paid order
POS: later paid purchase
Loyalty: reward used
In this order, within 90 days, on the same confirmed member ID.
Resulting tag
Cross-channel repeat customer
Illustrative rule. Sources, match keys and timing are agreed in the build.
What you get
- Repeat buying defined across the sources you join.
- Supported identity links with uncertainty visible.
- A customer tag for your chosen CRM or email tool.
Systems usually joined: Online store, POS, Loyalty. The team checks the records, match keys and destination with you.
A question that crosses teams.
Retail, hospitality and customer teams planning service and retention around repeat visits.
Good questions. Clear answers.
What counts as a repeat customer?
Your team chooses the rule. It might require two paid purchases in a set window or a return across channels. The formula shows the events and conditions you agreed.
Can two people sharing an email be merged?
A shared email can be ambiguous. The team checks the identity evidence and keeps conflicts visible rather than assuming those records belong to one person.
Can the tag go to our email tool?
Yes, through the destination route agreed in the build. Your team also agrees which records and data controls are appropriate for that use.
Follow the next piece.
Related problems
Definitions & comparisons
Build it with us
Bring the problem. We'll map the pieces.
A dedicated team checks the sources, defines the result and builds it with you. Scope and price are agreed with the team.