# Worked fictional Brand Lift brief: Arbor Operations

All company details, IDs, dates, budgets, native receipts, and results in this example are fictional. No real study was launched. The example demonstrates a provisional readout, not advertiser performance.

## The decision

Arbor sells workflow software to operations teams. Maya, the growth lead, prepares this record on December 6, 2026. The business question is whether its LinkedIn campaign changed product consideration among the studied audience. The intended decision is whether the current consideration message merits a further planned test. This survey cannot establish incremental purchases or revenue; those require separate evidence.

Maya prepares the record. Budget owner Jordan approves planning. Operator Lee manages the account. Analyst Sam reviews results. These names and roles are simulated.

## Study plan and simulated evidence

Account ARBOR-01; study BL-01; selected campaign ARBOR-CONSIDER-01. Standard Sponsored Content only, United States, English survey. The brand name is Arbor Operations. One product-consideration question asks how likely the respondent is to consider Arbor Operations. The simulated native question has Highly likely and Somewhat likely as desired responses; Neutral, Somewhat unlikely, and Highly unlikely are undesired. This question wording is illustrative; copy the actual available native wording into a real brief.

The benchmark selection is United States, Software. The campaign and study run November 2, 2026 at 00:00 UTC through December 1 at 23:59 UTC. Final review is December 17, after the full 15-day post-end window. Eligible planned spend is USD 65,000 across the included campaign during the study, recorded in simulated settings receipt SETTINGS-01 on November 1. The current public one-question budget minimum is USD 60,000. A simulated native eligibility receipt ELIGIBILITY-01 says eligible; Lee has campaign-manager access in ACCESS-01. No CTV or other concurrent tests are included, per simulated account inventory INVENTORY-01; a real operator must verify current restrictions and availability.

Jordan's simulated planning approval is APPROVAL-PLAN-01. Separate simulated launch approval APPROVAL-LAUNCH-01 is dated November 1 at 09:00 UTC and authorizes Lee to submit this exact study that day, with the planned November 2 start. Simulated submission receipt SUBMIT-01 records November 1 at 10:00 UTC; simulated approval receipt APPROVED-01 records November 1 at 23:00 UTC. Simulated start receipt START-01 records November 2 at 00:00 UTC. Submission, platform approval, and scheduled start are separate events. These times are fictional exercise inputs, not a promised review turnaround or authority for any real campaign change.

## Provisional readout

Sam retrieves simulated report REPORT-01 at 12:00 UTC on December 6. The scheduled test ended December 1, so the final review date has not arrived. The displayed framework is Bayesian. The report shows the product-consideration question and desired-response definition above.

| Simulated native field | Value |
| --- | --- |
| Test-group respondents | 200 |
| Test-group desired / undesired responses | 48 / 152 |
| Control-group respondents | 200 |
| Control-group desired / undesired responses | 40 / 160 |
| Displayed desired-response rates | Test 24%; control 20% |
| Displayed absolute lift | 4 percentage points |
| Displayed relative lift | 20% |
| Displayed estimated total lift | Unknown; not supplied in this example |
| Displayed lift probability | 92% |
| Displayed native status | Lift detected |
| Attribute breakdown | Not supplied |
| Benchmark result | Not supplied |
| Scope/campaign changes | None recorded in simulated change log CHANGE-01 |

The 92% probability is a fictional native-output field, not a number calculated from the raw counts. The 4-percentage-point difference and 20% relative difference illustrate units; they are not a reconstruction of LinkedIn's balancing or statistical model. In a real report, retain the exact native estimates even when simple raw arithmetic differs.

Sam records: the supplied native report indicates positive product-consideration lift, but the readout is provisional because the 15-day post-end window is still open. It does not establish sales, qualified leads, or revenue. The absence of an estimated-total-lift value, breakdown, or benchmark does not justify inventing those fields.

Next action: Sam retrieves a fresh native report on December 17 and checks the status, estimates, scope, and available evidence again. Jordan will review the resulting recommendation before approving any new spend. There is no final result in this example and no automatic budget increase.

## Evidence index

All named receipts above are simulated descriptions inside this exercise, not attached native files. A real reader must replace each with their own inspectable evidence. Public rules come from LinkedIn's current creation, results, metric-definition, and methodology Help pages, captured October 30, 2026 in the research ledger. Do not treat a fictional receipt name as proof about a live account.