Predicted customer value
Early in the customer's life.
SOLUTION
Your order and CRM history already separate your best customers from one-time buyers. Datahash turns that history into predicted value, value bands, and lifecycle stages, then feeds them to bidding and audiences on Meta, Google, and the other platforms you buy on.
IN ONE SENTENCE
Customer value and segmentation is a solution that scores each customer from first-party order and CRM history, predicted value, value band, lifecycle stage, and category affinity, and sends those scores to ad platforms as conversion values and audiences.
WHEN THIS IS YOU
Early in the customer's life.
From recency, frequency, and spend.
Prospect, first buyer, repeat, lapsing, lapsed.
So acquisition spend can exclude or down-weight them.
So audiences match what each customer is likely to buy next.
Custom events for first-time purchasers.
Learn moreGoogle's new customer acquisition goal.
Learn moreHigh-value seeds for lookalikes, existing-customer exclusions, and stage-based segments, refreshed from your source of truth.
Illustrative. No client numbers.
Order and CRM history, identifiers, and consent checked; the business question agreed.
Which scores and segments, which platforms, and the test agreed, with a go or no-go on fit.
Scores computed and delivered as values and audiences, verified in each platform.
Results read against your current campaigns with a holdout, then refreshed on a schedule.
It depends on the score. Value bands and lifecycle stages work from a year or so of orders. Predicted value and category affinity need more customers and more history before they beat simpler rules, so we start with what your data supports today and move to predictive scores as the history grows.
No. Our consultants work out with you which scores the goal needs and what it takes to produce them from the data you hold. If your team already has customer scores, we can use them. Bring whoever owns your customer data to the first working session.
Scores reach the platforms the same way conversions do: hashed identifiers on consented records, sent server-side. The platforms receive a value or an audience membership, not your customer database or the logic behind the score. Consent is checked before any record is sent.
Yes. Existing-customer and recent-buyer exclusions are among the first things we set up, because they need no prediction at all, just an accurate, refreshed list of who already buys. Acquisition budgets then go to people who are actually new, and the list keeps refreshing as customers buy.
NEXT STEP