# Data, tracking and analytics

> Which channel sells, not just which signs up: tracking, attribution to the CRM and numbers that agree.

Source: https://fcgsystems.es/en/services/data-tracking-analytics/ · FCG Systems

**Tracking and attribution through to the sale, with numbers that agree.**

Ads reports one number, the CRM another and the launch spreadsheet a third. When data doesn’t match, decisions come down to gut feeling and budget gets allocated blind.

We measure every step, from the first click to the sale closed on a call, and connect every source into a single reference database. When signal loss justifies it, we send conversions from a server you control (server-side GTM or Meta’s Conversions API) instead of relying on the browser alone.

On top of that we build the dashboards leadership, marketing and sales actually use: sign-ups by source, conversion by stage and performance by closer. The result: you know which channel sells, which campaign deserves more budget and which numbers you can rely on.

## Signs you need it

- Every platform reports a different conversion count
- You know which channel brings sign-ups, not which one sells
- Reports are built by exporting CSVs by hand
- UTMs get lost between the form and the CRM
- GA4 is installed, but nobody trusts it
- Dashboards break whenever a tool changes

## Who it is for

- **CMOs and acquisition leads:** Launches with ads and several sources where the sale closes on a call, far from the pixel. You know which campaign brings sales, not just sign-ups.
- **Founders who don’t trust their numbers:** Ads says one figure, the CRM another and the launch sheet a third. One reference source and dashboards that read from it.
- **CTOs and technical owners:** A documented measurement plan, events deduplicated between browser and server, and dashboards that don’t break when a tool changes.
- **Sales teams:** The source of every lead visible in the CRM and per-closer performance without building reports by hand.

## What we build

- **Measurement plan:** What gets measured, what it’s called and where, documented before a single tag goes live.
- **GA4 and Google Tag Manager:** Clean event and conversion setup across site, forms and checkout.
- **Server-side tracking:** A server-side GTM container when signal loss justifies it, not by default.
- **Conversion APIs:** Browser and server events deduplicated with the same identifier, including sales closed away from the website.
- **Attribution:** UTMs and sources carried from first click to the CRM and the closed sale.
- **Source integration:** Ads, CRM, payments and platforms loaded into one shared database.
- **Dashboards:** Business dashboards per team, refreshed without exports.
- **Sales KPIs:** Clear definitions for conversion, sales cycle and per-closer performance.

## Browser tracking or server-side.

Server-side tracking doesn’t replace a solid browser setup: it complements it. These are the differences that matter when deciding where to spend.

| Criterion | Browser tracking | Server-side tracking |
|---|---|---|
| How events travel | From the user’s browser to each platform, tag by tag | From the browser or backend to a server you control, then on to each platform |
| Signal loss | More exposed to blockers and browser restrictions | Less exposed, though it doesn’t bring back users who decline consent |
| Data control | Each tag decides what it sends | You decide what data leaves for each platform |
| Sales outside the website | Hard to measure | Can be sent from the CRM or payments through conversion APIs |
| Cost and upkeep | Low: tags in Google Tag Manager | A server or managed service, configuration and monitoring |

## How we work

1. **Measurement audit:** What’s measured today, where signal is lost and how far each source drifts from the CRM and payments.
2. **Measurement plan:** Events, names, parameters and the reference source for each number, in writing.
3. **Implementation:** GA4 and Google Tag Manager, plus server-side or conversion APIs when they pay off.
4. **Validation:** Test events, browser and server deduplication and a cross-check with CRM and payments.
5. **Dashboards:** Sources loaded into one shared database, with dashboards per team on top.
6. **Upkeep:** Reviews whenever tools, campaigns or the funnel change.

## Deliverables

- Documented measurement plan
- GA4 and GTM implementation, in your accounts
- Source attribution through to the CRM
- Analytics database in your name
- Dashboards per team
- KPI guide and definitions

## What changes

- **One number:** Marketing, sales and leadership debate decisions, not which figure is right.
- **Smarter budget:** You know which sources drive sales, not just sign-ups, and where to move spend.
- **Fewer manual reports:** Dashboards refresh on their own and nobody builds spreadsheets on Monday morning.

## Format

- Format: Fixed-scope project
- Duration: 1–3 weeks for tracking; 3–8 with database and dashboards
- Typical tools: GA4, Google Tag Manager, Server-side GTM, Meta Conversions API, Postgres, Airtable, Looker Studio, Tally

## FAQ

### What is server-side tracking and do I need it?

It means sending events to a server you control and on to each platform from there, instead of the browser talking to all of them. You don’t always need it: it pays off when signal loss affects campaigns with meaningful budget or when you want more control over your data. First we make sure the basic tracking is done right.

### Which server-side tracking tool should you use?

Usually a server-side GTM container, on your own infrastructure or a managed service. It depends on event volume, how much control you want and who will maintain it. Everything sits in your accounts and is documented, so you don’t depend on us.

### Does server-side tracking remove the need for consent?

No. It changes where events are processed, not your privacy obligations: if a user doesn’t consent, that measurement shouldn’t happen anyway. We configure it to respect consent and document what data is sent and to whom, so your legal advisors can review it.

### What is a conversion API?

It’s how an ad platform such as Meta receives events straight from your server or CRM instead of from the browser. It lets you report sales that close on a call. It runs alongside the pixel with the same event identifier, so the same conversion isn’t counted twice.

### Why don’t Ads, GA4 and CRM numbers match?

Because each platform counts with its own rules, attribution windows and blockers. Getting them to match 100% isn’t realistic, but you can define a reference source and know how far each one drifts, and why.

### How long does it take and when will I see results?

Tracking usually takes 1 to 3 weeks; with a database and dashboards, 3 to 8. If you have a launch coming up, we prioritise what you need to measure by that date and deliver the rest afterwards.

### Can you connect dashboards to our CRM?

Yes. We bring CRM, forms, payments and ad platforms into a shared database, and dashboards read from there. That way swapping a tool doesn’t break every report.

## Related case studies

- [An own campus connected to the sales CRM](https://fcgsystems.es/en/case-studies/own-campus-connected-to-the-crm/)
- [A custom CRM that replaces Airtable, with commissions per agent](https://fcgsystems.es/en/case-studies/custom-crm-with-agent-commissions/)
- [Funnel, tracking and CRM connected for an online academy](https://fcgsystems.es/en/case-studies/sales-funnel-system-online-academy/)
- [Infrastructure for launches with thousands of sign-ups](https://fcgsystems.es/en/case-studies/high-volume-launch-infrastructure/)

## Contact

Email hola@fcgsystems.es or use the form at https://fcgsystems.es/en/contact/. Reply within one working day.