Operations
Operations covers the post-launch work — getting a working sandbox, handling errors and edge cases, and the production launch checklist. Most operational mechanics are shared across solutions; this section calls out Ad Commerce specifics.
What’s in operations
- Sandbox Setup — get a sandbox App ID paired with a test merchant; verify the ad creative + checkout flow end-to-end before pointing it at live ad traffic.
Operational mechanics shared with all solutions
Most operational concerns are universal across Firmly solutions. For these, see the canonical references:
| Topic | Where to read |
|---|---|
| Authentication patterns | Authentication |
| Error catalog and retry behavior | Errors & Conventions |
| Idempotency window | Errors & Conventions → Idempotency |
| Rate limits | Rate Limits |
| Production launch process | Going Live |
Ad Commerce-specific operational concerns
| Concern | Detail |
|---|---|
| Ad platform postback reliability | Fire conversion postback (Meta CAPI, Google Ads Conversion, TikTok Events) after complete-order succeeds. Retry on 5xx/timeouts with backoff; on a 4xx, log and alert (a retry won’t succeed). These failures should not affect viewer experience but do affect the campaign’s optimization model |
| Click-ID drift | A click-ID from one ad campaign should not leak into another viewer’s session. Use cart-session-scoped persistence, not global state |
| Inventory pre-checks for limited stock | Ad campaigns can drive concurrent traffic spikes. If you’re advertising a limited-stock SKU, surface “out of stock” in the creative if a pre-check fails — better than letting the viewer reach complete-order and getting NotEnoughStockError (409) |
| Creative inspection by ad platforms | Some ad platforms inspect creative behavior. Make sure all Firmly API calls fire on viewer interaction, not on impression render |
Related
- Single Product Purchase Flow
- For Destinations → Going Live — the production launch checklist
- Errors & Conventions — error catalog and retry patterns