Title: Burnpedia Image Save Button Analytics Author: PinMaster Published: September 1, 2026 Last modified: September 1, 2026 --- Search plugins ![](https://ps.w.org/burnpedia-image-save-button-analytics/assets/banner-772x250. png?rev=3675474) ![](https://ps.w.org/burnpedia-image-save-button-analytics/assets/icon-256x256.png? rev=3675474) # Burnpedia Image Save Button Analytics By [PinMaster](https://profiles.wordpress.org/lalokupfer/) [Download](https://downloads.wordpress.org/plugin/burnpedia-image-save-button-analytics.1.0.1.zip) * [Details](https://wordpress.org/plugins/burnpedia-image-save-button-analytics/#description) * [Reviews](https://wordpress.org/plugins/burnpedia-image-save-button-analytics/#reviews) * [Installation](https://wordpress.org/plugins/burnpedia-image-save-button-analytics/#installation) * [Development](https://wordpress.org/plugins/burnpedia-image-save-button-analytics/#developers) [Support](https://wordpress.org/support/plugin/burnpedia-image-save-button-analytics/) ## 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. 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](https://burnpedia.app) — a Pinterest scheduling and analytics tool we run. Paste a free API key from [burnpedia.app](https://burnpedia.app/dashboard/api) 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](https://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. ## 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 save button on a post image — it appears when a reader points at the picture, and it is always visible on a phone.⌉[ 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 same post on a phone, where the button stays on screen.⌉[ 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" columns a free account fills in.⌉⌊The Analytics screen: which posts readers save, a 30-day trend, and the "Your Pins on Pinterest" columns a free account fills in.⌉[ The Analytics screen: which posts readers save, a 30-day trend, and the “Your Pins on Pinterest” columns a free account fills in. [⌊Button settings — where it sits, how big it is, and which images to skip.⌉⌊Button settings — where it sits, how big it is, and which images to skip.⌉[ Button settings — where it sits, how big it is, and which images to skip. [⌊The Account screen, where the optional free connection lives.⌉⌊The Account screen, where the optional free connection lives.⌉[ The Account screen, where the optional free connection lives. ## Installation 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. ## 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. A free Burnpedia account is needed for exactly one thing: the three columns showing how **your own** Pins for those posts are doing on Pinterest. ### 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 and expires within minutes. No cookie is set, no user agent or referrer is kept, and nothing about a reader is ever sent off your server. ### 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: 1. **A page cache has not been cleared yet.** Purge it and reload. 2. **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. 3. **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**. 4. **The image, or something around it, carries an excluded class** — `no-save`, one you added yourself, or Pinterest’s `data-pin-nopin` attribute. 5. **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 about 5 KB over the wire and one stylesheet under 2 KB, both served from your own site, with no jQuery, no framework and no external request at all. The buttons are drawn over your images rather than inserted into them, so the page does not move when they appear. ### 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 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. ### 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. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Burnpedia Image Save Button Analytics” is open source software. The following people have contributed to this plugin. Contributors * [ PinMaster ](https://profiles.wordpress.org/lalokupfer/) [Translate “Burnpedia Image Save Button Analytics” into your language.](https://translate.wordpress.org/projects/wp-plugins/burnpedia-image-save-button-analytics) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/burnpedia-image-save-button-analytics/), check out the [SVN repository](https://plugins.svn.wordpress.org/burnpedia-image-save-button-analytics/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/burnpedia-image-save-button-analytics/) by [RSS](https://plugins.trac.wordpress.org/log/burnpedia-image-save-button-analytics/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 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. ## Meta * Version **1.0.1** * Last updated **22 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.5 or higher ** * Tested up to **7.1** * PHP version ** 7.4 or higher ** * Tags * [click analytics](https://wordpress.org/plugins/tags/click-analytics/)[image sharing](https://wordpress.org/plugins/tags/image-sharing/) [Pinterest](https://wordpress.org/plugins/tags/pinterest/)[save button](https://wordpress.org/plugins/tags/save-button/) * [Advanced View](https://wordpress.org/plugins/burnpedia-image-save-button-analytics/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/burnpedia-image-save-button-analytics/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/burnpedia-image-save-button-analytics/reviews/) ## Contributors * [ PinMaster ](https://profiles.wordpress.org/lalokupfer/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/burnpedia-image-save-button-analytics/)