Yes, it can. By default RevenueCat sends renewals to Meta as Subscribe, the same event as a first payment, and Adapty sends a renewal as two events, Subscribe and fb_mobile_purchase. As I read Meta’s attribution settings, a renewal is credited to a campaign only when it lands inside the attribution window after someone clicked or saw one of your ads. Most renewals fall outside that window, so they sit in Events Manager and never reach the campaign. Some can fall inside it: a weekly plan renews about 7 days after the first payment, on the edge of a 7 day click window, and an existing subscriber who sees your ad in the day before they renew can be credited where the ad set counts 1 day view. So I check the mapping first and keep renewals out of the event the campaign optimizes for. I judge cost on new payers, counted in the billing tool.
On one subscription account I worked on, renewals entered Meta’s purchase event partway through the work. From that date on, Meta’s purchase count was no longer comparable with the weeks before it.
Scope: subscription apps on Meta app promotion campaigns, on iOS and Android, with a billing tool such as RevenueCat or Adapty, or a mobile measurement partner (MMP) such as AppsFlyer or Adjust, sending events to Meta. Games get their own section near the end. The sample behind my own observations is small. I am an Adapty Berlin ambassador and I cohosted a public webinar with Adapty in August 2026, so weigh every mention of Adapty accordingly.
Where can renewals and existing users enter my Meta numbers?
In six places. Only the first two are about the event mapping.
| Source | How it reaches Meta | Where it shows | What I do |
|---|---|---|---|
| A renewal sent as Subscribe | RevenueCat’s default, with a revenue value in US dollars | In app subscriptions and the subscribe conversion value, on the campaign only inside the window | Know which columns mix first payments and renewals |
| A renewal sent as a purchase | Adapty’s default adds fb_mobile_purchase to Subscribe | In app purchases, in app purchase ROAS, and the event value optimization learns from | Remove it from the purchase event the campaign optimizes for |
| A weekly plan renewing soon after the click | The first renewal arrives about 7 days after the first payment | A second Subscribe from the same person, on the edge of a 7 day click window | Count new payers in the billing tool |
| An existing subscriber who sees an ad | A renewal within 1 day after an impression | A conversion under 1 day view | Use the exclusions Meta allows |
| A reinstall | The SDK logs an install the first time the app starts on a device | Meta installs above the MMP’s | Compare install counts by platform |
| An MMP forwarding every source | Adjust sends data from all attribution sources to Meta by default | Events Manager totals, organic and renewals included | Compare attributed numbers only |
What do RevenueCat and Adapty send to Meta by default?
RevenueCat’s Meta page maps five events. Trial Started goes to StartTrial. Trial Converted, Initial Purchase and Renewal all go to Subscribe. Non Renewing Purchase goes to fb_mobile_purchase. Its troubleshooting page says the same in one line: “Trial conversions, initial subscription purchases, and renewals map to Subscribe by default.”
The value goes with them. RevenueCat sends revenue in US dollars, and its Meta page says “Events sent with revenue attached count toward Meta’s Revenue number, including trial conversions and renewals that occur when the app isn’t active.” A Sales reporting setting decides whether that revenue is gross or after store commission, and RevenueCat says to use the same basis when you compare ROAS. You can choose other Meta standard event names for each event. The docs do not say that renewals can be switched off for Meta. The only custom events they document for Meta are Funnels events, which Meta does not use “for ad attribution or campaign optimization”, in RevenueCat’s words.
Adapty’s Facebook Ads integration maps Subscription renewed to Subscribe and fb_mobile_purchase, and all names in an event’s field “are selected by default”. Adapty’s event list says a renewal starts “from the second billing, whether it’s a trial or non-trial subscription”, and the list gives a trial conversion its own event. On the same default, a trial start reaches Meta as three events: StartTrial, Subscribe and fb_mobile_purchase. To send fewer, you remove names from the field. Adapty’s page says the integration “works on iOS 14.5+ only for users with ATT consent”.
Meta’s own app events reference defines Subscribe as “The start of a paid subscription for a product or service you offer.” A renewal is not a start. Meta does not document how it wants renewals sent, as Subscribe, as a purchase or as a custom event.
The MMPs work differently. Adjust shares subscription events with Meta only when you map them, and once data sharing is on it sends “data from all attribution sources to Meta, by default”. AppsFlyer lets you send each mapped event only when it is attributed to Meta, or for “All media sources, including organic”, and its default for the value is “No data”, so revenue reaches Meta only if you choose it.
If the Meta SDK in the app also logs purchases, the same payment can arrive twice. That is a separate fault, and my post on missing trials covers it.
Which Meta columns does a renewal land in?
It depends on the event name. Meta’s in app purchases metric “includes any instances of the standard event fb_mobile_purchase”, and in app purchase ROAS is “calculated as mobile app purchases conversion value divided by amount spent”. The value of Subscribe goes to a separate subscribe conversion value. The in app subscriptions metric counts “subscribe events”, not people.
So on RevenueCat’s default, renewals that Meta credits raise the subscribe columns and leave purchase ROAS alone. On Adapty’s default they raise both. That matters most for value optimization. For Advantage+ app campaigns that maximize the value of conversions, Meta’s help page says “The only optimisation event available is purchase.” On Adapty’s default mapping, a credited renewal adds to the purchase value that campaign is set to maximize.
Can a renewal land inside Meta’s attribution window?
Sometimes. Meta’s attribution settings page counts click conversions “within 1 day or 7 days after a link click on your ad” and view conversions “within 1 day after an impression of your ad”. The window runs from the click or the impression, not from the install. The page lists those settings for website and in store conversions, and Meta does not spell them out for app events after the install, so the rest of this section is my reading, plus arithmetic. AppsFlyer’s Meta discrepancy page reads it the same way: “Meta ads doesn’t show events if they occurred over 7 days after the ad click.”
Annual and monthly renewals arrive long after the original click, so they cannot be credited to it. A weekly plan bought straight after the click renews about 7 days later, on the edge of a 7 day click window. With a 3 day trial, the first payment comes on day 3 and the first renewal on day 10, outside it.
The other way in is a new impression or click. A subscriber who sees one of your ads in the day before their subscription renews can be credited if the ad set counts 1 day view, which I keep on. The same Meta page says that on iOS 14 and later, app install campaigns that use Meta’s attribution report on 1 day or 7 day click, so this path does not apply to them. Advantage+ app campaigns leave out people who “installed or opened your app in the last 90 days”, which keeps out subscribers who use the app. A weekly subscriber who keeps paying without opening the app is still eligible.
Events Manager is not the campaign. Adjust’s Meta FAQ says Events Manager “shows all events Adjust sends to Meta, including events from organic traffic and other media sources”. A billing tool that sends every renewal does the same. Read Events Manager to see whether events arrive. Read the campaign for what Meta credited.
On iOS, RevenueCat says it “doesn’t update SKAN conversion values”. A renewal reaches SKAN only if the app itself writes it on the device before the last window closes, on day 35. What can SKAN measure after a trial covers when that happens.
What happens to optimization when renewals sit in the event?
Meta documents nothing about how it treats a renewal in delivery, so this part is my reading. A campaign learns from the conversions credited to it. A credited renewal tells Meta that an ad found a payer, when the payer was already yours. The cost per result in Ads Manager drops, and nothing about acquisition has improved.
The reporting side is easier to see. A cost per Subscribe can sit below what a new payer really costs, so a campaign can look comfortably under a CPA ceiling set on new payers when it is not. When a team wants an old low CPA back, the first question I ask is whether the old number was ever real.
After a mapping change, weeks on either side of the date are not comparable on Meta. I note the date in the report and compare Meta’s numbers only within one side of it. The billing tool’s numbers do not change with the mapping, so they carry the comparison across.
How do reinstalls and returning users show up?
Meta’s installs metric counts an install when people “opened your app for the first time, and once per person”. Meta’s SDK logs App Install “the first time an app starts on a particular device”, per its event collection page. Meta does not say how the two rules meet for someone who reinstalls.
The MMPs draw the line with a window. In AppsFlyer, a reinstall inside the reattribution window, 90 days by default, is not a new install and sends no install postback, unless it came from a retargeting campaign. After the window it counts as a new install. For Meta re-engagement campaigns, AppsFlyer’s discrepancy page says installs inside the window “may be appearing as new installs by Meta ads”. Adjust treats reinstalls as sessions. It reattributes a user only after an inactivity period, 7 days by default, followed by an ad engagement, and reports that as a reattribution and a reinstall. A gap where Meta shows more installs than the MMP can be reinstalls, or a longer view window on Meta’s side: on one account, campaigns with 1 day view counted 1.20 times the MMP’s installs, and campaigns on click only came in at or below it.
A lapsed subscriber who comes back through an ad pays again. Check what your billing tool or MMP calls that payment. Adjust has a separate reactivation event, for example. Whatever it is called, if it maps to Subscribe or a purchase, Meta will count it as a conversion like any other.
Late renewals also fall out of the MMP’s attribution. AppsFlyer says that Meta “requires attribution providers to delete their user-level data 6 months after the install”, and that later events from those users count as organic. Adjust’s Meta FAQ says the limit is 150 days, after which it shows those users under Expired Attributions in place of their Meta campaign. So in the MMP an annual renewal does not show under the Meta campaign that brought the user. Read long term revenue per cohort in the billing tool, as in which revenue is the money.
Should I exclude existing subscribers from Meta app campaigns?
Yes, where Meta lets you. It costs little, but it fixes less than the mapping does. On Advantage+ app campaigns the 90 day rule applies automatically. The Advantage+ help page linked above says “You can’t exclude specific audiences from seeing Advantage+ app campaigns”, and also that custom audience exclusions can be set in advertising settings. Meta’s Advantage+ app campaigns page puts those exclusions at the app level, in App advertising settings. Meta’s app ads overview sends existing users to other objectives: “Re-engage existing users: Choose the engagement, leads, sales or traffic objective”. Meta’s goal that excludes existing customers is documented for Sales campaigns only.
My Andromeda playbook says you do not need custom audiences for targeting, and I still think so. An exclusion is a different job. It keeps payers you already have out of the counts.
How do I count new payers only?
- Open the integration that sends events to Meta and write down, per event, which Meta event name it sends. Check the billing tool and the MMP, because both can send.
- Keep renewals out of the event your campaign optimizes for. On Adapty, remove fb_mobile_purchase from the Subscription renewed field if the campaign optimizes for purchases or value. On RevenueCat, the docs let you choose another standard name for Renewal. Before you change it, check that the new name is not the one your campaign optimizes for.
- Compare Meta’s attributed Subscribe or purchase count with first payments in the billing tool, for the same dates, platform and country. First payments are trial conversions plus first purchases. Meta should normally show fewer, because the billing tool includes organic payers. If Meta is close to the billing count or above it, suspect renewals or double counting.
- Know which Ads Manager column your bid uses. In app purchases and in app purchase ROAS follow fb_mobile_purchase. Subscribe has its own count and value.
- Write the date of any mapping change into the report.
- Judge cost on new payers at the same cohort age, from the billing tool. Which number to trust for which decision covers the general case of two tools that disagree.
What changes for a mobile game?
Games have no renewals, but they have repeat payers. Meta’s in app purchases metric counts every purchase event, so a player who buys three times inside the window counts three times. That suits value optimization, since the value is what you want. Next to it, read Meta’s unique in app purchases, which counts Meta accounts rather than actions. A pass or a VIP plan that renews works like a subscription, and the sections above apply to it.
What should you check this week?
- The event name each tool sends for a renewal, a trial conversion and a first purchase.
- Which of those names your campaign optimizes for, and which Ads Manager column your bid and your report use.
- Meta’s attributed count against first payments in the billing tool, for one platform and one country.
- The date of any mapping change, marked in the report.
- Meta installs against the MMP’s, with the MMP’s reattribution window in mind.
- Cost per new payer at the same cohort age, from the billing tool.
Every RevenueCat, Adapty, AppsFlyer, Adjust and Meta page linked above was checked on 20 November 2026. Where Meta does not document a point, I have said so, and the reading is mine. No account is named.
Questions people ask
Does Meta count subscription renewals as new purchases?
It counts whatever your billing tool or MMP sends under a purchase or subscribe event name. By default RevenueCat sends renewals as Subscribe and Adapty sends them as Subscribe and fb_mobile_purchase. As I read Meta’s attribution settings, a renewal is then credited to a campaign only if it falls inside the attribution window after a click or a view of one of your ads. Most renewals fall outside it, but some fall inside.
Does RevenueCat send renewals to Meta?
Yes, by default. RevenueCat’s Meta integration maps Trial Converted, Initial Purchase and Renewal all to Subscribe, with a revenue value in US dollars. RevenueCat says those values count toward Meta’s revenue number, renewals included. You can pick other Meta standard event names. Its docs do not say that renewals can be switched off for Meta.
Why is my cost per Subscribe in Meta lower than my cost per new subscriber?
Subscribe can hold more than first payments. On RevenueCat’s default mapping it also holds renewals, and Meta counts events, not people. Compare Meta’s attributed Subscribe count with first payments in the billing tool for the same dates, platform and country. If Meta is close to or above the billing count, suspect renewals or double counting.
Should I stop sending renewals to Meta?
Keep them out of the event your campaign optimizes for. Whether to send them at all, for example under another name for reporting, depends on what your billing tool allows. Adapty lets you remove event names from the Subscription renewed field. RevenueCat lets you choose another Meta standard name but does not document switching renewals off.
Can I exclude existing subscribers from Meta app campaigns?
Partly. Advantage+ app campaigns automatically leave out anyone who installed or opened the app in the last 90 days. Meta’s help pages say you cannot exclude specific audiences from Advantage+ app campaigns, and also that custom audience exclusions can be set for the app in App advertising settings. A subscriber who keeps paying without opening the app can still see your ads.