Technical guidance for deploying and operating IVT Solution
Use this reference to understand site setup, installation, protection modes, Revenue Guard, traffic-quality signals and publisher-side reporting across IVT Solution.
Start with the registered site and its intended protection scope
IVT Solution is configured around registered publisher properties. Before deployment, confirm that the correct main site or subdomain exists in the platform and that the intended protection mode, reporting scope and advertising configuration are assigned to that exact property.
Work from the exact main domain or registered subdomain that will receive the IVT Solution client script.
Review protection mode, applicable site rules, reporting access and any advertising configuration for that property.
Generate the site-specific header script and any required ad placement code from IVT Solution.
Confirm the exact-site setup and expected reporting before expanding a deployment across additional properties.
Use the generated code for the exact registered site
Header script
IVT Solution generates a client-loader script for the selected domain or subdomain. Add the generated script once in the page header for that exact property.
Ad placement code
Where an IVT Solution-managed ad placement is configured, use the generated placement element at the intended placement location. The exact value is produced by the platform for the registered site and ad unit.
Keep main-site ownership and exact-site deployment distinct
A main site can act as the parent property for registered subdomains. Operational settings and reporting should remain attributable to the property and site family they belong to. Exact-site deployment ensures that client configuration is not accidentally reused across unrelated properties.
Represents the primary registered publisher property and its site-family relationship.
Represents a separately recognized deployment property within its parent site family.
Interpret signals as evidence, not automatic verdicts
IVT Solution combines multiple publisher-side traffic-quality dimensions. Individual unusual signals should be interpreted in context and correlated with other available evidence.
Browser and interaction evidence associated with automated or non-human behavior.
Timing, repetition and request-rate patterns evaluated against configured expectations.
Network, VPN, proxy, TOR, hosting and related infrastructure context.
Referrer and traffic-source context used to distinguish unusual acquisition from confirmed risk.
Available evidence combined into explainable risk and confidence context.
Publisher-side interaction and click-integrity evidence kept separate from third-party ad creative.
Choose the operating mode that matches the intended enforcement level
Native traffic-quality analysis and reporting remain active without website blocking, challenge or ad suppression.
Configured native protection and AdClick controls are active while external intelligence providers remain outside the active protection path.
Configured external intelligence may supplement native protection as corroborating evidence while the native protection foundation remains primary.
Website access and advertising eligibility are separate decisions
Website protection is governed by the active protection mode and applicable rules. Advertising eligibility is evaluated separately. A visitor may therefore remain able to access website content while publisher-side monetization is restricted.
Evaluate publisher-side ad eligibility before permitted ad requests proceed
Revenue Guard is a separate publisher-side decision layer. It can restrict ad eligibility when configured risk conditions are sufficiently supported without requiring the same outcome for website access.
Evaluate available native traffic-quality evidence and contextual risk.
Use only the website-access action permitted by the active mode and configured rules.
Revenue Guard independently determines whether the publisher-side ad request is eligible to proceed.
Eligible requests continue to the advertising platform without IVT Solution manipulating third-party creative or ad frames.
Keep traffic, protection and advertising observations attributable
Reporting should distinguish native traffic-quality evidence, protection outcomes, configured provider evidence and publisher-side advertising observations. Platform-reported advertising measurements remain separate from IVT Solution's own observations.
Use VPN, proxy, TOR and hosting evidence in context
Network characteristics can contribute useful risk context, but a network category by itself is not proof of invalid traffic. Stronger conclusions should rely on corroborating evidence and the active protection configuration.
Evaluate publisher-side interaction evidence without manipulating ad creative
Click-integrity analysis operates on publisher-side evidence and does not inspect or manipulate advertising creative content inside third-party frames.
Use timing and repetition patterns as part of correlated risk analysis
Behavior and rate protection can evaluate request frequency, repeated actions and related timing evidence. These signals should remain part of the broader traffic-quality context rather than becoming isolated automatic verdicts.
Apply explicit publisher controls independently from traffic-quality classification
Geo and IP rules are publisher-configured access controls. Their enforcement should remain distinguishable from a traffic-quality classification so reporting can explain why a visitor was restricted.