Search syndication turns user intent into structured advertising results. The visible response may be simple, but the operating path must coordinate publisher access, feed contracts, bid policy, traffic quality, delivery limits and commercial reporting.
Connect supply to multiple demand feeds
Nexus Search administration connects provider feeds with publisher search links. Operators configure feed assignment, search type, backfill, revenue share, caps and source macros. Request and response contracts are validated with the selected provider during integration.
- Affiliate and direct-publisher access
- XML and JSON provider contracts
- Feed assignment and eligibility
- Provider-specific integration validation
Define publisher-link eligibility
Use the Search link Targets tab to choose which sub-IDs, domains and keywords are eligible for that link. These selectors define traffic boundaries; provider feed assignment and commercial settings are separate steps.
Inside Nexus / configuration example
A Search publisher link has its own Subid, Domains and Keywords controls. Define eligibility at that link level; provider-feed settings are a separate configuration.
Set link-level targeting
Use the dedicated Subid, Domains and Keywords selectors to define the traffic eligible for a publisher link.
Captured from a new, unsaved Search link. The selectors display All; this illustrates the editor, not a recommended traffic policy.
Make commercial policy explicit
Search feed and link editors expose revenue-share and search-cap settings. XML feeds have a distinct set of minimum-bid, QPS, click and budget controls. Keep these product-specific settings separate instead of assuming every module offers the same pricing fields.
Reconcile technical and commercial evidence
Click and search logs, feed connection errors, target-level delivery and provider reporting help explain why a route performs differently from its headline bid. Nexus brings those signals into the same operating model used for routing and partner control.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.