Marketplace listings and integration directories are where buyers of a larger platform discover add-ons. The listing format is fixed by the marketplace. You get a description, a few images, sometimes a video, and usually a link. An interactive demo cannot always sit inside the listing, but it can do a lot of work around it.
Short Answer
Use the listing's own fields for screenshots and copy, then link an interactive demo from wherever the listing allows a link, and on your own integration page.
- Check what each marketplace allows. Links, video and images vary.
- Build one demo per integration that shows the connected result.
- Use the demo's best steps as the listing's screenshots.
Why Listings Are Harder than They Look
You do not control the page. Each marketplace has its own image sizes, description limits and rules about links. And the buyer is mid-task in another product, deciding whether your add-on is worth connecting.
- Listing screenshots are small and often cropped.
- Descriptions are short.
- The buyer wants to know what happens after they connect.
What the Demo Should Show
An integration demo should show the result inside the buyer's workflow, not your settings page.
| Step | Show |
|---|---|
| Start | The host platform screen where the buyer works |
| Connect | The one screen where they authorize, if it is short |
| Result | Your product's output appearing where they need it |
| End card | Install link and docs |
Check that recording another company's product is allowed in that marketplace's rules before you publish.
Where to Put the Link
- The listing's website or support link field, if it allows a specific page.
- Your own integration page for that platform, with the demo embedded.
- Your help article on setting up the integration.
- Partner enablement material you share with the platform's team.
Reuse the Demo's Best Steps as Images
The demo's steps are clean screenshots with callouts. Pick the strongest ones for the listing's image slots, sized to the marketplace's requirements.
An Illustrative Worked Example
This example is hypothetical. A team builds an integration that posts invoices into a chat tool.
- They record the flow from creating an invoice to seeing it posted in a channel.
- They blur the real workspace names.
- They embed the demo on their own integration page.
- The listing's support link points to that page.
- They use two demo steps as listing images.
The Old Way Versus a Better Way
| Old way | Better way |
|---|---|
| Screenshots of your settings page | Screenshots of the result in the host platform |
| One generic product demo for all integrations | One short demo per integration |
| Listing links to your homepage | Listing links to the integration page with the demo |
| Listing images made separately | Listing images taken from the demo's best steps |
| Set and forget | Checked when either product changes |
Build the Integration Page the Listing Points To
The listing does the discovery. Your own integration page does the persuading. Give it a clear structure.
- A one-line statement of what the integration does.
- The embedded demo, near the top.
- Setup steps in text, for search and for readers who prefer text.
- Links to the help article and to install.
This page is also what you share with the platform's partner team, so they can explain the integration to their own customers.
Two Products Change, Not One
An integration demo shows two products. Either can change. When the host platform updates its interface, the demo can go stale even though you shipped nothing. Add integration demos to your release checks, and look at them when the host platform announces a redesign. See keeping demos up to date.
A 30-Day Rollout Plan
Week 1. List your marketplace listings and note what each allows. Images, video, links.
Week 2. Record one demo per integration, starting in the host platform.
Week 3. Build or update each integration page with the demo embedded.
Week 4. Update listing images and links, then add the demos to your release checks.
Questions to Ask Before You Start
Answer these before recording. They take a few minutes and prevent most rework.
- What does each marketplace allow in a listing?
- Do its rules allow showing the host platform's interface?
- Which integration page will the listing point to?
- Who checks the demo when either product changes?
- Which demo steps make good listing images?
Where Proovyt Fits (Full Disclosure)
Proovyt is an interactive demo tool, and this is our blog.
- Publish for a hosted link and an embed snippet.
- Blur and replace text on every screenshot.
- A brand kit keeps integration demos consistent with your site.
Proovyt does not export video or images in bulk yet. See the product page and pricing.
Common Mistakes
- Showing your settings page instead of the result in the host platform.
- Assuming every marketplace allows an outbound link.
- Leaving another company's real workspace data in screenshots.
- One generic demo for every integration.
The Bottom Line
The listing is a small window. Use it to send buyers to a demo that shows the connected result, on a page you control.
Frequently Asked Questions
Can I embed a demo inside a marketplace listing? Usually not. Most marketplaces control the listing format. Link to a page where the demo is embedded.
Should each integration have its own demo? Yes, if the result differs. Each one shows a different workflow.
Can I use demo steps as listing images? Yes, if they meet the marketplace's image requirements.
What about the host platform's branding in my demo? Follow that marketplace's rules for showing their product.
Where else should integration demos go? Your help center. See demos in help centers.