Your personalization agent finds a customer record and serves their pricing, history, offers. Feels like a win. It isn’t.
Finding a match and confirming a match are two different things.
The agent treats them as one. Reads a cookie, hits your database, gets a hit, serves. But that cookie could be stale. Shared laptop. Reassigned to a new account entirely. A stranger gets someone else’s negotiated pricing — and your dashboard never flags it, because it only breaks on edge cases and washes out in the aggregate.
Government identity systems learned this the hard way. They call it identity proofing: never collapse “found a candidate,” “the signal is real,” and “this is actually that person” into one automatic step. Each can fail independently.
So split it into three gates. Do I have a signal. Is the signal trustworthy. Does it resolve to exactly one person. All three pass — personalization unlocks. Any one fails — hold the visitor in a neutral state instead of guessing.
The rule for every agent you run: a lookup is a claim, not a confirmation. Make it prove identity before it acts on identity.
InTheValley senior engineers know how to build the three-gate identity proofing check into your personalization layer.
