Merch5 · Products · Widget use cases
Use cases

Seven pages where a shop belongs

The widget works best where attention already is. These are the placements that actually convert — and the ones that do not, so you can skip them.

Multiple widgets per account Separate analytics for each
🔒 yourbrand.com/admin
Your CMS editor </> Embed
EMBED / CUSTOM CODE
<script src="https://merch5.com/w.js"></script> <div id="merch5" data-store="yourbrand"></div>
📈
3.1% conversionFrom the blog embed
Widgets per account
1Catalog behind all of them
Per embedAnalytics, separately
$0Per additional widget
Placements that work

Where people actually click buy

Under the content, not next to it

A shop block at the end of a long article or video page catches readers at the moment they feel something. Sidebars get ignored.

Community and about pages

People who came to read about who you are already like you. That is the cheapest merch traffic you will ever get.

Game and product pages

Fans of a game, an app or a tool convert on merch far better than cold audiences. Games →

Event and tour pages

Sell alongside the ticket, not at a table in the venue. Events →

Thank-you and success pages

The screen after a purchase or a signup is dead space. A single tee on it converts surprisingly well.

Podcast episode pages

Listeners who scroll to the show notes are the most engaged part of your audience. Podcasts →

Honest advice

What works, and what to skip

Skip these

Placements that quietly fail

  • A pop-up over the first paragraph
  • A tiny sidebar box at 200px wide
  • The pricing page of a B2B product
  • A separate "Merch" tab nobody opens
  • Anything that loads before the content
Do these

Placements that pay for themselves

  • End of long-form content
  • Community, about and team pages
  • Post-purchase and success screens
  • Event, release and launch pages
  • A permanent block in the footer of a fan site
  • A dedicated shop page with the widget full width
Run several at once

One store, many embeds, separate numbers

You can put a different widget on every page and give each one its own catalog — a limited drop in a blog post, the full range on the shop page, a single team tee on the careers page.

Each embed reports its own views, add-to-carts and revenue, so after a week you know which page deserves the placement and which one to drop.

/blog/* — limited drop, 2 items, 3.1% conversion
/shop — full catalog, 18 items, 1.4% conversion
/careers — team tee, company-paid, 41 claims
/thanks — one bestseller, 2.7% conversion

Use case questions

As many as you like, at no extra cost. Each one has its own catalog, styling and analytics inside the same account.

Yes. A visitor who adds an item on the blog and then opens the shop page keeps their cart — it is the same store underneath.

Nothing. Building the store, generating mockups and hosting are free. We charge printing and shipping out of an order only after your customer has paid for it.

We do. Each order is routed to the production partner closest to the buyer and ships with tracking to more than 100 countries. Print and delivery problems are on us, not on you.

Your margin accumulates in the dashboard and is paid out automatically every two weeks. You set the retail price, so you decide what that margin is.

Pick one page and try it for a week.

The data will tell you where the shop belongs better than any guess.