How to Build a Meta Custom Conversion for High-Value Orders on Shopify

TL;DR

A thank-you page URL rule counts page views, and a page view has no order value, so it can't tell a $40 order from a $400 one. Meta's Marketing API reference shows the shape that works: a conversion that counts "when someone triggers the Purchase standard event and purchase value is greater than 100" [1]. On a store running the app, Meta gets a server-side Purchase for every order, with the order total in your shop's currency, the products, the unit count and, on the Plus plan, whether the buyer is new or returning. Pick the threshold from your own orders, build the rule in Events Manager, and check it on the next order above the line.

Key Takeaways

• Put the rule on the Purchase event's value parameter. A URL rule can't express an order amount.
• Set the threshold on the full order total, tax and shipping included, in your shop's currency, because that's the value the app sends.
• An order that crosses the line only through an accepted post-purchase upsell won't match, since the upsell isn't in the Purchase value.
• On the Plus plan, a second rule on customer_type set to new counts first-time buyers. Orders with no customer record carry no label.
• Meta's learning bar of 50 events in 7 days applies to an ad set optimizing for the conversion [5].
• Meta allows 100 custom conversions per ad account, and its restrictions rolling out from September 2, 2025 flag ones that suggest health conditions or financial status [2].

Why the thank-you URL rule is the wrong Facebook custom conversion on Shopify

Because a URL rule counts page views, and a page view doesn't carry the order's value. Meta's pixel guide teaches the URL version: put "a URL, or partial URL" in pixel_rule, with thankyou.html as its example of "a page appearing after purchase" [2]. It works because "PageView standard events record the referrer URL of the page that triggered the function call," and "You can use these recorded URLs in the Events Manager to define visitor actions" [2]. Nothing in a thank-you page's address says whether the order was $40 or $400, so "high value" can't be written as a URL rule at all.

Shopify adds a second problem: page views and orders don't line up one to one. Shopify's page_viewed event "logs an instance where a customer visited a page" and "is available on the online store, Checkout, Order status and Customer Account pages" [6]. A shopper who opens the order status page again from the confirmation email is one more visit, while Shopify's own checkout completion fires "once for each checkout" [7].

WeltPixel Conversion Tracking's Purchase doesn't depend on any of that. The app sends it for each Shopify order from its own servers, whether or not the thank-you page loaded in the shopper's browser. That's the event to put the rule on. Why purchase tracking moved off that page in the first place is the subject of the thank-you page tracking deadline article.

What does your Shopify Purchase event carry?

A value the rule can compare, and a few fields you can build other rules on. On a store running the app, Meta (a Plus-plan channel) receives the Purchase from the server, never from the browser. Its custom data holds:

What isn't there matters as much. The Purchase carries no discount code, no separate tax or shipping amount and no campaign UTMs, so a rule on any of those has nothing to read from this event.

Meta defines content_ids as "The content IDs associated with the event, such as product SKUs" [4], but the app's default is the Shopify Product ID. A product rule has to use the identifier the app actually sends, which is covered in how product ID and catalog match work on Shopify.

One more check before you build: if the Facebook & Instagram channel or any other tool sends its own Purchase to that dataset, your rule counts those events too; see the native channel and an app sharing one Meta pixel.

Where should the high-value threshold sit?

Where your own orders say "big", measured in the number the app sends. Export recent orders from Shopify (Orders → Export) and sort by the order total, since that's the value Meta will compare: tax and shipping in, discounts out, in your shop's currency. On the Plus plan, orders created by staff in the admin, plus POS, API and renewal orders, reach Meta too unless Exclude Admin/API Orders is ticked in the app's Meta settings, so a high-value rule counts them as well.

Take an illustrative store with 1,400 orders over the last 8 weeks, 175 a week. Of those, 210 came to $150 or more, which is 15% of orders and about 26 a week. That's a cut worth tracking: rare enough to mean something, common enough to show up every week.

Two things move orders across a $150 line that a cart-value habit won't predict. Tax and shipping count: on the same illustrative store, a $130 cart with $8 shipping and 10% sales tax on both comes to $151.80, and it matches. If you think of "high value" as merchandise only, restate the threshold with the method in the purchase value, tax and shipping guide. Upsells go the other way. A $140 order that reaches $175 only through an accepted post-purchase offer won't match, because the Purchase value leaves the upsell out; the post-purchase upsell tracking guide follows that revenue.

Build the custom conversion in Events Manager

Meta says custom conversions "are created entirely within the Events Manager" [2]. The screens change, so the steps below name what to set rather than which button to click.

1. Find the dataset the app sends to. In the app's Meta settings, note the pixel ID. That's the dataset whose events your rule will watch. If the app sends to more than one Meta pixel, each dataset needs its own custom conversion. Where that ID comes from is in the Meta Conversions API setup guide.

2. Open that dataset in Events Manager and start a new custom conversion.

3. Base the rule on the Purchase event.

4. Add a condition on value: greater than your threshold. Meta's Marketing API writes the same rule like this, with 100 as the threshold [1]:

   {"and":[{"event":{"eq":"Purchase"}},{"value":{"gt":100}}]}
   

   Meta created its example with custom_event_type set to PURCHASE and named it "High value Purchase Custom Conversion" [1].

5. Name it after the order. Meta's guide says that "Beginning September 2, 2025, we will start to roll out more proactive restrictions on custom conversions" that "may suggest information not permitted under our terms", including any "suggesting specific health conditions" or "financial status (e.g., "credit score", "high income")" [2]. "Purchase over $150" describes the order. A name about the buyer's wealth is the kind of wording Meta lists.

6. Check it on the next order above the line. The rule lives on the dataset, and the app's purchases reach that dataset through the Conversions API. Meta's server event reference says "All action sources enable ad optimization capabilities" and that every action source enables "ad measurement and custom audience creation capabilities" [3]. We couldn't find a Meta page that says in one sentence that custom conversions count server events, so confirm it yourself: after the next order above your threshold, open the custom conversion in Events Manager and look for activity, and check that the dataset's Purchase events show a value parameter. To see the Purchase's value sooner, the Test Event Code field on the app's Meta card sends events to Events Manager's Test Events tab, as testing server-side conversion events without polluting reports describes. The app warns that test events "may not be included in actual data", so clear the code before the check above.

A second one for first-time buyers

On the Plus plan, the app's Purchase also carries customer_type, new or returning, whenever the Shopify order has a customer record. That makes a second custom conversion possible: Purchase where customer_type is new.

Meta's reference documents rules on a custom parameter. Its example counts a custom event "for a given color" by "specifying it as a custom parameter" [1]. A rule on customer_type is the same move with a different field.

One limit comes with it: an order with no customer record carries no label, so it matches neither new nor returning. On Meta the label is there for your own reporting, and a rule like this turns it into a count of first-time buyers next to all purchases, per campaign. New vs returning customer tracking on Shopify covers what the label means on each platform.

Report on it or optimize for it?

Report on it first: add it as a column on campaigns you already run, which is the cheapest way to find out whether your best ads bring your biggest orders. The learning bar only comes in when an ad set optimizes for it.

Meta's reference describes custom conversions as a way to "Optimize ads delivery based on online and offline conversion events that you define" [1], and the bar is the same as for any event, 50 events in 7 days per ad set [5]. The illustrative store above makes about 26 orders a week over $150, across all its ads. No single ad set gets near 50 in 7 days on that, so it keeps optimizing for Purchase and reads the high-value column on the side. If you're weighing a narrower event anyway, choosing an optimization event on a low-volume store walks through the trade.

Keep the count down, too. "The maximum number of custom conversions per ad account is 100" [2], and a store that builds one per threshold, product and buyer type can reach it.

FAQ

Can a Facebook custom conversion use the purchase value?

Yes. Meta's Marketing API reference documents a custom conversion that counts "when someone triggers the Purchase standard event and purchase value is greater than 100" [1]. Build yours the same way in Events Manager, with your own threshold.

Does WeltPixel Conversion Tracking create the custom conversion for me?

No. The app sends Meta the Purchase with its value and the other parameters in the table above. You create the custom conversion in Events Manager on the dataset whose pixel ID is in the app.

Will the custom conversion count orders from before I created it?

Judge it on orders placed after you build it. Build it in October, not in Black Friday week, and you'll have weeks of verified orders behind it.

Give the rule an order value to read

WeltPixel Conversion Tracking builds Meta's Purchase from each Shopify order on its servers, carrying the order total, your shop's currency, the products and, on Plus, whether the buyer is new. Meta comes with the Plus plan at $39/month [8], alongside TikTok, Google Ads, Reddit, Pinterest, Snapchat, OpenAI Ads, Klaviyo and theMarketer; the free plan covers GA4 only, up to 100 storefront orders a month.

Sources

1. Meta for Developers, Marketing API "Custom Conversion" reference, developers.facebook.com/docs/marketing-api/reference/custom-conversion/, accessed October 14, 2026
2. Meta for Developers, Meta Pixel "Conversion Tracking" (custom conversions, the 100 limit, the September 2, 2025 restrictions), developers.facebook.com/documentation/meta-pixel/implementation/conversion-tracking, accessed October 14, 2026
3. Meta for Developers, Conversions API "Server Event Parameters", developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/server-event, accessed October 14, 2026
4. Meta for Developers, Conversions API "Custom Data Parameters", developers.facebook.com/documentation/ads-commerce/conversions-api/parameters/custom-data, accessed October 14, 2026
5. Meta for Developers (Meta Horizon Store), "Understanding and optimizing your ad campaign" (last updated April 8, 2026), developers.meta.com/horizon/resources/optimize-ad-campaign/, accessed October 14, 2026
6. Shopify Dev, Web Pixels API "page_viewed", shopify.dev/docs/api/web-pixels-api/standard-events/page_viewed, accessed October 14, 2026
7. Shopify Dev, Web Pixels API "checkout_completed", shopify.dev/docs/api/web-pixels-api/standard-events/checkout_completed, accessed October 14, 2026
8. WeltPixel Conversion Tracking, Shopify App Store listing (free plan; Plus $39/month), apps.shopify.com/weltpixel-conversion-tracking, accessed October 14, 2026