Domain Verification
The integrity of content on Facebook is a serious concern, and domain verification is a step towards ensuring that only verified owners can edit the way their content appears on Facebook. Many publishing apps use link editing to customize and create engaging content for the Facebook community. In an effort to preserve this essential functionality in a way that protects the integrity of publishers' content, verified link owners will now have the ability to overwrite link metadata when creating link page posts.
This document provides information about:
What is Domain Verification?
Domain Verification provides a way for you to claim ownership of your domain in Business Manager. This ownership allows you to control editing privileges of your links and other content to prevent misuse of your domain and to keep bad actors from spreading misinformation.
Who is Domain Verification for?
Domain Verification is the best way to handle ownership if:
- You have a larger number of Pages that are difficult to maintain manually via Open Graph markup tags
- You have adopted or have the ability to adopt Business Manager to manage your assets
- You have the ability to upload HTML files to the web root directory or the ability to edit DNS TXT records
- You can edit Link Page Posts that link to content you own—ownership will eventually serve as a means to determine who has access to link editing
- You want to control who can edit link descriptions on ads pointing to your domain
- You want to configure web events with Aggregated Event Measurement
Enabling More Domain Verification Use Cases in Aggregated Event Measurement
Facebook introduced Aggregated Event Measurement (AEM) to support measurement of web events after Apple begins enforcing its App Tracking Transparency prompt requirement.
We will be supporting the Public Suffix List for domain verification and event configuration. This means that merchants using a registered domain on the Public Suffix List will be able to use that domain for verifying and configuring their top 8 events on the domain. For example, if "myplatform.com" is a registered domain on the Public Suffix List, then Jasper, a merchant with the subdomain "jasper.myplatform.com", would now qualify as an effective eTLD+1 and would be able to verify "jasper.myplatform.com" and use it to configure their top 8 events in the web events configuration tool. Please note this would not apply to URL paths (e.g. "myplatform.com/jasper") or an eTLD+2 domain (e.g. "abc.jasper.myplatform.com"). For the URL path and eTLD+2 use cases, businesses can alternatively consider moving to Landing Page Views or Link Click optimization, or purchasing their own domains to try and avoid disruption to their ad campaigns once Apple begins enforcing its prompt.
Advertisers who use your platform may benefit from this update if your platform domain is registered in the Public Suffix List. You can learn more about the Public Suffix List here.
For more information on verifying domains and configuring web events, visit our Help Center article: Facebook Pixel Updates for Apple's iOS 14 Requirements
