{"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-12T21:51:18","modified_gmt":"2026-09-12T21:51:18","slug":"burnpedia-image-save-button-analytics","status":"publish","type":"plugin","link":"https:\/\/su.wordpress.org\/plugins\/burnpedia-image-save-button-analytics\/","author":23546237,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"1.10.0","stable_tag":"1.10.0","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-12 21:51:18","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":327,"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},"1.1.0":{"tag":"1.1.0","author":"lalokupfer","date":"2026-09-04 06:28:48","revision":3680711},"1.10.0":{"tag":"1.10.0","author":"lalokupfer","date":"2026-09-12 21:51:18","revision":3693150},"1.2.0":{"tag":"1.2.0","author":"lalokupfer","date":"2026-09-04 07:00:40","revision":3680766},"1.3.0":{"tag":"1.3.0","author":"lalokupfer","date":"2026-09-04 07:30:35","revision":3680800},"1.4.0":{"tag":"1.4.0","author":"lalokupfer","date":"2026-09-06 06:42:32","revision":3683057},"1.5.0":{"tag":"1.5.0","author":"lalokupfer","date":"2026-09-06 13:13:22","revision":3683470},"1.6.0":{"tag":"1.6.0","author":"lalokupfer","date":"2026-09-06 13:43:02","revision":3683491},"1.7.0":{"tag":"1.7.0","author":"lalokupfer","date":"2026-09-06 14:32:08","revision":3683522},"1.8.0":{"tag":"1.8.0","author":"lalokupfer","date":"2026-09-06 21:18:37","revision":3683964},"1.8.1":{"tag":"1.8.1","author":"lalokupfer","date":"2026-09-10 09:20:57","revision":3689624},"1.8.2":{"tag":"1.8.2","author":"lalokupfer","date":"2026-09-12 07:14:45","revision":3692412},"1.9.0":{"tag":"1.9.0","author":"lalokupfer","date":"2026-09-12 15:51:55","revision":3692889},"1.9.1":{"tag":"1.9.1","author":"lalokupfer","date":"2026-09-12 21:03:47","revision":3693135}},"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","1.1.0","1.10.0","1.2.0","1.3.0","1.4.0","1.5.0","1.6.0","1.7.0","1.8.0","1.8.1","1.8.2","1.9.0","1.9.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":3693149,"resolution":"3","location":"assets","locale":"","width":2880,"height":1800},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3693134,"resolution":"4","location":"assets","locale":"","width":2880,"height":1800},"screenshot-5.png":{"filename":"screenshot-5.png","revision":3693134,"resolution":"5","location":"assets","locale":"","width":2880,"height":1800},"screenshot-6.png":{"filename":"screenshot-6.png","revision":3693149,"resolution":"6","location":"assets","locale":"","width":656,"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\" numbers a connected Burnpedia account adds.","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.","6":"The hidden Pin image on a post: a tall graphic readers never see, which the\nsave button hands to Pinterest instead of the photograph they pressed."}},"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=3693149","caption":"The Analytics screen: which posts readers save, a 30-day trend, and the\n\"Your Pins on Pinterest\" numbers a connected Burnpedia account adds."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-4.png?rev=3693134","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=3693134","caption":"The Account screen, where the optional free connection lives."},{"src":"https:\/\/ps.w.org\/burnpedia-image-save-button-analytics\/assets\/screenshot-6.png?rev=3693149","caption":"The hidden Pin image on a post: a tall graphic readers never see, which the\nsave button hands to Pinterest instead of the photograph they pressed."}],"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>And which image, not just which post.<\/strong> Open <strong>Saved images<\/strong> under any post\nand each picture on it is listed with a thumbnail and its own count. On a\nroundup or a gallery post that answers the question a single number cannot:\nof the six photographs on the page, which one do readers actually want?<\/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.<\/li>\n<li><strong>You choose what the description says.<\/strong> A box in the post editor sets the\nPin description for every image in that post, so what a reader saves carries\nthe sentence you wrote rather than alt text meant for a screen reader. Leave\nit empty and the alt text is used, exactly as before.<\/li>\n<li><strong>A hidden Pin image, if you make one.<\/strong> Attach a tall image built for\nPinterest \u2014 the sort with your headline written across it \u2014 and the save\nbutton hands Pinterest that picture instead of the photograph the reader\npressed. Nobody sees it on the page. Set one per post, or none at all.<\/li>\n<li><strong>A list of the images with no alt text.<\/strong> When an image has no alt text,\nthe Pin a reader saves from it is described with the post's title instead, so\nevery photograph in that post goes to Pinterest carrying the same sentence.\nThe Analytics screen lists the posts where that happens \u2014 the ones readers\nsave most first \u2014 with a link straight to each post. It works from the day you\ninstall it, before anybody has saved anything, and it only reads your own\nposts.<\/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>Already using another pin button?<\/h4>\n\n<p>If <strong>jQuery Pin It Button for Images<\/strong> is installed on this site, the Save Button\nsettings screen offers to bring its settings across in one press \u2014 the button\ncorner, the classes you excluded, and the posts you switched it off on. Nothing\nof theirs is changed and it is not deactivated: that stays your decision, and you\ncan run both while you compare them. Settings that have no equivalent here are\nlisted rather than guessed at.<\/p>\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. No account is needed and nothing is\never sent anywhere.<\/p>\n\n<p>The only thing on this screen that is not ours to give away free is the\n<strong>per-post<\/strong> Pinterest breakdown, which comes from a different product and is\ndescribed below \u2014 everything the Save Button itself measures is unlimited.<\/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 an 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 <strong>Pinterest analytics<\/strong> for <strong>your own\nPins<\/strong> to those same posts \u2014 impressions, saves and outbound clicks. It answers\nthe question the click count cannot: the images readers wanted to save, next to\nhow the Pins you published yourself actually performed.<\/p>\n\n<p>A free Burnpedia account shows the <strong>site-wide total<\/strong> of those three numbers.\nThe <strong>per-post<\/strong> columns \u2014 which of these posts your Pins earn on \u2014 are on\nBurnpedia's paid plans; the screen says so and links to them. Getting the key\nitself is free either way, and you can connect this site in one press without\ncopying a key at all.\nWithout a key the plugin makes no outbound request except that one connection,\nwhich happens only when you press the button for it, and nothing on the screens\nabove changes. Exactly what is sent, and when, is listed under <strong>External\nservices<\/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 under 8 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, a number per day, and a number for each image on a\npost. The image is identified by a short code this plugin works out from the\nimage's own web address, never by anything about the person who saved it.<\/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 unless you ask for it.<\/strong> With no API key saved and\nthe install count switched off \u2014 which is how the plugin arrives \u2014 it makes no\noutbound request of any kind. There is no analytics, no phone-home you did not\nswitch on, no advertising and no third-party asset: 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>There are two separate things you can switch on, and neither is on by default.\nOne is an API key, which adds the Pinterest numbers. The other is the install\ncount below, which is not required for anything and unlocks nothing \u2014 it exists\nonly so we can tell how many sites use this plugin.<\/p>\n\n<p><strong>Connecting this site in one press (optional).<\/strong> On the <strong>Account<\/strong> screen you\ncan press <strong>Connect this site to Burnpedia<\/strong> instead of copying an API key by\nhand. It is the only thing in the plugin that makes a request before a key\nexists, and it happens only after an administrator presses that button:<\/p>\n\n<ul>\n<li>Your browser opens <code>https:\/\/burnpedia.app\/connect\/wordpress<\/code>, carrying this\nsite's address and its title, so the approval screen can name the site you are\nabout to connect. It also carries a random one-time request ID and a\nfingerprint of a secret that never leaves your server.<\/li>\n<li>After you approve it there, your site makes one\n  POST https:\/\/burnpedia.app\/api\/site-connect\/claim request, sending that\nrequest ID and the secret, and receives an API key which is saved for you. The\nkey is never shown in your browser.<\/li>\n<li>The request expires after fifteen minutes and can be collected only once. If\nyou press Cancel, or never approve it, nothing is sent and nothing is created.<\/li>\n<li>You never have to use it. Pasting a key by hand still works exactly as before,\nand is the way to connect a site that cannot reach the internet.<\/li>\n<\/ul>\n\n<p><strong>The reader-click counting is not involved in any of this and never contacts\nanyone<\/strong>, with or without a key.<\/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><p><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.<\/p><\/li>\n<li><p><code>POST https:\/\/burnpedia.app\/api\/v1\/events\/save-clicks<\/code> \u2014 at most once every\ntwelve hours, when an administrator opens the Analytics screen. Sends: your API\nkey, this website's address, and how many times readers pressed Save on each of\nthe last 90 days \u2014 a date and a whole number, nothing else. Receives: how many\ndays were recorded. It puts those counts beside your Pin results in your\nBurnpedia dashboard. <strong>Nothing about any reader is in it.<\/strong> The plugin stores\nno IP address, no user agent, no referrer and no cookie, so there is nothing\nabout a visitor for it to send. Switch it off under <strong>Save Button \u2192 Account<\/strong>\nand the counts never leave your server.<\/p><\/li>\n<\/ul>\n\n<p><strong>The install count (optional, off by default).<\/strong> WordPress.org does not tell\nplugin authors how many sites are running their plugin \u2014 for this plugin it\npublishes no figure at all. The plugin asks you once, in a dismissible notice,\nand you can change the answer at any time under <strong>Save Button \u2192 Account<\/strong>.\nSaying no sends nothing and closing the box without answering also sends\nnothing. If you switch it on, this site sends a short report:<\/p>\n\n<ul>\n<li><code>POST https:\/\/burnpedia.app\/api\/plugin-insights<\/code> \u2014 once when you switch it on,\nthen at most once a week while an administrator is using wp-admin, once if you\ndeactivate the plugin, and once if you delete it. Sends exactly nine things: a\nrandom ID generated on this site, which plugin and which version, which of\nthose four events it is, your WordPress version, your PHP version, your site\nlanguage, whether this is a multisite network, and whether an API key is saved\n(true or false \u2014 never the key). Receives: nothing your site uses.<\/li>\n<\/ul>\n\n<p><strong>Your website address is not in that report and is never sent, so we cannot\ntell which website you are.<\/strong> The random ID is made up on your server and means\nnothing outside it. Switch the setting off and the ID is deleted, so counting\nstops and a later change of mind cannot be joined to it. It is off until you\nchoose it, no feature depends on it, and nothing about any reader or any logged-in\nuser is in it.<\/p>\n\n<p>Every request above is made from your server, never from a reader's browser,\nand every one happens only while an administrator is signed in to wp-admin \u2014 a\nvisitor reading your site can never cause any of them. Each also carries a header\nnaming the plugin and its version, so we can tell which version a request came\nfrom.<\/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 Pinterest numbers are optional. If you want them, go to <strong>Save Button \u2192\nAccount<\/strong> and press <strong>Connect this site to Burnpedia<\/strong>. Approve it in the tab\nthat opens \u2014 a free account takes a moment to make if you do not have one \u2014 and\nyour site collects its own key. There is nothing to copy or paste. A free\naccount shows the site-wide total; the per-post columns are on the paid plans.<\/p>\n\n<p>If your site cannot reach the internet, or you would rather do it yourself, the\nsame screen still takes a key you paste in by hand.<\/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 Burnpedia account is needed for exactly one thing: showing how <strong>your own<\/strong>\nPins for those posts are doing on Pinterest. A free account shows the site-wide\ntotal of impressions, saves and outbound clicks; the per-post columns are on\nBurnpedia's paid plans.<\/p><\/dd>\n<dt id=\"i%20already%20use%20jquery%20pin%20it%20button%20for%20images.%20can%20i%20switch%3F\"><h3>I already use jQuery Pin It Button for Images. Can I switch?<\/h3><\/dt>\n<dd><p>Yes, and you do not have to set everything up again. With that plugin on the\nsite, Save Button detects its settings and offers to copy the ones that have an\nequivalent here \u2014 in one press, with a list of exactly what will change shown\nfirst. It never edits their settings and never deactivates them, so you can run\nboth side by side and keep whichever you prefer.<\/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 under 8 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%20choose%20what%20the%20pin%20description%20says%3F\"><h3>Can I choose what the Pin description says?<\/h3><\/dt>\n<dd><p>Yes. Every post has a <strong>Save Button (Burnpedia)<\/strong> box in the editor sidebar with\none field: the Pin description for that post's images. Whatever you type there is\nwhat Pinterest fills in when a reader saves any image from the post.<\/p>\n\n<p>Leave it empty and nothing changes \u2014 the image's own alt text is used, and then\nthe post title. An individual image that carries Pinterest's own\n    data-pin-description attribute keeps that, because it is a more specific\nchoice than a whole-post default.<\/p>\n\n<p>The box appears for anyone who can publish that post type. It is not shown to\ncontributors, because the text goes out on a public Pin under your site's name.<\/p><\/dd>\n<dt id=\"which%20of%20my%20images%20are%20missing%20alt%20text%3F\"><h3>Which of my images are missing alt text?<\/h3><\/dt>\n<dd><p>Open <strong>Save Button \u2192 Analytics<\/strong> and look for <strong>Images that would be Pinned with\nno description<\/strong>. It lists the posts whose images have no alt text \u2014 ranked by\nhow often readers save from them, or by date if nobody has saved anything yet \u2014\nand says how many images in each need it. Each post title links to its editor.<\/p>\n\n<p>It matters for Pinterest specifically: an image with no alt text is saved with\nthe post's title as its description, so a post with six photographs sends six\nPins with identical text. Writing alt text fixes that, and it also helps people\nusing screen readers and search engines. A Pin description set on the post\nremoves it from the list too, but it gives every image in that post the same\nwords again.<\/p>\n\n<p>The list reads only your own posts. It sends nothing anywhere.<\/p><\/dd>\n<dt id=\"can%20i%20use%20a%20separate%20image%20for%20pinterest%3F\"><h3>Can I use a separate image for Pinterest?<\/h3><\/dt>\n<dd><p>Yes. Open a post, find the <strong>Save Button (Burnpedia)<\/strong> box and choose a <strong>hidden\nPin image<\/strong>. It is usually a tall graphic, often 1000 by 1500, with the headline\nset across it \u2014 the shape that works in a Pinterest feed and would look wrong in\nthe middle of an article.<\/p>\n\n<p>Readers never see it. When somebody presses the save button anywhere on that\npost, Pinterest opens with that graphic rather than the photograph they pressed,\nand with your Pin description. A copy of it is also placed in the page, hidden,\nwhich is where Pinterest's own browser tools look for images to offer.<\/p>\n\n<p>Two honest notes. Their browser does download it even though they never see it \u2014\nthat is exactly what makes it findable, so only set one on posts where you want\nit saved. And the count still records which photograph they pressed, because\n\"which picture makes people save\" is worth knowing separately from what gets\nsaved.<\/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=\"can%20i%20turn%20a%20most-saved%20image%20into%20a%20pin%3F\"><h3>Can I turn a most-saved image into a Pin?<\/h3><\/dt>\n<dd><p>If you also run our scheduling plugin, yes: every row in the table gets a\n<strong>Schedule a Pin<\/strong> button that opens that post at the scheduling panel, so the\nimage readers are already saving is one click from being queued.<\/p>\n\n<p>Nothing appears if you do not have that plugin. This one never suggests\ninstalling anything.<\/p><\/dd>\n<dt id=\"does%20anything%20about%20my%20readers%20leave%20my%20site%3F\"><h3>Does anything about my readers leave my site?<\/h3><\/dt>\n<dd><p>No, and there is nothing that could. The plugin never stores an IP address, a\nuser agent, a referrer or a cookie, so no visitor detail exists here to be sent.<\/p>\n\n<p>If you have connected a Burnpedia account, the plugin sends your <strong>daily\ntotals<\/strong> \u2014 this website's address, a date and a whole number per day \u2014 so those\ncounts can sit beside your Pin results in your dashboard. It goes at most once\nevery twelve hours, only while you are on the Analytics screen. You can switch it\noff under <strong>Save Button \u2192 Account<\/strong>, and with no API key saved nothing is sent at\nall.<\/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.10.0<\/h4>\n\n<ul>\n<li>New: <strong>Images that would be Pinned with no description<\/strong>, on the Analytics\nscreen. An image with no alt text is saved to Pinterest with the post's title\nas its description, so every photo in that post gets the same text. The list\nshows which posts that happens on and links to each one.<\/li>\n<li>It works on the day you install it: with no saves yet it checks your most\nrecent posts, and once readers save, the posts they save most come first.<\/li>\n<li>A post with its own Pin description is not listed, since that description is\nused for every image in it. Reads only your own posts; sends nothing anywhere.<\/li>\n<\/ul>\n\n<h4>1.9.1<\/h4>\n\n<ul>\n<li>Corrected the plugin's own screens, which still said a <strong>free<\/strong> Burnpedia\naccount fills the three per-post \"Your Pins on Pinterest\" columns. It does\nnot, and the listing was corrected in 1.8.2 while the plugin was not \u2014 so the\nonly people still being told the wrong thing were the ones who had already\ninstalled it. A free key shows the totals for your whole website; the per-post\ncolumns are on Burnpedia's paid plans. Getting a key is free either way, and\nnothing about what the Save Button itself measures has changed.<\/li>\n<li>The same correction on the greyed-out columns, on the Account screen and in\nthe reminder notice \u2014 all three places where you decide whether to connect.<\/li>\n<\/ul>\n\n<h4>1.9.0<\/h4>\n\n<ul>\n<li>The plugin now asks, once, whether it may count this site \u2014 in a notice you\ncan answer with one press instead of only on a settings screen you had to go\nlooking for. It asks a single time and then never again, whatever you answer.<\/li>\n<li>Saying no sends nothing at all, and closing the box without answering is not\ntaken as an answer either \u2014 it just stops asking. You can still change your\nmind either way under <strong>Save Button \u2192 Account<\/strong>.<\/li>\n<li>Nothing new is sent and no new address is contacted: this is the same\noptional, off-by-default install count as before, with the question put where\npeople will actually see it.<\/li>\n<\/ul>\n\n<h4>1.8.2<\/h4>\n\n<ul>\n<li>Corrected the listing. This page said a free Burnpedia account fills in the\nthree \"Your Pins on Pinterest\" columns. It does not: a free account shows the\nsite-wide total of impressions, saves and outbound clicks, and the per-post\ncolumns are on Burnpedia's paid plans - which is what the plugin's own screen\nhas always said. Getting the key is still free, and so is everything the Save\nButton itself measures.<\/li>\n<li>No code change.<\/li>\n<\/ul>\n\n<h4>1.8.1<\/h4>\n\n<ul>\n<li>The listing now mentions two things the plugin has been doing for a while and\nnever said out loud: that the Analytics screen breaks saves down <strong>per image<\/strong>,\nnot just per post, and that it can <strong>bring your settings over from jQuery Pin\nIt Button for Images<\/strong> in one press.<\/li>\n<li>No functional change. Nothing in the plugin behaves differently.<\/li>\n<\/ul>\n\n<h4>1.8.0<\/h4>\n\n<ul>\n<li>New: a <strong>hidden Pin image<\/strong> per post. Attach the tall, headline-across-it\ngraphic you made for Pinterest, and the save button hands Pinterest that\npicture instead of the photograph the reader pressed. Readers never see it on\nthe page.<\/li>\n<li>Pinterest's own <code>data-pin-media<\/code> attribute is honoured too, so a single image\ncan override the whole post.<\/li>\n<li>The Pin description follows the graphic: when one is set, the pressed\nphotograph's alt text is no longer offered, because it describes a different\npicture.<\/li>\n<li>The click count is unchanged \u2014 it still records which photograph a reader\npressed, which is a different question from what got saved.<\/li>\n<li>Note that readers' browsers do download the hidden image, which is what makes\nit findable. It is only ever added to posts where you set one.<\/li>\n<\/ul>\n\n<h4>1.7.0<\/h4>\n\n<ul>\n<li>New: the Analytics screen now shows <strong>which image<\/strong> on a post readers saved,\nnot just how many saves the post got. Open \"Saved images\" under any post title\nfor a thumbnail of each one and its own count.<\/li>\n<li>On a roundup or a gallery post this answers the question the old number could\nnot: of the six photos on the page, which one do readers actually want?<\/li>\n<li>Counts recorded before this update stay on the post as a whole. They are\nreported separately rather than split between images, because nothing can know\nafter the fact which image an old save was on.<\/li>\n<\/ul>\n\n<h4>1.6.0<\/h4>\n\n<ul>\n<li>New: if you are switching from <strong>jQuery Pin It Button for Images<\/strong>, the Button\nscreen now offers to copy its settings across \u2014 where the button sits, whether\nit shows on hover, which classes to skip and the minimum image size. One press,\nand you can say no.<\/li>\n<li>It never changes or switches off that plugin: it only reads its settings, and\nit tells you plainly which of them have no equivalent here rather than quietly\ndropping them.<\/li>\n<li>A setting you have already changed yourself is never overwritten.<\/li>\n<\/ul>\n\n<h4>1.5.0<\/h4>\n\n<ul>\n<li>New: <strong>Connect this site to Burnpedia<\/strong> \u2014 one button on the Account screen.\nApprove it in the tab that opens and your site collects its own API key. There\nis nothing to copy, nothing to paste, and the key is never shown in a browser.<\/li>\n<li>Pasting a key by hand still works exactly as before, and is still the way to\nconnect a site that cannot reach the internet.<\/li>\n<li>The button, the counting and the analytics table are unchanged, still free,\nand still contact nobody.<\/li>\n<\/ul>\n\n<h4>1.4.0<\/h4>\n\n<ul>\n<li>New: an optional install count under Save Button \u2192 Account. WordPress.org\npublishes no install figure for this plugin, so we genuinely cannot tell how\nmany sites use it. Switch this on and your site sends a random ID once a week\nso it can be counted. Your website address is never sent. It is off unless you\nturn it on, nothing depends on it, and turning it off deletes the ID.<\/li>\n<\/ul>\n\n<h4>1.3.0<\/h4>\n\n<ul>\n<li>If you also run our scheduling plugin, every row in the Analytics table now\nhas a <strong>Schedule a Pin<\/strong> button that opens that post straight at the panel\nwhere you queue it. The image your readers keep saving is one click from being\na Pin you posted on purpose.<\/li>\n<li>Nothing changes, and nothing is shown, on a site without that plugin.<\/li>\n<\/ul>\n\n<h4>1.2.0<\/h4>\n\n<ul>\n<li>Your daily click totals can now appear in your Burnpedia dashboard, beside\nwhat your own Pins for those pages earned \u2014 the first time both halves of that\npicture have been in one place. Optional, off with one tick under <strong>Save\nButton \u2192 Account<\/strong>, and it sends a date and a number and nothing else.<\/li>\n<li>Documented the new request under <strong>External services<\/strong>.<\/li>\n<\/ul>\n\n<h4>1.1.0<\/h4>\n\n<ul>\n<li>New: a <strong>Pin description<\/strong> box in the post editor. It sets the description\nPinterest opens with when a reader saves any image from that post, so you are\nno longer limited to alt text written for a screen reader. Leave it empty and\nthe previous behaviour is unchanged.<\/li>\n<li>The plugin's internal version number had been left at 1.0.0 through the 1.0.1\nrelease, so browsers kept serving the old copy of the stylesheet after an\nupdate. Fixed, and a test now compares the two.<\/li>\n<\/ul>\n\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:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/361886","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=361886"}],"author":[{"embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/lalokupfer"}],"wp:attachment":[{"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=361886"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=361886"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=361886"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=361886"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=361886"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/su.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=361886"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}