Testing creative feed fallbacks: Check last published profile and update results when source fails; Test each failure path separately using a preview or test campaign; Ensure default rows are active, eligible and use accurate fallback copy
Image: AdTech Market Guide

Verification

Part of Creative management technology

Testing fallbacks when a creative feed is unavailable

Test source-feed outages, failed updates, unmatched rows and missing assets separately, then verify default content and ad-server fallbacks.

Start by naming the failure. An unreadable source feed, a failed update, a row with no rule match, and an image that fails validation can produce different results. Turning off the source file and looking for a default ad does not test every path.

Check what serves when the source fails

A source spreadsheet or remote file becoming unavailable does not, alone, show that the next impression will be blank or use a default row. Check the last published profile and the update or transformation result.

A no-match result and a failed source update are separate failure paths. A default feed row is a content-selection fallback; it does not repair a failed source update.

Test each failure separately

ScenarioEvidence to collect
Source feed cannot be read during an updateUpdate error, last published profile and whether approved content remains eligible to serve
Feed is valid but no row matchesSelected default row or next documented fallback
Default row is inactive or does not cover the rule inputsPlacement default eligibility and observed result
Product image is missing or invalidTransformation error and any rendered result that can be checked
Product is unavailable or its price is staleEligibility and destination-page consistency
Placement default is incompatible or outside its run datesPlacement settings and observed delivery

These are proposed tests, not test results. Use a test campaign or a preview setup that reflects the intended configuration. For each case, record the profile, creative, placement size, rule inputs and time. A preview checks configuration; use delivery evidence where the result depends on the ad server or placement.

Testing each failure scenario separately

  • Source feed cannot be read during an updateCheck update error, last published profile, and whether approved content remains eligible to serve
  • Feed is valid but no row matchesVerify selected default row or next documented fallback
  • Default row is inactive or does not cover rule inputsCheck placement default eligibility and observed result
  • Product image is missing or invalidReview transformation error and any rendered result
  • Product is unavailable or price is staleConfirm eligibility and destination-page consistency
  • Placement default incompatible or outside run datesCheck placement settings and observed delivery

Make defaults usable

For a Studio strategy that uses default rows, check the default-row setup against the relevant Studio documentation. Coverage may require several rows for schedules, dimensions or dependent feeds. Check the strategy in use for proximity targeting.

The Campaign Manager 360 placement default ad is a separate layer. Check the default-ad setup for the exact placement against the relevant Campaign Manager 360 documentation. Check type, size and run dates for the exact placement.

For product campaigns, choose fallback copy that remains true without the missing item detail. A generic brand message may be suitable; an unverified price or stock claim is not. Where Merchant Center product data is used, check the relevant Merchant Center landing-page requirements for the campaign.

Record whether each result is acceptable, needs a corrected default or alert, or calls for pausing the affected creative. Repeat the checks after material feed, template or placement changes.

Verifying fallbacks in Studio and Campaign Manager 360

  1. Check default-row setup against Studio documentationEnsure coverage for schedules, dimensions, or dependent feeds; validate proximity targeting
  2. Review Campaign Manager 360 placement default adVerify type, size, and run dates match the exact placement
  3. Use fallback copy that remains truthfulAvoid unverified prices or stock claims; use generic brand messaging where appropriate
  4. Validate landing page requirementsEnsure Merchant Center product data meets campaign-specific landing-page rules
  5. Record outcome and take actionNote if result is acceptable, needs correction, requires alert, or demands pausing the creative

More from Verification

Verification

Ad verification technology

Understand what ad verification measures, where coverage can fail and what to request before using its reports to make campaign decisions.