Building & Leading a PPC Analyst Team: From Hiring to High Performance

The Four Seats That Run a Modern PPC Analyst Unit

A modern 3–4 person PPC analyst unit at an analytics-focused firm needs four distinct functional seats. The generalist who handles keyword research, bid adjustments, and monthly reporting in a single role is being structurally displaced by automation — not eliminated, but restructured. Your PPC Team Is Now a Data Team identifies the shift plainly: teams that design around execution seats lose to teams that design around data ownership seats. More than 80% of Google advertisers now use automated bidding, automating what that generalist once did by hand.

Tracking Specialist owns Google Tag Manager, pixel integrity across platforms (Google Ads, Meta, LinkedIn), conversion event configuration, and UTM taxonomy. This seat ensures data enters the measurement system correctly. Search Engine Land's paid search team guide identifies this as a discrete role and flags combining it with campaign execution as a structural weakness: the person managing campaigns should never also decide what counts as a conversion.

Campaign Analyst executes daily Google Ads and Meta operations — keyword management, bid adjustments within approved parameters, ad copy rotation, pacing reviews, and anomaly reporting. This seat produces the daily performance signal that every other role acts on.

Analytics Engineer builds and maintains the measurement infrastructure: ad-platform-to-data-warehouse pipelines, cross-platform attribution models, and decision-ready dashboards. This seat ensures data is structured correctly once it is inside the system — a layer above the Tracking Specialist, who ensures it enters correctly.

Paid Media Strategist translates business objectives into channel strategy, budget allocation, and audience architecture. This role reads Analytics Engineer output to make directional decisions that the Campaign Analyst executes.

How the Four Roles Map to Daily Campaign Workflows

The four seats form a left-to-right data pipeline: raw web and platform events flow in, structured decisions flow out.

The Tracking Specialist receives the raw stream — clicks, form submissions, purchases — and configures how those events enter reporting systems via GTM. The Campaign Analyst reads the resulting daily dashboard and executes the approved actions that keep campaigns on target. The Analytics Engineer transforms tagged data into cross-client attribution models, deduplicating ROAS figures across platforms: platform-reported ROAS overstates real ROAS by 15–30% in most multi-platform accounts due to attribution overlap between Google and Meta, making deduplication mandatory for accounts running both. The Paid Media Strategist reads the clean figures and decides how to reallocate budget, shift channel mix, or revise audience strategy.

The feedback loop runs in reverse as well: the Strategist sets direction and targets, the Campaign Analyst executes, the Tracking Specialist verifies data integrity, and the Analytics Engineer confirms numbers are trustworthy before anyone acts on them again.

KPI Ownership: Who Is Accountable for What

The RACI framework requires exactly one Accountable owner per metric. Designating both the Campaign Analyst and the Paid Media Strategist as Accountable for CPA is the most common governance failure in small PPC teams: when CPA drifts, nobody escalates because nobody has exclusive ownership. RACI Matrix: Your Ultimate Guide 2026 quantifies the cost of unclear accountability: roughly 47% of project spending is at risk when roles and responsibilities are undefined — the same structural gap that lets dual-accountable CPA targets go unescalated for weeks.

The clean split across four key metrics:

CPA — Campaign Analyst is Responsible: monitors daily deviation and reports immediately. Paid Media Strategist is Accountable: owns the business response to deviation and sets the target.

ROAS — Analytics Engineer is Responsible for the cross-platform, deduplicated ROAS figure. Paid Media Strategist is Accountable for setting targets based on the real figure, not the platform-reported one.

CTR — Campaign Analyst monitors performance and tests ad variants. CTR is a creative relevance signal, not a business outcome; it must always be paired with CVR to separate click-generating creative from conversion-driving creative.

CVR (traffic side) — Campaign Analyst owns the ad-click-to-conversion rate. Analytics Engineer owns the attribution accuracy of the CVR calculation.

The Autonomous-vs-Sign-Off Line

Requiring manager approval on every adjustment destroys execution velocity. Skipping approval on structural changes creates uncontrolled risk. Drawing this line before your first analyst starts prevents both failure modes.

Campaign Analysts operate autonomously when: adjusting bids within ±15% of the current CPA or ROAS target, pausing underperforming keywords against clear performance thresholds, rotating a new ad variant into an existing A/B test, and repairing broken conversion tags.

Paid Media Strategist or PPC Manager sign-off is required when: changing the CPA or ROAS target itself, switching bid strategy type (for example, from Maximize Conversions to Target CPA), reallocating budget across campaigns by more than 20%, adding entirely new keyword themes, or changing which events count as conversions. Attribution model changes always require approval — they redefine what every metric in the account is optimizing toward.

Choosing Between Configuration A and Configuration B

Two configurations cover the 3–4 analyst seat range.

Configuration A (3 analyst seats) pairs a Tracking Specialist, Campaign Analyst, and Paid Media Strategist. The PPC Manager absorbs analytics engineering — data pipeline work, attribution modeling, and cross-client dashboards. This configuration suits teams with managed spend below $150,000/month and fewer than 50 active campaigns, where standard platform dashboards meet client reporting needs. The structural weakness appears at scale: around 6 clients or 50+ campaigns, analytics engineering work exceeds 15+ manager hours per week and the Manager becomes the bottleneck.

Configuration B (4 analyst seats) adds a dedicated Analytics Engineer as the third hire, before the Paid Media Strategist. This is the default above $150,000/month or 50+ campaigns, and whenever clients require custom attribution, multi-touch analysis, or LTV modeling.

The sequencing rule matters more than which label you choose. Hire the Tracking Specialist first — broken tracking makes analytics engineering work unreliable, since you cannot build valid attribution models on corrupt event data. Add the Campaign Analyst second to relieve execution load. Only then hire the Analytics Engineer, once clean data exists to model from.

In Karthik's scenario — ₹1.2 crore/month managed spend, 54 active campaigns, conversion tracking unaudited for 18 months — the suspected ROAS inflation (Google reports 4.8:1 against a client target of 4.5:1) is a data-fidelity problem, not a strategy gap. Configuration A with the Tracking Specialist as Hire 1 is the correct first move, even though managed spend technically qualifies for Configuration B immediately. Sequence integrity matters more than configuration completeness.

Hands-On Exercise: Design Your Team Configuration

Scenario: your analytics firm manages $180,000/month across 72 active campaigns for 9 SaaS clients. Conversion tracking was last audited 6 months ago. One client requires a cross-channel LTV model and custom multi-touch attribution. You have budget for three analyst hires.

1. Which configuration — A or B — fits this scenario, and why?
2. Sequence all three hires in order and assign each a role name from this chapter.
3. List two decisions your Campaign Analyst can make autonomously once ramped, and two that will always require your sign-off.

Success criteria: Configuration B selected (spend >$150K plus custom attribution requirement). Tracking Specialist is Hire 1. Autonomous examples apply the ±15% bid threshold; escalation examples include bid strategy type change and CPA target revision.

Next, 02-skills-based-hiring-job-descriptions shows how to write outcome-anchored job descriptions and run a skills-based hiring process for each of these four analyst seats.

The biggest obstacle in PPC analyst hiring is not finding candidates — it is filtering them. Most job descriptions list tasks ("manage Google Ads campaigns") and screen for platform exposure rather than diagnostic ability. Eighty-five percent of employers now use skills-based hiring, up from 57% in 2022, and 67% report fewer mis-hires as a result. This chapter shows you how to apply that shift: rewriting the job description so it screens for results, designing a structured take-home audit that separates root-cause diagnosers from surface-metric reporters, and running a five-question scorecard interview that makes ranking candidates straightforward.

From Activity-Based to Outcome-Anchored Job Descriptions

Every activity-based bullet follows the same broken pattern: it names a task performed rather than a result produced. The fix requires three components in every bullet — a measurable threshold, a time boundary, and an accountability owner. A bullet missing any of these is still an activity description, regardless of how specific it sounds.

The transformation is mechanical:

The outcome-anchored version serves a second purpose beyond candidate attraction: each bullet becomes a scorecard question. "Own GA4 conversion accuracy; resolve discrepancies >3% within 5 business days" maps directly to your measurement competency interview question. Writing the job description and the scorecard simultaneously is not extra work — it is the same work.

Required 2026 Platform Proficiencies

For Google Ads, a 2026 hire must demonstrate capability in three areas — not just hold a certification. Search and Performance Max campaign management means understanding keyword match types, asset-group structure, Smart Bidding strategy selection (including when to switch away from it: below 50 conversions per month, Smart Bidding underperforms manual CPC by 30–50%), and reading the Recommendations tab critically rather than accepting it wholesale. Measurement and attribution covers data-driven attribution (Google's default since 2022), enhanced conversions, and consent mode — the prerequisites for accurate conversion reporting. The Google Ads Measurement Certification aligns to this area. Auction intelligence means reading impression share split correctly: IS lost to budget signals spend exhaustion; IS lost to rank signals a bid or quality score problem. These two signals point to entirely different fixes and are the single most reliable separator between surface-metric reporters and root-cause diagnosers.

For GA4, minimum required skills are configuring key events for conversion tracking, validating attribution models, building exploration reports, and creating audiences for RLSA or Customer Match. For Looker Studio, the minimum bar is connecting native Google Ads and GA4 data sources, building calculated fields (e.g., a ROAS formula), constructing a budget-pacing bullet chart, and scheduling automated report delivery. GA4 and Looker Studio together form the backbone of PPC reporting — analysts who use them only for viewing pre-built reports are not operating at a 2026 professional standard.

Building the Interview Scorecard

Structured interviews are more predictive of job performance than unstructured conversations and save approximately 40 minutes per candidate. The operating rule is simple: every interviewer asks the same five questions in the same order, scores independently before any debrief, and compares results against pre-declared pass/fail thresholds rather than against each other's impressions.

A five-question PPC analyst scorecard should cover: platform knowledge — Search (Q1), root-cause diagnosis (Q2, knockout), measurement and attribution (Q3), reporting communication (Q4), and GA4/Looker Studio toolchain (Q5). Q2 carries a knockout designation: any candidate scoring below 4 on a 1–5 behaviorally-anchored scale is a no-hire regardless of scores elsewhere. This mirrors the daily reality of the role — an analyst who describes metric movements without diagnosing their cause produces reporting that misleads client decisions.

Setting pass/fail thresholds must happen before any candidate responses are read. Thresholds set after reviewing responses reflect the strongest candidate rather than the role's actual requirements, converting a structured process back into unstructured gut-feel hiring.

The 30-Minute Anonymised Account Audit

Work-sample tests — tasks that mirror real job content — have five times the predictive validity of résumé screening. The PPC analyst version is a 30-minute anonymised account audit: candidates receive 90 days of campaign-level data scrubbed of client identifiers, with a brief business context paragraph, and must identify the most significant underperformance issue, explain its root cause (not just its symptom), and outline three prioritised actions with expected outcomes.

Dataset design is where the test's power lives. Include impression share broken into IS lost to budget and IS lost to rank for each campaign. A strong candidate identifies the campaign with high IS lost to rank and zero IS lost to budget, correctly reads this as a bid or quality score problem rather than a spend problem, and proposes a Quality Score audit, ad relevance review, or bid-strategy adjustment — not a budget increase. This single data point filters most applicants. A candidate who reads IS lost to rank as a budget problem has confused two diagnostic signals that require opposite interventions.

Give candidates a 48-hour window but state an explicit 30-minute effort cap. Unlimited time conflates thoroughness with prioritisation skill. A candidate who submits a 10-page analysis in 3 hours is not demonstrating depth — they may be demonstrating an inability to prioritise under the time constraints that define the actual job.

Ranking Candidates with Structured Justification

After scorecards are complete, rank finalists by weighted total, with Q2 weighted at 2× to reflect its diagnostic importance. For each hire and no-hire decision, produce a written justification that names specific scorecard evidence — a score tied to a candidate response — rather than adjectives like "felt sharp" or "strong communicator."

The written justification disciplines the hiring debrief. When each evaluator must name the evidence for their verdict, post-hoc rationalisation in favour of likeable candidates who failed the technical screen becomes visible. Store completed scorecards and justifications in your ATS as a bias-audit trail and a calibration benchmark for the next hire.

Hands-on Exercise

Find four job description bullets from a live PPC analyst posting — your own or from a public job board — and rewrite each one as an outcome-anchored bullet. For each rewrite, confirm it passes three checks: (1) it contains a measurable threshold (a number or percentage), (2) it specifies a time boundary, and (3) it names who owns the outcome. Then map each rewritten bullet to one of the five scorecard question areas it would test.

Success criteria: All four rewrites pass the three-component check. At least three of them map to distinct scorecard question areas without overlapping, demonstrating that a well-written job description generates its own scorecard rather than requiring one to be designed separately.

Once your analysts are hired, the work of getting them contributing quickly begins. Next: Onboarding Analysts with a 30-60-90 Day Ramp Plan Tied to Campaign Ownership

Your new analyst is hired, their start date is set, and their laptop is ready. What happens next determines whether they are independently running campaigns by Day 30 or still asking for help on basic tasks by Day 60. The answer is almost never about talent — it is almost always about structure.

The Three-Phase Ramp Framework

The 30-60-90 framework maps a new analyst's first quarter to three phases: Learn (Days 1–30), Apply (Days 31–60), and Own (Days 61–90). Each phase has one primary goal, a set of concrete deliverables, and a numeric KPI checkpoint at the boundary. Programmes built this way are 2.5× more likely to be rated effective, according to the Association for Talent Development via AllenComm — and the stakes for getting it wrong are significant: mid-level replacement costs exceed $30,000 per Oxford Economics data cited by AllenComm, with SHRM estimating total turnover costs at 50–200% of annual salary.

For a PPC analyst, the three phases map directly to campaign ownership:

• Learn: The analyst observes, audits, and builds under supervision. No live campaign changes without a manager countersign.
• Apply: The analyst manages one primary account independently, with weekly check-ins. The first formal optimisation recommendation requires manager review before implementation.
• Own: The analyst carries a full portfolio, delivers monthly strategy memos, and leads at least one client call.

Phase transitions are earned by hitting KPIs — not granted by calendar time.

Day-One Access Provisioning

Access gaps are the most common — and most avoidable — reason a ramp starts a week late. The minimum access stack must be provisioned before the analyst's first login.

Two provisioning actions require lead time. MCC invitations must be sent the week before start date — Google Ads MCC invites require the invitee to accept, and a same-day invite loses Day 1 to an email queue. CRM partner connector seats require vendor portal action, which may need a procurement approval cycle; flag this two weeks in advance.

The Day 30 upgrade on GA4 from Analyst to Editor is not optional — GA4's access model requires Editor role before an analyst can connect a property to Looker Studio or modify audience and event definitions. Assign these roles at property level, not account level, to avoid propagating access to other clients' properties.

Milestone Deliverables and KPIs

Each phase boundary is a formal check-in with numeric pass/fail thresholds. An analyst who misses a Day 30 KPI does not automatically progress to the Apply phase.

Day 30 — Learn phase close: - Account audit submitted and accepted by team lead (binary: accepted or not) - QA pass rate on first supervised campaign: 100% before countersign - Time-to-first-solo-campaign: ≤Day 30

Day 60 — Apply phase close: - QA pass rate across all active campaigns: ≥90% - Report accuracy score (spot-check 5 metrics against platform source data, tolerance ±1%): ≥95% - Weeks of primary account managed without escalation: ≥3 - First formal optimisation recommendation: approved and implemented

Day 90 — Own phase close: - QA pass rate: ≥95% - Report accuracy score: ≥98% - Manager satisfaction rating: ≥4.0 / 5.0 - 90-day retention: analyst still in role (binary pass/fail)

These thresholds are illustrative — calibrate your own targets after two ramp cycles.

The Day-45 Diagnosis

Studies suggest up to 20% of new-hire turnover occurs within the first 90 days, per AIHR, making mid-ramp the most critical diagnostic window. When an analyst misses a KPI at Day 45, diagnose root cause before assigning remediation. There are exactly three categories:

1. Access or tooling gap. The analyst cannot physically complete the task because a permission is missing or a tool is unavailable. Example: low QA pass rate because GA4 Custom Dimensions are invisible to an Analyst-role user after a landing page URL change. Fix: provision the correct access, re-run the task with a one-week grace period.

1. Skill or knowledge gap. The analyst has access but lacks the training to use it correctly. Fix: a targeted session on the specific failure mode — not a broad remediation plan.

1. Workload mismatch. Two or more major deliverables collided in the same week. Fix: redistribute account load and reschedule the missed milestone. Do not treat a scheduling conflict as a performance problem.

Diagnose all three before assigning any intervention. A tooling diagnosis demands a tooling fix. Conflating an access gap with a skill gap wastes two weeks on the wrong solution and signals to the analyst that you are not paying close attention.

Handing Off to Solo Campaign Ownership

First solo campaign ownership happens when the analyst earns it through the countersign protocol, not when the calendar reaches Day 28. The target window is Day 25–35.

The protocol: 1. Analyst completes the QA checklist in full: tracking verified (conversion actions firing in preview), bid strategy confirmed, creative assets approved, negative keywords attached, landing page live with <2.1s mobile load time per WE Interactive's 2026 PPC Checklist. 2. Team lead spot-checks three checklist items at random. 3. All three pass → team lead countersigns → campaign goes live. 4. Any fail → analyst corrects and restarts the checklist from step one. No partial passes.

Once countersigned, daily oversight drops to weekly check-ins. The analyst has explicit authority over keyword, bid, and budget pacing — with one constraint: the first formal optimisation recommendation still requires written manager sign-off before implementation, a gate removed at Day 60 once QA and accuracy targets are met.

New campaigns need 30+ days of conversion data before bid signals are reliable — brief the analyst in week one so optimisation recommendations reference the correct window.

Portfolio expansion follows the same ladder, phase-shifted 30 days per account → 04-campaign-portfolio-accountability-rhythms.

Hands-On Exercise

Using the framework from this chapter, apply it to a real or hypothetical analyst joining your team next month:

1. Write out the Day 1 access provisioning checklist for your specific platforms (include scope level for each — child account vs. MCC, property vs. account, etc.). Mark which items require vendor or procurement action and their minimum lead time.
2. Define three Day 30 KPIs with explicit pass/fail thresholds, tied to the specific accounts and campaign types that analyst will own.
3. Draft a Day-45 diagnosis checklist: three root-cause questions — one per category (access, skill, workload) — that you would work through before assigning any remediation.

Success criteria: Each Day 30 KPI has a numeric threshold and is tied to a named deliverable. Your diagnosis checklist asks root-cause questions that could produce three different answers, not questions that lead to a single predetermined conclusion.

Equal campaign counts feel fair. They rarely are. When your senior analyst owns Brand Search while your junior inherits a £18K Performance Max in its learning phase alongside an under-threshold Meta Advantage+ account, your team is misaligned regardless of how evenly the list divides. This chapter gives you a scoring model to allocate portfolios by management burden, a weekly rhythm that surfaces problems without micromanaging, and escalation thresholds that keep analysts accountable — building on the team roles defined in 01-designing-ppc-analyst-team-roles.

The Weighted Scoring Model

Portfolio allocation must equate management burden, not campaign count. A fair distribution balances total score-points assigned to each analyst, not campaign headcount — equal campaign lists rarely produce equal workloads.

Score every live campaign 1–5 across four dimensions, then multiply by their respective weights:

• Monthly spend (30 pts): higher spend increases budget risk and stakeholder scrutiny
• Platform complexity (30 pts): algorithmic opacity, creative asset overhead, reporting depth
• Conversion volume (20 pts, inverted): fewer monthly conversions demand more manual oversight, so lower volume earns a higher score
• Campaign risk (20 pts): new launches, active learning phases, recent CPA volatility, live promotions

Portfolio Weight = (Spend_score × 30) + (Complexity_score × 30) + (ConvVol_score × 20) + (Risk_score × 20), normalized to 100 points. Target ±15% variance from the team mean.

Performance Max and Meta Advantage+ Shopping Campaigns (ASC) consistently score 5 on platform complexity. Per Dataslayer's 2026 PMax guide, PMax takes 2–6 weeks to exit its learning phase — double the 1–2 weeks for standard Search. Google requires 30 conversions at the account level as a launch eligibility prerequisite; after launch, the post-launch stabilization target is 50 conversions per campaign per month before the AI bidding algorithm performs reliably. Assigning a PMax in its learning phase to a junior analyst places your highest-complexity task in your lowest-capacity seat.

Allocating Eight Campaigns Across Three Analysts

Take a £63K/month portfolio: Performance Max (£18K/month, learning phase, 55 monthly conversions), Non-Brand Lead Gen Search (£12K, 40 conversions), Meta ASC (£15K, 80 conversions), Competitor Conquest Search (£8K, 22 conversions, volatile CPCs), YouTube Brand Awareness (£6K, 14 conversions), Display Remarketing (£4K, 28 conversions), Meta Retargeting (£5K, 35 conversions), and Brand Search (£3K, 120 conversions).

After scoring, total team weight is 446 points — a mean of approximately 149 per analyst for a three-person team. The correct allocation:

Senior analyst (154 pts): Performance Max (74 pts) and Competitor Conquest Search (80 pts). Both campaigns require experienced interpretation: PMax demands judgment to distinguish algorithm instability from genuine underperformance; Competitor Conquest has volatile exact-match CPCs and only 22 monthly conversions — below the threshold where standard optimizations reliably move outcomes.

Mid-level analyst (137 pts): Non-Brand Search (68 pts) and Meta ASC (69 pts). Significant spend, moderate complexity; the ASC suits someone with campaign judgment who can escalate to the senior analyst.

Junior analyst (155 pts): Brand Search, Display Remarketing, Meta Retargeting, and YouTube Brand Awareness (155 pts combined). Four campaigns, all in stable phases with clear optimization levers and no active learning periods (see 03-onboarding-analysts-30-60-90-ramp).

Total variance from mean: ±6 pts. Within the ±15% target.

Campaign-Owner RACI for Cross-Platform Launches

When Google Search, Performance Max, and Meta ASC go live in the same two-week window, tasks fall to whoever is paying closest attention — unless ownership is made explicit.

For a cross-platform launch, the manager holds Accountability (A) for all platform go-lives; execution Responsibility (R) sits with the assigned analyst per platform. The Tracking Specialist is Consulted (C) on creative tasks but holds Responsible for all pixel and tag QA. Junior analysts are Responsible for Day 1–3 anomaly monitoring on their portfolio campaigns; the senior analyst holds Responsible on PMax and Competitor Conquest.

The most common failure is co-Accountability — writing "Senior Analyst + Manager" as joint owners of a single deliverable. When two people are Accountable, neither owns the outcome. One Accountable per deliverable, always.

Your Weekly Operating Rhythm

Async-first design lets the manager access performance data without requiring analyst availability at the same time. The operating rhythm for a three-person PPC team:

Daily (9am, each analyst): 10-minute self-serve pacing check against the shared Looker Studio dashboard. No meetings. This is the primary mechanism for catching overspend before it becomes an escalation.

Monday (9am, rotating analyst): Written weekly performance report — annotated Looker Studio view plus one paragraph explaining what changed and why. Dataslayer's practitioner norm is to deliver this before the stand-up so the 20-minute sync focuses on decisions, not data updates.

Monday (10am): 20-minute stand-up. Agenda: prior-week KPI summary, 2 minutes per analyst (6 min total); escalations and pacing flags (5 min); upcoming launches or structural changes (5 min); cross-analyst dependencies (4 min).

Wednesday (12pm): Manager reviews the async escalation log. Five minutes maximum. Required fields: campaign name, anomaly type, current value versus threshold, analyst recommendation, decision needed by.

Friday (4pm): Per-campaign status note from each analyst. Async. No meeting.

Escalation Thresholds Inside the Cadence

Thresholds must scale with account size. A 15% pacing deviation on a £3K campaign is noise; on a £25K campaign it is a £3,750 error requiring immediate action. Improvado's 2026 budget pacing framework sets the acceptable pacing bands; the anomaly triggers below are practitioner-recommended values:

Two additional trigger types belong in every escalation policy: Lost Impression Share (Budget) exceeding 10% for three consecutive days signals structural underfunding and warrants a budget reallocation review. Hourly CPC exceeding 150% of the 7-day same-hour average signals auction disruption and warrants investigation before the next scheduled Wednesday check. For root-cause diagnosis, Improvado's PPC analysis guide covers anomaly decision trees.

The Manager's Rolled-Up KPI Dashboard

The dashboard has one job: reveal which analyst's portfolio needs attention in under five minutes. Dataslayer's 2026 practitioner standard specifies up to ten KPIs (widgets) on one screen — no scrolling, status-at-a-glance indicators — because managers who need to stitch insights from multiple views start delaying decisions.

For a PPC team, a practical set to include: spend-to-budget pacing (% of linear target), CPA versus target, ROAS versus target, conversion volume (week-over-week change), CTR versus 4-week average, Lost Impression Share (Budget), and click volume trend. Each campaign row shows a status indicator: green (within acceptable band), amber (approaching threshold), red (escalation triggered).

If the manager needs to drill into individual campaign views to understand portfolio health, the five-minute standard is already broken.

Hands-on Exercise

Apply the weighted scoring model to a real or illustrative portfolio:

1. List your active campaigns and score each 1–5 on spend, platform complexity, conversion volume (inverted), and campaign risk.
2. Calculate portfolio weight per campaign and sum per analyst.
3. Reassign campaigns until team-mean variance is ≤15%.
4. Draft the Wednesday escalation log entry for a £30K account pacing at 108% of its daily target — include anomaly type, current value, analyst recommendation, and decision deadline.
5. Build the manager dashboard row for your highest-weight campaign: pacing bullet indicator, CPA status, and LIS (Budget) threshold flag.

Success criteria: Weight variance ≤15% from team mean; escalation entry includes all required fields; dashboard row readable in under 90 seconds.

Next chapter: 05-coaching-analysts-performance-gaps — How to turn campaign performance data into structured 1-on-1 coaching conversations and measurable two-week improvement targets for analysts with performance gaps.

Most coaching conversations fail before they start — not because the manager lacks empathy, but because they walk in without evidence. A hunch that "the numbers look off" produces a defensive analyst and a vague commitment. A coaching brief built from the same data your analyst owns produces a diagnosis you can act on together.

Build the Coaching Brief Before You Enter the Room

Prepare the brief the day before each 1-on-1. Pull Tier-1 signals from your manager dashboard: impressions, clicks, CTR, and CPA for each of the analyst's accounts. Compare CTR against the analyst's own 90-day baseline first — then against industry benchmarks. The cross-industry average Google Ads CTR is 6.66% (n=16,446 US campaigns, WordStream Google Ads Benchmarks 2025), but Finance & Insurance averages 2.55% CVR versus Auto Repair's 14.67% — benchmarking against fleet averages instead of vertical norms is one of the fastest ways to lose an analyst's trust.

Your brief has four parts:

1. Evidence — which specific accounts, which metrics, over what time window
2. Preliminary gap hypothesis — skill, tool/access, or workload (a hypothesis, not a verdict)
3. GROW entry questions — one or two open Reality questions drawn from the GROW coaching model (Goal → Reality → Options → Will) to probe what actually happened
4. Draft two-week targets — written in advance, shared and negotiated in the meeting, not handed down after

The brief takes about 15 minutes to build. Without it, the first 10 minutes of every 1-on-1 burn on locating the same data together — leaving no time for the conversation that matters.

Diagnosing the Gap: Skill, Tool Access, or Workload

Before you write a coaching plan, you must identify which type of gap you are dealing with — because each one requires a different intervention.

• Skill gap: The analyst does not know how to do something. Fix: training, shadowing, or structured review.
• Tool/access gap: The analyst knows how but cannot do it — a GA4 property is not linked to her Google Ads account, or a negative keyword list is admin-locked. Fix: permissions change or tool provisioning.
• Workload distribution gap: The analyst is capable and has access but is managing more accounts than the team model supports. Fix: redistribution or hiring. (Within the first 90 days, check 03-onboarding-analysts-30-60-90-ramp for Day-45 triage before escalating to redistribution.)

AIHR's skills gap analysis framework identifies premature coaching as the most common mis-triage: managers reach for skill training when the root cause is missing access. The diagnostic sequence is three questions in order: (1) "Do you have access to X?" before (2) "Do you know how to do X?" before (3) "How often are you doing X?"

A 31% CVR drop with only an 8% CPC increase warrants access and workload checks before coaching. If the analyst recently absorbed extra accounts and lacks GA4 access for them, the problem is structural — coaching it as a skill deficiency will damage the relationship.

From Data to Feedback: The SBI Method with Campaign Evidence

Vague feedback is the most common trust-eroder in analyst management. "Your performance has been poor lately" has no Situation, no observable Behavior, and no quantified Impact. The SBI Feedback Model from the Center for Creative Leadership solves this by requiring each element:

Situation: Name the campaign, account, and date. "In the Account A performance report submitted last Tuesday..."

Behavior: Name the observable action or omission. "...you flagged a CTR drop to 5.1% but did not include a root-cause hypothesis or a proposed next step within 24 hours, which is the team standard."

Impact: Quantify the result. "...We ran the same underperforming ads for six additional days, continuing to spend budget without a pivot decision."

Then add the SBII extension — "What was happening on your end that made it hard to complete that step?" — before closing. This opens dialogue rather than ending on judgment, and frequently surfaces that the real gap is a process expectation the analyst never knew existed.

Setting Two-Week Improvement Targets That Stick

When a coaching conversation surfaces a genuine gap, close the 1-on-1 with a two-week sprint: 2–3 specific, observable, time-bound targets agreed in the room, not assigned in a follow-up email.

A well-formed target: "Refresh RSA headlines and descriptions on all ad groups with CTR below 5% by Day 5; bring account CTR from 5.1% to at least 6.0% by Day 14, confirmed in the weekly performance report." A poorly formed target: "Improve CTR on Account A."

Structure the sprint with a mid-point check on Day 7 — 10 minutes, not a full 1-on-1. At Day 14, either the metric moved and the sprint closes, or it did not and you escalate to a formal 30-day plan. According to Asana's Performance Improvement Plan guidance, the pre-PIP two-week sprint is the standard early-alert structure: 2–3 tightly defined targets, a mid-point check, and explicit success criteria defined in advance. Its value is in catching gaps while they are still correctable without formal documentation (see 04-campaign-portfolio-accountability-rhythms).

The Quarterly Analyst Scorecard: Three Domains, One Picture

A scorecard that measures only CTR and CPA punishes analysts for market conditions they cannot control and rewards those who happened to inherit strong accounts. Separate the quarterly review into three domains:

KPI Outcomes carry the lowest weight because they are partly market-driven. Analysis Quality carries the highest (40%) because it is the best long-term predictor of analyst performance and is entirely within the analyst's control. An analyst whose CTR is flat due to competitive auction pressure but who delivers sharp diagnostic write-ups with GA4-sourced hypotheses is building capability — a KPI-only scorecard misses that entirely. Process Adherence (30%) is a leading indicator: an analyst who maintains negative keyword lists and files reports on time tends to catch CPA drift before it becomes a coaching event.

Share the scorecard template with analysts at the start of the quarter (Culture Amp 1-on-1 research). Criteria that arrive as surprises at review time are not evaluation tools — they are grievances waiting to happen.

Hands-On Exercise

Goal: Build a coaching brief and two-week sprint plan for a real or anonymised analyst on your team.

1. Pull six weeks of CTR and CPA data for one analyst account where you have noticed a shift.
2. Check the analyst's 90-day baseline before comparing to any industry benchmark.
3. Confirm the analyst has tool access to investigate the gap — GA4 property linked, read permissions in place.
4. Write the four-part brief: Evidence, Gap Hypothesis, GROW Reality questions, Draft two-week targets.
5. Run the 1-on-1. Update the hypothesis based on what the analyst tells you before agreeing on final targets.

Success criteria: Your brief names a specific account, dates, and the metric delta. Your GROW questions are open-ended and cannot be answered yes or no. Your two-week targets follow the format "metric from X to Y by [date], confirmed in [artefact]."

Next chapter: 06-reporting-automation-ai-assisted-workflows covers how to build the reporting infrastructure that makes coaching conversations data-ready every week — automated Looker Studio dashboards, anomaly alerts, and the team workflow shift from manual CSV exports to decision-making.

The 2026 Reporting Stack

Your team is spending 4–6 analyst hours every week pulling CSVs, normalising currencies, and assembling numbers that were accurate at export and stale by the time anyone reads them. Automation fixes this — but only the assembly layer. The judgment layer stays yours.

The 2026 reporting stack runs on three tiers: data ingestion (platform APIs feed a pipeline or native connector), transformation (calculated fields normalise currencies, segment prospecting from retargeting, and compute blended CAC), and visualisation (Looker Studio serves live dashboards to three audiences: campaign managers, marketing leads, and executive stakeholders).

The weekly report template within this stack tracks seven KPIs: ROAS, CPA, CTR, CVR, impression share, blended CAC, and an incrementality estimate. Each earns its place. ROAS and CPA measure campaign efficiency. CTR and CVR diagnose creative and landing page health. Impression share is a leading indicator — a falling share without rising CPC signals a budget constraint before ROAS has time to drop. Blended CAC adds tool subscriptions and agency fees that ad-spend-only CPA misses. The incrementality estimate prevents retargeting attribution inflation, covered in the section below.

Building a Looker Studio Dashboard for Your PPC Team

Looker Studio connects natively to Google Ads, GA4, and — since November 2025 — Meta Ads, making single-dashboard cross-platform reporting feasible without paid middleware. Use the native Google Ads connector with "Overall Account Fields" to mix campaign, ad group, and keyword dimensions in a single report. Connect GA4 for post-click behavioural metrics — engaged sessions per click, bounce rate, scroll depth — but never for revenue attribution. GA4's model differs from Google Ads', and using both as revenue sources creates double-counting.

Two calculated fields anchor the dashboard. First, a prospecting/retargeting segment toggle: create a filter control keyed to a campaign naming convention — campaigns containing "PROSP" vs "RETARG." This single filter lets analysts and stakeholders switch between ROAS views in seconds, making the segmentation operational rather than just analytical. Second, a blended ROAS field: connect a Google Sheets source containing backend payment-gateway revenue, blend it with platform spend totals by date, and display platform ROAS and blended ROAS side by side using Looker Studio's data blending feature. The gap between platform-total and backend-actual is the attribution overlap figure leadership needs to see.

Reading Modelled Conversions Without Being Misled

Google's "Conversions" column combines modelled and directly measured conversions without a native column separating them. Modelled conversions are ML estimates for users who denied cookie consent; they require at least 700 ad clicks over 7 days per country per domain to activate (About consent mode modelling — Google Ads Help). According to About modelled online conversions — Google Ads Help, values take up to 5 days to fully stabilise and are subject to retroactive increases after the conversion date. A Monday morning report covering the prior week contains provisional Thursday-through-Sunday data that will change.

The dashboard fix is low-tech: add a visible text card reading "Google Ads Conversions include modelled data. The most recent 5 days are provisional — allow up to 5 business days for final values." This prevents managers from adjusting bids on an incomplete week and sets the correct expectation for what "final" means in a post-cookie-deprecation account.

AI Anomaly Alerts That Actually Get Acknowledged

Alert fatigue makes your alert system worthless. According to Marketing Anomaly Detection & Automated Alerts — Improvado, 40–60% of false-positive alerts trace to data pipeline failures, not campaign performance changes. Teams that investigate campaign performance before verifying the tracking pipeline waste analyst time on non-existent problems and teach themselves to ignore the system.

Configure three tiers for a 50–200 campaign account. Tier one, a data quality check: if conversions drop more than 50% vs the 7-day average while spend holds normal, route to your analytics engineer as a pipeline failure — not the campaign manager. Tier two, budget pacing: underspend below 85% of planned linear daily spend; overspend above 115%. Use day-of-week baselines — Monday front-loads spend in most accounts, Friday coasts — so a flat daily target does not generate false positives on both days. Tier three, CPA drift: trigger when the 3-day rolling CPA exceeds the 7-day baseline by 20% or more, catching creative fatigue before it compounds into an expensive week.

Require every alert to be acknowledged within 4 hours with a root-cause tag: creative fatigue, audience saturation, tracking issue, or false positive. Monitor your weekly acknowledge ratio — below 70% means your thresholds need recalibration.

Fixing the Prospecting-Retargeting ROAS Confusion

The most common cross-platform reporting error is aggregating prospecting and retargeting ROAS into one headline number. Retargeting campaigns structurally produce 6–10x ROAS because audiences already know the brand — they harvest existing demand, not build new demand. Prospecting campaigns targeting cold audiences should return 2–3x. Blending a 9x retargeting figure with a 1.8x prospecting figure produces a combined number that looks healthy while the acquisition engine is quietly failing.

According to How to Compare ROAS Across Meta, Google, and TikTok Ads — Pixis AI, Meta's default attribution window (7-day click, 1-day view) captures view-through conversions that Google Search simultaneously claims — making a direct ROAS comparison between platforms an apples-to-oranges exercise. The structural fix is to enforce the naming convention at campaign creation, report prospecting and retargeting in separate scorecard panels with separate targets, and never aggregate them for a headline metric.

Shifting the Team from Assembly to Decision-Making

Automation eliminates the 4–6 hours of weekly CSV assembly and the 5–8% calculation error rate from timezone and currency mismatches. But teams that automate delivery without protecting the narrative end up with executives who ignore the dashboard and request the old email attachment.

The automation handles data assembly: the KPI scorecard, anomaly flags, prospecting health, and retargeting efficiency views. The analyst owns one task that automation cannot do — the decision narrative. Three sentences, written weekly, answering what changed, why it changed, and what the team will do differently. According to PPC Report Automation — AgencyAnalytics, this narrative is what earns the PPC team a seat in budget allocation decisions. Automate the assembly; protect the judgment.

Hands-On Exercise: Build Your First Automated Weekly Report

Using a real or demo Google Ads account:

1. Connect the account to Looker Studio with the native connector, "Overall Account Fields."
2. Create a campaign name filter toggling between "PROSP" and "RETARG" — prefix two existing campaigns as a pilot if the naming convention is not yet enforced.
3. Blend a Google Sheets backend-revenue source with Ads spend by date; display platform ROAS and blended ROAS side by side.
4. Add a text card marking the last 5 days of conversion data as provisional.
5. Set one anomaly threshold: conversion count drop >50% with normal spend routes to a data quality check, not campaign review.

Success criteria: A non-analyst stakeholder can toggle prospecting vs retargeting ROAS, see the platform-vs-blended ROAS gap, and understand why last week's conversion count may still change — all without requesting a CSV from anyone on the team.

This is the final chapter in the course. Return to Designing a 3-4 Person PPC Analyst Team for a Data-Driven Analytics Firm to see how the team structure from Chapter 1 maps directly to the reporting stack you've built here.