# Completed fictional bid decision: Rivet Analytics

This is an invented B2B software example. No account was inspected and no campaign was changed. Dates, figures, and availability are scenario inputs, not recommended thresholds or observed results.

## 1. Define the result

Organization: Rivet Analytics. Decision owner: paid acquisition lead. Review date: 30 October 2026.
Campaign/ad set: fictional Demo Lead / operations audience. Currency: USD.
Objective: Leads. Conversion location: website. Performance goal: maximize conversions. Optimization event: Lead, triggered after a completed demo-request form.
Current strategy: Highest volume, no entered cost goal.
Available controls: scenario assumes a dated operator screenshot shows Cost per result goal available for this exact configuration. This does not establish availability for the reader.
Reporting: 1–14 October, impression-date basis, 7-day click attribution held fixed. Platform export retrieved 23 October. CRM outcomes joined to the same 100 distinct submitted leads and reviewed 28 October. Scenario assumes qualification is complete for this cohort.
Event evidence: scenario assumes submitted forms reconcile to CRM records; no known delivery defect. Actual production evidence would need to be attached privately.

## 2. Separate constraints

The business requires $30 per platform Lead and will consider lower volume to pursue it. That target is a requirement, not an observed cost. The existing observed cost is $40.
No independently justified auction-bid ceiling is supplied. No purchase value or value-optimization eligibility is supplied. A ROAS goal has no supported basis in this record.
The owner has not approved a test budget, loss limit, or change window. These remain Unknown.

## 3. Record the baseline

Spend: $4,000. Platform Leads: 100. Qualified meetings from those same leads: 20.
Cost per platform Lead = $4,000 / 100 = $40.
Cost per qualified meeting = $4,000 / 20 = $200.
Qualified share = 20 / 100 = 20% for this fictional mature cohort.

Do not enter $200 in a Lead cost goal to target $200 qualified meetings. The field controls the average cost of the selected platform result. Do not assume that changing the goal preserves the 20% qualified share.
The desired $30 Lead cost is 25% below the observed $40. That describes the gap; it is not a forecast of savings or a validated setting.

## 4. Choose a candidate

Candidate: review Cost per result goal because the requested constraint is average cost per platform Lead and the owner accepts potential underdelivery.
Availability: assumed present only within this fictional scenario.
Highest volume remains the prior configuration. Bid cap controls a different quantity and would not guarantee maximum reported Lead cost. Value controls lack evidence here.
Tradeoff: a restrictive cost goal may reduce spend and results without delivering the desired business cost. Track qualified meetings separately.

## 5. Prepare one change

Change readiness: HOLD.
Proposed variable: bid strategy / cost goal for the stated Lead event. Exact entered amount: awaiting owner decision; $30 remains the business requirement.
Fixed variables: audience, creative, placements, event, attribution settings, reporting date basis, and budget configuration would need an agreed snapshot.
Unresolved: approved test spend, precise loss-limit formula, observation dates, final review allowing conversion/CRM lag, stop/revert rule, and operator approval.
Previous setting: Highest volume without an entered goal.
Next action: acquisition lead submits the candidate and baseline to the owner, asks for those test conditions, and attaches actual eligibility and measurement evidence. No live change follows from this worksheet.

## 6. Review the result

No test has occurred. Actual test spend, results, quality, and final decision remain Unknown. The completed decision is a concrete candidate with a held change, not a successful experiment.

## Sources and terminology

Mechanics checked 30 October 2026 UTC:
- https://developers.facebook.com/documentation/ads-commerce/marketing-api/bidding/overview/bid-strategy
- https://developers.facebook.com/documentation/ads-commerce/marketing-api/bidding/overview/pacing-and-scheduling
- https://www.jonloomer.com/bid-strategies-best-practices-for-meta-advertising/

Cost per result goal is the familiar interface label for the cost-cap mechanism. Exact labels and availability must be checked in the reader's configuration. The review sequence is Maestro editorial guidance, not a Meta eligibility requirement.