Docs
Firmly Agentic Commerce
Set theme to dark (⇧+D)

Publisher sites

Publisher sites are content-first companies — editorial media, deal and coupon sites, reviews, buying guides, and vertical communities — whose primary business is generating audience attention through content and monetizing that attention. As a commerce destination, publisher sites are the highest-intent category: users arrive via a deal roundup, a product review, an editorial pick, or a buying guide, and they are typically much closer to purchase than users from organic search or generic social feeds.

Firmly is the commerce backend; the publisher owns the editorial voice and reader relationship.

​​ The commerce challenge

  • Affiliate economics are leaky — readers click out, merchants drop the cookie or de-attribute, and conversions go unreported
  • Recommendation articles produce intent; capturing the transaction inside the publisher’s surface lifts conversion meaningfully
  • Building checkout inside an editorial CMS is engineering work in a category where editorial revenue and engineering capacity are both squeezed
  • Per-merchant deals don’t scale — your editorial covers categories across hundreds of brands

​​ Which Firmly solutions apply

Publisher Commerce as the anchor; Agentic Commerce for the AI-driven editorial agent layer.

Choice Default Why
Auth Browser session per reader Each article session creates a transactional session
Integration pattern Hosted checkout or Embedded checkout Publishers split — some prefer Firmly-hosted (lightest lift), others prefer embedded inside the article surface
Protocol Direct REST Publisher CMSes typically have backend services that integrate cleanly with REST
Discovery scope Curated by editorial focus (apparel publisher → apparel merchants, etc.) Editorial relevance trumps catalog breadth

​​ Typical use cases

​​ What to think about

  • Affiliate attribution. Firmly relays the originating publisher to the merchant, so commissions and origination credit flow back deterministically — much better than third-party cookie attribution. See How Firmly Works.
  • Editorial trust posture. Pre-purchase disclosure matters in editorial contexts; readers expect transparency. See Consent & Disclosure.
  • Embedded vs hosted. Publishers with strong article-page UX prefer embedded; smaller publishers prefer hosted because it’s the lightest lift.
  • Curated merchant set. Publisher-specific catalog scope (only merchants the editorial focus has actually reviewed) is usually a configuration choice on the App ID.
  • Multi-product carts. Gift guides and category roundups generate multi-product carts naturally — see Multi-product flow.

​​ Getting started

  1. Sandbox Setup — credentials and a test merchant aligned with the publisher’s editorial focus
  2. Browser session authentication — per-reader sessions
  3. Hosted Checkout or Embedded Checkout — pick by editorial UX appetite
  4. Publisher Commerce overview — the solution-level frame