2026 is the year marketing teams handed real decisions to AI agents. Those agents run on your customer data platform, your event schemas, your identity graph and your consent signals. We architect that foundation — so what sits on top can actually be trusted.
Agentic AI arrived in the marketing stack, third-party identity finished collapsing, and consent stopped being a legal checkbox and started being a measurement problem. Each of them punishes a weak data foundation — and they arrived together.
At Summit 2026 Adobe introduced CX Enterprise Coworker, an agent layer that plans and executes work across Experience Platform, Real-Time CDP, Customer Journey Analytics and Journey Optimizer. Journey Agent and Data Insight Agent go further still. All of them reason over your XDM schemas and identity graph. Where that foundation is wrong, agents don't fail loudly — they scale the error.
The share of conversion signal organisations are recovering by moving to server-side collection — events routed through infrastructure you control before distribution, rather than fired from the browser into a dozen vendors. It is now the default architecture for resilient measurement, not an optimisation.
The proportion of Consent Mode v2 implementations reported to fall short of compliance standards. Consent is no longer a banner your legal team signs off — it is a signal that has to propagate correctly through every tag, every server call and every downstream model. Most implementations quietly don't.
We are not a full-service transformation firm and we don't pretend to be. We do one thing — the customer data and measurement layer — at a depth that generalists cannot reach.
Measurement designed around the decisions the business actually makes, not the events that happened to be easy to capture. Thirteen years on Adobe Analytics and seven on Customer Journey Analytics — implementation and migration, Web SDK and Edge Network, server-side collection, data layer design, and the unglamorous discipline of making numbers reconcile across Adobe, Google and the back end.
Segments that resolve to real people, journeys that respond in the moment, and experimentation with enough statistical honesty to be worth acting on. Adobe Target across A/B, MVT, experience targeting, Auto-Target and Recommendations; Journey Optimizer for orchestration; Real-Time CDP for the identity and activation layer that makes any of it possible.
The layer most teams bolt on last and regret first. Consent platform configuration, tag-to-consent mapping, cookie inventories that match the policy you actually published, and regional variation across GDPR, ePrivacy, CPRA and TCF. Then the harder half: designing measurement that stays accurate as consent rates fall, rather than simply going dark.
The newest layer, and the one with the widest gap between the demo and the deployment. Adobe's agents reason over XDM schemas, identity stitching and data usage labels — so schema hygiene, governance labelling and consent enforcement stop being back-office concerns and become the determinant of whether an agent can be given authority at all. We assess readiness honestly, including when the answer is that the foundation has to come first.
The largest live programme in the Adobe base, and we have taken sites through it end to end. The work is rarely the migration itself — it is the identity strategy, the data-quality assumptions inherited from an implementation nobody has audited in years, and giving stakeholders a straight answer about which historical reporting genuinely comes with them and which does not.
Extremely common, and rarely a licensing problem. It is usually schema design that fought the use cases, an identity graph built on identifiers the site was never actually collecting, or activation paths that were never finished. An architecture review finds which — and sometimes concludes the platform was the wrong answer for the use case.
Falling consent doesn't just shrink the sample — it biases it, in ways that quietly break attribution, audience sizing and every model trained downstream. The fix is part remediation, part re-architecture: consent-safe collection, server-side routing, and honest modelling of what can and cannot be recovered.
Agentic features are the fastest-moving part of the Adobe stack, and the readiness question is genuinely technical: are the schemas coherent, is identity resolving, are data usage labels applied, will consent be enforced when an agent activates an audience? We answer it as an assessment rather than a sales conversation.
We work white-label behind agencies and Adobe Solution Partners on CJA, AEP and consent workstreams. You keep the client relationship and the commercial; we bring certified senior delivery capacity, in your time zone, without the hiring cycle.
Depth in the Adobe Experience Cloud, with genuine working knowledge of the alternatives — which is what makes a vendor-neutral recommendation worth anything.
Product and company names and logos are trademarks of their respective owners, shown here to describe the platforms we work in. Hoi Polloi Tech is an independent practice and holds no resale relationship with any vendor.
Product names are the trademarks of their respective owners and are used here to describe the platforms we work in. Hoi Polloi Tech holds no resale relationship with any vendor.
Our name says it — hoi polloi, the many. Enterprise-grade measurement architecture has been priced and packaged for the few. We think that is a distribution problem, not a difficulty problem.
Bring the hard question — a stalled AEP rollout, a CJA migration nobody wants to own, a consent rate that broke your reporting. You will leave the call with a point of view, whether or not you engage us.