fipolo & co
CS

Four kinds of engagement

Each can start small. An audit is a complete piece of work on its own, and nothing obliges you to buy the build that follows it.

  • 01

    Measurement, rebuilt so you can trust it

    Server-side tracking (sGTM), GA4, consent and Consent Mode, CDP, attribution. The usual starting point, because every other decision on this page depends on the data being right.

    You get: an audit of what is currently measured and what is silently wrong, a prioritised fix list, and the implementation if you want it.

  • 02

    E-commerce that earns its keep

    Shop builds and rebuilds, SEO, performance marketing, product feeds and comparison sites, expansion into a new market with the localisation that actually decides whether it works.

    You get: a plan ordered by effort against impact, then the build — ours, yours, or shared with your team.

  • 03

    Reporting people actually open

    BI and dashboards, segmentation, customer and product profitability — the numbers a board asks for, assembled from the systems you already run.

    You get: defined metrics, a working report, and the pipeline behind it documented well enough to hand over.

  • 04

    Automation of the boring half

    ERP and CRM processes, order and customer flows, e-mail automation, and AI agents where they genuinely beat a script. Repetitive steps out, so the time goes to what customers notice.

    You get: the manual steps mapped, the ones worth automating costed, and the automation built and running.

Not sure which of these it is? That is a normal place to start — describe the symptom and we will say which one it turns out to be.

Why server-side

Where the data goes missing

The same visit, two routes. The difference is not in how GA4 is configured but in how much of the visit it ever hears about.

Why server-side Two measurement paths compared: from the browser a share of the data is lost to blockers, cookie lifetimes and network failures, while a server-side layer sends from our own server and loses only what consent withholds. From the browser blockers cookie lifetime network failures Through our server nothing identifying leaves without consent 0 % 100 %
These figures are the shape of the problem, not a measurement of your site. How much is missing on yours is what an audit answers.

Capabilities

What we are deep in, and what we are not

Listed by how far the work actually goes. Not everything here is daily work and there is no reason to pretend otherwise — you can see exactly what you would be buying.

Daily work

  • Behaviour tracking
  • Server-side measurement (sGTM)
  • CDP and segmentation
  • Attribution
  • Reporting and BI
  • Vibe coding
  • AI agents (Claude Code, MCP)

Build and run

  • SEO
  • Performance marketing
  • Websites and e-shops
  • E-mail and automation
  • Product feeds and comparison sites
  • ERP and CRM automation
  • International expansion and localisation

Happy to discuss

  • Conversion optimisation and UX
  • GDPR-compliant measurement and consent
  • Brand visibility in AI assistants

Reporting

Five sources, one report

The numbers a board asks for usually disagree not because they are wrong, but because each comes from somewhere else.

Five sources, one report shop GA4 ad accounts ERP CRM one data model a report someone opens
Metric definitions are written before the first chart is built. Otherwise the numbers get argued about instead of decided on.

How it works

How it works

Four steps, and you can get off after any of them. Most engagements start with the first one alone.

  1. Half a day on what you already haveWe go through the measurement, the shop and the data that exist today. Most of the problems are visible before anything gets built — and some of them turn out not to be worth fixing.
  2. One page you can disagree withWhat to change, in what order, what it should do and what it costs. In writing, because a proposal you cannot argue with is not a proposal.
  3. We build itAt our end, at yours, or half and half with your team. Always so that somebody else could take it over — that is the test, not whether it works on the day.
  4. We keep it running, or hand it over properlyWith documentation and someone at your end who understands it. The end of an engagement should not be the moment it quietly breaks.

Automation

What still gets done by hand every week

Most companies do not have a data shortage. They have a problem with how many steps between order and invoice a person still performs.

What still gets done by hand every week by hand, every week order stock check customer e-mail ERP entry invoice board report set up once, runs itself order stock check customer e-mail ERP entry invoice board report
We map which steps repeat unchanged - those are the ones worth automating. The rest stays with people.

Tell us what is broken