# Worked Message Ad brief: fictional operations workshop

**Entire scenario and all figures are fictional.** Cedarline Systems, its sender, account IDs, receipts, dates, page, and reporting rows are invented to show the decisions. `example.com` is a reserved example domain. No destination or account was checked, no message was sent, and no result was observed. This is a website-route example, so a LinkedIn Lead Gen Form and CRM form sync are not launch blockers.

## 1. Campaign and offer

| Field | Fictional answer |
|---|---|
| Brief owner and review date | Maya Chen, demand generation; 30 October 2026, America/New_York |
| Advertiser, ad account ID, owner | Cedarline Systems; simulated account `EXAMPLE-ADS-204`; Maya Chen |
| Objective | Website visits |
| Audience, geography, language, fit | US operations directors at mid-sized industrial distributors; English profile language. They own order exception workflows, the workshop topic. Audience eligibility and size are unverified in a real account. |
| Offer and terms | A free 30-minute live workshop, “Map an order exception in 30 minutes,” with a blank exception map and a completed sample. Registration requires a business email. No limited seats, performance promise, or invented customer proof. |
| Offer dates and approval | Fictional workshop: 19 November 2026, 1:00–1:30 p.m. ET. Fictional registration closes 18 November 2026, 5:00 p.m. ET. Simulated owner-approved event brief `EXAMPLE-OFFER-01`, dated 29 October 2026; no real approval. |
| Why pay for an inbox send? | The role-specific workshop asks for one clear registration. If the event details or page cannot be verified, hold the send. |
| Route and one action | Website. Register for the workshop. Success event: completed registration confirmation, not a click. |

## 2. Sender and message

| Field | Fictional answer |
|---|---|
| Sender | Alex Rivera, operations education lead at Cedarline; profile URL deliberately not supplied. No real profile or consent is asserted. |
| Sender request owner and permissions | Maya is the fictional Account Manager requester; simulated permission receipt `EXAMPLE-PERM-01`, dated 30 October 2026. Maya’s first-degree connection to Alex and Alex’s verified primary email are simulated in `EXAMPLE-SENDER-01`, not checked. |
| Business Manager and acceptance | Fictional account is Business Manager-owned; simulated BM admin/access check `EXAMPLE-BM-01` and acceptance `EXAMPLE-ACCEPT-01`, both dated 30 October 2026. A real launch requires account readback. |
| Creator | Fictional Creative Manager Jordan Lee; simulated role receipt `EXAMPLE-CREATIVE-01`, dated 30 October 2026. Creative Manager creates the ad; Account Manager requests the sender. |
| Ad name | `Cedarline | Nov 19 exception workshop | US ops` |
| Subject | `Map an order exception in 30 minutes` |
| Body | `Hi, I’m Alex at Cedarline. On November 19, we’re running a free 30-minute workshop for operations teams at industrial distributors. We’ll map one order exception from intake to resolution and share a blank map you can use with your team. If this is part of your work, you can register for the live session below.` |
| Macros and fallback | None. The same literal subject and body are the fallback. No claim of individual research. |
| Advertiser CTA | `Register` |
| Required second button | LinkedIn automatically adds `Not Interested`; it is not the advertiser CTA. Confirm both in preview. |
| In-body links, footer, banner | No in-body links, footer, or banner. |

The copy describes the session and the next step. Its date is tied to the fictional event brief, not a claim about current availability or scarcity.

## 3. Website destination

| Field | Fictional answer |
|---|---|
| Destination | `https://example.com/cedarline/exception-workshop?utm_source=linkedin&utm_medium=message_ad&utm_campaign=exception_workshop_2026_11&utm_content=ad_01` |
| Final URL and test | Simulated redirect/mobile test receipt `EXAMPLE-WEB-01`, 30 October 2026, 10:00 ET. This URL was **not** opened or verified. |
| Promise and conversion | Simulated page repeats the workshop date, time, free price, topic, sample map, and registration requirement. Confirmation event: `workshop_registration_complete`. |
| Tracking | The UTM tuple identifies this ad. Simulated analytics receipt `EXAMPLE-EVENT-01`, 30 October 2026, 10:05 ET. It does not prove a real event. |
| Mobile/accessibility/privacy | Simulated checks `EXAMPLE-QA-01`, dated 30 October 2026; require real browser readback before launch. |
| Test conversion | Simulated confirmation `EXAMPLE-CONV-01`, dated 30 October 2026; require a real test. |

Lead Gen Form ID, form preview, and form sync are **not applicable** to this website route. Website registration still needs a working path and a CRM attribution check.

## 4. Account and delivery

All entries in this table are simulated fixture receipts. They cannot clear an actual account or launch gate.

| Check | Fictional receipt |
|---|---|
| Format for website visits in account | `EXAMPLE-FORMAT-01`, 30 October 2026, 09:00 ET |
| Creator permission and sender acceptance | `EXAMPLE-CREATIVE-01` and `EXAMPLE-ACCEPT-01`, 30 October 2026 |
| English and region | US/English intended. English profile-language effect noted. EEA/Swiss opt-in rule is not applicable to this US-only audience. |
| Desktop/mobile preview, two buttons, URL | `EXAMPLE-PREVIEW-01`, 30 October 2026, 10:15 ET |
| Test message and macro fallback | `EXAMPLE-TEST-01`, 30 October 2026, 10:20 ET; literal copy only |
| Active, ad set launch, review, delivery | **Not performed.** No live receipt exists. |

**Disposition:** Copy is draftable as a fictional specimen. Account check and launch are **held** until real permissions, format availability, sender acceptance, destination tests, and preview are verified. Submission, activation, platform review and actual delivery must be observed separately at their respective lifecycle steps; actual delivery is not a prelaunch prerequisite. Do not remove sender approval to pause an ad. An edit would create a new review step and would not change already delivered messages.

## 5. Reporting calculation (fictional arithmetic fixture)

Suppose the ad had a completed run from **2–15 November 2026 ET**, with CRM follow-up through **9 December 2026 ET** and a report pulled **10 December 2026 ET**. These are invented rows for practicing the calculation, not results or benchmarks. Every native metric below is filtered to simulated account `EXAMPLE-ADS-204`, ad set `EXAMPLE-ADSET-01`, ad `EXAMPLE-AD-01`, website route, and that same send window. Spend is USD. The simulated export uses the dedicated Sponsored Messaging view’s `Clicks` column (CTA, body-link and banner clicks), not the separate eligible Sponsored Message clicks definition.

| Source and unit | Fictional observation |
|---|---:|
| LinkedIn billed sends | 1,000 |
| LinkedIn opens | 400 |
| LinkedIn Sponsored Messaging clicks (CTA, body links, and banner; same reporting column throughout) | 40 |
| LinkedIn spend | $800 |
| Website completed registrations tagged with the exact campaign/ad UTM tuple, 2–18 Nov | 10 |
| CRM unique people matched to those 10 registrations, after duplicate merge | 10 |
| CRM qualified registrations by 9 Dec under the fictional rule “operations owner, industrial distributor, attended or requested the map” | 4 |

The native send/open/click rows are one ad cohort, so open rate is **400 ÷ 1,000 = 40%**, our explicitly calculated clicks-per-send rate is **40 ÷ 1,000 = 4%** and LinkedIn click-to-open rate is **40 ÷ 400 = 10%**, and cost per send is **$800 ÷ 1,000 = $0.80**. These figures say nothing about real Message Ad performance. The ten registrations are counted by confirmation event and exact UTM tuple; ten CRM people matched after dedupe. The four qualified records are a subset of those ten. For this complete fictional fixture, registration rate is **10 ÷ 1,000 = 1%**, qualified rate is **4 ÷ 1,000 = 0.4%**, and cost per qualified registration is **$800 ÷ 4 = $200**. The denominators use the same ad and send cohort, with the stated later outcome window. Native reporting is aggregate: the table does **not** claim person-level matching of individual sends or opens to CRM people. If CRM matching, attribution, cost, or the follow-up window were incomplete, downstream rates and cost per qualified registration would be `Unknown/partial`, not zero.

Simulated reconciliation `EXAMPLE-CRM-01`, dated 10 December 2026, joins website registration ID to CRM submission ID and deduplicates people by normalized business email. It records 10/10 registrations matched, zero unmatched registrations, and completed qualification follow-up for all ten through 9 December. These are explicitly invented coverage assumptions, not real receipts. They support the fictional calculation only.

## 6. Review handoff

Fictional reviewer: Maya Chen, 30 October 2026. Revision `EXAMPLE-01`. The next real owner would replace every `EXAMPLE-*` receipt with dated account and destination evidence, check the exact account, then run the standalone review prompt. This worked brief is not a launch authorization.