Branded Commerce FAQ
For cross-cutting questions, see the General FAQ and Technical FAQ.
Setup and scope
Do I need to write any code for Branded Commerce?
No. Branded Commerce pages are Firmly-hosted under the partner’s own domain via DNS — the partner adds two CNAME records (production + staging), provides brand assets and ad-platform credentials, and that’s it. Firmly’s edge serves the pages; the partner doesn’t ship code. See Integration Patterns.
What environments do I get?
Both production and staging, from day one. Each is an independent enrollment in Cloudflare for SaaS with its own CNAME and its own TLS certificate. Staging stays in place permanently for pre-production testing of new themes and campaigns — there’s no “promote staging to production” path. See Partner onboarding.
Who does what during onboarding?
The partner provides DNS records, brand assets, ad-platform credentials, and legal copy. Firmly applies theming, provisions TLS, configures the merchant adapters, sets up affiliate routing, and stands up the staging environment. The full split is documented in Branded Commerce → Who does what.
Do I take on PCI scope?
No. Payment data is captured by Firmly’s checkout component and tokenized via the merchant’s PSP. The partner doesn’t see card data, store it, or transmit it. PCI scope is entirely on Firmly’s side.
Theming and brand identity
What is “Powered by Firmly” and is it required?
A small attribution mark Firmly places on every partner-branded page (PDP, landing page, checkout, thank-you). It acknowledges Firmly as the commerce engine behind the experience while the partner’s brand remains the dominant identity. The buyer sees the partner’s logo, colors, fonts, and domain throughout — the “Powered by Firmly” mark is small and unobtrusive.
The mark is part of the standard Branded Commerce arrangement and is enabled by default. Whether it can be removed or customized is a commercial matter — discuss it with Firmly during onboarding.
Can I A/B test the theme?
Partner-side A/B testing of themes is handled today by Firmly ops (manual configuration of two theme variants and traffic splitting). Self-service A/B testing is on the roadmap. Discuss your specific A/B needs with Firmly during onboarding.
Can I run multiple brand properties under one Firmly account?
Yes. Per-property theming is supported — one onboarding can produce multiple theme variants (e.g., several deal sites under one parent organization). Each property gets its own theme; the same merchant set can be reachable across all of them. See Partner onboarding → Per-property theming.
Multi-merchant landing pages
Can a landing page span multiple merchants?
Yes — a curated landing page can feature products from multiple merchants in the same grid. Each card shows live pricing from its respective merchant. When the buyer clicks a product, they enter the single-product PDP → checkout flow for that merchant only.
Performance tracking and attribution
What’s the ROAS tracking story when the buyer clicks “Visit Merchant”?
There’s a known limitation:
| Buy on Firmly | Visit Merchant | |
|---|---|---|
| Affiliate commission | Tracked | Tracked (affiliate redirect) |
| Ad ROAS | Tracked (Firmly fires pixel) | Not tracked — Firmly does not control the merchant’s pages |
ROAS tracking covers Firmly-hosted conversions only. Affiliate commission is tracked regardless of path. See Operations → Performance tracking.