The Engineer Behind Your Data

I did not start as an engineer. I started in digital marketing.

I managed WordPress sites and ran SEO and Ads campaigns. I wanted to know what worked and what wasted budget. So I looked at the numbers.

Very quickly, I realized I was flying blind:

• Standard marketing tools reported false numbers.
• Form leads never matched the CRM.
• Cookie banners broke the tracking they were supposed to protect.

You cannot steer ROAS or CAC with data like that. I did not want to guess. I wanted to fix the cause.

Curiosity took over. I am a fertile ignorant: I do not know yet, so I dig until I do.

I understood one thing. To get good marketing data, I had to master the code behind it. Plugins and dashboards only show the surface.

So I went all in:

• I completed École 42, where I learned pure programming in C.
• I mastered vanilla JavaScript and the DOM.
• I built mobile apps with React Native.

Then I looked at marketing tracking again, this time as an engineer. Bloated plugins, fragile CSS scraping and tag soup. It would never pass a code review. And reliable marketing data starts with reliable code.

Today I am a Tracking Engineer. I combine two views that rarely meet.

I think like a marketer. I understand ROAS, CAC and Google Ads audiences, so I know which number drives a decision. I work like an engineer. I respect Core Web Vitals, the DOM and server-side architecture, so the number is correct and the site stays fast.

In practice:

• Native data pipelines built with CustomEvent and vanilla JS.
• Events decoupled from the UI, so tracking survives every redesign.
• First-party, server-side tracking that ad-blockers and Apple ITP cannot cut.
• A protected main thread, with INP kept under 200 ms.
• Consent wiring that is fully compliant with the GDPR and the Swiss nFADP.

Pure signal. Zero noise.