During a shopping event, raise advertising exposure only when the expected contribution and available stock justify it. Higher conversion can support a higher CPC, but a discount can shrink margin at the same time. Event traffic is not automatically profitable traffic.

Establish the event baseline

Record the event dates for the specific marketplace, the offer start and end, price, contribution per order, available inventory and replenishment lead time. Export a comparable non-event period and note differences in weekdays and campaign mix. Do not import an unsupported industry multiplier as a forecast for your product.

Create separate review views for discovery and established traffic. A brand query and a broad seasonal query can react differently, so a campaign-level average may hide a costly expansion.

Calculate the event CPC allowance

Hypothetical example: event revenue is £25 per order, contribution before ads is 35% of that revenue, and expected order CVR is 15%.

Contribution per order = £25 × 0.35 = £8.75
Break-even expected CPC = £8.75 × 0.15 = £1.3125
CPC at a 25% target ACoS = £25 × 0.15 × 0.25 = £0.9375

A 50% ACoS target would allow £1.875 CPC under the same conversion assumption, but it would exceed the 35% contribution margin. It is loss-making on this basis, not a sustainable break-even bid. Any deliberate loss budget needs its own explicit limit.

Run a lower-CVR scenario too. At 10% CVR, the same 25% target supports only £0.625 CPC. The difference shows why a hopeful event conversion forecast should not become an unchecked bid increase.

Track the settings as well as the outcomes

Amazon's bidding strategy and placement settings can change the effective bid used for an opportunity. Record the base bid and all applicable adjustments before the event. Amazon dynamic bidding guide.

Use this manual spreadsheet record:

Date	Campaign	Price	Contribution_per_order	Base_bid	Placement_setting	Spend	Clicks	Orders	Export_time
enter	enter	enter	enter	enter	enter	enter	enter	enter	enter

Track budget consumption, product eligibility, stock and delivery promises during the event. Use mature data for performance decisions; recent sales can still arrive. Amazon conversion metrics.

Use pre-agreed intervention conditions

Condition	Response to consider
Spend rises but recent conversions are incomplete	Hold performance conclusions; enforce the approved spend limit
Margin falls after a discount or fee change	Recalculate affordable CPC
Stock cover approaches replenishment lead time	Reduce exposure on constrained products
Delivery no longer meets the event need	Stop time-sensitive messaging and reassess gift queries
An unintended bid or modifier is active	Restore the intended setting and verify it

Change one bounded scope at a time so the intervention can be understood. Avoid simultaneous wholesale changes to creative, bids and targeting unless an operational failure requires them.

Close the event with a mature review

Expire temporary rules and verify the resulting settings. Re-export the full event period after its attribution window and reporting delay. Compare spend, sales, contribution after ads and stock impact with the baseline, while recording price and seasonal differences.

If contribution margin is 40% and observed ACoS is 42% on the same revenue basis, advertising exceeds contribution by two percentage points. Higher revenue alone cannot justify describing that as a profit increase.

For the underlying calculation, read target ACoS to bid. For gift-specific timing, use the Mother's and Father's Day playbook.

Related Arctavia resources

Use these supporting pages to compare Amazon PPC operating models and implementation choices.

• Amazon Ad Rejections: Check Claims, Images and Destinations
• Amazon Ads ACoS Suddenly Increased: What to Check First
• Amazon Ads ML Bid Review: Guardrails Before Aggression
• Amazon PPC Automation: Data, Decisions and Operating Controls
• Amazon PPC Automation Migration Checklist
• Amazon PPC Automation vs Agency: Which Operating Model Fits Better?