Solutions
The same evidence chain, five very different problems.
Consent work looks different depending on what you run. A storefront’s trackers arrive from apps, an agency’s problem is twenty clients rather than one site, and a publisher’s problem is an advertising supply chain. These pages describe the shape of each.
Ecommerce
On a storefront, theme code is only one possible source. Sales-channel apps, reviews widgets, upsell tools and campaign pixels can add separate scripts that a theme-only review misses.
Typical plan: Starter or Growth
SaaS and B2B
Two surfaces with genuinely different conditions: a public marketing site full of advertising tags, and an authenticated product where you have a relationship, a contract and a different set of options.
Typical plan: Growth
Agencies
One site is a configuration problem. Twenty sites is an operations problem, and the thing clients actually pay for is the written finding, not the banner.
Plan: Agency: 25 properties
Publishers
A publisher’s consent problem is not a list of vendors. It is an auction involving parties nobody enumerated in advance. Read this before assuming any consent platform covers it.
Typical plan: Growth or Agency
Enterprise
At this scale, the practical constraint can be maintaining current evidence of what each property is doing, who owns it and which policy applies.
Plan: Agency, or the managed service
Start with your own site
A free scan names what is loading before anyone has chosen anything.