Acentecom · Google team

Junior media buyer: role brief

Draft for Gianfranco and Uzi · from Carlos · v2, Oct 8, 2026 (v1: Sep 30) · Status: waiting on Uzi's OK to open the search

Review notes for Carlos: what changed since v1

Why a second person Updated

156
campaigns live before the Sep 24 pause (136 Search, 13 PMax, 7 Demand Gen)
34
Google Ads accounts, 8 brands
$6.40M
Q4 new-customer revenue target (Sep 15 to Dec 31)
up to 16
test builds a week (one landing and one ad test per brand)

Since Aaron left on Oct 1, one person covers strategy, builds, feeds, tracking QA and daily operations. Since the Sep 30 tactical we also run one landing test and one ad test per brand every week, and the Netz migration means every campaign gets checked again before it goes back live.

Gian put it plainly on Oct 7: the strategy keeps moving, but the numbers fall behind. The junior owns that part: the daily numbers, the checks and the builds, so the strategy work gets done and nothing is left unwatched.

Which target this moves: none directly. It protects the weekly test cadence and the speed of launches, which is where the Q4 plan expects the growth to come from.

Who owns what Updated

AreaCarlos (lead)Junior
Strategy and targetsQ4 plan, pacing against target, budget split between brands and channelsPrepares the weekly pacing read: actual against month-to-date target, by brand
Daily numbersReads the summary, decides what to act onChecks the daily report ran and the numbers make sense; flags any brand below its NC ROAS floor or behind pace before the daily sync
TestingPicks the tests, writes the hypothesis, calls the resultBuilds the ads and campaigns for each test, keeps the test log current, flags when a test reaches its volume floor
Bids and budgetsApproves every changePrepares the daily scaling proposals for review, applies the approved ones
Advertorials and landing pagesAngle, outline and copyUploads to KittyBuilder or Netz, creates the Voluum lander and campaign, runs the QA visit (tracking, CTA, checkout, California version)
Netz migrationDecides which campaigns go back live and any URL changeKeeps the migration sheet current, checks that each link loads before it is switched on, lists the doubts for the end-of-day review
Search terms and keywordsStructure and new anglesWeekly search-term review, keyword additions, negative lists
Feeds and Merchant CenterFeed strategy, policy decisionsDaily disapproval check, title and image variants, feed edits
Policy and approvalsAppeals, landing-page fixesDaily ad approval check, resubmits disapproved ads after a fix
ReportingReads and comments on results, presents in the weeklyAnswers data requests, keeps the Voluum and Netz link sheets current
Demand Gen and videoCreative direction, audience planUploads assets, builds ad groups, rotates creatives
Tasks and requestsSets prioritiesKeeps the Google tasks in ClickUp current; files dev requests on the dev board

A day in the role New

US Eastern time, because the stores and the budgets run on it (some budgets run out by 2 to 4 pm).

A week in the role New

DayMain work
MondayWeekly pacing read ready before noon. Search-term review and negative lists.
TuesdayGoogle Weekly Tactical: Carlos sets the landing test and ad test per brand. The junior turns them into a build list in ClickUp the same day.
WednesdayBuilds and page uploads. Everything goes to review by end of day.
ThursdayQA, fixes, tests go live. What is asked on Tuesday ships Thursday or Friday, as agreed with Gian.
FridayTest log update: which tests reached their volume floor and are ready to read. Weekly feed and Merchant Center check.

Ground rules New

Most of this job is building things that spend money the same day. These rules hold from the first day, and changes go through Carlos's review until day 60.

Never

  • Edit a Voluum campaign that is live. Any change goes into a new campaign.
  • Point an ad or a feed item at a bare store URL. Every link goes through Voluum.
  • Publish a Netz funnel without Carlos. Publishing ships every saved draft in that funnel, including other people's.
  • Push a KittyBuilder page without review. Push means live; there is no staging.
  • Trade the NC ROAS floor for volume, or step a budget past the caps (+20% up, -33% down, 7 days between steps) without Carlos.
  • Select what to change by campaign or ad group name. Use the ID. Names repeat across accounts and brands.

Always

  • Log every change: what, where, before and after, who approved it.
  • Quote NC ROAS from Triple Whale with its model (Triple Attribution 14d or Last Click 7d). Google Ads conversions are not the ROAS source.
  • Check a health landing page for drug names and claims before sending traffic. Google reads the page, not only the ad.
  • Ask the person who owns a thing only for what only they can do. Everything else we do ourselves.

Access to set up before day one New

ToolUsed forLevelWho grants it
Google Ads (MCC, 34 accounts)Builds, checks, approved changesStandard, not adminCarlos
Merchant Center (per brand)Disapprovals, feed checksStandardCarlos
Feed Google SheetsTitles, images, variantsEditorCarlos
VoluumLanders, campaigns, link QAOwn seatSaro or Gian
Netz (admin.netz.com)Pages and funnel QAOwn seat, no publishingPawel
KittyBuilderAdvertorial uploadsEditorGian
Triple WhaleNC ROAS, new-customer revenueReadGian
Daily Google reportDaily numbers, pacing, testsLinkCarlos
ClickUp and Slack (#google channels)Tasks, requests, daily notesMemberGian

How we know it is working New

First 90 days Updated

Days 1 to 30: learn and check

  • Week 1: access, account map (8 brands, 34 accounts, naming conventions), the Voluum and Netz rules. Shadows the daily checks.
  • Week 2: runs the daily checks with Carlos reviewing them. Joins the Tuesday tactical.
  • Week 3: runs the daily checks and the QA visits alone. Builds the first test ads from a brief.

Days 30 to 60: build

  • Builds test campaigns, ads and Voluum setups from a brief without rework.
  • Owns the weekly search-term review and the weekly pacing read.

Days 60 to 90: propose

  • Proposes tests of their own, each with a hypothesis and a metric.
  • Applies routine changes within the caps without pre-review. Bids, budgets outside the caps and anything live in Voluum or Netz stay with Carlos.

Profile and hiring

Hiring steps New

  1. Screening call with Carlos (30 minutes).
  2. Paid practical task, about 2 hours: build one Search ad group and two responsive search ads from a one-page brief; write negatives from a search-term export; find the errors planted in a sample link sheet.
  3. Final call with Gian.

Media buyer or native copywriter New

On Oct 7 we talked about a junior media buyer, a copywriter for native, or both.

Recommendation: hire the media buyer first. The gap Gian named is operational: numbers, checks and builds. Copy for ads and advertorials is covered today by Carlos, the copy framework we got from Olga, and Agus's reviews.

A native copywriter makes sense once the advertorial tests (decision on Oct 21) show which angles win and we need more than one new advertorial per brand each week. If we hire one, they would own advertorial and native drafts, and Carlos would keep the angle and the final approval.

Decisions needed from Gian and Uzi New

  1. OK to open the search (Uzi).
  2. Budget and contract type: employee or contractor.
  3. Location and time zone, given the 4-hour overlap with US Eastern.
  4. Target start date. With a start in early November, the junior is running the daily checks alone by late November, during BFCM.
  5. Media buyer only, or media buyer now and native copywriter later.

How we work together