Will excluding renewals hurt my event volume?

It reduces it, which matters on small stores. The trade is worth making — volume built from renewals teaches the model the wrong thing, and more bad signal is not better than less good signal.

Can I still use renewal data at all?

Yes, as a custom event. It is genuinely useful for retention audiences and lifetime-value analysis; it just should not be driving acquisition campaigns.

Pixel tracking for Shopify subscription stores

Updated 1 September 2026

Every subscription renewal creates a Shopify order, and a default pixel setup reports every one as a fresh conversion. Meta attributes those renewals to whatever ad happens to be running, so a store with a healthy subscriber base can show excellent ROAS on campaigns that acquired nobody. The reporting is not slightly optimistic; it is counting the same customer indefinitely.

What changes on a subscriptions store

Pixel tracking differences on a subscriptions Shopify store
What	How it differs
Purchase	Should fire on a customer’s first order only.
Renewals	Send as a distinct custom event, kept out of ad optimisation.
Lookalikes	Trained on renewals, they find existing-subscriber lookalikes rather than new-signup lookalikes.
Reported ROAS	Inflated by however many renewals landed inside the attribution window.

Recurring orders are not new conversions

A subscription renewal creates a Shopify order, and a pixel that fires Purchase on order creation will fire on every renewal. Meta receives what looks like a new customer conversion each month, attributes it to whatever ad is running, and reports a ROAS that is counting the same acquisition over and over.

The signal you actually want is the first order. Renewals are retention, not acquisition, and mixing them into the same event teaches Meta’s model that your ads perform far better than they do — which leads to overspending on the assumption that scale will hold.

Separating acquisition from retention

The practical approach is to send Purchase only for a customer’s first order and a distinct custom event for renewals. Ads optimise against the first, while the renewal event stays available for lifetime-value analysis and for audiences built around active subscribers.

This also fixes value-based lookalikes, which are otherwise badly skewed on a subscription store. A model trained on renewal events learns to find people who look like existing long-tenure subscribers, when what you want is people who look like subscribers at the moment they first signed up.

Setup checklist

1Confirm whether your pixel currently fires Purchase on renewal orders — most do.
2Restrict Purchase to first orders and route renewals to a custom event.
3Rebuild value-based lookalikes once acquisition events are clean.
4Track subscriber lifetime value separately rather than through ad-platform reporting.
5Re-check after any change to your subscription app, which may alter how orders are created.

Questions

Will excluding renewals hurt my event volume?: It reduces it, which matters on small stores. The trade is worth making — volume built from renewals teaches the model the wrong thing, and more bad signal is not better than less good signal.
Can I still use renewal data at all?: Yes, as a custom event. It is genuinely useful for retention audiences and lifetime-value analysis; it just should not be driving acquisition campaigns.