For a ChatGPT product-feed launch or tracking migration, verify the complete path from catalog record to selected product, landing page and final tracking parameters. GPTAd recommends assigning owners, checking a representative sample and recording the account's tracking mode. A successful upload alone does not establish ingestion, serving readiness or correct reporting labels.
Reviewed October 15, 2026. GPTAd is an independent publisher. The checklists and fictional examples below are editorial guidance.
Legacy feed-tracking accounts must migrate by November 5, 2026, according to OpenAI. Administrators can opt in through the “Feed tracking is changing” banner. Verify the account’s current mode. Campaign management
Give each stage an owner
Product-feed API access requires enablement. OpenAI documents stable item IDs, public HTTPS product and image URLs, and catalog processing checks. A successful SFTP upload does not prove successful ingestion, and completed ingestion does not prove every product can serve. Product feeds
Translate those distinctions into an ownership sheet:
- Catalog owner: maintains the source record and decides when changes are ready.
- Transfer owner: confirms the intended file reached the intended feed.
- Processing reviewer: checks counts and diagnostics against the expected catalog.
- Campaign owner: checks which products the campaign is supposed to select.
- Destination reviewer: checks product pages and tracking behavior.
A small team may assign several roles to one person. The point is to prevent “the upload worked” from becoming the answer to every downstream question.
Reconcile a sample before expanding
Choose a small review sample representing different product circumstances: an ordinary item, a recently changed item and an item that should not be selected. Write the expected outcome for each before checking the result. This makes the exercise a test of the pipeline rather than a tour of whatever happens to appear.
For a fictional shop selling desk accessories, the sample could include a currently available desk mat, a lamp with a changed price and a discontinued organizer. The review asks whether each record is current, whether the intended selection includes it, and whether its destination reflects the same offer. These are hypothetical test cases, not observed campaign results.
Delta updates support existing title, price and availability changes; new products and other field changes use an updated SFTP catalog. Product campaigns combine a feed, product selection and a template, with at most one non-archived product-ad template per feed ad group. Product feeds
Treat catalog changes as reasons to rerun the relevant sample checks. Do not assume that a previously correct product selection remains correct after the source data changes.
Audit duplicate tracking keys
Under the new tracking mode, precedence is Feed < Account < Campaign < Ad group < Ad, and unrelated query keys survive. After any feed-specific removal of utm_* parameters, legacy behavior gives remaining feed URL values highest priority. Campaign management
Consider this deliberately simplified hypothetical example. A feed product URL contains utm_campaign=catalog_oct and item_variant=oak. The account adds utm_source=chatgpt. The campaign specifies utm_campaign=workspace_launch. Assume no feed-specific utm_* removal and no ad-group or ad override.
Expected result: legacy mode favors catalog_oct; new mode favors workspace_launch. Both retain item_variant=oak and add utm_source=chatgpt. This illustrates precedence, not an observed production URL. Keep customer information out of tracking parameters.
The business consequence is naming continuity. A reporting system that groups visits by utm_campaign may show a different label after migration even though the team intended to promote the same offer. Agree on the desired label before changing the tracking mode.
Run a migration review
Inventory tracking keys at every configured level. For each repeated key, record the old expected winner, the new expected winner and the reporting destination that uses it. Mark disagreements for a human decision rather than silently standardizing everything.
Then choose a representative set of product URLs and write the expected final parameters. Have the administrator verify the account's migration state and review the change with whoever owns web analytics. After the change, check the resulting destinations and keep a dated record of the mode and naming decisions.
If the banner or available controls differ from the documentation, resolve that discrepancy through the account's supported help route before treating the migration as complete. As of this article's review date, the deadline is close enough to warrant a named owner and a scheduled review. The deliverable is a verified catalog-and-tracking path, not merely a checked box beside “feed uploaded.”
