Direct Support: How to Test Campaign Segmentation at the Monthly Audit — Content-To-Target Fit for a Engine-Compatibility Check Article_title Direct Support: How to Test Campaign Segmentation at the Monthly Audit — Content-To-Target Fit for a Engine-Compatibility Check Article_summary Engine-Compatibility Check guidance for campaign segmentation in a controlled direct Tier 2 support project, covering keeping engines, lists, and test groups separate enough to diagnose, one contextual target link, verification evidence, and safe campaign scaling. Article Direct Support: How to Test Campaign Segmentation at the Monthly Audit — Content-To-Target Fit for a Engine-Compatibility Check Campaign Segmentation becomes useful only when the campaign boundary is explicit. In this engine-compatibility check for a direct Tier 2 support project, the destination is an imported Money Robot page that already points to the money site; it is never the money-site URL itself. For tiered-link planners, that rule keeps the link graph understandable and prevents a lower tier from accidentally bypassing the layer it should support during the monthly audit. For this direct Tier 2 support engine-compatibility check covering campaign segmentation during the monthly audit, the contextual destination appears once as tiered campaign checklist. One relevant link is sufficient for the page's purpose, avoids repeating the same destination inside a single document, and leaves the surrounding explanation readable. The anchor is selected from a plain topical pool in the project data, while the URL token is resolved by GSA only at submission time. Protect the Route Between Tiers Compare HTTP response consistency against outbound-link count and inspect the underlying URLs before assigning the shortfall to automation settings.