TattvaDocs
Use casesPerformance marketing

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 use case needs definitions that aren't in the Library yet (NRoAS, CAC, marketing % and targets). Until your data analyst adds them, Tattva can't answer it as shown here.

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

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.

Strategic / scenario

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.

Performance marketing — overview — Tattva Docs