Docs

Two lines of HTML and you are showing cards. This page covers the install, where to put the card, how views are counted, and what to tell your own visitors.

Install

The snippet has two parts: a div that marks where the card goes, and one script tag. Replace PUBLIC_KEY with your product's key. It starts with pk_, and the Install step in your dashboard shows the snippet with your key already filled in.

The min-height on the div holds the card's space open while it loads, so nothing on your page jumps. It is 64px for a row, 140px for a card and 32px for a pill.

Plain HTML

Paste both lines where the card should appear.

HTML
<div data-pluggyback-slot="main" data-format="row" style="min-height:64px"></div>
<script async src="https://pluggyback.com/card.js" data-key="PUBLIC_KEY"></script>

Next.js

Make one small component and render it wherever you want the card. It works in server and client components alike.

pluggyback-card.tsx
import Script from "next/script";

export function PluggybackCard() {
  return (
    <>
      <div data-pluggyback-slot="main" data-format="row" style={{ minHeight: 64 }} />
      <Script async src="https://pluggyback.com/card.js" data-key="PUBLIC_KEY" />
    </>
  );
}

React

Put the script tag in your index.html, once, just before </body>:

index.html
<script async src="https://pluggyback.com/card.js" data-key="PUBLIC_KEY"></script>

Then render the slot in any component:

PluggybackCard.jsx
export function PluggybackCard() {
  return <div data-pluggyback-slot="main" data-format="row" style={{ minHeight: 64 }} />;
}

If your site has a content security policy

Allow https://pluggyback.com for scripts, connections and images, or the browser will block the card. Add it to the three directives you already have:

Content-Security-Policy
script-src https://pluggyback.com;
connect-src https://pluggyback.com;
img-src https://pluggyback.com;

Options

Everything is set with attributes on the div. Only the first two are needed, plus the min-height that goes with the format.

data-pluggyback-slotAny short name
Names the slot. The default is "main". Give each extra slot its own name.
data-formatrow, card, pill
The shape of the card. See placement below.
data-themelight, dark, auto
Optional. The default, auto, follows your page.
data-radiusA number of pixels
Optional. Corner radius, to match your own boxes.
data-fontinherit
Optional. Makes the card use your site's font.

A second slot, as a dark card with squarer corners and your own font:

HTML
<div
  data-pluggyback-slot="sidebar"
  data-format="card"
  data-theme="dark"
  data-radius="4"
  data-font="inherit"
  style="min-height:140px"
></div>

Verify your site

We need to know the site is yours before your product goes to review. Any one of these does it.

  1. Install the snippet. When we find the script with your key on your home page, the domain is verified. Most members never do anything else.
  2. Add a meta tag to the <head> of your home page.
  3. Add a DNS TXT record on your domain.
Meta tag
<meta name="pluggyback-verify" content="TOKEN">
DNS TXT record, value
pluggyback-verify=TOKEN

Your dashboard shows your real token in place of TOKEN. Cards are only served on the domain you verified, so a snippet copied to someone else's site shows nothing.

Placement

Put the card where a visitor has just finished something: read a post, got a result, completed a task. That is where people are open to seeing what else exists.

Row64 px tall, as wide as its container
A dashboard, under a result, between two sections. Reserve it with min-height:64px.
CardAbout 300 by 140 px
A sidebar, the end of a blog post, the screen after a finished action. Reserve it with min-height:140px.
Pill32 px tall, one line
A footer. Reserve it with min-height:32px.
  • The slot must sit where real visitors can see it. Hidden, stacked, tiny or transparent slots earn nothing.
  • Keep the min-height from the snippet. It reserves the card's height, so your page does not jump.
  • One card per slot per page load. It does not rotate while it is on screen.
  • Do not ask visitors to click, and do not click your own cards.

Want paying customers to see no cards? Do not render the slot for them. In React that is one condition:

JSX
{user.isPaying ? null : (
  <div data-pluggyback-slot="main" data-format="row" style={{ minHeight: 64 }} />
)}

Counting rules

A view earns the site that showed it 1 credit and costs the member whose card it was 2. So what counts as a view matters, and these are all the rules.

  • Half the card, one second. At least half of the card must be on screen for one full second, in a tab that is open and visible.
  • Once a day. One view per visitor, per product, per day. A day is a UTC day.
  • Ten per visitor. At most 10 counted views per visitor on one site in a day.
  • Three slots a page. At most 3 slots count on one page.
  • People only. Bots, crawlers, link previews and automated browsers are never counted.
  • Your domain only. Views count on the domain you verified, and nowhere else.
  • Clicks are free. They are counted and reported, and cost no credits.

Earned credits show as pending first. They become spendable 24 hours after the day they were earned on has closed. If a site's numbers look wrong, its pending credits are put on hold until a person has looked. The member is told what looked unusual and can reply.

Wording for your privacy page

The card sets no cookies and stores nothing in the browser. You are still showing third-party content, so tell your visitors. Paste this into your own privacy page and edit it to fit. We are makers, not lawyers: if your site needs legal sign-off, get it from someone qualified.

Paste into your privacy page
This site shows small promoted cards for other independent software products through Pluggyback (pluggyback.com). To show a card and count that it was seen, Pluggyback receives your IP address and browser type. It uses them for a moment to make an anonymous code that changes every day, then discards them. Pluggyback sets no cookies, stores nothing on your device, and keeps no profile of you. It only keeps daily totals of how many cards were seen and clicked.

What we do with data, in full, is on our privacy page.

Coding agents

A coding agent can do the whole setup for you: list your product, add the card and check your site, with one key and our MCP server. The agent guide shows how to connect it.

For the install alone, give it your snippet from the dashboard and tell it where the card should go. For background, point it at pluggyback.com/llms.txt: the whole product in plain text, with nothing to scrape.

Questions

The card is not showing. What now?

Nothing shows until your product is approved, so a new install looks empty to visitors. That is expected. To check the install itself, run Check my site from your dashboard. When something is off it names the exact reason: script missing, wrong key, different domain, or our fetch was blocked.

A slot also stays empty when there is nothing suitable to show. It collapses rather than showing a gap.

Can I have more than one slot?

Yes. Add another div with a different slot name. The script tag only goes on the page once. Up to 3 slots count on one page; any more still show cards but earn nothing.

Can I hide cards from paying customers?

Yes. Just do not render the slot for them. There is an example under Placement.

Can I restyle the card?

Light or dark, corner radius, and your own font. Nothing else. Cards stay recognisable everywhere, and nobody can dress one up as their own content.

What happens if Pluggyback is down?

The slot collapses to nothing. No error, no broken layout, no waiting: the script loads async.

Do clicks cost credits?

No. Only views cost credits. Clicks are counted and shown to you, and they are free.

How do I stop?

Remove the snippet. That is enough to stop showing cards. You can also pause showing or being shown from your dashboard, and your credits stay on your account.