Meta Ads
Meta Blocked Web-Only Creative in Website and App Campaigns. Repair the Destination, Not Just the Error.

Updated: November 10, 2026
For Website and App campaigns, replace applink_treatment=web_only with automatic destination selection or a compatible manual destination. Then test web, installed-app and non-installed-app paths separately so an API fix does not create a broken customer journey.
The field removal exposes a routing decision
Meta’s v26.0 changelog says creatives with applink_treatment=web_only can no longer attach to ads using Website and App conversion locations, with the change applying to all Marketing API versions on October 27, 2026. Removing the field may make the request succeed, but it also changes who decides the destination.
Document whether the business wants automatic selection or a specific compatible route. Treat that as a campaign decision with an owner, not a connector patch hidden in code.
Inventory affected creation paths
Search templates, bulk uploaders, creative cloning, vendor tools and retry queues for web_only. Include ads created before the deadline that may be edited or duplicated later.
Log the campaign conversion location, creative ID, app-link fields, fallback URL and tool version. A successful edit to budget or status does not prove the creative can be recreated.
Operating control table
| Control | Evidence | Failure prevented |
|---|---|---|
| Inventory | Tools and creatives using web_only | Hidden clone failure |
| Routing choice | Automatic or compatible manual path | Connector decides silently |
| Device tests | Installed, absent and fallback states | Broken deep link |
| Measurement | Web/app event reconciliation | Conversion shift misread |
| Release control | Named pause or rollback path | Bad route stays live |
Test three customer states
Verify the click when the app is installed, when it is not installed and when the device or browser cannot resolve the preferred link. Confirm landing content, campaign parameters, consent behavior and the path back to purchase.
Use real mobile devices when possible. Preview tools often cannot reproduce operating-system handoff, deferred deep linking or store fallback behavior.
Preserve measurement continuity
Check that web and app destinations emit distinct but reconcilable events. Keep click identifiers and campaign parameters through redirects where permitted, and verify the conversion action selected for optimization.
A routing repair can shift conversions between web and app reports without changing total demand. Annotate the release and compare deduplicated business outcomes, not only platform columns.
Release with a rollback boundary
Update the integration in a controlled account, reconcile created-ad payloads and inspect the live destination. Keep a list of campaigns that cannot support the chosen replacement.
Rollback means pausing the affected creative or reverting to a tested compatible destination—not restoring a field Meta no longer accepts.
Connect the control to the wider system
Use this process alongside the Meta app-destination measurement checklist. The platform setting, creative promise, measurement rule and downstream experience should describe the same operating decision.
Pre-launch checklist
- Write the decision and its owner in plain language.
- Capture the source configuration and evidence.
- Test one realistic customer or reporting path end to end.
- Verify mobile presentation, links and accessibility.
- Record the success threshold and rollback trigger.
- Schedule the first review before material spend or traffic accumulates.
Run a cross-functional release review
Ask the channel owner, creative lead, analyst and conversion owner to inspect the same end-to-end case. Each reviewer should state what was configured, what the customer sees, which event proves the outcome and which limitation changes the interpretation. Resolve differences before launch.
Repeat the case on mobile and with one adverse condition. The control is useful only when it explains the exception as clearly as the happy path.
Frequently asked questions
Should this be automated?
Automate repeatable validation and monitoring, but keep material policy, claim and budget decisions inside named approval limits.
What is the minimum evidence?
Preserve the source configuration, decision owner, expected outcome, observed result and any exception that changes interpretation.
When should the team roll back?
Rollback when the control is inactive, the customer experience breaks, totals do not reconcile or the agreed threshold is breached.
