Performance marketing — overview
Ten use cases covering the weekly NRoAS question, ad-action decisions, channel scenarios, creator trends, efficiency targets and MBR/QBR assembly.
Planned
This is a working catalogue for a performance-marketing team: the questions that come up in the weekly marketing review and the finance review, mapped to Tattva recipes. The examples use a made-up D2C brand, Acme, with products SKU-A, SKU-B and SKU-C.
The 10 use cases
Daily / weekly
NRoAS drop RCA
The most common weekly question. "Why is my acquisition NRoAS not holding up?"
Ad action decisions
Which ads to kill, pause, scale, or reduce spend on — with reasoning.
Audience overlap diagnosis
Deep dive: are two ad sets eating each other's new-customer reach?
Product-lag RCA
"SKU-A is 30% behind target. Why?" The product-level weekly RCA.
Target vs landing
Month-end projection that accounts for sale days and the weekday mix.
Monthly
These come up monthly. Trackers run hourly, daily or weekly, so for these you either keep a weekly tracker or ask the question when the month closes and save the answer as a report.
Creator pattern trends
What creator pattern is working this month, and has it changed?
Creator size mix
Mega vs Micro vs Nano — which size is delivering for which product?
MBR / QBR assembly
Draft the monthly or quarterly business review from what Tattva already holds.
Strategic / scenario
Channel budget scenarios
"What if I move 10% from Meta to Google?" Forecast revenue and CM3 impact.
Marketing efficiency
Reaching a marketing-% target by closing the gaps lever by lever.
How a typical team works
Context for readers new to the function:
- Channel mix: heavy Meta dependence, Google second, with a goal of relying less on Meta over time.
- Efficiency target: bring marketing % (spend ÷ net revenue) down while revenue keeps growing.
- Cadences: daily monitoring, a weekly RCA with marketing, a weekly review with finance, a monthly MBR, a quarterly QBR.
- Data home: BigQuery holds spend, revenue and the new-vs-repeat split. Ad-set targeting (interests, audiences) is often not exported, which limits the overlap diagnosis; see Audience overlap diagnosis.
A note on logic trees
Performance teams reason through logic trees: from "the metric moved" down to a root cause, one branch at a time. Each use case includes the tree the team uses. Tattva doesn't store these trees. Use them to steer your follow-up questions ("now check whether new-customer share fell on the top ads"), and ask your data analyst to define the metrics each branch depends on so every step is computed the same way.
Use cases
Real questions teams ask, mapped to Tattva — the data you need, how to ask, what comes back, and how to keep watching it.
NRoAS drop RCA
The weekly performance-marketing question, "Why is my acquisition NRoAS not holding up?", answered with the right tables, the right breakdown, and a trail you can check.