Scope Validation · ScaleSKUs MCP Academy #18

You want an automation for walnuts. You choose a category, preview the rule, and discover that almonds and seeds are included too. The calculation may be correct, but the scope is wrong. This lesson focuses on a step that should happen before any automation is saved: inspecting the actual entities it would affect. Ask ScaleSKUs to preview a walnut-only scope and show the matched campaigns, products and keywords.

A preview is a way to test your selection. It is not approval to apply the suggested bid action. We will compare a broad category selection with a verified four-campaign selection. The automation taxonomy in this account contains a broader dried-fruits, nuts and seeds category. The initial selection matches one hundred and eighty-eight keywords across forty-four ad groups, including seed, Brazil nut and almond terms.

That is not a walnut-only result. Also, the automation taxonomy is not interchangeable with the product taxonomy returned by another tool. A more specific product label elsewhere does not guarantee the same automation selector exists. Inspect the actual scope values used by the preview. Ask the assistant to show the requested filter and the returned matched entities together, so a convincing explanation cannot hide the wrong selection.

We next inspect the enabled advertised products in candidate campaigns. Campaigns three, eleven, twenty-one and thirty-two have checked product sets that map to walnuts. Their enabled counts are five, six, one and four respectively. Campaign four needs separate treatment: seven products are known walnuts and thirteen have unknown category mapping. That does not prove those thirteen are another category. It means the campaign is not cleanly verified for this purpose.

Keep unknown separate from confirmed mismatch. Use the stable campaign identifiers in the selection, while retaining readable campaign names in the review table for the person approving the setup. The useful preview is the one that actually uses the four verified campaign identifiers. It returns twenty-four matched keywords, compared with one hundred and eighty-eight in the broad category preview. An intermediate result included Campaign four and produced thirty-four matches, so it was not the requested four-campaign scope.

This is why we verify the payload and the result, rather than trusting a statement that the scope is correct. The corrected sample contains walnut-related keywords. That supports the narrower selection. It still does not verify pack size for every query or guarantee that future changes to the campaigns cannot introduce unrelated products. The scope probe uses a minimum of ten clicks over fourteen complete days and a hypothetical ten percent bid reduction.

Those settings make a preview concrete; they are not a recommendation to reduce every keyword that has ten clicks. Before a real rule is created, the business condition must justify its action. Some matched keywords also inherit their ad-group bid, so the displayed keyword-level change may not operate as a reviewer expects. Ask which entity owns the effective bid and what exact value would change.

A useful preview explains both why an entity is selected and how the proposed operation would affect it. Save a review checklist alongside the proposed configuration. Confirm the exact campaigns, enabled product mapping, ad type, entity type, date window and conditions. Inspect a sample of matched entities, including edge cases and inherited bids. Record exclusions explicitly, such as Campaign four while its unknown products are unresolved.

Recheck the scope after product additions or campaign restructuring. If the preview grows unexpectedly, investigate before approving the action. This is especially important when a broad category or an inferred product association is involved. The scope review should be repeatable by another account manager, not depend on remembering why a campaign name sounded relevant. Once the selection is verified, you can design the actual business rule around that scope.

Add your real profitability objective, evidence window, action limits and approval requirement. Preview again because a change to conditions can change the matched set. Keep the proposed action separate from the scope demonstration until both are ready. For practice, take one product family and compare a category-based preview with an explicit campaign selection. Explain every difference in the results. The outcome of this lesson is a reliable boundary around an automation: you know what it can touch, what remains uncertain, and what must be checked before execution.