• Home
  • Pugpig Bolt
  • Authentication and Subscriptions

Bolt Paywall customisation

Written by Benji Weiser

Updated at December 19th, 2022

  • Pugpig Bolt
    Bolt apps Content and Workflows Bolt CMS Pugpig Distribution Service URLs, Domains and Linking Bolt Search Authentication and Subscriptions Bolt Analytics Push notifications Bolt Release Notes Debugging Advertising App stores
  • Pugpig Site
    Search URLs, Domains and Linking Content Management System Analytics SEO Advertising Consent Management Platform Site Release Notes Debugging Authentication and Subscriptions
  • Pugpig Archive
  • Working with Pugpig
    Pugpig Support Releasing new versions Pugpig Packs & Agreements Pugpig Policies
  • Pugpig Consulting
+ More

Table of Contents

Theming Buttons Copy

This article highlights the appearance customisation available within the app paywall. Please see this article for the paywall overview.

Theming

You can choose all of the colours and fonts on the paywall, as well as the logo icon, though initially these will inherit the theming of the rest of the app to appear cohesive and this is often sufficient. 

Buttons

The order, size and shape of the buttons is fixed. We apply logic to display only the buttons that are relevant to the user and app. They can be themed independently of one another.

  1. In app purchase: this button will appear if there are IAPs configured and available. This links to our subscription modal where the user can choose and purchase any available subscription.
  2. 3rd party authentication: this button will appear if an auth service is configured and the user is not already signed in. This launches the sign in flow in a separate view.
  3. Cancel button, this closes the paywall and returns the user to where they were prior to invoking it.

Copy

The copy on the paywall is drawn from several places, this is to ensure it’s as relevant as possible to the user and their situation. These are listed below. All of these are localised in our supported languages.

Introduction: this is set in the app, and can be used to explain to the user why they’re seeing the paywall and what their options are

Authorisation status: this copy only appears in the case of a use who is signed-in but is not entitled to the content. Currently the most common example of this is users who have cancelled their subscription in your authentication service. This text will inform then why they aren’t entitled and what their options are. In this case we’ll also still display the in app purchase button, as a way for them to gain access.

IAP button: The price here is pulled from the relevant App Store (App Store Connect or Google Play) and takes into account the users eligibility for introductory pricing, so should always accurately reflect the lowest price they’ll pay. This can overwritten to just be a normal string, and not feature pricing information. Prices will be localised to the user’s app store currency.

Sign in button: this is set in the app. If your authentication service uses a specific identifier (such as member number) in lieu of a standard email-password combination it can be wise to explain that here. i.e. “Sign in with member number”, but be mindful of the limited space a button provides.

Cancel button: this is set in the app

All strings set in the app can be changed serverside with a new config, but note that a user will have to open the app to download the config and it will be applied the next time the user opens it.

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Adding voucher (promo) codes for your mobile or web app
  • The Bolt paywall and subscription modal
  • Available Third Party Integrations
  • Alternative purchasing mechanisms for Bolt apps
pugpig logo white
Navigation
  • Products
  • Customers
  • News
  • Podcast
Contact
  • Contact us
  • LinkedIn
  • Twitter
Technical Support
  • Status Page
  • Documentation
  • Customer Support
Corporate
  • Company
  • Jobs
  • Privacy Policy

© Kaldor Ltd. 2022

Powered by Pugpig

Expand