Paromita Das
← ALL PROJECTS
Marketing measurement & decision science

Marketing Analytics Copilot

A production-style measurement application that puts marketing mix modeling, multi-touch attribution, experimentation, and budget simulation behind one interface — so a marketing team can answer "where should the next dollar go?" without waiting on an analyst.

Marketing Analytics Copilot overview
Role
Sole builder — framing, modeling, and interface
Stack
Python, Streamlit, statsmodels, Plotly
Methods
MMM, multi-touch attribution, A/B testing, budget optimization
Audience
Marketing leadership and client stakeholders
01 — The problem

Every channel report told a different story.

Marketing teams typically hold three incompatible views of the same spend: platform-reported conversions, a last-touch dashboard, and a quarterly mix model that arrives too late to act on. Each is defensible. Together they stall the decision.

I wanted one place where the methods sit side by side, disagree visibly, and still produce a recommendation someone can take into a budget meeting.

02 — Approach

Four layers, one narrative.

01
Campaign analytics

Spend, delivery, and conversion diagnostics by channel and campaign — the shared baseline everything else is measured against.

02
Marketing mix modeling

Regression with adstock and saturation transforms to estimate incremental contribution and diminishing returns per channel.

03
Multi-touch attribution

Path-level credit assignment across several models, shown as a comparison rather than a single number — the disagreement is the insight.

04
Experimentation & budget simulation

Significance testing on live tests, plus a response-curve simulator that reallocates budget and projects the outcome before money moves.

03 — Decisions it supports

Built to end an argument, not extend it.

Where to shift budget

Response curves show which channels are saturated and which still have headroom.

Which result to trust

Method-vs-method comparison makes the size and direction of the disagreement explicit.

What to test next

Gaps between modeled and observed lift become the experiment backlog.

What to report upward

Client-ready summaries generated from the same models, so the deck matches the data.

04 — What I'd carry forward

The modeling was the easy half. Making three methods disagree legibly — that's what made it usable.

The same pattern shows up in my day job: the analysis is rarely the bottleneck. Getting stakeholders to a shared, defensible view of the trade-off is. This project is where I test interface decisions before they hit real executive reporting.

View the code Next project →
Let's connect

Have a problem your data hasn't answered yet?

Email me