Services
Digital analytics and CRM02 / 07

Analytics you can trust, CRM that converts

End-to-end implementation and consulting: one central CDP captures each event once and routes it to product analytics, attribution, CRM and your warehouse, with unified identity and a governed taxonomy. Everything measured, nothing on gut feel.

Max M ยท live operation production
Analytics and CRM in one integrated view
signal qualitylive
When it makes sense

When it makes sense

  • 01

    Every tool reports a different number and nobody knows which one is right.

  • 02

    You spend on paid media but can't connect campaigns to what users do inside the product.

  • 03

    Product decisions run on opinion because nobody trusts the events hitting the dashboard.

  • 04

    Web and app are tracked separately, so the same user shows up as two different people.

  • 05

    CRM blasts the whole list because there are no behavioral segments to target.

  • 06

    You need to prove consent (GDPR, LGPD) and can't tell who opted in to what.

How it works

How it works

  1. 01

    Audit and architecture

    We map your current tracking, define the event plan and design the architecture: what gets collected, where it flows and why.

  2. 02

    Collection layer implementation

    A central CDP instrumented across app and web, destinations configured (product analytics, attribution, engagement, ads, warehouse) and identity unified from anonymous to logged in, with attribution stitching.

  3. 03

    Taxonomy governance

    A versioned naming convention: snake_case, past-participle event names, required properties like source_section, review for every new event and a 30-day deprecation window.

  4. 04

    CRM activation

    Behavioral segments feeding push, in-app, email and WhatsApp, always consent-based, with per-channel performance measurement.

Deliverables

What we deliver

  • A versioned tracking plan: 60+ standardized events across 11 domains, with owners and defined properties.01
  • CDP implemented with live destinations: product analytics, mobile attribution, engagement, ads and warehouse.02
  • Unified identity from anonymous to logged in, with install attribution attached to every event's context.03
  • Product funnels and dashboards validated against raw warehouse data.04
  • Live CRM journeys: push, in-app, email and WhatsApp driven by behavior and consent.05
  • Documentation and process: naming convention, new-event workflow and deprecation without breaking reports.06
Results

Results

37%

of FESTAS app opens on Android reach an event card click: a funnel measured end to end, with the same number in every tool.

16%

of Android opens end in a ticket click (11.6% on iOS). Numbers that survive an audit because the collection layer is governed.

90%

drop in cost per install once paid media started deciding with this data, per consolidated app attribution (AppsFlyer).

This is the one page on this site where we open up the entire stack. In analytics, hiding the how is hiding the product: below are the tools we implement, the taxonomy that governs every event and the real funnel from FESTAS, our own product, measured in production.

The stack we implement

Your app and site
RudderStackCentral CDP
AmplitudeAmplitude
AppsFlyerAppsFlyer
CleverTapCleverTap
FirebaseFirebase
Google AnalyticsGoogle Analytics
MetaMeta
BigQueryBigQuery

An event is captured once and flows to every tool, in real time.

When it makes sense

  • Every tool reports a different number and nobody knows which one is right.
  • You spend on paid media but can't connect campaigns to what users do inside the product.
  • Product decisions run on opinion because nobody trusts the events hitting the dashboard.
  • Web and app are tracked separately, so the same user shows up as two different people.
  • CRM blasts the whole list because there are no behavioral segments to target.
  • You need to prove consent (GDPR, LGPD) and can't tell who opted in to what.

How it works

  1. Audit and architecture

    We map your current tracking, define the event plan and design the architecture: what gets collected, where it flows and why.

  2. Collection layer implementation

    A central CDP instrumented across app and web, destinations configured (product analytics, attribution, engagement, ads, warehouse) and identity unified from anonymous to logged in, with attribution stitching.

  3. Taxonomy governance

    A versioned naming convention: snake_case, past-participle event names, required properties like source_section, review for every new event and a 30-day deprecation window.

  4. CRM activation

    Behavioral segments feeding push, in-app, email and WhatsApp, always consent-based, with per-channel performance measurement.

Governed taxonomy: predictable names, no guesswork

event taxonomyjson
[
  {
    "event": "fssp_tracking_search_executed",
    "properties": {
      "results_count": 42,
      "source_section": "search_bar"
    }
  },
  {
    "event": "fssp_tracking_concerts_ticket_clicked",
    "properties": {
      "event_id": "evt_8f31",
      "source_section": "event_detail"
    }
  }
]
FESTAS funnel: app open, event card click and ticket click, Android and iOS
Real FESTAS funnel, last 30 days: out of every 100 Android opens, 37 become an event card click and 16 reach a ticket click. On iOS, 11.6% reach the ticket click. One number across every tool, because there is only one event.
Acquisition by channel with attribution consolidated in the CDP
CRM deliverability per channel, with active opt-in. Percentages, normalized data.

What we deliver

  • A versioned tracking plan: 60+ standardized events across 11 domains, with owners and defined properties.
  • CDP implemented with live destinations: product analytics, mobile attribution, engagement, ads and warehouse.
  • Unified identity from anonymous to logged in, with install attribution attached to every event's context.
  • Product funnels and dashboards validated against raw warehouse data.
  • Live CRM journeys: push, in-app, email and WhatsApp driven by behavior and consent.
  • Documentation and process: naming convention, new-event workflow and deprecation without breaking reports.

Measured in production

FAQ

FAQ

Who owns the accounts and the data?

You do. Everything is set up in your own accounts (CDP, analytics, attribution, warehouse) and we work as admins you can revoke anytime. Zero lock-in: if we part ways, the stack stays yours, fully documented.

How long does a full implementation take?

It depends on scope: how many platforms (web, iOS, Android), how many destinations and the state of your current tracking. The order never changes: audit and tracking plan first, then instrumentation and destinations, with CRM activation starting as soon as the first segments are reliable. You follow progress event by event, in the tracking plan itself.

How do you charge?

Fixed-scope project for the implementation, plus an optional monthly retainer for governance and CRM operations. No per-event fees, no license resale: you contract the tools directly and pay only for our work.

Will you work with the stack we already have?

Yes. Architecture matters more than logos: a CDP at the center, a governed taxonomy and the warehouse as source of truth. We only recommend switching tools when there's a measurable reason, never out of preference.

We're in a different timezone. Is that a problem?

No. We run async-first: a written tracking plan, documented decisions and recorded walkthroughs, plus one weekly call scheduled in your timezone. We work in English, Portuguese and Spanish.

Stop arguing about which number is right

Send us your product context and we'll come back with a diagnosis of your current tracking: what's duplicated, what's missing and the path to a single source of truth.

Talk to Max M