Burnpedia Image Save Button Analytics

Burnpedia Image Save Button Analytics is not affiliated with, endorsed by or
sponsored by Pinterest, Inc. Pinterest is their trademark, named here only to
say where the button saves to.

A reader is looking at a photograph in your post and would happily save it to
Pinterest. Most of the time nothing on the page invites them to, so they scroll
on.

This plugin puts a small save button on the images in your posts. It is an
image hover button: point at a picture and it fades in, press it and Pinterest’s
own save window opens with your image, your headline and a link back to the post
already filled in. On a phone, where there is nothing to hover, it is simply
always there.

It also counts the presses, so you can see which of your images readers
choose to save. Every press is recorded here, on your own site, in your own
database, and shown to you as a plain table — this post, this many saves, this
month and all time.

What you get

• A save button on every content image — on hover on a desktop, always
  visible on a phone or a tablet.
• A private count of every press, per post, for the last 30 days and for all
  time, with a 30-day trend line.
• The right file gets saved. WordPress serves several sizes of every image;
  the button always hands over the largest one, not the small copy a phone
  happened to download.
• Your headline and your link, already in the save window. The description
  comes from the image’s own alt text, so it is the one you wrote.
• It stays out of the way — it never appears on icons, avatars or emoji, it
  skips anything with the class no-save, and it respects Pinterest’s own
  data-pin-nopin attribute.
• It never fights another plugin. If Pinterest’s own Pin It button
  (pinit.js) is already on the page, this one steps aside rather than drawing a
  second button beside it.
• Your own clicks do not count. While you are logged in, pressing the button
  does not add to the number.

Nothing here is locked

The button, the counting and the analytics screen are free. Not a trial, not a
limited number of posts, not a watermark, not a “pro” upsell in the middle of the
table. No account is needed and nothing is ever sent anywhere.

The optional extra, and where it comes from

Everything above is the whole plugin. One further feature is optional, and it
needs an account with our own service, Burnpedia — a
Pinterest scheduling and analytics tool we run.

Paste a free API key from
burnpedia.app into Save Button →
Account and the Analytics screen gains three more columns of Pinterest
analytics — impressions, saves and outbound clicks for your own Pins for
those same posts. It answers the question the click count cannot: the images
readers wanted to save, next to how the Pins you published yourself actually
performed.

A free account at burnpedia.app is enough to get one.
Without a key the plugin makes no outbound request at all, and nothing on the
screens above changes. Exactly what a saved key sends, and when, is listed under
External services below.

What it does NOT claim to know

When a reader saves your image, the Pin that gets made lives in their
account. Pinterest reports that Pin’s impressions and saves to them, not to you,
so this plugin does not show those numbers and does not estimate them.

What it measures is the part it can measure honestly: how many readers pressed
save on each image. That is a demand signal about your own photographs, and it
is the one that tells you which kind to make more of. Those counts stay on your
server, they are private to you, and they are free.

Fast, and quiet

• One JavaScript file, deferred, with no jQuery and no framework — about 5 KB
  over the wire.
• One stylesheet, under 2 KB over the wire.
• Zero external requests. No font, no icon set, no tracker, no CDN.
• No layout shift. The buttons float above your images and are not inserted
  into your post’s markup at all, so nothing on the page moves — including the
  full-width images that a wrapper element would quietly break on a block theme.
• No cookies, on either side.

Works with what you already use

Classic themes and block themes, the block editor and the classic editor,
galleries, captions, lazy loading and responsive images. Right-to-left sites get
the button on the correct side without configuring anything, and a full-width
image stays full width — the plugin never wraps your post content, which is what
breaks wide images on a block theme.

Privacy

No visitor data is collected: no IP address is stored; rate limiting keeps only a
short-lived salted hash that cannot be read back to an address and expires within
minutes. There is no cookie, no user agent, no referrer and no profile. What is
stored is a number per post and a number per day.

External services

This plugin is a client for Burnpedia (https://burnpedia.app), a Pinterest
scheduling service we operate. It is used for one optional feature: the three
extra columns on the Analytics screen showing how your own Pins for these posts
perform.

Nothing is sent anywhere until you save a Burnpedia API key. With no key
saved, the plugin makes no outbound request of any kind. There is no telemetry,
no analytics, no phone-home and no third-party asset — every script and style in
this plugin is served from your own site, and the click counter talks to your own
site and nothing else.

When a key is saved, these requests are made, and only these:

• GET https://burnpedia.app/api/v1/me — when an administrator opens the
  Analytics or Account screen, or presses Check connection. Sends: your API
  key. Receives: your plan, and whether a Pinterest account is connected.
• GET https://burnpedia.app/api/v1/analytics/site — when an administrator opens
  the Analytics screen. Sends: your API key and this website’s domain name.
  Receives: impressions, saves and outbound clicks for the Pins you published
  through Burnpedia for this website, over the last 30 days.

Both are read-only, both are made from your server, and both happen only while an
administrator is looking at one of this plugin’s own screens. Every request also
carries a header naming the plugin and its version, so we can tell which version
of the plugin a request came from.

Burnpedia’s terms: https://burnpedia.app/terms
Burnpedia’s privacy policy: https://burnpedia.app/privacy

Pinterest itself is never contacted by this plugin. The save button opens
Pinterest’s own save dialog in the visitor’s browser when the visitor clicks it,
exactly like following a link; the plugin sends nothing to Pinterest and loads
nothing from it.

Burnpedia is our own service and is not affiliated with Pinterest, Inc.

1. Install and activate the plugin.
2. That is it — the button is already on the images in your posts, and readers
   can save to Pinterest in one press.
3. Open Save Button in the menu to see which images readers are saving.

To change where the button sits, how big it is, or which post types it appears
on, go to Save Button → Button.

The three extra Pinterest columns are optional. If you want them, go to Save
Button → Account, follow the link to create a free Burnpedia account, and paste
in the API key it gives you.

1. 

   The save button on a post image — it appears when a reader points at the picture, and it is always visible on a phone.

2. 

   The same post on a phone, where the button stays on screen.

3. 

   The Analytics screen: which posts readers save, a 30-day trend, and the "Your Pins on Pinterest" columns a free account fills in.

4. 

   Button settings — where it sits, how big it is, and which images to skip.

5. 

   The Account screen, where the optional free connection lives.

1.0.1

• Renamed the plugin to Burnpedia Image Save Button Analytics.
• Rewrote the description: removed comparative wording, and said plainly what
  the optional Burnpedia connection adds and where to get a key.

1.0.0

• First release.