Advantage+ catalog ads use a catalog and delivery signals to select relevant items for an impression. That automation cannot repair an incorrect price, unavailable product, mismatched item ID, wrong destination, or mixed product set. A reliable launch begins with the commercial truth in the feed and the event-to-item relationship.

VISUAL LESSON

What you will learn

  1. 01Define a campaign-specific product set.
  2. 02Reconcile catalog items with website events.
  3. 03Run a representative item and destination QA.
A product catalog passes identity, price, availability, location, and event checks before selected items enter an advertising campaign
Catalog automation is trustworthy only when the feed, product set, events, and destinations agree.

ILLUSTRATIVE WORKED EXAMPLE

Audit an illustrative 120-item product set

Items selectedIllustrative set
120
Feed fields passEight need repair
112
Event IDs matchFourteen unresolved
106
Launch-readyAfter all checks
100
Illustrative example—not a benchmark. Replace every sample value with your own campaign, market, and measurement data.

PRACTICAL INTERFACE MAP

Move from catalog inventory to a launchable ad

Catalog01Confirm the business asset

Record catalog owner, data source, refresh time, currency, market, diagnostics, pixel or dataset, and permissions.

Product set02Write the inclusion rule

Filter by campaign category, availability, market, price, margin, condition, or approved custom labels; inspect edge cases.

Ad03Preview representative items

Test identity, copy, destination, price, availability, event match, tracking, policy status, and mobile checkout before publish.

Conceptual walkthrough. Labels, controls, and availability can vary by account, region, plan, and interface version; verify the current screen before acting.

STEP-BY-STEP LESSON

Commercial brief → clean feed → matched events → catalog ad

DefineMarket and items
ReconcileFeed and events
PreviewAd to checkout

THE LEAD ATLAS METHOD

Lead Atlas Data can research business contacts specific to the campaign's market, locations, and categories while the catalog team governs the products and destinations used in paid delivery.See how custom list research works ↗
01

Write the catalog campaign contract

State the objective, conversion location, market, currency, item families, exclusions, inventory policy, price and promotion rules, landing experience, optimization event, and catalog owner. Decide whether the campaign should advertise all eligible items or a product set with a specific commercial job.

Do not mix unrelated categories merely to increase inventory. A coherent set makes creative, destination, margin, and reporting review more interpretable.

02

Audit feed truth before filtering

Inspect item ID, title, description, category, image, condition, price, sale price and dates, availability, brand, landing URL, mobile behavior, variant relationship, market, and update time. Compare a sample with the live site and checkout.

Separate feed rejection, warning, stale value, and business-rule failure. An eligible item can still be inappropriate because it is low margin, out of season, unsupported in the advertised market, or inconsistent with the offer.

03

Build and challenge the product set

Create the smallest rule that captures the intended inventory, then inspect included and excluded examples. Test capitalization, blank fields, overlapping labels, variants, sale windows, country feeds, and items that change state during the campaign.

Freeze the rule and expected count for launch. If the count changes materially after refresh, investigate the specific additions and removals rather than assuming the feed simply grew.

04

Reconcile events and destinations

Verify that view, add-to-cart, and purchase events send the same content IDs and item context expected by the catalog. Test browser and server event deduplication, currency and value, consent behavior, redirect paths, and representative variants.

Complete the customer journey on mobile for available, sale, unavailable, and edge-case items. The ad, page, basket, final price, shipping or serviceability, and confirmation event should remain consistent.

05

Launch with an exception ledger

Publish only the approved set and retain the feed snapshot, rule, item sample, event evidence, previews, destinations, and owners. Monitor diagnostics, item-count movement, delivery by product set, policy, price or availability conflicts, conversions, refunds, and downstream quality.

Deliverable: catalog contract, source and permission map, field audit, product-set rule, included and excluded sample, event-to-item reconciliation, destination tests, exception queue, approval record, launch snapshot, monitoring owner, and rollback plan.

THE TAKEAWAY

Treat the catalog as production data: define the product-set rule, verify every customer-visible field, reconcile content IDs with events, and test representative items before publishing.

OFFICIAL REFERENCES

Check the platform’s current instructions.

Platform labels, eligibility, and workflows can change. These official help pages were used to validate this lesson.