Ad Attestation and Ad ID

Updated: Dec 17, 2024

This topic applies to you only if your app uses ads. Meta allows certain 2D and hybrid apps on Meta Horizon Store to contain in-app ads as described by the Meta Ads policy. Please review the policy to determine if your app may contain ads, and to understand the requirements that your in-app ads must comply with. To better serve users, 2D and hybrid app developers are required to complete the in-app ads attestation before app review and being approved to publish their apps. This attestation asks you to tell Meta if your apps contain in-app ads. If you indicate your app contains ads, your app will show a “Contains ads” label on the Product Details Page (PDP) in the Meta Horizon Store.

This documentation will show you how to complete and update an ads attestation.

How to complete in-app ads attestation

During the initial app submission or when converting an existing immersive app to a 2D or hybrid app, you must answer the in-app ads attestation question. This question appears in the build section of the app submission flow and is accessible when you select a 2D or hybrid build in draft mode. However, it is disabled for immersive builds, as these cannot contain ads. Once a build is live, you cannot change your answer.

For future submissions, if you attach a 2D or hybrid non-live build manually, you must answer the attestation question. This requirement does not apply if you are only updating the app’s price, screenshots, description, or other metadata items.

The first time you answer this question or change your previous answer, Meta will conduct an app review, which includes reviewing your app against the ads VRCs to ensure compliance. This manual review process may take a few days, during which you cannot publish a new version of the app.

How to update in-app ads attestation

Keep your in-app ads attestation current by following these steps when adding or removing ads from an app:

Prepare the new app build. You may want to upload this build to a non-live channel to test it.

Make sure the new build is in draft mode, then upload the new app build to the live channel, or move the build from another channel to the live channel.

Note: It’s important to put the new build in draft mode. If you accidentally publish a new build with a different ads behavior, immediately roll back your app to the previous version, to avoid severe consequences including the app being removed from the Meta Horizon Store.

Go to the developer platform and start a new app submission by clicking the Edit app button on the app submission page.

In the new submission, go to the build section and select, new build.

If the new build is a 2D or hybrid app, you will be able to update the attestation at this point.

If the app is immersive, the question will be disabled and the app will be changed to ads-free.

Save the app and submit for review.

When the new submission is approved, you will receive an email and you can release the new version on the developer platform. After the new version is released, your app will update the “contains ads” label on the app information page for users.

Note

Updating ads attestation will be manually reviewed by Meta to make sure the new version is compliant with our ads policy. The review will take a few days to complete, and your new version cannot publish before the review is approved.

Did you find this page helpful?