Skip to main content
A product mapping tells PayGlue: when a customer buys product X from provider Y, give them Ghost membership tier Z and send welcome email type W.
Running more than one Ghost blog? Create a separate provider product per blog and map each one only in the organization it belongs to. Mapping the same product in multiple organizations grants Ghost membership on all of them for a single purchase. See the FAQ for details.

Where mappings are created

Mappings are not created on a dedicated page. Instead, you configure them inline when you set up a Buy Button, Paywall, or Pricing Table. When you select a product and a Ghost tier in one of those editors and click Save, the mapping is recorded automatically.
1

Open an editor

Go to Installation > Buttons, Paywall, or Pricing Table in your PayGlue dashboard and open or create an item.
2

Select a provider and product

Choose your payment provider and select the product. Choose Link a product as the link type. Select your payment provider and the product you want to map.
Payglue Product Mapping
3

Configure Ghost settings

Choose what happens after the customer buys a product
Payglue Ghost Cms Mapping
  1. One-Time or Subscription
  2. Subscribe to the newsletter. (Defaul: Yes)
  3. Welcome email for new member (Magic link is recommended.)
4

Configure email

Select which welcome email Ghost should send. Magic link is recommended.
Payglue Welcome Email Actions
5

Save and copy the webhook URL

Save the mapping. Copy the webhook URL and add it to your provider’s webhook settings.
6

Save

Click Save. The mapping is created automatically and appears in Analytics > Product Mapping.

Viewing all mappings

Go to Analytics > Product Mapping in your dashboard to see all configured mappings — which product maps to which Ghost tier, the trigger event type, and where each mapping was created (button, paywall, or pricing table).
Payglue Analytics
You cannot edit or delete mappings directly from this view. To change a mapping, open the Buy Button, Paywall, or Pricing Table item it belongs to and update the settings there.