Insights

Perspectives on customer data as infrastructure.

Category thinking, architecture, and field notes on identity, deployment, activation, and first-party data monetization, written by the people who own these decisions.

The Blog

Latest thinking.

Illustration of a shopper discovering sponsored beauty products across Khanoumi’s shopping journey, with ad delivery and reporting infrastructure below and the Khanoumi and Binoban logos.

From sponsored products to Retail Media

More than 300 million impressions, three million clicks, and five active placements: how Khanoumi’s BeautyAds is building a Retail Media business on Binoban.

Read the article →
An experimenter compares two similar greenhouse boxes, waters one and measures the difference in growth.

Did the Campaign Make a Difference? A Practical Guide to Incremental Measurement

Define a valid outcome, assign a holdout and compare rates to estimate what changed because of the campaign.

Read the article →
A merchant selects a useful benefit at a workbench while balancing customer value and incentive cost.

Beyond Blanket Discounts: Choosing Incentives Around Customer Value and Margin

Connect each benefit to a customer need, account for its cost and test whether the policy creates additional contribution.

Read the article →
A customer moves across stepping stones from receiving a lamp to using it and considering a compatible accessory.

The Second Purchase: Building a Journey Around Customer Progress

Recognize delivery, use and changing needs to build a second-purchase journey with clear eligibility, exits and measurement.

Read the article →
A conductor coordinates message instruments around one customer carrying a completed purchase.

One Customer, Multiple Channels: Keeping Messages in Sync

A shared audience is the beginning. Consistent communication also needs current state, send-time checks and a clear path for cancellation.

Read the article →
A gardener operates separate gates as customers enter, remain in and leave a living audience garden.

Dynamic Audiences: Building Segments That Follow Customer Behavior

Define entry, exit, timing and exclusions so a customer’s next action changes the audience they belong to.

Read the article →
A human-operated switchboard connects customer evidence to one useful message while holding back excess envelopes.

From Customer Data to Customer Action: A Practical Guide to CDXP

Follow one customer from a completed purchase to a useful next contact, and see how identity, customer state, audiences and execution fit together.

Read the article →
Illustration of a woman carrying groceries, receiving a reward coin in her wallet, and driving across the city toward the next reward, with the same journey shown below as connected steps, above the Ozone and Binoban logos.

How Ozone connects Okala and Tapsi in one customer journey

An Okala purchase leads to a Tapsi ride, and the ride leads back to Okala. How Ozone runs this journey across services on Binoban.

Read the article →
Illustration of a person feeding raw customer signals, purchases, products, timing, payments, and messages, into a machine that stamps out a repeated customer profile, which then routes to audiences, journeys, and messaging.

From Events to Customer State: Why Computed Traits Matter in a CDXP

Customer data tells us what happened. Computed Traits help us understand what that history means now, and make it usable for segmentation, journeys, personalization, and decisioning.

Read the article →
Illustration of customer data inputs, profile, transactions, timing, terms, and shipments, feeding a decision engine that outputs revenue, personalized recommendations, and marketing, with results looping back into the system.

Let's Start Moving CDXP Beyond Marketing

The same architecture that scores a message can also decide credit limits, financing terms, and advertiser recommendations.

Read the article →
Illustration of a robot generating a stream of clicks across product cards into an invoice printer, contrasted with a person completing one real purchase that arrives as a verified, delivered box.

If an Agent Clicks an Ad, Who Pays for It?

For years, the advertising industry treated all non-human traffic as one thing: bots, crawlers, fraud. An agent fits none of those categories, and its click needs a different unit of measurement.

Read the article →
Illustration of a person calibrating the distance between a human customer profile and a separate agent profile, with search, comparison, and cart actions passing between them without merging the two.

An Agent Is Not the Customer's Twin

Identity, profiles, and data contamination in Agentic Commerce.

Read the article →
Illustration of a person imagining a product while a robot filters candidate options down to one, then routes the chosen item through stores and delivery to arrive at the door.

The Store Gets the Order. But Who Shapes the Purchase Decision?

Power, AIDA, and the economics of Retail Media in the age of agents.

Read the article →
Illustration of people hiding behind report pages while a person looks ahead through a giant telescope built from data charts, spotting a growing tree of opportunity in the distance.

When data becomes a defense mechanism

The hidden risk for leaders is not irrationality. It is safe, data-backed sameness. Data should be an instrument of foresight, not a shield against blame.

Read the article →
Illustration of a person connecting an underground machine holding customer and product data to an above-ground retail media machine that prints impression and conversion tickets for a featured product.

Retail media is not an ad product. It is a data infrastructure problem

The durable retail media business is built on trusted data, catalog quality, measurement, and settlement, not on ad placements alone.

Read the article →
Illustration of a person operating a self-contained, walled machine that resolves customer profile cards into a single identity, holding keys to its access, with only a verified result passing through to the outside.

Why on-prem customer data platforms are coming back

A market correction driven by data residency, integration gravity, AI governance, and the operational reality of large enterprises.

Read the article →
Illustration of a person turning a gear that connects scored customer profiles to a robotic arm delivering a message to a customer, with the outcome measured on a balance scale and looped back into the system.

AI in customer data will fail unless it can activate and measure decisions

Prediction is rarely the problem. AI creates value only when scores become activated, governed, measured decisions.

Read the article →
Illustration of a website page emitting content, engagement, and scheduling signals into a machine that a person operates, checking consent before routing the result to a contact record, settings, a message, and support.

How Binoban tracks and activates visitor intent on its own website

A website should not only publish content. It should understand intent and route demand, inside its own consent boundary.

Read the article →
Illustration of a person operating a machine that turns customer profile cards and behavior signals into a growth chart, powering a personalized storefront, an audience segment, and an ad placement, while coins collect in a revenue crate.

The economics of first-party data monetization

Monetization should be evaluated as a controlled business line, not a campaign add-on, with its own revenue logic and payback.

Read the article →
Illustration of a person standing at a signpost between a red build path, with engineers assembling tangled hardware amid clutter and a declining chart, and a green buy path, with a running machine outputting checked deliverables and a growth chart.

Build vs buy: why enterprise CDXP is harder than it looks

The instinct to build internally underestimates the real work: identity, consent, integrations, governance, and maintenance.

Read the article →
Illustration of a person operating a locked, fenced data center that receives customer signals from the left while blocking outbound connections to external cloud services on the right, with a city skyline beyond the perimeter.

On-premise MarTech is control, not compromise

For large enterprises, deployment model is a strategic decision about data ownership, security, and governance, not a step backward.

Read the article →
Illustration of a person comparing two machines: a data-storage machine on the left consolidating customer signals into one profile, and an activation machine on the right routing that profile out to multiple outbound channels.

CDP vs CDXP vs CRM: what enterprises actually need

CRM, CDP, BI and marketing automation each solve part of the problem. Enterprises need the layer that makes them agree.

Read the article →
Illustration of a person operating a machine that ingests customer signals from the left, resolves them into a glowing unified identity, and routes engagement across channels like email, chat, and notifications to individual people on the right, powered by identity, integration, intelligence, orchestration, and measurement modules.

CDXP is a category, not a feature

The category that turns a website from a brochure into an operating surface.

Read the article →
Illustration of a person operating a machine that resolves a stream of fragmented, overlapping identity fragments into a single verified profile, then locks the resolved record behind a secured, keyed server.

Identity resolution is a control problem, not an accuracy contest

Vendors compete on match rate numbers. Enterprises should ask who controls the rules, and where the data lives.

Read the article →
Illustration of a person operating a retail media console with audience segments and analytics, routing sponsored product, brand, and display campaigns through a pipeline to on-site, app, web, and search placements, turning audiences into revenue.

Retail media begins with first-party intelligence, not ad inventory

Durable media revenue is built on identity and audience quality you actually own, not on the scramble for sponsored placements.

Read the article →

Work with the team

Bring a hard customer data problem. We'll bring the architecture.