Each project summarizes the initial problem, work delivered, and outcome.
01
Greenfield Real-Time CDP implementation in insurance
Client: one of Spain's top insurance companies
The organization did not have a CDP. The project had to introduce AEP as a shared data, orchestration, and personalization layer, and deliver a working MVP first. The architecture had to support historical loads, real-time events, and later evolution without rebuilding the foundation.
Pega decided which communications to send, while a previous platform handled email delivery. The project had to move delivery to AJO, preserve the Pega integration, and migrate app analytics to CJA.
Measurement, consent, and CJA architecture at a major bank
Client: a major bank
Measurement was split across the public site, the logged-in area and the app, each with its own implementation. Without a common data layer, neither reporting nor activation could be trusted.
AEP architecture for an international education platform
Client: an international education ecosystem linked to a major banking institution
Several business lines shared users, content, and interactions but needed to retain their own data and consent states. The new architecture had to unify identities, support personalization, and follow the corporate data model.
Client: a consumer finance institution operating across several European markets
The email marketing platform was being retired. Audiences depended on warehouse data, while permissions lived in OneTrust. Its replacement had to preserve segmentation logic and consent exclusions while correctly distinguishing customers from prospects.
Ecommerce measurement and offline conversions in retail
Client: an ecommerce retailer specializing in sports equipment
Measurement combined gtag.js, an incomplete data layer, and ecommerce events with errors. Bank transfers were confirmed outside the website, consent affected tag loading, and part of the traffic ended up classified as Unassigned.
Measurement, consent, and pixels for fashion retail
Client: an international fashion company with ecommerce operations across several markets
Measurement had to move from Universal Analytics to GA4 without losing control of the data layer, consent, or marketing tags. The implementation also needed a shared guide to coordinate business, development, and analytics.
Data, reporting, and conversion automation for education
Client: an international education and media group with multiple brands and enrollment processes
Multiple brands produced operational files on an SFTP server that had to feed reporting and analytics. The process needed several update methods, had to run from an allowlisted IP address, and had to match confirmed enrollments against transactions already recorded.
Google Cloud: Compute Engine, Cloud Functions and Cloud Scheduler
Client: a major public university with numerous domains, schools, and digital properties
Measurement was distributed across numerous websites, subdomains, and owners. Before implementing changes, the organization needed to know where Analytics and GTM were present, which identifiers were in use, and where access or configuration was missing.
Measurement and tag management across multiple organizations
Client: organizations across retail, fashion, travel, leisure, education, and consumer goods
Each organization had a different mix of websites, apps, Analytics accounts, tag managers, and reporting requirements. The work required adapting each solution while keeping data collection and documentation consistent.
These projects were delivered for clients of the consulting firms where I worked. They are presented by sector and scale to preserve confidentiality. Quantitative data comes from project documentation.
Does this resemble your problem?
The services explain how I would approach a similar engagement. My experience provides the professional context for each role.