See it on plugupp.com<\/a><\/li>\n<\/ul>\n\nExternal services<\/h3>\n\n
This plugin relies on the Freemius platform. Three separate calls are involved, and they are described here in full, followed by one call to WordPress.org on two admin screens.<\/p>\n\n
1. Reading your prices from the Freemius API<\/strong><\/p>\n\nYour server requests https:\/\/api.freemius.com\/v1\/products\/{product ID}\/pricing.json<\/code>. It sends the numeric Freemius product ID in the URL and your Freemius API Bearer Authorization Token in an authorization header. Nothing else is sent, and nothing about your visitors is sent. The call happens only on your server, never during a visitor's page view: when you press Refresh now or Test token in the admin, when a webhook arrives, when a scheduled refresh runs, and whenever you save the product. If no token is configured, the call is never made.<\/p>\n\nWhen a save has proved the token, your server also reads the product's secret key from https:\/\/api.freemius.com\/v1\/products\/{product ID}.json<\/code> (it signs every webhook delivery; it is stored on your site and never shown or logged) and registers this site's webhook with the same API: it lists the product's webhooks at https:\/\/api.freemius.com\/v1\/products\/{product ID}\/webhooks.json<\/code>, then creates one for this site or brings its own up to date, and removes its own when you delete the product. The only thing sent is this site's webhook URL and the six event types it subscribes to. Webhooks pointing anywhere else are never touched.<\/p>\n\n2. Choosing the visitor's currency<\/strong><\/p>\n\nThe visitor's browser requests https:\/\/checkout.freemius.com\/geo.json<\/code>. The request carries nothing beyond the request itself, which necessarily includes the visitor's IP address as any web request does. The answer is a currency code, which the browser keeps for one hour so the call is not repeated on every page. This happens only on pages where a price or a currency toggle has been rendered, and only when the visitor has not already chosen a currency.<\/p>\n\n3. The overlay checkout<\/strong><\/p>\n\nWhen you switch the Checkout setting to \"Open the checkout in an overlay\", the visitor's browser loads the Freemius checkout script from https:\/\/checkout.freemius.com\/js\/v1\/<\/code> so the checkout can open in place. With the default hosted setting, this script is never loaded and your buy buttons remain ordinary links.<\/p>\n\n4. The More from PlugUpp panel<\/strong><\/p>\n\nOn this plugin's own Products and Settings screens, and nowhere else, your site asks the WordPress.org plugins API (https:\/\/api.wordpress.org\/plugins\/info\/1.2\/<\/code>) for the list of plugins published by the PlugUpp account, once a day, and shows them as cards with their WordPress.org icons (served from https:\/\/ps.w.org\/<\/code>). The request carries the author name and nothing about your site. This is the same API WordPress itself uses for the Add New plugin screen and for update checks. If it cannot be reached, a short built-in list is shown instead.<\/p>\n\nWebhooks are inbound.<\/strong> A webhook is a call from Freemius to your site, not from your site to Freemius. Your site never initiates it and sends nothing. Each delivery is verified twice before it is acted on: the URL carries a key this plugin generated, and the body carries a signature checked against your product's secret key.<\/p>\n\nFreemius is operated by Freemius, Inc. Their terms of service are at https:\/\/freemius.com\/terms\/ and their privacy policy is at https:\/\/freemius.com\/privacy\/.<\/p>\n\n\n
\n- Install the plugin through Plugins, Add New, or upload the plugin folder to
wp-content\/plugins\/<\/code>, then activate it.<\/li>\n- Open Freemius Pricing in the WordPress admin menu. It lands on Products.<\/li>\n
- Press Add product and fill in the numeric Freemius product ID and its API Bearer Authorization Token, from the Freemius dashboard under the product, then Settings, then Keys. Nothing else is typed: the product's name arrives with the prices, and the product secret key, which signs webhooks, is read with the token. Both the token and the secret come from the Freemius dashboard, under the product, then Settings, then Keys.<\/li>\n
- Press Test token to check it, then Add product to save.<\/li>\n
- You are now on the product's own screen, and the webhook is already registered with Freemius: the save did it, and the Status list says so. If it could not be, the same line says why and shows the URL and the six events to paste into the Freemius dashboard, under the product, then Webhooks, then Listeners, yourself.<\/li>\n
- The same screen has a Shortcodes section: the shortest working form of each shortcode with what it renders for your product, then every plan and pricing row with a ready-made price shortcode and button shortcode on each line. Copy the one you want into a page. In the block editor, insert Freemius price, Freemius buy button or Freemius currency toggle from the inserter under Widgets instead, and pick the row from dropdowns.<\/li>\n
- Freemius Pricing, then Settings holds the site-wide choices: default currency, whether a visitor's currency choice is remembered, hosted or overlay checkout, how stale prices may get before a background refresh, and the default label and CSS classes for buy buttons. Freemius Pricing, then Logs shows what the plugin has been doing.<\/li>\n<\/ol>\n\n\n
\nDo I need Freemius's own WordPress plugin as well?<\/h3><\/dt>\nNo. This plugin talks to the Freemius API directly and does not depend on any other plugin. The two can coexist if you already run the official one. This plugin renders its own blocks and shortcodes, and the one thing it does to the rest of the page is add the visitor's currency to any link pointing at the Freemius checkout, whoever rendered it, so a button you built yourself opens in the currency the visitor was reading. With the overlay checkout setting on, it also opens those links in the overlay. Nothing else on the page is touched.<\/p><\/dd>\n
Where do I get the API Bearer Authorization Token?<\/h3><\/dt>\nIn the Freemius dashboard, open the product, then Settings, then Keys. The token this plugin needs is the one Freemius labels API Bearer Authorization Token. It is read only for this purpose: the plugin makes exactly one kind of request with it, a read of that product's plans and prices. Paste it into the API Bearer Authorization Token field on the product's screen under Freemius Pricing, press Test token, then save. The field is masked, the value is never written to the log, and it is never sent anywhere except to api.freemius.com.<\/p><\/dd>\n
Do I have to set up the webhook?<\/h3><\/dt>\nNo. Saving the product with a working token registers it with Freemius for you, and keeps it up to date on every save; the Status list on the product's screen says so. It is what makes a price change appear in seconds. Without it, a page view notices that the stored prices are older than the refresh interval you set and schedules a background refresh, and a daily job catches anything missed. With it, Freemius tells your site the moment something changes. The webhook URL is generated for you on the product's own screen; it contains a key only your site and your Freemius dashboard know, and every delivery is also checked against your product's secret key before it is acted on.<\/p><\/dd>\n
Freemius said my plan doesn't support creating webhooks. Is the token wrong?<\/h3><\/dt>\nNo. The same token has just fetched your prices and your secret key, and the product is saved and live. Freemius reserves webhooks, along with some other features, for products it considers actively selling, and unlocks them after a few production sales; a product that has not reached that point gets that sentence, from the API and from the dashboard alike, so there is nothing to paste by hand. The plugin says so on the product's screen and marks the save as a warning rather than an error. Until Freemius enables them, the prices refresh on the interval set under Settings, and once a day regardless; every later save tries the registration again, so the webhook appears by itself once Freemius allows it.<\/p><\/dd>\n
Which currencies are supported?<\/h3><\/dt>\nWhatever your product is priced in, taken from the pricing rows the Freemius API returns. The plugin ships symbols for US dollars, euros and pounds sterling, which are the currencies the Freemius pricing API offers; a currency added later still renders, using its three letter code in place of a symbol. The currency toggle lists only the currencies a product is actually sold in, and does not render at all when there is only one.<\/p><\/dd>\n
What happens if the Freemius API is down?<\/h3><\/dt>\nYour prices stay exactly as they are. The stored copy on your site is only ever replaced by a successful fetch, so a failed refresh changes nothing a visitor sees. You get an admin notice saying which product could not be refreshed, and the reason is recorded in the log. A page never waits on the API, so an outage at Freemius cannot slow down or break your site.<\/p><\/dd>\n
Does this work with caching plugins and CDNs?<\/h3><\/dt>\nYes, and it is built for them. Prices are rendered into the page from the copy stored on your site, so a cached page is a correct page. The visitor's currency is applied in their own browser from data already in the HTML, with no request back to your server, so a cached page can never show one visitor another visitor's currency. Nothing here varies the HTML by visitor, which is what would defeat a page cache.<\/p><\/dd>\n
How often are the prices refetched?<\/h3><\/dt>\nOn a webhook, immediately. Otherwise, the first page view after the stored copy passes the refresh interval you set under Freemius Pricing, then Settings schedules a background refresh, and a daily scheduled job refreshes every product regardless. The interval is a backstop for a webhook that never arrived, not a polling frequency: a site nobody visits still refreshes once a day.<\/p><\/dd>\n
What external services does this plugin use?<\/h3><\/dt>\nThe Freemius platform, in three ways. Your server reads your prices from https:\/\/api.freemius.com\/v1\/products\/{product ID}\/pricing.json<\/code>, sending the product ID and your API Bearer Authorization Token and nothing else, and only when you refresh, test a token, receive a webhook or a scheduled refresh runs. The visitor's browser calls https:\/\/checkout.freemius.com\/geo.json<\/code> to work out which currency to show, sending nothing beyond the request itself, and caching the answer for an hour. If you turn on overlay checkout, the visitor's browser also loads the checkout script from https:\/\/checkout.freemius.com\/js\/v1\/<\/code>; with the default hosted checkout it does not. Webhooks run the other way, inbound from Freemius to your site, and each one is verified by both a generated URL key and a body signature. Freemius terms: https:\/\/freemius.com\/terms\/ . Freemius privacy policy: https:\/\/freemius.com\/privacy\/ .<\/p><\/dd>\nAre there blocks, or only shortcodes?<\/h3><\/dt>\nBoth, and they are the same thing. Three blocks under Widgets in the inserter: Freemius price, Freemius buy button and Freemius currency toggle. Each one renders your headline row as soon as it is inserted, and the sidebar fills its Plan, Licences and Billing cycle dropdowns from the rows your product actually sells, so an impossible combination cannot be chosen. They are dynamic blocks: nothing is written into the post, and the page renders through exactly the same code the shortcode of the same name uses, which is why a price in a block and a price in a shortcode can never disagree. Select a Shortcode block holding one of the three and the editor offers to convert it, carrying every attribute across, and the block type menu converts a block back into a shortcode the same way. The shortcodes are not deprecated and are not going anywhere: they are what a page builder, the classic editor, a widget area or a template file wants.<\/p><\/dd>\n
Can I turn a block back into a shortcode?<\/h3><\/dt>\nYes. Select the block, open the block type button at the left of its toolbar and choose Shortcode. You get an ordinary Shortcode block holding the equivalent shortcode, ready for a page builder, a widget area or a template file, and anything left at its default is left out so a block nobody configured becomes a plain [pflp_price]<\/code>. One thing does not survive the trip: styling set in the colour, typography and spacing panels is inline CSS on the block, and a shortcode has nowhere to carry inline CSS. The editor says so once, the first time you convert a styled block. Anything you picked from a preset does survive, because a preset is a class name your theme already defines, and those class names are added to the shortcode's class<\/code> attribute.<\/p><\/dd>\nCan I style the buy button in the editor?<\/h3><\/dt>\nYes. The buy button block carries the WordPress colour, typography, spacing and border panels, a Width setting with the same four choices as the core Buttons block, and the price and the toggle carry colour and typography. A hover effect is one choice for the whole site, under Buttons on the Settings screen, because the panels cannot set one. Underneath, the button still leads with wp-element-button<\/code>, the class WordPress gives its own buttons, so in most block themes it already matches before you change a thing. The Advanced panel's Additional CSS class(es) is the block spelling of the shortcode's class<\/code> attribute, which all three take, and classes are added to the ones the price, button or toggle already carries rather than replacing them.<\/p><\/dd>\nDo I have to write out every attribute?<\/h3><\/dt>\nNo. Every attribute on every shortcode is optional. [pflp_price]<\/code> on its own renders your headline price, and [pflp_button]<\/code> on its own links to the checkout that sells it. Left out, plan<\/code> means the plan Freemius marks as featured (otherwise the first plan that has a price), licenses<\/code> means that plan's lowest numbered tier, and cycle<\/code> means annual, falling through to monthly and then lifetime if that row has no annual price. Name an attribute only where you want something other than that. An attribute you do write is never second-guessed: cycle=\"annual\"<\/code> against a row with no annual price renders nothing rather than quietly showing a monthly figure.<\/p><\/dd>\nHow do I add a buy button?<\/h3><\/dt>\n[pflp_button] renders one, taking the same plan, licences and cycle attributes as a price. It is an ordinary link to your Freemius hosted checkout, carrying the wp-element-button<\/code> class WordPress gives its own buttons, so in most block themes it already matches the rest of your site. label<\/code> sets the words on one button and Settings sets the words on all of them; class<\/code> is there for a theme that needs its own hooks, on all three shortcodes, and id<\/code> on the button; and align=\"center\"<\/code> puts the button in a block of its own and moves it across the line, which all three shortcodes take. As blocks, all three carry the usual alignment buttons in the block toolbar. A button you built yourself still works: the plugin adds the visitor's currency to any link pointing at the Freemius checkout.<\/p><\/dd>\nWhat about the free plan?<\/h3><\/dt>\nNothing from this plugin: a plan with no price has no figure to show and no checkout to link to, so the block's Plan dropdown does not offer it and a shortcode naming it renders nothing. For the free tier of a pricing table, use an ordinary button, the core Buttons block or your theme's, linking to the plugin's download page (its WordPress.org listing, usually). That link is a fixed fact rather than a live price, so there is nothing to keep current.<\/p><\/dd>\n
Can I show a price in a fixed currency?<\/h3><\/dt>\nYes. Add currency=\"gbp\"<\/code> to the shortcode and that price is pinned: it is never swapped and it is not counted as a currency the rest of the page offers. Useful for a sentence that has to read in one currency regardless.<\/p><\/dd>\nWhat happens if a shortcode names a plan or tier that does not exist?<\/h3><\/dt>\nNothing is shown for it, and a warning goes to the log naming which shortcode asked and what could not be found. A price leaves a gap and a button is not rendered at all, because a link to a checkout that sells nothing is worse than no link. Both are deliberate. Showing a zero, or falling back to some other row's price, would put a wrong figure in front of a customer, which is worse than showing nothing.<\/p><\/dd>\n\n<\/dl>\n\n\n
1.0.4<\/h4>\n\n\n- Fixed: deleting an older copy of the plugin from the Plugins screen while the renamed copy is active no longer removes the products, tokens and prices the active copy is using.<\/li>\n
- Changed: the plugin is now called PlugUpp Live Pricing for Freemius, with the slug and text domain plugupp-live-pricing-for-freemius, at the WordPress.org review team's request that a third-party name be framed as an integration. Nothing about how it works changes; settings, stored prices and webhooks carry over, because they are filed under the pflp prefix, not the slug.<\/li>\n<\/ul>\n\n
1.0.3<\/h4>\n\n\n- Fixed: a border set in the buy button block's border panel now draws. WordPress zeroes the border width on every button and never writes a border style, so the panel's width and colour rendered as no border at all.<\/li>\n
- Added: a Width setting on the buy button, the 25, 50, 75 and 100 percent that the core Buttons block offers, so a button can span a pricing card.
[pflp_button width=\"100\"]<\/code> does the same.<\/li>\n- Added: a Hover effect option under Buttons on the Settings screen. Lift raises every button 1px under the pointer with a soft shadow of its own colour, on screens 1025px and wider only, so a touch screen never leaves a tapped button lifted. Off by default.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Changed: the block's Plan dropdown offers only plans that sell something. A plan with no price has no figure to show and no checkout to link to, so nothing could render from it; the product's own screen says so, and the free tier of a pricing table is an ordinary button linking to the download page.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Added: only the product ID and the API Bearer Authorization Token are typed. The product secret key is read from Freemius with the token on every save, so there is no third field.<\/li>\n
- Added: the webhook registers itself with Freemius when a product is saved with a working token, is kept up to date on every save, and is removed when the product is deleted. The product's Status list says so; the URL and the six events sit behind Show webhook URL for pasting by hand if that cannot happen. A product for which Freemius has not yet enabled webhooks (it reserves them until a product is actively selling) is saved with a warning that says so, and the token is not blamed.<\/li>\n
- Changed: the product's name comes from Freemius with the prices and is refreshed with every fetch and every save, and the Label field is gone. The Products list, the product's own screen, the Test token result and the block editor's product dropdown all show the name the Freemius dashboard gives it, and
product=\"...\"<\/code> on a shortcode takes the product ID, its Freemius slug or its name.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n\n- First public release. Freemius price, Freemius buy button and Freemius currency toggle blocks, the matching
[pflp_price]<\/code>, [pflp_button]<\/code> and [pflp_currency]<\/code> shortcodes rendering through the same code, prices fetched from the Freemius API and stored on the site, webhook and scheduled refreshes, a visitor currency toggle with geo detection, currency-aware checkout links with an optional overlay, and a Freemius Pricing admin menu with a products list, a per-product screen carrying the webhook URL and a Shortcodes section with a ready-made price and button shortcode for every plan and pricing row, site-wide settings and a log. The blocks fill their plan, licence tier and billing cycle dropdowns from the stored rows, preview through the server so the editor shows what the page renders, carry the editor's own colour, typography, spacing and border panels, align all three from the block toolbar, and convert to and from a shortcode in one click.<\/li>\n<\/ul>","raw_excerpt":"Freemius pricing, live on your own pages with blocks or shortcodes, in each visitor's currency, refreshed so it never goes stale.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/368891","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=368891"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/plugupp"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=368891"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=368891"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=368891"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=368891"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=368891"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=368891"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}