{"id":361886,"date":"2026-09-01T06:57:18","date_gmt":"2026-09-01T06:57:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/burnpedia-save-button-image-hover-buttons-with-click-analytics\/"},"modified":"2026-09-01T06:56:57","modified_gmt":"2026-09-01T06:56:57","slug":"burnpedia-image-save-button-analytics","status":"publish","type":"plugin","link":"https:\/\/wordpress.org\/plugins\/burnpedia-image-save-button-analytics\/","author":23546237,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.0.1","stable_tag":"1.0.1","tested":"7.1","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"Burnpedia Image Save Button Analytics","header_author":"Burnpedia","header_description":"Adds a save-to-Pinterest button to your post images on hover, and shows which images readers save. Free click analytics, no account needed.","assets_banners_color":"f0cdbb","last_updated":"2026-09-01 06:56:57","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"https:\/\/burnpedia.app\/developers","header_author_uri":"https:\/\/burnpedia.app","rating":0,"author_block_rating":0,"active_installs":0,"downloads":37,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"1.0.1":{"tag":"1.0.1","author":"lalokupfer","date":"2026-09-01 06:56:57","revision":3675475}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3675474,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3675474,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3675474,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3675474,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3675474,"resolution":"1","location":"assets","locale":"","width":2880,"height":2000},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3675474,"resolution":"2","location":"assets","locale":"","width":1170,"height":1992},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3675474,"resolution":"3","location":"assets","locale":"","width":2880,"height":1800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3675474,"resolution":"4","location":"assets","locale":"","width":2880,"height":1800},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3675474,"resolution":"5","location":"assets","locale":"","width":2880,"height":1800}},"screenshots":{"1":"The save button on a post image \u2014 it appears when a reader points at the\npicture, 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\n\"Your Pins on Pinterest\" columns a free account fills in.","4":"Button settings \u2014 where it sits, how big it is, and which images to skip.","5":"The Account screen, where the optional free connection lives."}},"plugin_section":[],"plugin_tags":[263837,278593,20972,312,18088],"plugin_category":[56],"plugin_contributors":[275437],"plugin_business_model":[],"class_list":["post-361886","plugin","type-plugin","status-publish","hentry","plugin_tags-click-analytics","plugin_tags-image-hover-button","plugin_tags-image-sharing","plugin_tags-pinterest","plugin_tags-save-button","plugin_category-social-and-sharing","plugin_contributors-lalokupfer","plugin_committers-lalokupfer"],"banners":{"banner":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/banner-772x250.png?rev=3675474","banner_2x":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/banner-1544x500.png?rev=3675474","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/icon-128x128.png?rev=3675474","icon_2x":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/icon-256x256.png?rev=3675474","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-1.png?rev=3675474","caption":"The save button on a post image \u2014 it appears when a reader points at the\npicture, and it is always visible on a phone."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-2.png?rev=3675474","caption":"The same post on a phone, where the button stays on screen."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-3.png?rev=3675474","caption":"The Analytics screen: which posts readers save, a 30-day trend, and the\n\"Your Pins on Pinterest\" columns a free account fills in."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-4.png?rev=3675474","caption":"Button settings \u2014 where it sits, how big it is, and which images to skip."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-5.png?rev=3675474","caption":"The Account screen, where the optional free connection lives."}],"raw_content":"<!--section=description-->\n<p><em>Burnpedia Image Save Button Analytics is not affiliated with, endorsed by or\nsponsored by Pinterest, Inc. Pinterest is their trademark, named here only to\nsay where the button saves to.<\/em><\/p>\n\n<p>A reader is looking at a photograph in your post and would happily save it to\nPinterest. Most of the time nothing on the page invites them to, so they scroll\non.<\/p>\n\n<p>This plugin puts a small <strong>save button on the images in your posts<\/strong>. It is an\nimage hover button: point at a picture and it fades in, press it and Pinterest's\nown save window opens with your image, your headline and a link back to the post\nalready filled in. On a phone, where there is nothing to hover, it is simply\nalways there.<\/p>\n\n<p>It also counts the presses, so you can see <strong>which of your images readers\nchoose to save.<\/strong> Every press is recorded here, on your own site, in your own\ndatabase, and shown to you as a plain table \u2014 this post, this many saves, this\nmonth and all time.<\/p>\n\n<h4>What you get<\/h4>\n\n<ul>\n<li><strong>A save button on every content image<\/strong> \u2014 on hover on a desktop, always\nvisible on a phone or a tablet.<\/li>\n<li><strong>A private count of every press<\/strong>, per post, for the last 30 days and for all\ntime, with a 30-day trend line.<\/li>\n<li><strong>The right file gets saved.<\/strong> WordPress serves several sizes of every image;\nthe button always hands over the largest one, not the small copy a phone\nhappened to download.<\/li>\n<li><strong>Your headline and your link<\/strong>, already in the save window. The description\ncomes from the image's own alt text, so it is the one you wrote.<\/li>\n<li><strong>It stays out of the way<\/strong> \u2014 it never appears on icons, avatars or emoji, it\nskips anything with the class <code>no-save<\/code>, and it respects Pinterest's own\n  data-pin-nopin attribute.<\/li>\n<li><strong>It never fights another plugin.<\/strong> If Pinterest's own Pin It button\n(<code>pinit.js<\/code>) is already on the page, this one steps aside rather than drawing a\nsecond button beside it.<\/li>\n<li><strong>Your own clicks do not count.<\/strong> While you are logged in, pressing the button\ndoes not add to the number.<\/li>\n<\/ul>\n\n<h4>Nothing here is locked<\/h4>\n\n<p>The button, the counting and the analytics screen are free. Not a trial, not a\nlimited number of posts, not a watermark, not a \"pro\" upsell in the middle of the\ntable. No account is needed and nothing is ever sent anywhere.<\/p>\n\n<h4>The optional extra, and where it comes from<\/h4>\n\n<p>Everything above is the whole plugin. One further feature is optional, and it\nneeds an account with our own service, <a href=\"https:\/\/burnpedia.app\">Burnpedia<\/a> \u2014 a\nPinterest scheduling and analytics tool we run.<\/p>\n\n<p>Paste a free API key from\n<a href=\"https:\/\/burnpedia.app\/dashboard\/api\">burnpedia.app<\/a> into <strong>Save Button \u2192\nAccount<\/strong> and the Analytics screen gains three more columns of <strong>Pinterest\nanalytics<\/strong> \u2014 impressions, saves and outbound clicks for <strong>your own Pins<\/strong> for\nthose same posts. It answers the question the click count cannot: the images\nreaders wanted to save, next to how the Pins you published yourself actually\nperformed.<\/p>\n\n<p>A free account at <a href=\"https:\/\/burnpedia.app\">burnpedia.app<\/a> is enough to get one.\nWithout a key the plugin makes no outbound request at all, and nothing on the\nscreens above changes. Exactly what a saved key sends, and when, is listed under\n<strong>External services<\/strong> below.<\/p>\n\n<h4>What it does NOT claim to know<\/h4>\n\n<p>When a reader saves your image, the Pin that gets made lives in <strong>their<\/strong>\naccount. Pinterest reports that Pin's impressions and saves to them, not to you,\nso this plugin does not show those numbers and does not estimate them.<\/p>\n\n<p>What it measures is the part it can measure honestly: <strong>how many readers pressed\nsave on each image.<\/strong> That is a demand signal about your own photographs, and it\nis the one that tells you which kind to make more of. Those counts stay on your\nserver, they are private to you, and they are free.<\/p>\n\n<h4>Fast, and quiet<\/h4>\n\n<ul>\n<li>One JavaScript file, deferred, with no jQuery and no framework \u2014 about 5 KB\nover the wire.<\/li>\n<li>One stylesheet, under 2 KB over the wire.<\/li>\n<li><strong>Zero external requests.<\/strong> No font, no icon set, no tracker, no CDN.<\/li>\n<li><strong>No layout shift.<\/strong> The buttons float above your images and are not inserted\ninto your post's markup at all, so nothing on the page moves \u2014 including the\nfull-width images that a wrapper element would quietly break on a block theme.<\/li>\n<li>No cookies, on either side.<\/li>\n<\/ul>\n\n<h4>Works with what you already use<\/h4>\n\n<p>Classic themes and block themes, the block editor and the classic editor,\ngalleries, captions, lazy loading and responsive images. Right-to-left sites get\nthe button on the correct side without configuring anything, and a full-width\nimage stays full width \u2014 the plugin never wraps your post content, which is what\nbreaks wide images on a block theme.<\/p>\n\n<h4>Privacy<\/h4>\n\n<p>No visitor data is collected: no IP address is stored; rate limiting keeps only a\nshort-lived salted hash that cannot be read back to an address and expires within\nminutes. There is no cookie, no user agent, no referrer and no profile. What is\nstored is a number per post and a number per day.<\/p>\n\n<h3>External services<\/h3>\n\n<p>This plugin is a client for <strong>Burnpedia<\/strong> (https:\/\/burnpedia.app), a Pinterest\nscheduling service we operate. It is used for <strong>one optional feature<\/strong>: the three\nextra columns on the Analytics screen showing how your own Pins for these posts\nperform.<\/p>\n\n<p><strong>Nothing is sent anywhere until you save a Burnpedia API key.<\/strong> With no key\nsaved, the plugin makes no outbound request of any kind. There is no telemetry,\nno analytics, no phone-home and no third-party asset \u2014 every script and style in\nthis plugin is served from your own site, and the click counter talks to your own\nsite and nothing else.<\/p>\n\n<p>When a key <strong>is<\/strong> saved, these requests are made, and only these:<\/p>\n\n<ul>\n<li><code>GET https:\/\/burnpedia.app\/api\/v1\/me<\/code> \u2014 when an administrator opens the\nAnalytics or Account screen, or presses <strong>Check connection<\/strong>. Sends: your API\nkey. Receives: your plan, and whether a Pinterest account is connected.<\/li>\n<li><code>GET https:\/\/burnpedia.app\/api\/v1\/analytics\/site<\/code> \u2014 when an administrator opens\nthe Analytics screen. Sends: your API key and this website's domain name.\nReceives: impressions, saves and outbound clicks for the Pins you published\nthrough Burnpedia for this website, over the last 30 days.<\/li>\n<\/ul>\n\n<p>Both are read-only, both are made from your server, and both happen only while an\nadministrator is looking at one of this plugin's own screens. Every request also\ncarries a header naming the plugin and its version, so we can tell which version\nof the plugin a request came from.<\/p>\n\n<p>Burnpedia's terms: https:\/\/burnpedia.app\/terms\nBurnpedia's privacy policy: https:\/\/burnpedia.app\/privacy<\/p>\n\n<p><strong>Pinterest itself is never contacted by this plugin.<\/strong> The save button opens\nPinterest's own save dialog in the visitor's browser when the visitor clicks it,\nexactly like following a link; the plugin sends nothing to Pinterest and loads\nnothing from it.<\/p>\n\n<p>Burnpedia is our own service and is not affiliated with Pinterest, Inc.<\/p>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>That is it \u2014 the button is already on the images in your posts, and readers\ncan save to Pinterest in one press.<\/li>\n<li>Open <strong>Save Button<\/strong> in the menu to see which images readers are saving.<\/li>\n<\/ol>\n\n<p>To change where the button sits, how big it is, or which post types it appears\non, go to <strong>Save Button \u2192 Button<\/strong>.<\/p>\n\n<p>The three extra Pinterest columns are optional. If you want them, go to <strong>Save\nButton \u2192 Account<\/strong>, follow the link to create a free Burnpedia account, and paste\nin the API key it gives you.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20an%20account%3F\"><h3>Do I need an account?<\/h3><\/dt>\n<dd><p>No. The button, the counting and the whole analytics screen work with no account\nof any kind, and nothing leaves your site.<\/p>\n\n<p>A free Burnpedia account is needed for exactly one thing: the three columns\nshowing how <strong>your own<\/strong> Pins for those posts are doing on Pinterest.<\/p><\/dd>\n<dt id=\"do%20you%20collect%20any%20visitor%20data%3F\"><h3>Do you collect any visitor data?<\/h3><\/dt>\n<dd><p>No visitor data is collected: no IP address is stored; rate limiting keeps only a\nshort-lived salted hash that cannot be read back to an address and expires within\nminutes. No cookie is set, no user agent or referrer is kept, and nothing about a\nreader is ever sent off your server.<\/p><\/dd>\n<dt id=\"is%20this%20a%20pin%20it%20button%3F\"><h3>Is this a Pin It button?<\/h3><\/dt>\n<dd><p>It does the same job. Pinterest's original Pin It button was a script you loaded\nfrom Pinterest; this is a save button your own site draws, so nothing is fetched\nfrom Pinterest and nothing about your readers is sent anywhere. Pressing it opens\nthe same save window.<\/p>\n\n<p>If you already run Pinterest's own Pin It button (<code>pinit.js<\/code>), this plugin\ndetects it and stays out of the way rather than putting two buttons on one image.<\/p><\/dd>\n<dt id=\"can%20i%20turn%20the%20hover%20off%20and%20show%20the%20button%20all%20the%20time%3F\"><h3>Can I turn the hover off and show the button all the time?<\/h3><\/dt>\n<dd><p>Yes \u2014 <strong>Save Button \u2192 Button \u2192 When it shows<\/strong>. Hover is the default on a\ndesktop because a button that is always visible sits on top of the photograph\nyou want people to look at. On phones and tablets it is always shown either way,\nbecause there is no hovering with a finger.<\/p><\/dd>\n<dt id=\"why%20don%27t%20i%20see%20the%20button%3F\"><h3>Why don't I see the button?<\/h3><\/dt>\n<dd><p>The usual reasons, in the order they turn out to be true:<\/p>\n\n<ol>\n<li><strong>A page cache has not been cleared yet.<\/strong> Purge it and reload.<\/li>\n<li><strong>Pinterest's own widget is on the page.<\/strong> If <code>pinit.js<\/code> is loaded \u2014 often by\na tag manager \u2014 this plugin steps aside rather than drawing a second button.<\/li>\n<li><strong>The image is smaller than the minimum.<\/strong> The default skips anything under\n200 pixels in either direction, which is what keeps buttons off icons and\nauthor photos. Lower it under <strong>Save Button \u2192 Button<\/strong>.<\/li>\n<li><strong>The image, or something around it, carries an excluded class<\/strong> \u2014 <code>no-save<\/code>,\none you added yourself, or Pinterest's <code>data-pin-nopin<\/code> attribute.<\/li>\n<li><strong>The post type is switched off<\/strong>, or the theme prints the post body without\nrunning WordPress's own content filter, which some page builders do.<\/li>\n<\/ol><\/dd>\n<dt id=\"why%20is%20the%20click%20count%20zero%3F\"><h3>Why is the click count zero?<\/h3><\/dt>\n<dd><p>Almost always a security plugin. Several of them switch the WordPress REST API\noff for logged-out visitors, and that is the path the count travels on \u2014 so the\nbutton still works, and the number never moves.<\/p>\n\n<p>There is a <strong>Send a test click<\/strong> button on the Analytics screen that sends one\nreal click along exactly the same path a reader's browser uses, without your\nlogin. It answers the question in about a second.<\/p><\/dd>\n<dt id=\"does%20it%20slow%20my%20site%20down%3F\"><h3>Does it slow my site down?<\/h3><\/dt>\n<dd><p>One deferred JavaScript file of about 5 KB over the wire and one stylesheet\nunder 2 KB, both served from your own site, with no jQuery, no framework and no\nexternal request at all. The buttons are drawn over your images rather than\ninserted into them, so the page does not move when they appear.<\/p><\/dd>\n<dt id=\"will%20it%20change%20my%20posts%3F\"><h3>Will it change my posts?<\/h3><\/dt>\n<dd><p>No. It never edits your content. The buttons are drawn in a layer above the page,\nwhich is also why full-width images stay full width.<\/p><\/dd>\n<dt id=\"which%20image%20gets%20saved%3F\"><h3>Which image gets saved?<\/h3><\/dt>\n<dd><p>The largest one your site offers. WordPress makes several sizes of every image\nyou upload, and a browser on a phone downloads a small one \u2014 saving that copy\nwould leave a phone-sized Pinterest image on somebody's board forever. This\nplugin reads the whole set and hands over the biggest, so what people save is\nalways the sharp copy.<\/p><\/dd>\n<dt id=\"can%20i%20stop%20it%20on%20certain%20images%3F\"><h3>Can I stop it on certain images?<\/h3><\/dt>\n<dd><p>Yes, four ways: add the class <code>no-save<\/code>, add <code>data-pin-nopin<\/code> to the image, add\nyour own class names under <strong>Save Button \u2192 Button<\/strong>, or raise the minimum image\nsize.<\/p><\/dd>\n<dt id=\"is%20my%20count%20exact%3F\"><h3>Is my count exact?<\/h3><\/dt>\n<dd><p>It is honest, and it is not a billing system. Presses are counted as they arrive,\nwith two limits that keep somebody from inflating it: no more than 30 clicks a\nminute from one visitor, and no more than 2,000 a day on any one post. Your own\nclicks, while you are logged in, are never counted.<\/p><\/dd>\n<dt id=\"what%20happens%20if%20i%20delete%20the%20plugin%3F\"><h3>What happens if I delete the plugin?<\/h3><\/dt>\n<dd><p>Everything it wrote is removed: the settings, the counts, the daily series and\nthe caches. Your posts and your images are not touched.<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>1.0.1<\/h4>\n\n<ul>\n<li>Renamed the plugin to Burnpedia Image Save Button Analytics.<\/li>\n<li>Rewrote the description: removed comparative wording, and said plainly what\nthe optional Burnpedia connection adds and where to get a key.<\/li>\n<\/ul>\n\n<h4>1.0.0<\/h4>\n\n<ul>\n<li>First release.<\/li>\n<\/ul>","raw_excerpt":"Adds a save-to-Pinterest button to your post images on hover, and shows which images readers save. Free click analytics, no account needed.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361886","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361886"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lalokupfer"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361886"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361886"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361886"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361886"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361886"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361886"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}