The collection, as of October 17
All numbers are Triple Whale, Triple Attribution 7-day, new customers only, Ledisa Google Ads. Google-reported conversions are not used.
On September 24 we paused every Google campaign for the checkout move to Netz and switched them back on one by one as each link was ready. So the weeks read as before the pause, the restart and now. The last week keeps collecting orders until October 24; treat it as provisional.
Table view
| Week | Spend | NC orders | NC ROAS 7d | Cost / NC order |
|---|
| Channel | Spend | NC orders | NC ROAS 7d | Floor | Read |
|---|---|---|---|---|---|
| Search non-brand | $39,484 | 533 | 1.08 | 1.4 | 60% of spend. Two advertorial tests running here (Room III). Below floor since the restart; this is where the gap is. |
| Search brand | $6,687 | 119 | 1.44 | 1.4 | Brand bids raised Oct 15 to buy impression share; bidding test starts Oct 22. |
| PMax generic (feed) | $13,243 | 189 | 1.06 | 1.7 | Fell from 1.73 the week before. Given a 160% tROAS target on Oct 18 (was untargeted). |
| PMax brand (feed) | $4,015 | 144 | 2.48 | 1.7 | 2.3–3.5 over the last three weeks, 2.48 this one. tROAS 385% → 350% on Oct 18. |
| Demand Gen (Discover, native) | $2,268 | 10 | 0.24 | 1.0 | Small test budgets ($100–150/day each). Three campaigns, Room IV. |
| Total | $65,696 | 995 | 1.17 | — | $66 per new customer; $56–60 in the two restart weeks. |
Q4 targets, Ledisa on Google
| Month | Spend | NC revenue | NC orders | NC ROAS | Cost / NC order |
|---|---|---|---|---|---|
| October | $374,298 | $596,201 | 7,615 | 1.59 | $49 |
| November | $398,706 | $648,373 | 8,281 | 1.63 | $48 |
| December | $480,920 | $764,698 | 9,749 | 1.59 | $49 |
Q4 calendar
What a new customer is worth, and the break-even it implies
What we changed, Oct 1–18
A ledger of every lever we pulled on Ledisa this month: your baseline, and the last changes before you take the controls.


Tests running
Four live experiments you inherit. Every read is provisional until the 7-day window settles; the decision dates are when a call is due, and from here the call is yours. Tell us under each one.
TRIAL · V3
TRIAL · REVIEW
STORY
TOP 5Projects in flight
Things we were building for Ledisa when the handover started. For each one, tell us: keep it as it is, stop it, or change it (and how).












The YouTube video request, on hold for you
Batch 1 with our creative team (ClickUp 1243w4q8bmf, Olga's editors) is paused until you decide. Tick the videos you still want, pick one option; it saves and Carlos acts on it.
Every edit also applies the Google policy fixes: product named Ledisa Berberine Patch, no Rx-drug references, no before/after bodies, honest urgency, hook in the first 5 seconds, end card with Buy 2 Get 2 Free and the 90-day guarantee, AI-presenter label where it applies. Native horizontal 16:9, never a pillarboxed vertical.
Your decision
The top 30, last 90 days
| # | Creative | Spend | NC rev | NC ROAS | NC orders | NC CPA | NC AOV | CTR | CPM | AL / Meta | File |
|---|
Access and onboarding, where we are
Our view as of Monday Oct 19. Almost everything is in. Tick what you can confirm from your side; untick anything that still doesn't work for you.
Granted, please confirm
Still open
How to ask for things
Three doors. Each one exists because the other way lost requests before.
Your ClickUp board
Carlos is creating a Dominuss board in the Acentecom ClickUp this week. One task per request, assigned to Carlos; he routes it to creative, dev or data and keeps the status honest. Write it as: WHAT you need · WHY (which campaign, which number it moves) · OUTPUT (file, link, format) · BY WHEN. Plain English, no internal jargon needed.
- Content decisions are yours: angles, pages, copy, creative direction. Our teams execute them; Carlos routes and unblocks.
- Requests for other teams are filed from this board, not in Slack threads. Slack is for the conversation; the task is the record.
- You will see status changes and comments; reply on the task, not only in the channel.
Creative: videos, images, copy
Goes through the board to Olga's team (40 video editors; Higgsfield is already in their stack). Deliveries land in Frame.io and the link comes back on the task. What helps them move fast: the source ad id from the marketing tool, exact timestamps for changes, the hook texts, the end card, naming like <ad_id>_YT_16x9. Olga confirms the ETA on the task.
- Google policy is checked before delivery (drug names, before/after bodies, unverifiable claims). The checklist is in Room V.
- The Room V request shows the format of a complete creative brief.
Pages, funnels, Netz and Voluum: Saro's team
Anything on a sales page, checkout, offer, funnel or tracking link is a ticket on the development board, filed by Carlos on your behalf (the board is private to the devs). Write to Carlos what you need and why; he files it, and he closes it after QA.
Communication rhythm (from the kickoff)
Slack only, in #ledisa-dominuss. Red-dot messages get a reply within the hour, otherwise the same day. Your weekly report lands on Tuesdays, the monthly one in the first week of the month. Big changes get a short plan in the channel first, applied on Mondays and Thursdays. We mirror that: anything we change on Search, PMax or Demand Gen that could touch your read gets posted before it happens.
Who does what
You run Ledisa on Google. Carlos assists. Performance gets reviewed together in the review meetings.
Dominuss runs
- Search, brand and non-brand · PMax and Shopping · Demand Gen · YouTube: structure, bids, budgets, tROAS, keywords, copy.
- Content decisions: angles, landing pages, review pages, creative direction, what gets built next.
- The tests in Room III and the projects in Room IV: continue, stop or redirect them.
- Naming, policy appeals, pacing against the floors and the Q4 targets.
- Reporting: the Tuesday report with a Loom, the monthly report in the first week of the month.
Carlos assists with
- Data: Tepui stays live for Ledisa, Triple Whale reads, Google Ads API pulls, pre-period baselines, the halo dashboard if you want it.
- Links and funnels: Voluum links for any lander or offer, filed with Saro's team under the rules in Room VII.
- Builds: pages and creative routed to Olga's and Saro's teams, with the policy scan before anything goes live.
- Plumbing: Merchant Center and feeds, conversion actions, the YouTube channel, account linking, access.
- History: what Google has blocked on Ledisa, what each campaign was set to and why, so nothing is relearned.
- Monitoring, not steering: our daily report, watchdog and page watchers keep reading Ledisa and flag what they see. Nothing on our side changes the Ledisa accounts any more; every automation that wrote to them was switched off on Oct 18.
Together, in the reviews
- Results review: we keep monitoring and bring the read to every review meeting. Performance against the new-customer floors (Search 1.4 · PMax 1.7 · Demand Gen 1.0 · YouTube 1.05, 0.9 while testing) and the Q4 growth targets.
- Test calls when a decision date lands (Oct 19, Oct 26, Nov 3, Nov 12).
- What to build next: pages, creative, products (Sleep), and the order we file them in.
- Anything that touches tracking, feeds or checkout, because those cross into Saro's and Igor's teams.
Your notes
What would help you most, and anything we got wrong. Sign with your name so we know who wrote what.
What would help you most right now
Open notes
Everything on this page saves as you type. The last edit shows on the rail at the bottom. Carlos reads it daily and answers in the channel.


