Prys sends install, subscribe, and paying events, each with its per-ad-set value, through the Conversions API, so Meta's Maximize ROAS campaigns optimize toward the merchants who actually pay, not the cheapest installs.
Prys is the Shopify app growth platform for Shopify app developers.

Prys sends install, subscribe, and paying values per ad set through the Conversions API, so Meta's Maximize ROAS goal optimizes toward high-LTV merchants, not cheap installs.
Spend and ROAS from Meta joined with installs, subscribers, paying, and LTV from Prys, per campaign, ad set, and creative.
The Conversions API sends events server-side, past the pixel and iOS limits, so Meta keeps learning which merchants pay even when browser tracking fails.
Meta ads work for Shopify apps when you feed them the right signal. Meta's AI optimizes toward whatever conversion you send it. Send installs and it finds cheap installs that never pay. Send paying-customer values and its Maximize ROAS goal optimizes toward the merchants who actually pay, then expands to more like them. The signal that makes Meta profitable for an app is paying customers, not installs.
Prys sends install, subscribe, and paying events to Meta through the Conversions API, server-side, mapped to Meta's conversion events, each carrying its value per ad set, the level where Meta actually optimizes. Those values unlock Meta's Maximize ROAS goal, so delivery weighs return per dollar and chases the merchants who pay rather than the cheapest installs; once you have enough paying data, you can set a ROAS target. Because it is server-to-server, it also bypasses the browser and iOS limits that break pixels, so Meta keeps learning which merchants pay and builds lookalikes from your paying customers. The dashboard then shows spend and ROAS from Meta next to Prys revenue and LTV, down to the creative.
Meta ads go straight to your listing by default, and Prys tracks them to paying customers. Route them through a landing page first and Prys covers that too: one snippet carries the Meta click across your landing page and funnel onto the App Store, so values still attribute to the exact ad set.
Paste a Dataset ID and access token. No developer approval, about two minutes.
Every click tied to installs, subscribers, and paying customers.
Prys sends each event with its per-ad-set value through the Conversions API.
Meta chases revenue, and you scale the ad sets and creatives that return.
Yes, when you feed Meta paying-customer values instead of installs. Its Maximize ROAS goal then optimizes toward the merchants who actually pay, and ROAS follows.
Prys sends install, subscribe, and paying events with per-ad-set values through the Conversions API, so Meta optimizes toward revenue and builds lookalikes from your payers.
About two minutes. Paste a Dataset ID and access token, no developer approval required.
Yes. The Prys snippet carries the Meta click across your landing page and funnel onto the App Store, so values attribute to the exact ad set.
Send install, subscribe, and paying events with per-ad-set values, so Meta's Maximize ROAS goal finds the merchants who actually pay.