內容簡介
Burnpedia Image Save Button Analytics 外掛可在您的文章圖片上添加一個小的保存按鈕，讓讀者能輕鬆將圖片保存至 Pinterest。此外掛還能統計每個圖片的保存次數，幫助您了解哪些圖片最受歡迎。
【主要功能】
• 在每個圖片上添加保存按鈕
• 計算每篇文章的保存次數
• 顯示過去 30 天的保存趨勢
• 提供圖片的自訂描述選項
• 確保保存的是最大尺寸的圖片
外掛標籤
開發者團隊
② 後台搜尋「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.
And which image, not just which post. Open Saved images under any post
and each picture on it is listed with a thumbnail and its own count. On a
roundup or a gallery post that answers the question a single number cannot:
of the six photographs on the page, which one do 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.
Your headline and your link, already in the save window.
You choose what the description says. A box in the post editor sets the
Pin description for every image in that post, so what a reader saves carries
the sentence you wrote rather than 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 — the sort with your headline written across it — and the save
button hands Pinterest that picture instead of the photograph the reader
pressed. Nobody sees it on the page. Set one per post, or none at all.
A list of the images with no alt text. When an image has no alt text,
the Pin a reader saves from it is described with the post’s title instead, so
every photograph in that post goes to Pinterest carrying the same sentence.
The Analytics screen lists the posts where that happens — the ones readers
save most first — with a link straight to each post. It works from the day you
install it, before anybody has saved anything, and it only reads your own
posts.
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.
Already using another pin button?
If jQuery Pin It Button for Images is installed on this site, the Save Button
settings screen offers to bring its settings across in one press — the button
corner, the classes you excluded, and the posts you switched it off on. Nothing
of theirs is changed and it is not deactivated: that stays your decision, and you
can run both while you compare them. Settings that have no equivalent here are
listed rather than guessed at.
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
ever sent anywhere.
The only thing on this screen that is not ours to give away free is the
per-post Pinterest breakdown, which comes from a different product and is
described below — everything the Save Button itself measures is unlimited.
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. 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 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
itself is free either way, and you can connect this site in one press without
copying a key at all.
Without a key the plugin makes no outbound request except that one connection,
which happens only when you press the button for it, and nothing on the screens
above changes. Exactly what is sent, 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 — under 8 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, a number per day, and a number for each image on a
post. The image is identified by a short code this plugin works out from the
image’s own web address, never by anything about the person who saved it.
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 unless you ask for it. With no API key saved and
the install count switched off — which is how the plugin arrives — it makes no
outbound request of any kind. There is no analytics, no phone-home you did not
switch on, no advertising 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.
There are two separate things you can switch on, and neither is on by default.
One is an API key, which adds the Pinterest numbers. The other is the install
count below, which is not required for anything and unlocks nothing — it exists
only so we can tell how many sites use this plugin.
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 the only thing in the plugin that makes a request before a key
exists, and it happens only after an administrator presses that button:
Your browser opens https://burnpedia.app/connect/wordpress, 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 that never leaves your server.
After you approve it there, your site makes one
POST https://burnpedia.app/api/site-connect/claim request, sending that
request ID and the secret, and receives an API key which is saved for you. The
key is never shown in your browser.
The request expires after fifteen minutes and can be collected only once. If
you press Cancel, or never approve it, nothing is sent and nothing is created.
You never have to use it. Pasting a key by hand still works exactly as before,
and is the way to connect a site that cannot reach the internet.
The reader-click counting is not involved in any of this and never contacts
anyone, with or without a key.
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.
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. Switch it off 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 are running their plugin — for this plugin it
publishes no figure at all. 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.
Your website address is not in that report and is never sent, so we cannot
tell which website you are. 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.
Every request above is made from your server, never from a reader’s browser,
and every one happens only while an administrator is signed in to wp-admin — a
visitor reading your site can never cause any of them. Each also carries a header
naming the plugin and its version, so we can tell which version 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.
