Docs / Capability guide
VerificationVendor extension
Apply an exact-host policy to verification signals and pixel behavior.
All capabilities · Related guide · Agent prompt for this capability
When to use this example
Use this example when your verification setup needs different pixel behavior on a defined set of hosts. An exact-host rule makes it possible to test the policy without relying on an external measurement service.
What the example gives you
The starter adds a policy label and suppresses verification pixels for configured hostnames. An unlisted or unknown host receives no safety assertion. The example does not block the auction or provide brand-safety certification.
Before you start
Go for local tests. Host installation also requires a supported kind, reachable gRPC address, matching descriptor/entitlement and an installed stack product. Read the packaged README for policy configuration.
Run the example
Extract the archive and follow README.md for setup, commands, and expected results. Start with go run . -kind verification_vendor -addr 127.0.0.1:50051. Local tests use sample data.
Follow the archive's service configuration and deployment steps before registering or installing it in Riptide. The prerequisites above describe the access and connectivity it needs.
Connect it to your application
Run go test -race ./... in the downloaded starter, then start -kind verification_vendor. Read the corresponding fixture and configure the policy before testing live requests.
VerificationVendor uses ExtensionService Describe, Health and Invoke with method PreBid. Return only verified or explicitly configured signals from your own policy/provider. Keep unknown results distinct from verified results. External certification requires validation by the relevant provider.
Run the gRPC smoke tests, then install using the stack-product workflow. Verify timeout and fallback behavior and remove the activation to test rollback.
Check the result
The descriptor matches the selected kind, gRPC calls return the documented result, and malformed/unsupported requests fail explicitly. A host timeout skips the extension within the request budget.