May 10, 2018

Blockchain in Digital Marketing: Uses, Limits and Evaluation

Marketing teams have a reasonable interest in tools that make spending, partner activity and payments easier to verify. Blockchain is sometimes proposed as a way to create a shared record across organizations that do not use the same systems.

That is a specific capability worth evaluating. It does not automatically establish that an impression came from a person, that a sale was valid or that the underlying data is private.

how block chain works

We approach the question through the business problem: what needs to be reconciled, who must agree on it and why would a distributed ledger improve the existing process?

What blockchain can establish

NIST describes blockchain as a shared digital ledger whose cryptographic structure makes alteration evident and more difficult. Participants maintain records under the network's validation and consensus rules.

This can help establish that a record was accepted and preserved under those rules. It does not, by itself, prove that the external event described in the record happened as claimed.

For marketers, that distinction separates an audit trail from an independent measurement of customer behavior.

Transparency: a shared record still needs shared definitions

A marketing transaction can involve an advertiser, agency, publisher and several technology providers. A shared ledger might help participating organizations reconcile selected events or agreed charges.

The proposed benefit depends on what each party records and makes visible. If fees are omitted, definitions differ or key participants do not contribute, the ledger will not reveal a complete picture simply because it is distributed.

Ask which discrepancies the system is intended to resolve. Would it reduce manual reconciliation? Make changes easier to audit? Clarify a defined payment obligation? Compare that benefit with the cost of integration and governance.

There are also established approaches to supply-chain transparency outside blockchain. IAB Tech Lab's sellers.json and SupplyChain specifications help buyers identify sellers and intermediaries in programmatic advertising. Evaluate the tools appropriate to the problem before selecting a particular architecture.

Fraud: a recorded event is not proof of genuine activity

An invalid click or fabricated impression can still be submitted as data. Recording it in a ledger does not turn it into a valid customer interaction.

The system needs a dependable way to assess the event before it is used for reporting or payment. That may involve source validation, traffic analysis, partner review and other controls suited to the risk.

Ethereum's documentation on oracles explains the challenge of bringing external information into smart contracts. The correctness and availability of the input remain important dependencies. A contract can execute as written and still produce an undesirable result if its inputs are wrong.

For an advertising proposal, ask who verifies the source, how disagreements are handled and what happens when a provider supplies bad data. A credible answer should explain the controls rather than promise that fraud becomes impossible.

Tracking and smart-contract payments

Consider an affiliate payment triggered by a qualifying purchase. A smart contract could automate a defined step after receiving an accepted signal, but the purchase still has to be identified and validated outside the ledger.

The workflow must account for program rules, attribution, cancellations, returns and disputes. It also needs a way to handle corrections without pretending that every initial order is final.

Define the roles clearly: which system records the purchase, who validates it, who authorizes payment and how exceptions are resolved. The commercial agreement and the code should describe compatible behavior.

Automated execution does not eliminate implementation risk. Ethereum's smart-contract security guidance discusses vulnerabilities and the need for access controls and other safeguards. Marketing teams should require qualified technical review for a system that controls payments or sensitive operations.

Privacy: visibility and confidentiality are different goals

A ledger designed to make information visible to several participants raises a separate question: who should be able to see which data?

Do not assume that cryptographic linking makes every stored field confidential. A public record and a restricted business record require different access and data-handling decisions.

Map the information before choosing the design. Identify what must be shared, what should remain in existing systems and how the organization will handle retention and correction requirements. Involve the people responsible for privacy, security and legal review early enough to influence the architecture.

A useful marketing audit trail should disclose only what is needed for its purpose. Adding more copies of sensitive information is not, by itself, a privacy improvement.

Validation speed and scale

Blockchain is a family of approaches. NIST's technical overview distinguishes different permission and consensus models, so a single processing-time claim should not be applied to every implementation.

For a proposed marketing use, define the actual performance requirement. Selecting an ad in real time and reconciling a completed campaign have different timing needs.

Ask for measurements at the expected transaction volume, including fees, storage, error handling and the time until a result is sufficiently final for the business process. A demonstration with a small dataset does not establish production readiness.

Adoption and operating responsibility

A shared system needs the relevant participants to use compatible rules and maintain their integrations. The required group depends on the use case; it is not necessary to assume that the entire advertising industry must adopt one network.

Confirm who operates the system, admits participants where relevant, manages updates and resolves disputes. Identify what happens if a provider leaves or a technical component fails.

Compare the proposal with a simpler shared database, a reporting integration or improved reconciliation procedures. The right choice is the one that addresses the problem at an acceptable cost and level of complexity.

Evaluate the business case before the technology claim

Start with a defined problem and a small, measurable test. Track the administrative work saved, discrepancies resolved, payment accuracy and operating costs. Keep the limitations visible alongside any gains.

Our guide to affiliate performance metrics can help clarify the reporting questions behind a technology decision. If your program needs a more practical measurement or operating plan, talk with our team about the underlying challenge.