ENTERPRISE DIGITAL ANALYTICS CONSULTANT

From tracking code to boardroom dashboard — analytics enterprises can trust.

I build end-to-end measurement systems for enterprise brands that need data they can defend to legal, finance, and the board.

See how the pipeline works Email me
10+
years, enterprise analytics
15+
executive dashboards shipped
50+
tracking issues solved
GA4→BQ→Dataform→PBI
the stack I own end to end
TRUSTED BY TEAMS AT GartnerAir CanadaHallmark Applebee's / IHOPTaj HotelsHasbro
IMPACT

Numbers from real engagements

20%
conversion lift — funnel analysis on the cleaned pipeline
$200K
reporting risk averted — Hallmark UA→GA4 migration, zero data loss
20+hrs
manual reporting eliminated monthly — SAP BEx → Power BI paginated
0
pre-consent requests — GDPR architecture, verified by network logs
ARCHITECTURE

The chain I build, stage by stage

Not a generic diagram — this is the production architecture behind the featured project. Watch it light up.

Website / Appdata layer contract
GTMconsent-gated tags
GA4events + custom dimensions
BigQuery rawdaily events_* export
Staging · dedupDataform, assertion-tested
Sessionization · attributionthe tables GA4 never gives you
Martsfct_sessions · fct_conversions · dim_users
Power BIsemantic model · incremental refresh
Executive dashboardone number everyone agrees on
MORE PROJECTS

Different problems, different stories

REVENUE ACTUAL
$4.21M vs plan +2.4%
OPEX
$1.37M vs plan −1.1%
MARGIN
31.2% ▲ 0.8pp

REPRESENTATIVE — FINANCIAL DATA CONFIDENTIAL

WOLVERINEMIGRATION STORY

Retiring SAP BEx without losing the numbers

Finance ran on deprecated SAP BEx reports kept alive by manual effort and shrinking expertise. They wanted their exact formats — not a redesign.

The move
Audit-first migration: every metric, filter, and hierarchy documented before building pixel-faithful Power BI paginated reports. Parallel run with reconciliation on every figure before cutover.
The lesson
In legacy migrations the deliverable is continuity, not modernity. Match the old output exactly; improve later.

Impact: 20+ hrs/month eliminated · key-person risk removed · logic finally documented.

GDPR · ENTERPRISE WEB ESTATEDEBUGGING STORY

The tags that fired before anyone said yes

GA4, Ads, Meta, and LinkedIn fired on page load — before the consent banner. A compliance exposure most stacks quietly carry.

The scale
A real enterprise container: 52 tags, 39 triggers, 68 variables — 16 GA4 event tags, 15 custom HTML tags, ad pixels for Google, Microsoft, Meta and LinkedIn, plus deprecated tags dating back to 2017 that nobody remembered adding.
The hunt
Gating the container was easy. The hard part was hardcoded tags outside GTM that no trigger could block, and race conditions where tags beat the consent check at real page speeds — found by watching network logs, template by template, browser by browser.
The proof
A repeatable QA framework: zero network requests from gated vendors pre-consent, verified across regions. Evidence, not assurances — it passed legal review without findings.

Impact: zero pre-consent collection — with a functioning measurement stack, not a gutted one.

Page load no tags fire CMP banner Termly / OneTrust GTM gate consent check granted → tags fire denied → blocked QA: network-log proof

CONSENT GATING FLOW

Lawyer bios performance dashboard with tiering framework, names blurred

PRODUCTION DASHBOARD — NAMES BLURRED FOR CONFIDENTIALITY

AMLAW 100 LAW FIRMBUSINESS TRANSFORMATION

3,262 lawyer bios, ranked by what they earn

A top law firm had thousands of attorney bio pages and no way to know which deserved SEO and content budget.

The shift
From "what happened?" to "what do we do Monday?" — every bio scored on traffic, engagement, and conversions, then sorted into a 4-tier action framework: stars, fix-first, promote, low priority.
The adoption
Marketing stopped debating anecdotes. Tier lists became the agenda.

Impact: SEO & content budget reallocated by tier — opinion replaced with data.

AMLAW 100 LAW FIRMINNOVATION STORY

Measuring AI search before most firms knew it existed

Visitors started arriving from ChatGPT, Perplexity, and Gemini. Leadership asked the question nobody had a dashboard for: are AI-referred visitors any good?

Built
LLM/GEO referral classification in the GA4 → BigQuery pipeline, plus a dashboard answering leadership's actual questions: AI-visitor quality vs SEO, month-over-month LLM growth, and which content categories AI engines cite.
The finding
AI-referred sessions converted at a higher rate than organic search (1.61% vs 1.09% on high-value actions) — small volume, outsized quality. That reframed the firm's content strategy for generative search.

Impact: first visibility into AI-search performance — a measurement category most firms still can't see.

AI search LLM and GEO performance dashboard comparing AI-referred and SEO traffic quality

PRODUCTION DASHBOARD — CLIENT IDENTITY REMOVED

Donor analytics dashboard showing traffic spike and donation conversion rate decomposition

PRODUCTION DASHBOARD — CLIENT IDENTITY REMOVED

NATIONAL MEMBERSHIP NONPROFITOPTIMIZATION STORY

The conversion rate that lied

The donation conversion rate collapsed −85.7% month over month. Panic — until the dashboard told the whole story.

The decomposition
Traffic had spiked +1,264% on viral content while donations actually rose +65.5% and average gift size doubled (+99%). The "collapse" was denominator dilution — millions of new low-intent visitors, not a broken funnel.
Why it worked
The dashboard was built to decompose, not just display: every rate KPI sits beside its numerator and denominator, with donor journey and funnel views (on the same GA4 → BigQuery → Dataform pipeline) to separate mix shift from real failure.

Impact: stopped a false alarm from redirecting strategy — and turned a traffic spike into a donor-acquisition analysis instead.

HOW I WORK

Process is the product

Enterprises don't just buy dashboards — they buy a repeatable way of getting to trustworthy ones.

01
Discovery
What decisions need data they don't trust today?
02
Audit
Tags, data layer, consent, warehouse — inventory before opinion.
03
Implementation
Tracking, models, dashboards — in code, in version control.
04
Validation
Assertions, reconciliation, network-log proof.
05
Documentation
Every metric defined once, findable by the next person.
06
Training
Teams run it without me. That's the exit test.
ENGINEERING PHILOSOPHY

Four rules, in order

01

Measure correctly

A documented data layer contract. GTM reads; it never scrapes. Consent is enforced at the gate, not promised in a policy.

02

Model correctly

Dedup and sessionization live in version-controlled SQL, upstream of every report. One metric, one definition.

03

Validate everything

Assertions fail the build before bad data reaches a dashboard. Reconciliation queries explain variance instead of arguing about it.

04

Only then visualize

The dashboard is the last mile, not the fix. If the number is wrong upstream, no visual will save it.

GITHUB

Open work

Production patterns rebuilt on Google's public GA4 dataset — open the code, don't just read claims.

github.com/vanu270

The flagship repo rebuilds the featured pipeline end to end: layered Dataform models, dedup and sessionization SQL, assertions that fail the build on bad data, and reconciliation queries against the GA4 UI.

Visit GitHub →

RESOURCES

Free tools I wish existed when I started.

CHECKLIST

GTM audit checklist

The 30-point audit I run on every new engagement.

Read →
GUIDE

GA4 event naming guide

Conventions that keep a property queryable years later.

Read →
SQL LIBRARY

BigQuery SQL for GA4

Dedup, sessionization, reconciliation — copy-paste.

Read →
GUIDE

Power BI performance

Why your dashboard is slow, in the right order.

Read →
CHECKLIST

Consent mode checklist

Prove compliance with network logs, not promises.

Read →
ABOUT

Why I do this

Ashish Tripathi

My first job was SEO, in Mumbai, in 2014. One month a client's traffic report showed a glorious spike — everyone celebrated. I dug in and found it was a bot crawling one broken page. Nobody had checked. That moment set the question I've been answering ever since: how much of what companies "know" is actually true?

The problems that excite me are the ones where the number is wrong and nobody knows why.

That's why I went deep instead of wide: four years at TCS building marketing analytics for Air Canada, Hasbro, and Taj Hotels; then at Astound Commerce, Hallmark's UA→GA4 migration with zero data loss, Floor & Decor's Tealium iQ implementation for GA4 and paid-media tracking, and Adobe Analytics measurement across eCommerce clients; now full pipeline engineering at Bitwise for Applebee's/IHOP, Gartner, and Wolverine. Duplicate events, consent race conditions, undocumented BEx logic — the unglamorous places where trust is actually won or lost.

Clients keep me around for the same reason each time: when my number differs from another tool's, I can show exactly why — in SQL, with evidence. I work remotely from Bangalore with teams across the US and Europe, and I write about this stuff because almost nobody else does.

GA4Adobe AnalyticsGTMTealium iQBigQueryDataformPower BILooker StudioJavaScriptSQLConsent ModeOneTrustTermlyGA4 Certified

Have a measurement problem your current stack can't answer?

I'm open to enterprise analytics consulting, audits, and senior analytics engineering roles.

tashitripathi35@gmail.com