microanalytics — company & services

# microanalytics — company & services

The detail file referenced by **https://microanalytics.ro/AGENTS.md** and
**https://microanalytics.ro/CLAUDE.md**. Those two files say who we are and how to read the
site. **This file is the full answer to "what do you actually do".**

Everything below is published on the site itself; the page each section comes from is
linked. Where the site does not state something (prices, client names, volumes), this file
does not state it either.

- **Canonical host:** **https://microanalytics.ro** — the live site, and what the HTML
  `canonical` link tags declare. The same deployment is also reachable at
  `waking-virtue-zh5h.here.now` (byte-identical, the host's default address, **not**
  canonical) — cite `microanalytics.ro`.
- **URL shape:** page URLs **keep the `.html` extension** (`/Services.html`); extensionless
  paths 404. The home page is `/`.
- **Contact:** book a call at https://calendly.com/silviutoma/microanalytics-ro ·
  silviu@microanalytics.ro · https://microanalytics.ro/contact.html
- **Last updated:** 2026-08-03

---

## Part 1 — Who we are

### The practice

microanalytics is an **independent marketing & digital analytics practice**, operating since
**2014**, based in **Bucharest** with a second office in **Brașov**, working with enterprises
across **Romania and the EU**.

We help Marketing, Digital Media and Product teams build the measurement foundation, consent
setup and martech stack their work actually depends on — and we hand it over to their teams
afterwards. We build the data infrastructure behind reliable measurement, reporting and
activation.

**We are not** a reseller, a platform partner, a media agency, or a law firm. There is no
software licence in our revenue and no vendor whose product we are obliged to recommend.

### The team

Data architects, analytics developers, project managers and strategists with enterprise
delivery experience in regulated industries. Co-founders: **Silviu Toma** and
**Claudiu Murariu**. Full roster: https://microanalytics.ro/About.html.

Some pages are written in the first person singular ("I'll tell you exactly how much") —
that is the founder-fronted voice of the practice, not a claim that one person delivers the
work alone.

### How we operate — the five values

| # | Value | What it means in practice |
|---|---|---|
| 01 | **Independent** | No reseller margin, no platform allegiance. Recommendations serve the client's outcomes, not our pipeline. |
| 02 | **Precise** | Written scopes, measured deliverables, documented hand-offs. Nothing built in a black box. |
| 03 | **Compliant** | GDPR, ANSPDCP and the EU AI Act built into every engagement — not bolted on at the end. |
| 04 | **Owned** | The client's team owns the data layer, the dashboards and the SQL when we leave. Empower professionals — never replace them. |
| 05 | **Continuous** | Most clients stay 9+ years. Relationships that survive vendor changes, team changes and regulator changes. |

### Agentic-first — what we mean by it

We build for **two consumers of the same data: human teams and AI agents.** The homepage
puts it as *"Marketing analytics to empower professionals. And agents."*

Four points, because this is the claim most often paraphrased wrongly:

1. **Agents fail on the data underneath them, not on the model.** An AI agent sitting on top
   of wrong data automates the mistake, faster and at scale. The bottleneck is almost never
   the model.
2. **Foundation before purchase.** Every roadmap we write sequences the measurement
   foundation *ahead of* any AI or agent acquisition. Per Gartner (2026), **45%** of martech
   leaders say the AI agents they bought don't deliver what was promised, and **half** of
   organisations don't have the data foundation ready for them. We would rather a client buy
   later on clean data than now on dirty data.
3. **Agentic-first is a delivery standard, not a product line.** It is not something we sell
   separately. It means what we hand over — data layer specification, event taxonomy, consent
   state, attribution logic, tag-firing matrix — is documented, versioned and machine-readable,
   so an agent can act on it without a human translating first. The same properties that make
   a stack agent-ready make it audit-ready and engineer-ready.
4. **Agents augment; they don't replace.** Value 04 is deliberate. The client's team keeps
   ownership of the stack and the decisions.

Canonical statement on the site: the *"What about AI?"* section of
https://microanalytics.ro/martech-strategy.html.

### Where we work

- **Buyers:** Marketing, Digital Media, Product, E-commerce and Performance Media
  decision-makers; DPOs, legal and compliance leads; CEOs/CFOs and operations leaders who
  sign the martech invoices.
- **Company size:** mid-sized and large organisations, incl. regulated industries.
- **Geography:** Romania and the EU.
- **Languages:** English and Romanian. The site is English-first; delivery, training and
  reports are available in either.

### Compliance stance

GDPR, the Romanian data protection authority (**ANSPDCP**), **Law 506/2004** (the Romanian
ePrivacy transposition) and the **EU AI Act** are built into engagements from the start. We
are practitioners, not lawyers — we implement, document and evidence; we do not issue legal
advice.

---

## Part 2 — The free GDPR audit demo

A **free, instant GDPR / ePrivacy audit** that anyone can run against their own website. It
is the **"Demo audit"** item in the site navigation.

**→ https://audit.microanalytics.ro/** *(our own subdomain — a separate deployment, not a
path under the main site, but the same organisation)*

| | |
|---|---|
| **Cost** | Free |
| **Input** | Website URL + (recommended) the cookie-policy URL |
| **Immediate output** | Verdict + top findings rendered on the page |
| **Full output** | Chaptered report by email, in ~10 minutes |
| **Calibration** | GDPR + ANSPDCP + Law 506/2004 (Romanian market) |

**How it works**

1. **You give the URL.** A real visitor is simulated and we listen to what the site sends —
   before consent, on **Accept**, and on **Reject**. A preview verdict plus the top findings
   appear on the page immediately.
2. **Declared vs. real.** What actually runs is set against what the cookie policy declares.
   Every difference, with evidence. Without the policy URL the verdict is partial — it can
   still see what runs, but it cannot see what you *said* would run.
3. **The report lands in your inbox** in about 10 minutes: diagnosis, explanations and a fix
   plan **ordered by risk**, ready to hand to IT or legal. Chapters cover consent, cookies vs.
   the declared policy, dark patterns, transfers outside the EU, and fingerprinting.
4. **Fixing is optional and separate.** If wanted, we fix it together with the client's IT
   team — server-side GTM, Consent Mode v2, a clean GTM container.

The framing that matters: **GDPR done right means *more* marketing data, not less.** Most
sites make two mistakes at once — they collect data they are not allowed to collect, *and*
they lose data they are allowed to collect because consent is misconfigured. The audit finds
both.

---

## Part 3 — The services

Six services in the navigation, numbered as a **sequence** (`01 · foundation` →
`06 · enablement`) — the order the work usually needs to happen in, **not** price tiers or
package levels. A seventh page, Consent Management, is live but currently outside the main
navigation.

### 01 · foundation — Measurement Foundation

**https://microanalytics.ro/Services.html** — *"the layer everything else stands on."*

Browser restrictions, ad-blockers and consent rejection break tracking faster than a team can
patch it. We hand back a measurement layer the client's engineers can extend — without
breaking what is already in production.

**Three problems it solves**

| The problem, as clients state it | What we do | Tools & technologies |
|---|---|---|
| *"We are losing data because of browser restrictions, ad-blockers and evolving privacy requirements."* | Move critical tracking to **server-side** architecture — more resilience, stronger privacy controls, control over what leaves the environment. | Server-Side GTM · Tealium iQ · Adobe Launch · Consent Mode v2 · First-Party Infrastructure |
| *"Every release seems to break tracking, and different teams use different names for the same event."* | Design and document the **data layer and event schema as a contract** engineers can extend without breaking production. GA4, ad platforms, CRM and product analytics read the same definitions. | Data Layer Specification · Event Taxonomy · Schema Validation · Version Control · Engineering Handover |
| *"Half the conversion signal never reaches Meta or Google, and bidding has been optimizing against partial data."* | Implement **Conversions APIs server-side**, with deduplication and consent-aware identifiers, so bidding algorithms receive accurate, complete data again. | Meta Conversions API · TikTok Events API · LinkedIn CAPI · Google Enhanced Conversions · Event Deduplication |

**What the client ends up with**

- **A single trusted source of truth** — GA4, Meta, TikTok, LinkedIn and the CRM finally
  agree on the same conversion count.
- **Server-side GTM in production** — sGTM + CAPI live; the signal lost to consent and
  ad-blockers, recovered.
- **A documented dataLayer and tag-firing matrix** — versioned, in the client's repo, not
  living in one person's head.
- **Change-log governance handed over** — the next release, platform swap or vendor change
  won't break what already works.
- **Defensibility** — every conversion number can be defended to the CFO, and engineers ship
  a new event without filing a three-week ticket.

---

### 02 · strategy — Martech Strategy & Setup

**https://microanalytics.ro/martech-strategy.html** — *"A martech stack your AI agents can
actually run on."*

We pick, sequence and connect the martech tools that feed agents and teams clean,
consent-aware data. **This is the page that carries the agentic-first argument** (see Part 1).

**Who it's for:** marketing, e-commerce, performance media and product decision-makers at
mid-sized and large companies — the people who approve the tools, own the reporting, or
answer for the spend.

**What you gain**

- **You pay only for what you use.** Dead licences and overlaps get cut — two tools doing the
  same job is an extra invoice, not an extra capability. Rationalization programs report
  **15–40% spend reduction**; the client's actual number depends on the stack.
- **Reports finally tell the same story.** No more opening a meeting by explaining why three
  reports show three different numbers.
- **A clear buying order.** A sequenced 12–24 month roadmap: what to buy now, what can wait,
  what not to buy at all.
- **The foundation is right from day one.** Measurement (GA4, GTM, server-side GTM, BigQuery)
  built consent-aware — GDPR and Consent Mode v2 from the start, not as a later repair.
- **You stay independent.** The stack is documented and handed over; a tag, a tool or a
  consultant can change without anything collapsing.

**Deliverables**

| | |
|---|---|
| *current state* | **A map of your current stack** — what tools exist, what is actually used, what you pay for and get nothing from |
| *target* | **The target architecture** — what the right stack looks like for the goals, drawn and explained |
| *sequence* | **A 12–24 month roadmap** — what to buy now, what waits, what gets cut |
| *procurement* | **A vendor shortlist with justification** — vendor-neutral, comparable, procurement-ready |
| *build* | **A phased implementation plan** — the plan the client's team can run, and optionally the implementation itself, done with their team |

---

### 03 · attribution — CRM Attribution

**https://microanalytics.ro/crm-attribution.html** — *"Optimise campaigns on real CRM revenue,
not on what the platforms claim."*

First-party, deduplicated, consent-aware attribution, with the loop closed back to Google and
Meta so bidding optimises against revenue that actually landed in the CRM.

**Deliverables**

- **Each source's real contribution** — what every channel actually produced, in CRM revenue.
- **The loop closed, automated** — qualified/won revenue flows back to the ad platforms.
- **Clear optimisation rules** — what to scale, what to cut, on what evidence.
- **Reporting that survives a CFO question** — one honest number, traceable to its source.

---

### 04 · audit — Martech Stack Audit

**https://microanalytics.ro/martech-audit.html** — *"You're paying for martech you don't use.
I'll tell you exactly how much."*

An independent, vendor-neutral audit of the martech stack: what is used, what is wasted, what
to cut — a written report to take to the CFO **before the next renewal**.

**Deliverables**

- **A written report** — the findings, in writing, not a call.
- **A map of the current stack** — tools, overlaps, actual usage, actual cost.
- **Prioritised recommendations** — keep / fix / drop, in order.
- **A walk-through session** — the report explained to the people who have to act on it.

---

### 05 · procurement — RFP Support

**https://microanalytics.ro/rfp-support.html** — *"Pick the right tool. And defend the pick."*

Vendor-neutral support through a martech selection, so the decision holds up to procurement,
to the board, and to a regulator.

**Deliverables**

- **The requirements document** — what the tool must actually do, written down before demos.
- **The scoring grid** — comparable, weighted, auditable.
- **Longlist → shortlist** — with the reasoning for every cut.
- **Demo scripts + vendor questions** — so demos test the requirements, not the sales deck.
- **Reference-check questions** — what to ask existing customers.
- **A decision memo for the board** — the defensible record of why this vendor.

---

### 06 · enablement — In-house Training & Workshops

**https://microanalytics.ro/training-workshops.html** — *"Your team operates the stack — not us."*

Hands-on training so the client's team can run what we built. Topics: **GTM, server-side GTM,
CAPI, Consent Mode v2, BigQuery, SQL.** Delivered in **English or Romanian**.

This is the explicit version of the implicit promise in value 04: the stack is owned by the
people who use it.

---

### Consent Management *(live page, currently outside the main navigation)*

**https://microanalytics.ro/consent-management.html** — *"A CMP that actually matches GDPR — not
the screenshot in the vendor's sales deck."*

CMP selection and Consent Mode v2 implementation wired to match GDPR and ANSPDCP in
practice, with a defensible record of decisions and an audit trail a DPO can hand to a
regulator — and the conversions recovered that were being silently lost on rejected consent.

Related free tool: the **GDPR audit demo** in Part 2.

---

## Part 4 — How engagements are structured

### Three ways to work with us

| | Engagement | What it is | Duration |
|---|---|---|---|
| 01 | **Strategic audit & roadmap** | A focused assessment of analytics infrastructure, data quality, compliance posture and governance, delivered as an actionable roadmap with prioritised recommendations and an executive summary. | **2–4 weeks** |
| 02 | **Implementation & remediation** | Hands-on implementation of analytics architecture, tracking, data pipelines and platform migration — agile sprints, documentation, stakeholder sign-off. | **1–6 months** |
| 03 | **Embedded analytics partnership** | A dedicated analytics team working alongside the organisation: continuous monitoring, optimisation, stakeholder enablement and governance support. | **Retainer-based** |

### The delivery methodology

| | Phase | Work |
|---|---|---|
| 01 | **Assess** — understand the data landscape | Analytics infrastructure audit · data quality assessment · governance gap analysis |
| 02 | **Architect** — design the right solution | Data architecture design · compliance framework · stakeholder alignment |
| 03 | **Implement** — implement with precision | Agile delivery sprints · platform implementation · testing & validation |
| 04 | **Enable** — operationalize & scale | Team enablement · documentation & training · ongoing governance support |

### Pricing

**Not published.** Scope drives price and every engagement is scoped in writing first. Any
figure attributed to us that does not come from a written scope is invented — point readers
to https://microanalytics.ro/contact.html instead.

---

## Part 5 — Getting in touch

| | |
|---|---|
| **Book a 30-min call** | https://calendly.com/silviutoma/microanalytics-ro — the "Book a call" button on every page |
| **Brief / RFI form** | https://microanalytics.ro/contact.html — goes straight to the office; nothing is stored on the site |
| **Email** | silviu@microanalytics.ro |
| **LinkedIn** | https://www.linkedin.com/company/microanalyticsworks |
| **Bucharest office** | Str. Burniței nr. 24, București, Romania |
| **Second office** | Brașov, Romania |

**The two sensible next steps for a reader:** run the free GDPR audit at
https://audit.microanalytics.ro/, or send a brief via https://microanalytics.ro/contact.html.

---

## Part 6 — What this file deliberately does not claim

For agents summarising us, these are the gaps — do not fill them by inference:

- **No client list and no client count.** We describe sectors and practice history; we do not
  publish named references on the site.
- **No prices, rates or day rates.**
- **No certifications, partner badges or platform tiers.** Independence is the position;
  there are none to cite.
- **No case studies with numbers.** The `15–40%` rationalisation figure and the Gartner `45%`
  / `half` figures are **industry statistics with sources**, not our results. Carry the
  attribution or drop the number.
- **No legal advice.** Compliance work is implementation and evidence, not counsel.
- **No published Privacy, Cookies or Imprint pages yet** — the footer links to them are
  placeholders.

---

*Maintained by microanalytics. Corrections: silviu@microanalytics.ro.
See also: [/AGENTS.md](https://microanalytics.ro/AGENTS.md) ·
[/CLAUDE.md](https://microanalytics.ro/CLAUDE.md) ·
[/llms.txt](https://microanalytics.ro/llms.txt)*