Choose and launch a LinkedIn Thought Leader Ad
Completed example: Cedarfield
Cedarfield is a fictional software company that helps B2B marketing teams route demo requests to the right sales representative. All names, posts, budgets and review numbers below are invented to demonstrate the worksheet. They are not benchmarks or campaign results.
1. Define the job
- Buyer: revenue operations leaders at US software companies with 100–500 employees and more than one sales territory.
- Problem: a demo request can reach the CRM without reaching the person responsible for following up.
- Ad's job: get these buyers to check their own routing process using a one-page checklist.
- Next step: visit the checklist page and use it. A meeting request is an optional later action.
- Evidence we can show: a test form submission, its CRM record, the ownership rule, and the assigned representative. Use a demonstration account without customer data.
- Evidence we do not have: a measured revenue increase or a reliable industry average for response times.
2. Compare three posts
Candidate A: CEO funding announcement.
“We raised our next round. Thank you to the customers, team and investors who made this possible. We’re hiring across engineering and sales, and I can’t wait to show you what comes next.”
This may interest employees, investors and applicants. It gives our buyer no routing problem to investigate and no checklist to use. The CEO's title does not make the post a match for this campaign. Do not sponsor it for this job.
Candidate B: implementation lead's routing demonstration.
“Your demo form can work perfectly while the request still goes nowhere. Submit one test request with a company name your sales team will recognize. Open its CRM record. Can you name the person who owns the next action? Now change the country and submit again. If the owner stays the same when the territory should change, check the routing rule before buying more traffic. I put the five checks we use in this one-page worksheet.”
The author does this work, the reader can repeat the test, and the worksheet continues the same task. A screen recording can show the test record and owner changing. Select this post, subject to the actual recording, public-post eligibility and sponsorship approval.
Candidate C: founder's response-time claim.
“Our customers doubled their pipeline by replying to every lead in five minutes. Speed wins. Book a demo and we’ll show you how.”
The claim sounds relevant, but we have no study, customer permission or campaign evidence supporting it. Do not sponsor it or quietly convert the number into a vague success claim. Ask the author for the source or write a different post based on the routing demonstration.
3. Prepare the selected post
| Field | Completed choice |
|---|---|
| Author | Maya, Cedarfield's fictional implementation lead |
| Why this person | She builds and tests the routing workflow she explains |
| Post | Candidate B, revised and approved by Maya |
| Original post URL | Not published in this fictional example; required before launch |
| Media | A 35-second demonstration in a test account; duration is an editorial choice |
| Opening image | Test request beside the CRM record with no owner; label the test data |
| Demonstration | Open the ownership rule, change country, submit again, show correct owner |
| Spoken explanation | Explain which field changed and why that should select a different representative |
| Closing action | “Use the five-check routing worksheet before your next campaign.” |
| URL | Your own published checklist page; confirm it works before the post goes live |
| Link tracking | Add campaign-specific UTM values to the link before publication; record the exact URL |
| Proof owner | Maya confirms the recording represents the workflow accurately |
| Author approval | Pending; written agreement on the post and LinkedIn sponsorship approval are separate steps |
| Comment owner | Marketing lead; route product questions to Maya |
4. Set a contained test
Use the current LinkedIn help links below to check the format and permissions. For this fictional video test, choose the video format and the engagement objective. Video views is also supported for video, but it would optimize for a different immediate action. A compatible objective does not guarantee checklist visits.
- Audience: the buyer described above. Inspect the available audience settings and forecast before launch; do not claim perfect reach to every named person.
- Placement: record whether LinkedIn Audience Network is enabled and keep placement differences in the review.
- Budget: $600 total over ten days, with no automatic extension. This is a made-up planning limit, not a recommended minimum.
- Measurement: a download is a web analytics event. Worksheet use means completing the test submission and checking the CRM owner; ask readers whether they did that and what they found. Treat replies as self-reported use. No such responses are supplied in the illustrative review below.
- Comparison: the company's own previous checklist campaign, only if audience, period, objective and metric definitions are sufficiently comparable. Otherwise this is an initial learning test.
- Launch checks: actual public post URL recorded; author approved; correct Page and account access; eligible post/media; correct audience and spend limit; working destination; tracking verified; comment owner assigned.
- Stop early if: wrong audience settings, broken destination, permission revoked, factual mistake, or spend outside the approved limit.
- Review date: the day after the ten-day test. Allow later sales outcomes their normal lag; record the follow-up date separately.
Agree on the decision before spending
For this fictional test, Maya and the marketing lead agree to these rules:
- Continue with a separately approved test if relevant buyers use the checklist, buyer conversations confirm it helps with routing, and measurement checks support the interpretation.
- Revise the next post if relevant buyers repeatedly ask for a missing explanation, such as which rule wins when territory and named-account ownership disagree.
- Stop delivery for the early-stop conditions above. At the spend limit, do not extend the campaign automatically.
- Collect more evidence if checklist use, buyer fit or tracking cannot be established. Downloads alone do not prove that someone used the checklist.
These rules are qualitative because this example has no validated customer economics or baseline. A real team should add its own minimum evidence and economic limits before launch.
Keep unresolved launch details visible
| Required field | Status and owner in this example |
|---|---|
| Ad account, Page and permissions | Unknown; marketing lead confirms access |
| Exact public post URL | Not published; Maya supplies it after approving copy and recording |
| Sponsorship approval | Pending; marketing lead requests it and Maya approves in LinkedIn |
| Format and objective | Video and engagement, subject to current eligibility |
| Exact tracked checklist URL and test | Not supplied; marketing lead publishes and tests it before launch |
| Placement selection | Not decided; marketing lead records it after reviewing the setup |
| Calendar start/end, daily setting | Not set; budget owner approves dates and pacing within the $600 limit |
| Review and sales follow-up dates | Review one day after delivery ends; sales lead sets the later follow-up date |
| Launch decision | Hold until the required recording, URL, access, approval and dates are confirmed |
5. Read the result without changing the question
This is a separate hypothetical later scenario: assume the recording, URLs, permissions, approval and dates above were resolved before delivery. The unresolved planning table is not evidence that a real campaign launched.
Reporting scope for this fictional review
| Source | Window and definition | Limit |
|---|---|---|
| Campaign Manager | Ten-day test, October 1–10, 2026; ad-account reporting timezone America/New_York; spend in USD, paid impressions and clicks specifically to the landing page | Totals include LinkedIn Audience Network in this scenario; inspect placement rows before comparing with the author view |
| Web analytics | October 1–10 in the same timezone; sessions carrying this campaign's UTM values; all checklist download events recorded sitewide | The download events have not been linked to the tagged sessions; counts are not unique people or proof of worksheet completion |
| CRM | Three demo requests created October 1–10; one marked sales-qualified as of October 11; no closed revenue as of that date | These are company-wide records in the window. No campaign match or attribution method has been supplied |
| Author post analytics | Snapshot on October 11; lifetime combined organic and paid impressions for the post | Different scope from the campaign window, and excludes Audience Network; not a paid denominator |
| Comments | Comments reviewed through October 11; relevant questions identified by the marketing lead | Buyer roles still need checking; comments are not a count of qualified leads |
The numbers below are invented observations within that scenario, not results to expect from a $600 budget.
| Observation | What it supports | Next action |
|---|---|---|
| $580 spent; 40,000 paid impressions in Campaign Manager | The campaign delivered; CPM = $580 / 40,000 × 1,000 = $14.50 | Check audience/placement reporting before judging reach quality |
| 120 paid landing-page clicks | Cost per landing-page click = $580 / 120 = $4.83 | Use this exact click definition; do not substitute all clicks |
| 78 tagged landing sessions; 9 sitewide checklist download events in web analytics | Both counts occurred in the test window; no supplied record links the downloads to those sessions | Check event-to-session linkage before reporting a campaign download rate; check tagging, consent and page load when comparing clicks with sessions |
| 3 demo requests, 1 sales-qualified conversation, no closed revenue yet | Company-wide actions recorded in the same window; no campaign match established | Read the actual conversations and match campaign data to CRM records before assigning credit |
| Author's post reports 51,000 combined impressions | The author view mixes paid and organic distribution | Keep it out of the paid CPM denominator; it also excludes Audience Network metrics |
| Comments ask which owner wins when a named account belongs to one representative but its country maps to another | The country-change demo did not explain conflicting rules | Check the commenters’ buyer fit and whether the question recurs. If it does, ask Maya to demonstrate which rule wins for one conflicting test record |
Decision: collect more evidence before funding another test. Investigate measurement differences and review the qualified conversation to establish buyer fit and checklist use. The original video already shows a country change. Check who asked about conflicting ownership rules and whether the question recurs among relevant buyers. If that meets the agreed revision rule, propose a separate demonstration of a named-account owner conflicting with the territory rule. Otherwise keep it as a question to investigate. Keep actual worksheet use unknown until readers supply evidence. Do not label this a profitable campaign from clicks or one conversation. A second test needs its own approved budget and a stated change.
Make your own copy
Use the blank worksheet beside this file. Keep the full source post and decision notes so another person can understand why you chose it. A checklist is finished when the required facts are present, not when every empty box has a plausible guess.
Current platform references, checked September 23, 2026: