TattvaDocs
Use casesPerformance marketing

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.

Planned

This use case needs definitions that aren't in the Library yet (NRoAS). Until your data analyst adds them, Tattva can't answer it as shown here.

The question: "Why is my acquisition NRoAS not holding up this week?"

This is the most repeated question in the weekly marketing review. Answering it by hand means walking through four or five derived tables, and the result is often not actionable. In Tattva it's one question, with every figure traceable in the Trail.

Who asks

  • The performance-marketing lead, usually in the weekly RCA call
  • The analytics team, when the lead asks mid-week

Frequency

Weekly, sometimes daily during sale weeks.

What NRoAS means here

NRoAS = new-customer revenue ÷ spend.

  • New-customer revenue: revenue from orders tagged to new customers, attributed to ads.
  • Spend: total ad spend. Many teams treat most Meta spend as acquisition spend.

Split revenue into new and repeat per ad, then divide by spend to get NRoAS per ad. Ask your data analyst to store NRoAS as a metric definition, so every answer and tracker computes it the same way.

Data you need

In BigQuery:

  • ads: ad ID, ad set, campaign, channel, creative, status
  • spend: daily spend per ad
  • orders: orders with customer ID and a new-vs-repeat tag
  • customers: first-purchase date (drives the new-vs-repeat tag)
  • campaigns: campaign and ad-set metadata

Common gap: ad-set targeting (interests, age groups, geos) is often not exported to the warehouse. The overlap branch below needs it; see Audience overlap diagnosis.

How to ask it

In Reasoning, type any of these:

  • "Why is acquisition NRoAS down vs last week, broken down by product and channel?"
  • "NRoAS dropped 18% week over week. Break it down by ad, ad set and creator. Which three changes explain most of the drop?"
  • "Compare this week's top 20 ads to last week's. Which ones shifted from new-customer to repeat revenue?"

What you'll get back

A good answer looks at several causes:

  1. Mix shift: did a few large ads get worse, or did many small ads slip?
  2. Repeat creep: did the repeat share of revenue rise on ads that used to acquire new customers? (If yes, suspect targeting drift; see the overlap diagnosis.)
  3. Conversion drop: did landing-page or checkout conversion fall in the same window?
  4. Creator decay: are some creators declining faster than their usual decay?

It ranks the causes by contribution. Open the Trail to check each figure. When NRoAS is a defined metric, the Compute card shows the periods, filters and SQL behind it, and lists the week-over-week comparisons under Comparisons (computed in code).

The logic tree

NRoAS down week over week?
├── Is overall spend up? (denominator effect)
│   └── If yes → look at per-ad NRoAS, not blended
├── Has new-customer share fallen on ads that used to acquire?
│   ├── Yes → audience overlap likely (see Audience overlap diagnosis)
│   └── No → continue
├── Is conversion dropping?
│   ├── Yes → check event tracking, payment gateway, landing-page health
│   └── No → continue
├── Is hook rate / hold rate dropping per creator?
│   ├── Yes → creator decay; compare with the usual decay period
│   └── No → continue
└── Did a new ad set go live this week?
    └── Yes → audience leaking from existing ad sets to the new one

Walk the tree with follow-up questions in the same session: "Now check whether new-customer share fell on the ads that dropped most."

How to make it recurring

  1. Click Save as tracker on the answer. Tattva creates a daily tracker and opens it.
  2. On the question, click Edit. Keep daily for sale weeks, or pick weekly otherwise; change it when the season changes.
  3. Set the Classification rule to Relative delta, name your NRoAS metric, and set critical if Δ > to 10. A run is Critical when NRoAS moved more than 10% in either direction, so a jump is flagged as well as a drop.
  4. On the Delivery tab, click Add destination and send runs to the team's Slack channel (webhook URL) and the lead's email.
  5. When you create your marketing-efficiency goal on Overview › Goals with Add goal, pick this tracker under Link to tracker (optional) and set Role to leading indicator. See Marketing efficiency.

Pitfalls

  • Looking only at blended NRoAS. A 5% blended drop can hide a 30% drop on one ad and a 25% rise on another. Always break it down.
  • Mixing levels. Meta sets budgets at ad-set level; performance data is at ad level. Comparison views can differ slightly from your dashboard for that reason. Check the SQL in the Compute card.
  • Ignoring decay. A creative's fifth week is supposed to be weaker than its first. Compare with the usual decay curve, not a flat baseline.
NRoAS drop RCA — Tattva Docs