Pugpig Bolt Piano Integration
Piano is a leading audience solutions provider used by publishers across the globe. We've worked closely with Piano to build a robust integration with Pugpig Bolt, giving you the ability to create powerful, seamless experiences for your users. This integration includes:
- Log in: Native and web-based PKCE
- Registration: Web-based PKCE only
- Receipt-linking: Create Piano profiles for users who subscribe via in-app purchase
- Running experiences on your timeline (using Piano Cards) or articles using our Piano Composer Integration
- Analytics: Tie user behaviour to their Piano profile
- Segmentation and messaging: Pass Piano IDs to other services, such as push
There are also some features that aren't currently supported but are either on our roadmap for future support or under consideration for such. These are:
- Content metering integrated with the Piano meters (you can of course use the Pugpig meter)
- Piano Content recommendations
We have a full PKCE login integrated with Piano ID. This flow can allow users to log in, or create an account. We are able to start the flow on either Registration or Login, depending on the context.
You can enable Piano's Passwordless flow for the app (note you will need to use the 'Confirm with digital code' option for this in addition to/instead of 'Confirm with magic link'). Please note when testing that Piano does not send emails for sandbox.
We strongly recommend you set up a Piano White Labelling Domain - https://docs.piano.io/faq-article/domain-whitelabeling-for-piano-id/
Known PKCE Issues
- There is a known issue with Piano log out. See log-out considerations for information.
- Piano has a known bug with Twitter social sign in. They are working to resolve it.
- We have identified a bug with the social sign in flow UX on Android and we are working with Piano to resolve it.
Information on how to configure social sign in (aka "social log in") can be found in Piano's documentation portal.
Note: Sign In With Apple uses the same redirect_uri as the URL on which the flow is invoked. This could be one of your whitelabelled auth domain (e.g. auth.acme.com) which is preferred, or id.tinypass.com or id.piano.io. We need to make sure we invoke the PKCE flow using the same domain you have configured.
Customising your Piano Templates for the app
We also pass in a parameter that you can use in your templates so that your app can show slightly different forms to your web site. Examples where this has been used include:
- Hiding the social sign in buttons on the app screens
- Customising the Login template to have a much more friendly user interface when it is used as the first screen in the PKCE flow
We base the access a user has from Piano resources, this allows you to control the access level of the user directly from Piano, and change these entitlements on the fly.
External Term Entitlements (Receipt Linking)
We have an out of the box integration to provide External Term entitlements if users purchase an In App Purchase for both iTunes and Google Play. See https://docs.piano.io/external-service-term/ for more information on the Piano side, and this article for more of an understanding on cross-platform entitlement
We are able to send any Piano user custom fields as dimensions to your analytics. We can also send the Piano User ID to push providers and other third parties. This enables segmentation in those other services based off information in your users profiles.
Read more about Piano.