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, right after the feed rename (watch-out below). Given a 160% tROAS target on Oct 18. |
| 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
Watch-out: Ledisa PMax since the Berberine rename
| Searches | Spend before | after | ROAS before | after |
|---|---|---|---|---|
| "glp 1 patch" family | $2,231 | $2,625 | 2.42 | 1.36 |
| "berberine …" | $302 | $1,180 | 3.44 | 1.09 |
| other patch searches | $1,140 | $1,194 | 1.99 | 1.85 |
| everything else | $747 | $882 | 1.67 | 1.32 |
- Titles that keep the name and carry the search: "Berberine Patches for GLP-1 Support – …". The Oct 15 rule allows GLP-1 as the mechanism; only the product name must be Berberine.
- Negatives for low-intent berberine searches (capsules, pills, supplement, dosage) on this campaign.
- Budget back to $1.5k while the feed re-learns. Our last step here was a 160% tROAS target on Oct 18.
- Done Oct 19 by Jure: new titles in six search angles through supplemental sources. First clean read from about Oct 23, once the items settle and TA 7d matures.
What changed, Oct 1–19
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
Ask the people directly
One shared board, and you go straight to whoever does the work. Nobody in the middle, Carlos included.
The shared board: Ledisa × Dominuss
The list Ledisa × Dominuss in the Acentecom ClickUp (Google Ads folder), with a template task pinned at the top. Anyone assigns anyone: you to us, us to you, you to each other, and you straight to Olga, Saro or anyone below. Statuses: To do → In progress → Waiting (blocked on the other side) → Review → Done. Tags: request · joint · review (for the next results meeting) · blocked.
- Write each task as WHAT · WHY (which campaign, which number it moves) · OUTPUT (file, link, format) · BY WHEN.
- Content decisions are yours: angles, pages, copy, creative direction. Our teams build what you decide.
- Slack is for the conversation; the task is the record. Reply on the task, not only in the channel.
- The requester closes the task after checking it: "Need to fix" with a comment, or "Done". Nothing sits in review.
Who does what on our side
House rules that travel with every request
Communication rhythm (from the kickoff)
Slack, 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. Results are reviewed together in the review meetings.
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: knows which Voluum campaign, lander and offer each Ledisa campaign uses, and why.
- Policy checks: a drug-term scan of any page or script before it goes live, when you want a second pair of eyes.
- 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.


