Skip to main content
Adrià García
Menu

Services

Scoped customer data, measurement, and architecture projects. Each service explains what is included, where it ends, and how it starts. No open-ended retainers.

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, prioritization, platform access, or document analysis.

Request an initial consultation

Areas of work

Customer data and journeys

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

02

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 license in place but no complete use case in production yet.

View the service →

03

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.

View the service →

Measurement, tracking, and consent

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

04

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.

View the service →

05

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.

View the service →

06

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.

View the service →

07

CJA migration and analytics modernization

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.

View the service →

Architecture and platform decisions

Audits and selection processes that turn a blocked implementation or complex purchase into executable decisions.

01

Architecture and implementation audit

I assess an existing MarTech implementation and turn the observed problems into prioritized 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.

View the service →

08

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.

View the service →

Problems that usually bring me into a project

They do not start with a feature list. They start with a blocked decision or an implementation that will not move.

  • 01

    The implementation exists, but XDM schemas, identity or consent make every new use case slow.

  • 02

    Web, apps, and platforms receive different events, and the tracking plan no longer describes what is actually collected.

  • 03

    Server-side delivery and conversions do not share identity, deduplication, or a clear consent rule.

  • 04

    The license is already in place, but the first production use case has not connected data, audience, and activation.

  • 05

    Business and technology are comparing platforms with different ownership models and need criteria to decide.

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

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

How I work

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

  1. 01

    Architecture before the catalog

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

  2. 02

    One owner for every decision

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

  3. 03

    A first scope with an exit

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

  4. 04

    Handover starts in design

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

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