When you switch your mobile measurement partner (MMP) to Singular, Meta's (Facebook's) ad delivery system may interpret the change as a disruption to its conversion signal — potentially triggering the learning phase for your ad sets. This guide explains how Meta's learning phase works, which migration actions put ad sets back into learning, and how to sequence your migration to protect campaign performance.
See also: Attribution Measurement During MMP Migration — general dual-MMP testing guidance for all networks, including Meta.
Understanding Meta's Learning Phase
Meta's learning phase is the period during which Meta's delivery system collects data to understand the best way to deliver your ad set. An ad set enters the learning phase whenever a significant edit is made — or when it is newly created. During this period, performance is often less stable and cost-per-result may be higher.
Important: Meta defines a significant edit as any change that resets the ad set's learning progress. Examples include changes to budget, bid strategy, audience, ad creative, or — critically for MMP migrations — the conversion event being optimized. For the full current list, see Meta's About the learning phase article.
Key learning phase facts from Meta's documentation:
- An ad set needs approximately 50 optimization events within a 7-day period to exit the learning phase. Ad sets that cannot reach this threshold are flagged as Learning Limited.
- The learning phase resets whenever a significant edit is made to the ad set.
- Meta recommends avoiding significant edits for at least 7 days after an ad set enters or re-enters learning to allow the algorithm to stabilize.
Note: Switching your MMP does not by itself reset the learning phase. What matters is whether the conversion signal sent to Meta changes — specifically, whether the event postbacks Singular sends to Meta are equivalent in name, timing, and volume to those your previous MMP was sending.
What Actions Trigger the Learning Phase During a Migration
The following actions during an MMP migration are likely to trigger or extend the learning phase for Meta ad sets:
-
Changing the optimization event name — e.g., renaming
purchasetofb_mobile_purchase, or switching to a different SDK event. - Interrupting postback delivery — a gap of even a few hours in event postbacks during the cutover window can cause instability.
- Changing event mapping in Partner Configuration — remapping which SDK events are forwarded to which Meta standard events counts as a significant edit from Meta's perspective.
- Switching to a different bid strategy or budget type at the same time as the MMP migration.
The following actions are unlikely to trigger the learning phase on their own:
- Adding Singular as an additional MMP while your existing MMP remains active (parallel/dual-MMP period).
- Completing the Singular partner configuration in Singular's platform before going live with postbacks.
- Changing the MMP attribution tracking link (non-SAN campaigns only) without changing bid strategy or event mapping.
Recommended Migration Approach
Follow these steps to minimize disruption to Meta campaign optimization during your migration:
-
Configure Singular before cutting over postbacks.
Complete your Facebook (Meta) Ads Attribution Integration in Singular — including the Facebook App ID, event mapping, and postback settings — before you turn off postbacks from your existing MMP. Use the same event names and mappings your previous MMP used wherever possible. -
Match event mappings exactly.
Map the same SDK events to the same Meta standard events (e.g.,fb_mobile_purchase,fb_mobile_complete_registration) that your previous MMP was forwarding. Avoid renaming or remapping optimization events during the migration window. -
Choose a low-spend cutover window.
Schedule the postback cutover during a period of naturally lower spend — such as a weekend or a period outside of key campaign flights — to reduce the impact of any temporary signal interruption. -
Run parallel postbacks briefly, then cut over cleanly.
If your previous MMP supports it, briefly run both MMPs sending postbacks to Meta simultaneously to confirm Singular's postbacks are landing. Then disable postbacks from the old MMP promptly. Avoid an extended dual-postback period, as duplicate events can cause Meta's system to over-count optimization signals.Important: Meta supports multiple MMPs, but sending the same optimization events from two MMPs simultaneously will cause duplication in Meta's auction system and can lead to over-optimization. Keep the overlap period as short as possible — typically less than 24 hours.
-
Avoid other significant edits during migration week.
Do not change budgets, bid strategies, audience targeting, or creatives during the 7-day period following your postback cutover. Let Meta's delivery system stabilize on the new signal before making additional changes. -
Monitor performance daily for the first 7 days.
Watch cost-per-result and event volume in both Singular and Meta Ads Manager during the post-migration week. If you see a significant drop in optimization events, contact your Singular CSM or Singular Support.
Historical Data Import
Important: Historical data import is an Enterprise feature. To implement it, contact your Customer Success Manager.
Singular can import existing device attribution data from your previous MMP so that Singular recognizes your existing user base as returning users rather than new installs. This is especially useful for retargeting and re-engagement campaigns where accurate user history affects audience segmentation and bid optimization.
Historical import does not affect your live Meta campaigns directly, but it ensures that users attributed prior to your migration are correctly represented in Singular's reporting and postback logic going forward. For details, see Importing Existing Attribution Data FAQ.
Frequently Asked Questions
No — switching your MMP does not by itself reset the learning phase. Meta's delivery system responds to changes in the conversion signal it receives, not to which MMP is sending it. If Singular sends the same optimization events at the same volume and with the same event names as your previous MMP, Meta's algorithm should continue optimizing without re-entering the learning phase.
The learning phase resets only when a significant edit is made to an ad set — such as changing the optimization event, bid strategy, budget, audience, or creative. For the current definition, see Meta's About the learning phase.
Meta requires an ad set to receive approximately 50 optimization events within a 7-day period to exit the learning phase. If an ad set cannot reach this threshold, Meta marks it as Learning Limited, which can restrict delivery efficiency.
During a migration, if postbacks are interrupted or event volume drops temporarily, an ad set that was previously stable may re-enter or remain in the learning phase. This is why minimizing any postback gap during the cutover is important.
Meta recommends avoiding significant edits to an ad set for at least 7 days after it enters or re-enters the learning phase. Making additional significant edits during this window resets the learning counter and prolongs the instability period.
For MMP migrations, this means you should avoid making other changes to your active Meta ad sets — such as budget adjustments, creative swaps, or audience changes — for the first 7 days after your postback cutover to Singular.
Yes, to the extent possible. Meta's optimization algorithm is trained on specific event names (e.g., fb_mobile_purchase, fb_mobile_complete_registration). If you change the event name being used for optimization during the migration, Meta treats it as a new optimization signal and resets the learning phase for affected ad sets.
In Singular's Partner Configuration for Meta, map your SDK events to the same Meta standard events your previous MMP was using. If you are unsure of your previous mapping, check your old MMP's Meta event configuration before migrating.
Meta supports multiple MMP integrations simultaneously, but it is important to manage event postbacks carefully during this period. See Attribution Measurement During MMP Migration for a full breakdown of dual-MMP support across networks.
For Meta specifically: both MMPs can register attribution, but sending the same optimization events from two MMPs simultaneously will result in duplicate event signals in Meta's system. Keep any dual-postback overlap period short — ideally under 24 hours — and confirm Singular's postbacks are landing before disabling the old MMP.
SKAdNetwork (SKAN) campaigns use Apple's privacy-preserving attribution framework and are separate from Singular's MMP attribution integration with Meta. SKAN postbacks can only be sent to one MMP at a time, so the cutover for iOS SKAN campaigns must be clean and immediate — there is no dual-MMP option for SKAN.
For iOS SKAN setup with Meta after migrating to Singular, see the Facebook Ads SKAdNetwork Integration guide.
A temporary dip in performance during and immediately after the cutover is normal, particularly if there was any interruption in postback delivery. Allow at least 7 days for Meta's delivery system to re-stabilize on the new signal before drawing conclusions.
If performance does not recover after 7 days, check the following:
- Confirm event postbacks are arriving in Meta's Events Manager with the expected event names and volumes.
- Verify your event mapping in Singular's Partner Configuration matches what your previous MMP was sending.
- Check whether any ad sets are flagged as Learning Limited in Meta Ads Manager.
- Contact Singular Support and provide your app name, Meta App ID, and a description of the events affected.