Burnpedia Image Save Button Analytics

by PinMaster

Description

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.

It also counts the presses, so you can see which of your images readers
choose to save.

How Burnpedia Image Save Button Analytics is different

It is light and steps aside: one deferred script with no jQuery; the
button is drawn over your images, never wrapped around them, and all it adds
to a post’s markup is an empty marker, plus your hidden Pin image if you set
one; and no second button when Pinterest’s own pinit.js is on the page.

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.
And which image, not just which post. Open Saved images under any post
to see each picture with a thumbnail and its own count — on a roundup, which of
the six photographs readers actually want.
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.
You choose what the description says. A box in the post editor sets the
Pin description for every image in that post, instead of alt text meant for a
screen reader. Leave it empty and the alt text is used, exactly as before.
A hidden Pin image, if you make one. Attach a tall image built for Pinterest
and the save button hands Pinterest that picture instead of the photograph the
reader pressed. Nobody sees it on the page. One per post, or none.
A list of the images with no alt text. Without it, a saved Pin is described
with the post’s title, so every photograph in that post carries the same
sentence. The Analytics screen lists those posts, most saved first, with a link
to each — from the day you install it, reading only your own posts.
Which day of the week readers save. The Analytics screen shows the average
saves for each weekday and, once there is enough to go on, names the day your
readers save most.
A “Most saved images” block. Add it to any page or sidebar and it shows
the images on your site that readers saved most, each linking to its post.
Nothing appears anywhere until you add the block.
Download your counts as a CSV file for a spreadsheet: every post and
image with a save, not just the ones on screen.
Respects Do Not Track and Global Privacy Control. A reader whose browser
asks not to be tracked is not counted. The button still works for them.
Shop product pages, if you want them. If your site has shop products, the
settings screen offers to put the button on the main product photos. It stays
off until you choose it.
One setup for a multisite network. A network administrator can set the
button up once for every site, and optionally stop sites changing it.
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.

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. No account is needed, and nothing is
sent anywhere unless you ask for it or save an API key, which also shares your
daily save totals unless you untick Share your click counts (every case is
listed under External services).

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 an API key from
burnpedia.app into Save Button
Account and the Analytics screen gains Pinterest analytics for your own
Pins to those same posts — impressions, saves and outbound clicks.

A free Burnpedia account shows the site-wide total of those three numbers.
The per-post columns — which of these posts your Pins earn on — are on
Burnpedia’s paid plans; the screen says so and links to them. Getting the key
is free either way, and one press connects this site without copying it.
Without a key the plugin makes no outbound request except the one-press
connection, the install count if you switch it on, a bug report you send, or the
More plugins list you open — each only when you choose it — and nothing on the
screens above changes. Exactly what is sent, and when, is listed under External
services below.

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, deleted by the
next save a reader makes in a later minute. There is no cookie, no user agent,
no referrer and no profile — only a number per post, a number per day, and
a number for each image on a post, identified by a code worked out from the
image’s own web address.

External services

This plugin is a client for Burnpedia (https://burnpedia.app), a Pinterest
scheduling service we operate. Its main use is one optional feature: the
three extra columns on the Analytics screen showing how your own Pins for these
posts perform. The optional install count and a bug report you send also go to
Burnpedia, each described below.

Nothing is sent anywhere unless you ask for it or save an API key. With no
API key saved and the install count switched off — which is how the plugin
arrives — requests leave this site only after you press Connect this site to
Burnpedia, when you send a bug report, or when you open the More plugins
list (all three below). Nothing happens
on activation, and nothing on a visitor’s page view. There is no third-party
advertising, no offer outside the plugin’s own screens and its box in the post
editor, and no third-party script or style: every script and style in this
plugin is served from your own site (the More plugins screen shows each
plugin’s icon from WordPress.org, as Plugins Add New does), and the click
counter talks to your own site and nothing else.

No request to Burnpedia carries your site’s address in its headers: each
one sets its own User-Agent (WordPress’s default one names the site). The More
plugins list is not one of them: WordPress fetches it itself, through
plugins_api() as Plugins Add New does, with that default User-Agent.
Where a request does send this website’s address, the list below says so.

There are two separate things you can switch on, an API key and the install
count, and neither is on by default.

Connecting this site in one press (optional). On the Account screen you
can press Connect this site to Burnpedia instead of copying an API key by
hand. It is one of the requests that can happen before a key exists (with the
install count, a bug report and the More plugins list), and it starts only
when an administrator presses that button:

Your browser opens https://burnpedia.app/connect/wordpress when you press
Open burnpedia.app to approve, carrying this site’s address and its title,
so the approval screen can name the site you are about to connect. It also
carries a random one-time request ID and a fingerprint of a secret your
browser never sees.
From the moment you press Connect this site to Burnpedia, while the
Account screen is open, your site asks
POST https://burnpedia.app/api/site-connect/claim every few seconds whether
you have approved it there (at least three seconds apart, and at most 100
times each time that screen is opened while the request is live), and once
each time you press I have approved it. Each ask sends that request ID and
the secret, and names the plugin and its version in its headers; it does not
carry your site’s address, not even in its User-Agent header. Once you
approve, the answer is an API key, saved for you and never shown in your
browser.
The request expires after fifteen minutes and its key can be collected only
once. If you press Cancel or deny it, or the request expires, the asking stops
and no key is created.
You never have to use it: pasting a key by hand still works.

The reader-click counting itself contacts nobody. With a key saved, its
daily totals are shared with Burnpedia unless you untick Share your click
counts (below).

When a key is saved, it adds these requests, and only these:

GET https://burnpedia.app/api/v1/me — when an administrator opens the
Analytics screen (an answer is reused for five minutes), right after a key is
saved or collected or the Account settings are saved, and when an
administrator 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 (an answer is reused for fifteen minutes). 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.
POST https://burnpedia.app/api/v1/events/save-clicks — at most once every
twelve hours, when an administrator opens the Analytics screen. Sends: your API
key, this website’s address, and how many times readers pressed Save on each of
the last 90 days — a date and a whole number, nothing else. Receives: how many
days were recorded. It puts those counts beside your Pin results in your
Burnpedia dashboard. Nothing about any reader is in it. The plugin stores
no IP address, no user agent, no referrer and no cookie, so there is nothing
about a visitor for it to send. Share your click counts is ticked by
default; untick it under Save Button Account and the counts never leave
your server.

The install count (optional, off by default). WordPress.org does not tell
plugin authors how many sites run their plugin. The plugin asks you once, in a dismissible notice,
and you can change the answer at any time under Save Button Account.
Saying no sends nothing and closing the box without answering also sends
nothing. If you switch it on, this site sends a short report:

POST https://burnpedia.app/api/plugin-insights — once when you switch it on,
then at most once a week while an administrator is using wp-admin, once if you
deactivate the plugin, and once if you delete it. Sends exactly nine things: a
random ID generated on this site, which plugin and which version, which of
those four events it is, your WordPress version, your PHP version, your site
language, whether this is a multisite network, and whether an API key is saved
(true or false — never the key). Receives: nothing your site uses.

No install-count report carries your website address, not even in the
User-Agent header: the plugin sends its own. The random ID is made up on your server and means
nothing outside it. Switch the setting off and the ID is deleted, so counting
stops and a later change of mind cannot be joined to it. It is off until you
choose it, no feature depends on it, and nothing about any reader or any logged-in
user is in it.

Report a bug and More plugins (only when you use them). Pressing Send
report on Save Button Report a bug sends
POST https://burnpedia.app/api/plugin-bug-report: your description, an optional
reply email, the plugin, WordPress and PHP versions, theme, language, whether it is
multisite and whether a key is saved (never the key) — and your site’s address
only if you leave “Include this site’s address” ticked (it starts ticked; untick
it and the address is not sent, not even in the request’s headers). Opening
Save Button More plugins asks WordPress.org (https://api.wordpress.org/plugins/info/) for
our plugin list via WordPress’s plugins_api(), as Plugins Add New does.
The list is kept for twelve hours (fifteen minutes after a failed try), and
opening the screen again in that time does not ask for it again. On that screen
your browser shows each plugin’s icon from WordPress.org, and More Details
and Install Now are WordPress’s own plugin details and installer, which
fetch from WordPress.org when you press them.

Apart from the connection page your own browser opens, every request to
Burnpedia above is made from your server, and a visitor reading your site can
never cause one. Each happens when an administrator acts in wp-admin (the
connection’s asks run while the Account screen waits for your approval), or
when the plugin is deactivated or deleted (which a host’s tools or WP-CLI can also
do), and each names the plugin and its version, in a header or in its body. The
More plugins list is WordPress’s own request.

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; that link carries the image’s address, the post’s
address and the Pin description, which is what the saved Pin is made of. The
plugin sends nothing to Pinterest and loads nothing from it.

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

Installation

Install and activate the plugin.
That is it — the button is already on the images in your posts, and readers
can save to Pinterest in one press.
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 Pinterest numbers are optional. If you want them, go to Save Button
Account, press Connect this site to Burnpedia, then Open burnpedia.app to
approve. Approve it in the tab that opens — a free account takes a moment to
make if you do not have one — and your site collects its own key. There is nothing to copy or paste. A free
account shows the site-wide total; the per-post columns are on the paid plans.

If your site cannot reach the internet, or you would rather do it yourself, the
same screen still takes a key you paste in by hand.

Screenshots

The save button on a post image — it appears when a reader points at the picture, and it is always visible on a phone.
The same post on a phone, where the button stays on screen.
The Analytics screen: which posts readers save, a 30-day trend, and the "Your Pins on Pinterest" numbers a connected Burnpedia account adds.
Button settings — where it sits, how big it is, and which images to skip.
The Account screen, where the optional free connection lives.
The hidden Pin image on a post: a tall graphic readers never see, which the save button hands to Pinterest instead of the photograph they pressed.
Report a bug from inside WordPress: it goes straight to the people who build the plugin, and nothing is sent until you press Send.

Faq

Do I need an account?

No. The button, the counting and the whole analytics screen work with no account
of any kind, and nothing leaves your site unless you ask for it: the one-press
connection, the install count if you switch it on, a bug report you send, or the
More plugins list you open.

A Burnpedia account is needed for exactly one thing: showing how your own
Pins for those posts are doing on Pinterest. A free account shows the site-wide
total of impressions, saves and outbound clicks; the per-post columns are on
Burnpedia’s paid plans.

I already use jQuery Pin It Button for Images. Can I switch?

Yes, and you do not have to set everything up again. With that plugin on the
site, Save Button detects its settings and offers to copy the ones that have an
equivalent here — in one press, with a list of exactly what will change shown
first. It never edits their settings and never deactivates them, so you can run
both side by side and keep whichever you prefer.

Do you collect any visitor data?

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, deleted by the
next save a reader makes in a later minute. No cookie is set, no user agent or
referrer is kept, and nothing about a reader is ever sent off your server.

Does it respect Do Not Track and Global Privacy Control?

Yes. When a reader’s browser sends either signal, their press is not counted —
the site checks it too, so an old copy of the page in a cache cannot count them
either. The save window still opens for them as normal. The plugin stores
nothing about readers anyway, so this is not required; it simply lets you say
that your count respects the choice.

Can I export the counts?

Yes. The Analytics screen has a Download all counts (CSV) button. The file
has one row per post and one per saved image, with the saves in the last 30 days
and all time, and opens in any spreadsheet. Only administrators can download it.

Can I show my most saved images on my site?

Yes, with the Most saved images block. Add it in the editor wherever you
like and choose how many images it shows; each one links to its post. It shows
images only, never the counts, and it lists only published, public posts.

Which day of the week do my readers save the most?

The Analytics screen answers that under Which day readers save, from the
last 90 days of your own counts. It averages each weekday rather than adding
them up, and it waits for two weeks and twenty saves before naming a day.

Does it work on shop product pages?

It can. If your site has shop products, Save Button Button offers to add
the button to product pages. It then goes on the product’s main photos, and not
on the small gallery thumbnails or the related products underneath. It is never
switched on for you.

Does it work on multisite?

Yes. On a network, Network Admin Settings Save Button sets the button up
once for every site. By default those settings are only the starting point and
each site can change its own; tick Apply these to every site and the network
settings are used everywhere. API keys and reporting choices always stay with
each site’s own administrator.

Is this a Pin It button?

It does the same job. Pinterest’s original Pin It button was a script you loaded
from Pinterest; this is a save button your own site draws, so nothing is fetched
from Pinterest and nothing about your readers is sent anywhere. Pressing it opens
the same save window.

If you already run Pinterest’s own Pin It button (pinit.js), this plugin
detects it and stays out of the way rather than putting two buttons on one image.

Can I turn the hover off and show the button all the time?

Yes — Save Button Button When it shows. Hover is the default on a
desktop because a button that is always visible sits on top of the photograph
you want people to look at. On phones and tablets it is always shown either way,
because there is no hovering with a finger.

Why don’t I see the button?

The usual reasons, in the order they turn out to be true:

A page cache has not been cleared yet. Purge it and reload.
Pinterest’s own widget is on the page. If pinit.js is loaded — often by
a tag manager — this plugin steps aside rather than drawing a second button.
The image is smaller than the minimum. The default skips anything under
200 pixels in either direction, which is what keeps buttons off icons and
author photos. Lower it under Save Button Button.
The image, or something around it, carries an excluded class — no-save,
one you added yourself, or Pinterest’s data-pin-nopin attribute.
The post type is switched off, or the theme prints the post body without
running WordPress’s own content filter, which some page builders do.

Why is the click count zero?

Almost always a security plugin. Several of them switch the WordPress REST API
off for logged-out visitors, and that is the path the count travels on — so the
button still works, and the number never moves.

There is a Send a test click button on the Analytics screen that sends one
real click along exactly the same path a reader’s browser uses, without your
login. It answers the question in about a second.

Does it slow my site down?

One deferred JavaScript file of under 8 KB over the wire and one
stylesheet, under 2 KB (plus one under 1 KB, only on a page that has the Most
saved images block), all served from your own site, with no jQuery, no framework and no
external request at all: no font, no icon set, no tracker, no CDN and no cookie.
The buttons are drawn over your images rather than inserted into them, so the
page does not move when they appear.

Does it work with my theme?

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.

Does it show the numbers for the Pins my readers make?

No. 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 — a demand signal about your own photographs that tells you
which kind to make more of. The counts are kept on your server, private and
free; with a key saved, they are also shared with Burnpedia unless you untick
Share your click counts.

Will it change my posts?

No. It never edits your content. The buttons are drawn in a layer above the page,
which is also why full-width images stay full width.

Which image gets saved?

The largest one your site offers. WordPress makes several sizes of every image
you upload, and a browser on a phone downloads a small one — saving that copy
would leave a phone-sized Pinterest image on somebody’s board forever. This
plugin reads the whole set and hands over the biggest, so what people save is
always the sharp copy.

Can I choose what the Pin description says?

Yes. Every post has a Save Button (Burnpedia) box in the editor sidebar with
one field: the Pin description for that post’s images. Whatever you type there is
what Pinterest fills in when a reader saves any image from the post.

Leave it empty and nothing changes — the image’s own alt text is used, and then
the post title. An individual image that carries Pinterest’s own
data-pin-description attribute keeps that, because it is a more specific
choice than a whole-post default.

The box appears for anyone who can publish that post type. It is not shown to
contributors, because the text goes out on a public Pin under your site’s name.

Which of my images are missing alt text?

Open Save Button Analytics and look for Images that would be Pinned with
no description. It lists the posts whose images have no alt text — ranked by
how often readers save from them, or by date if nobody has saved anything yet —
and says how many images in each need it. Each post title links to its editor.

It matters for Pinterest specifically: an image with no alt text is saved with
the post’s title as its description, so a post with six photographs sends six
Pins with identical text. Writing alt text fixes that, and it also helps people
using screen readers and search engines. A Pin description set on the post
removes it from the list too, but it gives every image in that post the same
words again.

The list reads only your own posts. It sends nothing anywhere.

Can I use a separate image for Pinterest?

Yes. Open a post, find the Save Button (Burnpedia) box and choose a hidden
Pin image. It is usually a tall graphic, often 1000 by 1500, with the headline
set across it — the shape that works in a Pinterest feed and would look wrong in
the middle of an article.

Readers never see it. When somebody presses the save button anywhere on that
post, Pinterest opens with that graphic rather than the photograph they pressed,
and with your Pin description. A copy of it is also placed in the page, hidden,
which is where Pinterest’s own browser tools look for images to offer.

Two honest notes. Their browser does download it even though they never see it —
that is exactly what makes it findable, so only set one on posts where you want
it saved. And the count still records which photograph they pressed, because
“which picture makes people save” is worth knowing separately from what gets
saved.

Can I stop it on certain images?

Yes, four ways: add the class no-save, add data-pin-nopin to the image, add
your own class names under Save Button Button, or raise the minimum image
size.

Is my count exact?

It is honest, and it is not a billing system. Presses are counted as they arrive,
with two limits that keep somebody from inflating it: no more than 30 clicks a
minute from one visitor, and no more than 2,000 a day on any one post. Your own
clicks, while you are logged in, are never counted.

Can I turn a most-saved image into a Pin?

If you also run our scheduling plugin, yes: every row in the table gets a
Schedule a Pin button that opens that post at the scheduling panel, so the
image readers are already saving is one click from being queued.

Nothing appears if you do not have that plugin. The table never suggests
installing it.

Does anything about my readers leave my site?

No, and there is nothing that could. The plugin never stores an IP address, a
user agent, a referrer or a cookie, so no visitor detail exists here to be sent.

If you have connected a Burnpedia account, the plugin sends your daily
totals — this website’s address, a date and a whole number per day — so those
counts can sit beside your Pin results in your dashboard. It goes at most once
every twelve hours, only while you are on the Analytics screen. You can switch it
off under Save Button Account, and with no API key saved the daily totals
are never sent.

What happens if I delete the plugin?

Everything it wrote is removed: the settings, the counts, the daily series and
the caches. Your posts and your images are not touched.

How do I report a bug?

Open Save Button Report a bug, say what happened and press Send report. It goes straight to the people who build this plugin, with the version numbers we need to reproduce it; leave your email and we will write back. The WordPress.org support forum works too.

Do you make other plugins?

Yes. Save Button More plugins lists our other free plugins, and each one installs in one click through WordPress’s own installer.

Reviews

Changelog

1.12.2

Fixed: requests to Burnpedia no longer carry your site’s address in their
User-Agent header. WordPress’s default one names the site, and until this version the install
count, a bug report, the one-press connection and every API request used it,
although this page said the address was not sent. Each of those requests now
sends its own User-Agent.
Fixed: answering “No, send nothing” (or “No thanks”) to the install count
sent one last “opt-out” report. It now sends nothing at all.
Fixed: the weekly install count could be sent by a logged-out request to
admin-ajax.php or admin-post.php, or while a subscriber was in wp-admin. It is
now sent only while an administrator uses wp-admin.
This page, the Account screen and the install-count question now name every
field the count sends and every request that can happen before an API key is
saved. The 1.12.1 entry below used to say one of those sentences had been
corrected; it had not been, so that line is removed and the sentence is fixed.
This page now says that the More plugins list is fetched by WordPress itself,
with WordPress’s own User-Agent, and what the plugin adds to a post’s markup:
an empty marker, and the hidden Pin image if you set one. The Analytics
screen says how this plugin is different, in a short note.
This page and the Account screen now say that, with a key saved, Share your
click counts is ticked by default and sends the daily totals, where they
used to say the counting never contacts anyone. The 1.5.0 and 1.2.0 entries
below are corrected to match (1.2.0 also sent this website’s address). They
also say which requests happen without an administrator in wp-admin
(deactivating or deleting the plugin) and where each names the plugin and its
version.
The CSV download is now written row by row as it is sent. A cell is quoted
only when it needs to be, and a title that starts like a formula is still
neutralised.
The “Connect a free account” reminder and the install-count question now
appear only on the plugin’s own screens, never on the Dashboard or the
Plugins list.
Uninstall now also removes the Report a bug screen’s short-lived result.
The parts shared with Burnpedia’s other plugins now load under new names, so
an older copy inside another Burnpedia plugin on the same site can no longer
undo these fixes.
This page and the Account screen now say how the one-press connection asks
for its key: every few seconds from the press of Connect this site to
Burnpedia, while the Account screen is open (at most 100 times each time it
is opened), until you approve, deny or cancel it or the request expires. They
used to say it asked once, after you approved, and that nothing was sent if you
never approved. This page also says when the account check runs and how long
the More plugins list is kept. No request changed.

1.12.1

The listing text is shorter, so WordPress.org shows all of it again —
including the More plugins disclosure, our terms and privacy links, and how
the plugin relates to Pinterest. No code changed.

1.12.0

New: Report a bug in the Save Button menu. Describe a problem and it reaches us
directly, with the plugin, WordPress and PHP versions we need to reproduce it.
Your site’s address is included only if you leave its box ticked (until 1.12.2
it also went in the request’s User-Agent header), and nothing
is sent until you press Send.
New: More plugins in the Save Button menu lists our other free plugins, each
installed in one click through WordPress’s own installer from WordPress.org.

1.11.0

New: Which day readers save. The Analytics screen shows the average saves
for each day of the week and names the day your readers save most, once there
is enough to go on.
New: Most saved images block. Show the images readers saved most on any
page or sidebar. It only appears where you add it.
New: Download all counts (CSV) for a spreadsheet.
New: readers whose browser sends Do Not Track or Global Privacy Control are
not counted. The button still works for them.
New: the settings screen offers to add the button to shop product pages,
on the main product photos only. Off until you choose it.
New: network settings for multisite — set the button up once for every
site, and optionally stop sites changing it.

1.10.0

New: Images that would be Pinned with no description, on the Analytics
screen. An image with no alt text is saved to Pinterest with the post’s title
as its description, so every photo in that post gets the same text. The list
shows which posts that happens on and links to each one.
It works on the day you install it: with no saves yet it checks your most
recent posts, and once readers save, the posts they save most come first.
A post with its own Pin description is not listed, since that description is
used for every image in it. Reads only your own posts; sends nothing anywhere.

1.9.1

Corrected the plugin’s own screens, which still said a free Burnpedia
account fills the three per-post “Your Pins on Pinterest” columns. It does
not, and the listing was corrected in 1.8.2 while the plugin was not — so the
only people still being told the wrong thing were the ones who had already
installed it. A free key shows the totals for your whole website; the per-post
columns are on Burnpedia’s paid plans. Getting a key is free either way, and
nothing about what the Save Button itself measures has changed.
The same correction on the greyed-out columns, on the Account screen and in
the reminder notice — all three places where you decide whether to connect.

1.9.0

The plugin now asks, once, whether it may count this site — in a notice you
can answer with one press instead of only on a settings screen you had to go
looking for. It asks a single time and then never again, whatever you answer.
Saying no sends nothing at all (until 1.12.2 it sent one last “opt-out”
report), and closing the box without answering is not taken as an answer
either — it just stops asking. You can still change your
mind either way under Save Button Account.
Nothing new is sent and no new address is contacted: this is the same
optional, off-by-default install count as before, with the question put where
people will actually see it.

1.8.2

Corrected the listing. This page said a free Burnpedia account fills in the
three “Your Pins on Pinterest” columns. It does not: a free account shows the
site-wide total of impressions, saves and outbound clicks, and the per-post
columns are on Burnpedia’s paid plans – which is what the plugin’s own screen
has always said. Getting the key is still free, and so is everything the Save
Button itself measures.
No code change.

1.8.1

The listing now mentions two things the plugin has been doing for a while and
never said out loud: that the Analytics screen breaks saves down per image,
not just per post, and that it can bring your settings over from jQuery Pin
It Button for Images in one press.
No functional change. Nothing in the plugin behaves differently.

1.8.0

New: a hidden Pin image per post. Attach the tall, headline-across-it
graphic you made for Pinterest, and the save button hands Pinterest that
picture instead of the photograph the reader pressed. Readers never see it on
the page.
Pinterest’s own data-pin-media attribute is honoured too, so a single image
can override the whole post.
The Pin description follows the graphic: when one is set, the pressed
photograph’s alt text is no longer offered, because it describes a different
picture.
The click count is unchanged — it still records which photograph a reader
pressed, which is a different question from what got saved.
Note that readers’ browsers do download the hidden image, which is what makes
it findable. It is only ever added to posts where you set one.

1.7.0

New: the Analytics screen now shows which image on a post readers saved,
not just how many saves the post got. Open “Saved images” under any post title
for a thumbnail of each one and its own count.
On a roundup or a gallery post this answers the question the old number could
not: of the six photos on the page, which one do readers actually want?
Counts recorded before this update stay on the post as a whole. They are
reported separately rather than split between images, because nothing can know
after the fact which image an old save was on.

1.6.0

New: if you are switching from jQuery Pin It Button for Images, the Button
screen now offers to copy its settings across — where the button sits, whether
it shows on hover, which classes to skip and the minimum image size. One press,
and you can say no.
It never changes or switches off that plugin: it only reads its settings, and
it tells you plainly which of them have no equivalent here rather than quietly
dropping them.
A setting you have already changed yourself is never overwritten.

1.5.0

New: Connect this site to Burnpedia — one button on the Account screen.
Approve it in the tab that opens and your site collects its own API key. There
is nothing to copy, nothing to paste, and the key is never shown in a browser.
Pasting a key by hand still works exactly as before, and is still the way to
connect a site that cannot reach the internet.
The button, the counting and the analytics table are unchanged and still
free; without a key they still contact nobody.

1.4.0

New: an optional install count under Save Button Account. WordPress.org
publishes no install figure for this plugin, so we genuinely cannot tell how
many sites use it. Switch this on and your site sends a random ID once a week
so it can be counted. Your website address is not in the report (until 1.12.2
it went in the request’s User-Agent header). It is off unless you turn it on,
nothing depends on it, and turning it off deletes the ID.

1.3.0

If you also run our scheduling plugin, every row in the Analytics table now
has a Schedule a Pin button that opens that post straight at the panel
where you queue it. The image your readers keep saving is one click from being
a Pin you posted on purpose.
Nothing changes, and nothing is shown, on a site without that plugin.

1.2.0

Your daily click totals can now appear in your Burnpedia dashboard, beside
what your own Pins for those pages earned — the first time both halves of that
picture have been in one place. Optional, off with one tick under Save
Button Account, and it sends this website’s address, a date and a number
per day, and nothing else.
Documented the new request under External services.

1.1.0

New: a Pin description box in the post editor. It sets the description
Pinterest opens with when a reader saves any image from that post, so you are
no longer limited to alt text written for a screen reader. Leave it empty and
the previous behaviour is unchanged.
The plugin’s internal version number had been left at 1.0.0 through the 1.0.1
release, so browsers kept serving the old copy of the stylesheet after an
update. Fixed, and a test now compares the two.

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.