Before you start
- Campaign Manager access with the data you'll be reporting on
- Offline conversion uploads working (MQL/SQL/Closed-Won flowing back from CRM)
- Clear stakeholder audience identified - CMO, CFO, board deck require different reports
- Reporting tool of choice: Looker Studio, HubSpot dashboards, Sheets, or PowerPoint
- 30 days minimum of campaign data - reports built on shorter windows mislead
The playbook
8 steps
Pick the audience first - the report depends on it
Three common stakeholder audiences, three different reports. (1) Marketing leadership (CMO/VP Marketing): wants channel mix, format performance, audience insights, optimization roadmap. (2) Revenue leadership (CRO/CFO): wants pipeline contribution, CAC, payback period - barely cares about CPL. (3) Board/exec deck: 2-3 slides max, headline pipeline number + trend direction + one strategic narrative. Don't try to serve all three with one report.
Expected outcome
Stakeholder audience defined; report scope matched to what they care about.
Lead with the pipeline number, not the spend number
First slide/section answers: 'How much pipeline did LinkedIn contribute this period?'. Not 'how much did we spend' (that's table stakes), not 'what was CPL' (too tactical for stakeholder reports). Pipeline contribution = sum of pipeline value attributed to LinkedIn-sourced opportunities in the period. If you don't have that number, get offline conversions flowing from your CRM before building the report - the report doesn't work without it.
Expected outcome
Report opens with pipeline contribution; spend and CPL appear as supporting context, not headline.
Build the standard 6-section structure
Section 1: Executive summary (1 page - pipeline contribution, spend, trend direction, 1 sentence on what changed). Section 2: Spend by campaign + objective (where money went). Section 3: Performance metrics (CTR, CPL, Cost per SQL, Conversion Rate - with comparison to previous period). Section 4: Audience insights (which job functions / seniorities / industries converted best). Section 5: Creative insights (which formats / variants drove the numbers). Section 6: Next-period actions (3-5 specific changes you're making, with rationale).
# 6-section template: 1. Executive summary (1 slide) 2. Spend allocation (1 slide) 3. Performance metrics + trend (2 slides) 4. Audience insights (1 slide) 5. Creative insights (1 slide) 6. Next-period actions (1 slide) Total: 7-8 slides for monthly reviewExpected outcome
Report follows a consistent 6-section structure stakeholders learn to navigate.
Cite Cost per SQL, not Cost per Lead, as the primary efficiency metric
CPL is what Campaign Manager shows by default. CPSQL is what determines whether LinkedIn is working. Most accounts have a 3-5x ratio between the two - $80 CPL with 25% SQL conversion = $320 CPSQL. Some accounts have a 10x+ ratio (broad audience, lots of form fills, low SQL conversion). Reporting CPL alone hides that gap. Always show both, with CPSQL as the headline efficiency metric.
TipWhen CPL is good and CPSQL is bad, the fix is audience tightening, not bidding adjustments. When CPL is bad and CPSQL is good, the fix is creative improvement, not audience changes. The pair of metrics tells you what to do.Expected outcome
CPSQL is the headline efficiency metric; CPL is shown alongside for context.
Add the comparison column, always
Every metric in the report shows current period + previous period + % change. 'CPL: $85' is noise. 'CPL: $85 (vs $112 prev period, -24%)' is signal. The comparison column is what turns a report from a data dump into a decision-input. Use red/green color coding for direction (green = improving = lower CPL/CPSQL or higher conversion rate).
Expected outcome
Every key metric shows a period-over-period comparison; trend direction visually obvious.
Include one audience-insight visualization per report
Pull Campaign Manager → Breakdown by Member Demographics → Job Function (or Seniority, or Industry). The chart that consistently lands with stakeholders: 'CPL and SQL conversion rate by Seniority' - shows which seniority levels are most efficient. Most CMOs have intuition about which seniorities matter; the data confirms or challenges that intuition. High-engagement, easy to discuss.
Expected outcome
One demographic breakdown chart per report; sparks productive discussion in review meetings.
End with 3-5 next-period actions, not 20
The 'recommendations' section is where most LinkedIn reports go wrong - they list 15-20 small optimizations. Stakeholders read the top 3 and ignore the rest. Limit to 3-5 specific actions: (1) what you're doing, (2) why (cite the data point), (3) what you expect to change. 'Reallocating $3k/mo from Campaign B (CPSQL $580) to Campaign C (CPSQL $290) - expecting blended CPSQL to drop ~$80 next month' is a usable recommendation. 'Continue to optimize creative' is not.
Expected outcome
3-5 specific, data-cited actions with expected impact; no generic recommendations.
Distribute and archive
Email the report (PDF or shareable link) to stakeholders on a consistent monthly cadence - same day of month, same time. Archive every report in a shared folder so trends are reviewable quarter-over-quarter. Reports that come at inconsistent times get less attention than reports that show up on a rhythm.
Expected outcome
Report distributed on consistent monthly cadence; archive folder maintained.
Shuttergen
Reports need creative-insights sections worth writing.
The 'creative insights' section is where most LinkedIn reports go thin - one or two variants, no real story. Shuttergen generates 8-12 thought-leader-style variants per campaign so the section has real performance comparisons to report on.
Pitfalls
What goes wrong
Leading with spend instead of pipeline
Spend is what marketing controls; pipeline is what stakeholders care about. Open with pipeline contribution; show spend as supporting context.
Reporting CPL only
CPL hides the audience-quality gap. A $40 CPL with 5% SQL conversion is worse than a $120 CPL with 30% SQL conversion. Always show CPSQL alongside CPL.
Missing comparison columns
Numbers without comparison are noise. Every key metric needs current period + previous period + % change. Color-coded direction makes it scannable.
Too many recommendations
Listing 15-20 optimizations buries the important ones. Limit to 3-5 specific, data-cited actions with expected impact. Stakeholders read top 3 and ignore the rest.
Inconsistent reporting cadence
Reports that arrive on random days get ignored. Same day of month, same time, every month - builds the stakeholder habit of opening the report.
Limits
When this playbook won't work
- Accounts without offline conversion uploads - CPSQL can't be reported, the framework breaks down
- Sub-30-day reporting windows - metrics fluctuate too much to be informative period-over-period
- Accounts running fewer than 2-3 campaigns - the 'audience insights' and 'creative insights' sections have nothing to compare
What stakeholders actually want from a LinkedIn ads report
They want to know if LinkedIn is working - in their language. Marketers say 'CPL improved 18%'. Stakeholders hear: 'Is this generating pipeline at a CAC we can sustain?' These are different questions. The report has to answer the stakeholder version, with marketing-language supporting detail underneath for anyone who wants to drill in.
They want a trend line, not a snapshot. Single-period reports get read once and forgotten. Reports that show this period vs last period vs trailing 3-month average get used for decisions. The comparison column is what turns a report into a decision tool.
They want to know what's next. A report without specific next-period actions reads as 'we'll keep doing what we're doing'. 3-5 specific, data-cited actions with expected impact is what gets the report into the CFO's monthly review rotation.
Reports need creative-insights sections worth writing. The 'creative insights' section is where most LinkedIn reports go thin - one or two variants, no real story. Shuttergen generates 8-12 thought-leader-style variants per campaign so the section has real performance comparisons to report on.
The CPL trap and how CPSQL fixes it
Most LinkedIn underperformance hides inside the CPL-to-CPSQL gap. A campaign reports $60 CPL - looks great. Sales tells you the leads are garbage and the SQL conversion rate is 4%. Real efficiency: $1,500 CPSQL. Another campaign reports $180 CPL - looks bad. Sales tells you those leads close at 35%. Real efficiency: $515 CPSQL. The 'underperforming' campaign by CPL is actually the winner.
Reporting CPL alone gives you wrong optimization signals. You'll defund the $180 CPL campaign (better source of pipeline) and pour budget into the $60 CPL campaign (cheaper noise). This is why offline conversion uploads aren't optional - they're what makes the report's primary efficiency metric meaningful.
The fix is structural. Get offline conversions (MQL, SQL, Closed-Won) flowing from your CRM into Campaign Manager weekly. Add a Cost per SQL column to every report view. Make CPSQL the headline efficiency metric. Keep CPL alongside for context but stop letting it drive decisions.
Internal: linkedin-ads-reporting, linkedin-ads-dashboard, linkedin-ads-performance-dashboard.
FAQ
Frequently asked
What should a LinkedIn ads report include?
What metrics should I report on for LinkedIn ads?
How often should I send LinkedIn ad reports?
Should I report CPL or Cost per SQL?
How do I show pipeline contribution from LinkedIn?
Looker Studio or PowerPoint for LinkedIn ad reports?
How many recommendations should I include in a LinkedIn ad report?
Related
Keep reading
Resource
Linkedin ads reporting
Reporting workflow and cadence.
Resource
Linkedin ads dashboard
Dashboard the report is built from.
Resource
Linkedin ads performance dashboard
Performance-focused dashboard layer.
Resource
Linkedin ads budget
Budget context for report recommendations.
Resource
Hubspot linkedin ads integration
Pipe CRM data back for CPSQL reporting.
Reports need creative-insights sections worth writing.
The 'creative insights' section is where most LinkedIn reports go thin - one or two variants, no real story. Shuttergen generates 8-12 thought-leader-style variants per campaign so the section has real performance comparisons to report on.