Integration Patterns
Ad Commerce integration patterns answer one question: where does the checkout UI render? Two patterns cover the vast majority of cases. For a post-click landing, the checkout UI can also be Firmly’s hosted checkout rather than one you build.
The two patterns
In-Ad Checkout
The entire checkout — address, payment, confirmation — renders inside the ad creative. No redirect.
Post-Click Landing
Click routes the viewer to a dedicated landing page where the full purchase completes.
How to pick
| If… | Pick |
|---|---|
| The ad surface supports interactive elements within the creative (social feeds, some video formats) | In-Ad Checkout |
| The ad surface is static display, audio, or connected-TV — no in-feed interaction | Post-Click Landing |
| The product detail needs richer presentation than the creative footprint allows | Post-Click Landing |
| Maximum-conversion priority | In-Ad Checkout (every redirect is a drop-off) |
How patterns relate to use cases
| Pattern | Best-fit use case |
|---|---|
| In-Ad Checkout | In-Feed Shoppable Ad |
| Post-Click Landing | Post-Click Purchase |
The shared platform
Both patterns use the same Firmly API surface — auth, cart, checkout, payment, order placement. What varies is where the UI renders and how much real estate is available for the checkout flow.
Related
- Single Product Purchase Flow — full API walkthrough applicable to both patterns
- Use Cases — which scenario is being built
- Agentic Commerce → Integration Patterns — the broader 4-phase matrix that applies across solutions