This article explains how to preserve Reels engagement and ensure successful track linking when migrating catalog to the FUGA Platform for Meta services. You will learn the requirements for metadata and audio consistency, the recommended timeline for deliveries and takedowns, and how to maintain consolidated audio pages across Facebook and Instagram.
Requirements for Successful Clustering
Meta utilizes a process called clustering to link different deliveries of the same recording. When successful, this ensures that Reels engagement and play counts are maintained and appear on a single consolidated audio page per track. To optimize for clustering and prevent ownership conflicts, the following must remain identical to the previous distributor's delivery:
The International Standard Recording Code (ISRC).
The exact same audio file previously delivered.
The release and track-level metadata.
Understanding Failed Clustering
Failed clustering occurs when Meta’s system cannot verify that two deliveries are the same recording. When this happens, a new, separate audio page is generated for the version delivered via the FUGA Platform. This new page will start with zero engagement and zero Reels counts.
Meanwhile, the old delivery from the previous distributor remains on its original audio page with all its legacy engagement. Because these pages are not linked, the engagement cannot be transferred. Furthermore, delivering inconsistent assets will trigger an ownership conflict, which will ultimately prevent the version delivered via the FUGA Platform from going live.
Migration Steps and Timeline
Follow these steps to ensure that your migration from your previous distributor to FUGA is successful and you are able to retain your tracks' usage activity:
Deliver the release to Meta (Facebook Audio Library and Facebook Fingerprinting) via the FUGA Platform. You can action these under Product Delivery Instructions on each product.
Allow a 3–4 business day period from delivery for the content to ingest and cluster automatically with the original delivery.
During this period, both the old and new deliveries should remain live simultaneously. This overlap increases the likelihood that Meta’s system will cluster the tracks together.
Once the 3–4 business day window has passed, request or send takedowns from your previous distributor.
When the tracks are properly clustered, usage activity and Reels counts will automatically transfer to the version delivered via FUGA.
Metadata Consistency and Ownership
To avoid service interruptions and ensure your release successfully goes live, you must maintain absolute consistency between the old and new deliveries. If metadata is inconsistent or both deliveries assert exclusive ownership, Meta’s automated clustering will fail and trigger an ownership conflict. This prevents the version delivered via the FUGA Platform from going live.
Ensuring the audio file is the exact same file previously delivered is critical. This allows Meta’s fingerprinting process to correctly identify the tracks as a single entity and merge them into the existing cluster, rather than treating them as a new or conflicting recording.
If you have questions regarding specific delivery statuses, contact your FUGA representative or reach out via our support channel at support@fuga.com.