Skip to main content
Adrià García
Menu

Services

Customer data, measurement and architecture projects, with an agreed scope. Choose an area to see what I can help with and who each service is for.

Customer data and journeys

From the platform and data model to the first flow that business can use and the internal team can operate.

First production use case

I build one complete use case, from the agreed source through to an activation or journey that the team can operate.

Who it is for
Teams starting from zero, or with a licence in place but no complete use case in production yet.

Tealium Data Hub delivery and support

I work across iQ, EventStream, and AudienceStream to structure customer data collection, processing, and activation.

Who it is for
Teams already using Tealium Data Hub, or those needing a scoped implementation without turning the whole platform into one project.

Measurement, tracking, and consent

Web and app collection, server-side delivery, CMPs, and analytics under one data contract with verifiable controls.

Measurement and tracking architecture

I design or rebuild data collection across web and apps so events, identities, and documentation follow the same contract.

Who it is for
Teams with a fragmented data layer, outdated tracking plans, or mismatches across web, apps, analytics, and activation.

Server-side tracking and event forwarding

I design and configure server-side flows for events, deduplication, first-party identity, and delivery to activation platforms.

Who it is for
Teams that need less browser dependency, better conversion data quality, or stronger governance over what destinations receive.

Technical consent implementation

I implement the technical consent and governance layer so preferences travel from collection to the systems that enforce them.

Who it is for
Teams that need to implement or fix a CMP and make consent, tags, the CDP, and destinations enforce the same decision.

CJA migration and analytics modernisation

I audit the current measurement setup, design the CJA model, and support a verifiable transition from Adobe Analytics, GA4, or Tealium.

Who it is for
Teams implementing Customer Journey Analytics or migrating measurement without carrying obsolete variables, unused reports, and legacy decisions into CJA.

Architecture and platform decisions

Review an implementation or compare platforms before investing, using technical and business criteria.

Architecture and implementation audit

I assess an existing MarTech implementation and turn the observed problems into prioritised findings and a remediation plan.

Who it is for
Teams with a CDP, analytics, tracking, or consent implementation that underperforms, or whose design they need to validate.

Platform selection

I compare requirements with real capabilities and expose the integration, operating, and ownership trade-offs before recommending an option.

Who it is for
Teams comparing a suite with composable or warehouse-native alternatives before committing the investment.

To start

Initial consultation No charge

A short conversation to understand the blocker, check whether I can help, and agree what the next step should be.

Who it is for
Teams with a specific question about CDPs, journeys, Tealium, measurement, tracking, or consent that need to check whether I am a fit.
What is included
  • A 20-minute initial conversation.
  • An initial hypothesis about the type of blocker.
  • A recommendation for the next step.
  • A proposed scope, if I can help.
How it starts
Email me the basic context and one specific question. Do not send personal data, credentials, or confidential documentation.
Limits
One question and 20 minutes. It does not include a configuration review, written diagnosis, prioritisation, platform access, or document analysis.

Request an initial consultation

Ways to work together

I can deliver directly, lead the internal team, or join temporarily to cover a specific architecture or delivery need.

  • Fixed-scope project

    One problem, a defined set of deliverables, and boundaries agreed before work starts.

  • Delivery or technical direction

    I can configure the solution or define the architecture and guide the team building it.

  • Contractor within the team

    Temporary support across architecture, delivery, troubleshooting, and technical coordination.

  • Ongoing support after a scoped engagement

    Backlog, incident, decision, and platform-evolution support after the initial delivery.

Rates are discussed by email. I do not publish figures or ranges, because they depend on scope.

How I work

Four rules that make an architecture decision possible to build, operate and change.

  • Architecture before the catalogue

    I start with sources, identities, state, consumers and constraints. Then I test which product fits.

  • One owner for every decision

    We agree which system owns each fact, rule and operational state before connecting more tools.

  • A first use case to build on

    The first deliverable solves one concrete use case without closing the path to the next one.

  • Handover starts in design

    Documentation and operating boundaries are part of the deliverable, not an improvised final week.