Curated Landing Page
The partner runs an ad promoting an occasion or theme rather than a single product — e.g., “Mother’s Day Gift Guide”, “Summer Essentials”, “Black Friday Deals”. The buyer taps the ad and lands on a partner-branded occasion page with a curated product grid, browses, picks a product, and completes checkout.
The key difference from a single-product deal is the landing-page browsing step — the buyer sees multiple products before choosing one.
What the buyer sees
1. Ad click
The ad creative highlights the occasion (not a single product) with a CTA like “Shop Deals” or “Shop Gift Guide”. The ad links to a landing-page URL on the partner’s domain:
The promo code is auto-applied to any product the buyer eventually selects.
2. Landing page — full page
A full-page, partner-branded occasion page with the curated grid.
Header (two-part):
- Partner header — partner branding plus “Powered by Firmly” attribution. A back arrow returns to the referring page.
- Promo banner — a prominent banner below the header showing the deal (“Exclusive offer: Save 20% with code MOM20”).
Merchant identity — “Shopping with [Merchant]” with the merchant’s domain (or, for multi-merchant pages, per-product merchant identity on each card — see below).
Occasion title — a large heading identifying the event (“Mother’s Day Gift Guide”, “Summer Skincare Essentials”).
Product grid — products displayed in a two-column grid. Each product card contains:
- Product image with a discount badge overlay (“20% OFF”)
- Product name
- Brief description (1–2 lines, truncated)
- Promotional pricing — original strikethrough + discounted price
- Promo reference (“with code MOM20”)
- Shop Now button — taps through to the PDP for that product
Footer — “Discount automatically applied at checkout” notice and “Powered by Firmly” attribution.
3. PDP — full page
After the buyer taps Shop Now on a product card, the experience is identical to the single-product deal PDP — full product detail with variant selectors, quantity, key benefits, and dual CTAs.
The header back arrow returns to the landing page (not all the way to the ad source).
4. Checkout — full page
Same checkout experience as the single-product flow — express wallets, Click to Pay, standard card entry, promo auto-applied, place order. See Single-product deal → Checkout.
5. Thank-you page
Same thank-you experience — savings callout, order details, merchant links. See Single-product deal → Thank-you page.
Multi-merchant landing pages
A landing page can feature products from multiple merchants. A “Black Friday Deals” or “Mother’s Day Gifts” page is not limited to a single merchant — the partner curates across their merchant portfolio.
How it works:
- Each product on the landing page has its own product configuration (merchant URL, affiliate link, offer details)
- The grid shows products from different merchants side by side, each with live pricing fetched from its respective merchant
- When the buyer taps a product, they enter the single-product PDP → checkout flow for that merchant only
Constraint — single-merchant checkout. Each purchase is against one merchant. After the thank-you page, the buyer can return to the landing page to browse more products (potentially from a different merchant). Each purchase triggers its own affiliate conversion signal and ad conversion signal — independently per merchant.
Why: each merchant has its own cart, shipping, payment, and order system. Affiliate attribution is per-merchant by definition — each network credits per merchant, not per cart.
Differences from the single-product flow
| Aspect | Curated landing page | Single-product deal |
|---|---|---|
| Ad CTA | “Shop Deals” / “Shop Gift Guide” | “Shop Now” / “Buy Now” |
| Landing page | Occasion page with curated grid | PDP directly |
| Phases | 5 (landing-page browsing added) | 4 |
| Buyer intent | Browsing / exploring a themed deal | Ready to buy a specific product |
| Back navigation | PDP → Landing page → Ad source | PDP → Ad source |
| Multi-merchant possible | ✓ (one grid, multiple merchants) | ✗ (one product, one merchant) |
What the partner owns vs. what Firmly handles
Same ownership model as the single-product flow, with these additions for the landing page:
| Partner | Firmly | |
|---|---|---|
| Occasion/theme selection + page design direction | ✓ | — |
| Product list curation (across one or more merchants) | ✓ | — |
| Per-product offer details (promo code, discount amount, copy) | ✓ | — |
| Landing-page hero image + editorial copy | ✓ | — |
| Building the landing page from the partner’s theme | — | ✓ |
| Live merchant data fetch per product card | — | ✓ |
| Click-tracking from product card to PDP | — | ✓ |
Performance tracking
Tracking is per purchase, not per landing-page view. Each completed order triggers:
- Affiliate attribution to the specific merchant of the purchased product
- Ad conversion signals to the partner’s ad platforms — Meta CAPI, Google Ads, TikTok / Pinterest / Snap / Reddit Conversions APIs
Engagement events (page views, card clicks, PDP views, add-to-cart, checkout-start, purchase) are tracked across the entire flow and surfaced in the partner’s analytics view.
Pre-purchase disclosure
Same as the single-product flow — partner T&C + privacy and merchant T&C are displayed at checkout. See Consent & Disclosure.
Related
- Single-product deal — the simpler one-product variant
- Buyer purchase flow — full sequence
- Operations → Operational workflow — per-product setup repeats for each landing-page product
- Marketplace — for an operator aggregating many merchants in one surface