With the Meta Pixel you can measure how many people land on your pages and check out.

But you probably have multiple payment pages. And when an Add To Cart or Purchase event is measured, you want to be able to see at a glance which payment page it was for. You can do this by creating a custom conversion.

Log in to your Meta for Business account and navigate to Event Manager > Custom Conversions.

Click Create Custom Conversion to create a new custom conversion.

Give your conversion a name and choose the pixel you use for Plug&Pay under Data Source. Then choose the Event you want to measure. For this custom conversion I want to measure how many people land on a specific payment page. For that I need the Add to Cart (Addition to shopping cart) event.

I can then create a rule. In this case I want to measure the Add to Cart for a specific payment page, so I enter as a rule that the URL must contain the URL of my payment page in Plug&Pay.

Optionally enter a conversion value.

After creating my custom conversion, I can see exactly how many times this custom conversion has fired under Custom Conversions.

In the example above I can see that this payment page has been viewed twice.

In the example above you can create a custom conversion for your payment pages to measure which exact payment page is being viewed.

You can also create a custom conversion for your thank-you page, so you know exactly via which payment page your customer checked out.

First navigate in Plug&Pay to Settings > Analytics. Here you can find and enable the setting to pass the specific order confirmation URL per payment page to Meta.

This setting ensures that your Plug&Pay thank-you pages contain the URL of the linked payment pages.

Create a new custom conversion as described above and now choose the Purchase (Purchase) event. For the rule, set that the URL must contain the URL of your payment page, including /confirmed.

When a checkout is completed via this payment page, I will be able to see in this custom event that a purchase took place on this specific payment page.

Are you using upsells in Plug&Pay and want to measure whether people are buying them? You can create custom conversions for those too!

When someone lands on the first upsell page, it also means they came from the payment page and therefore purchased the product on the payment page. The only way to reach the upsell page is to check out the product on the payment page.

When someone lands on the upsell page, you can therefore measure it as a purchase of the main product.

If you work with a more extensive upsell flow, things work slightly differently: on an upsell page, someone can purchase the offer or click 'No, thank you'. In both cases they can be redirected to the second upsell page. When the second upsell page opens, you therefore cannot directly say whether someone bought the first upsell.

That is why skipped=1 is added to the URL when someone does not take the offer.

Okay, we understand the above is quite complex.

Time for an example!

This is my upsell flow in Plug&Pay:

I have a payment page, followed by two upsells and a thank-you page.

If I purchase the upsell 'Lifetime access' but skip the upsell 'WWF Subscription', I cannot see in Meta whether the first upsell was purchased.

To measure this, we use a piece of the URL that Plug&Pay adds when an upsell is not purchased. If you skip an upsell, skipped=1 is added to the URL on the page after the upsell.

When I create a custom conversion, I can exclude events where skipped=1 appears in the URL. This way I know for certain that I am only measuring the people who purchased the upsell.

In Meta I create a new custom conversion. Under Rules I enter that the URL must contain the URL of my upsell page. I then add a new rule: the URL must not contain skipped=1.

This is what this looks like in Meta:

With this conversion I am therefore only measuring the people who purchased the first upsell. To also measure the second upsell, I add another custom conversion and enter the URL of the thank-you page to measure it and to exclude the skipped=1 addition.