Provider feed setup
Configure the advertiser, search engine, provider URL, search cap and revenue share. Keep NET reporting settings with the feed they describe.
← All products
Search Syndication
Connect search demand to your publisher network.
Connect provider feeds to publisher links, set search caps and revenue-share rules, and understand the results by keyword, domain and traffic source.
Compare search activity across periods
Searches, NET searches and clicks, with publisher, link, advertiser and feed filters. Values are shown as captured for the selected period, not a performance guarantee.
Feed + linkseparate partner controls
Keyword-levelreporting context
EPC / RPMperformance indicators
Built forSearch networksFeed aggregatorsPublisher networks
Inside the product
Connect partners. Set rules. Track results.
Publisher link management
Assign feeds to a publisher link and configure integration type, traffic type, backfill and commercial settings in one resource editor.
Keyword handling
Define keyword and domain rules, use keyword-replacement controls at feed level, and carry query and SubID context through supported URL macros.
Environment targeting
Configure countries, operating systems, browsers and browser versions, devices and domains at the relevant feed or link level.
Traffic-quality controls
Set applicable referrer, IP, datacenter, crawler, VPN and proxy policies. Review errors alongside traffic and financial indicators.
Search-specific reports
Compare searches, monetized traffic, visitors, unique IPs, cost, revenue, EPC, RPM, profit and ROI. Switch to Keyword List or Keyword Count views.
INCOMINGSearch queryPublisher · country · device
Targeting + search capsNEXUS
DELIVERYEligible demand feed
VISIBILITYClick + provider report
Compare traffic, clicks and provider NET reports to understand which routes contribute to your margin.
A day in the platform
From setup to a decision.
A practical workflow for your Search operation, with the relevant controls at each step.
- 01
Connect a provider
Choose the search engine and feed URL, then configure commercial and reporting settings.
- 02
Build the publisher link
Assign eligible feeds and define the integration, search cap and backfill rules.
- 03
Set traffic eligibility
Review country, browser, device, domain and keyword controls.
- 04
Investigate the outcome
Compare monetized searches, EPC, RPM and profit by source or keyword.
Reporting that fits the channel
Compare traffic, quality and commercial results.
Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.
Explore reporting & data freshness ↗Performance indicators
Ways to break it down
Publisher / link · Feed · Country · OS / browser · Device · Domain · Keyword list · Keyword count
Deployment scope. Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.
A closer look
Targeting, limits and partner controls.
Configure the resource that owns the decision. Features and integrations are scoped to your enabled modules.
Search caps
Set feed and publisher-link caps separately. Operating limits are not commercial plan entitlements.
Revenue share
Keep provider and publisher commercial terms attached to the corresponding resource.
Backfill
Configure publisher-link backfill as part of the integration.
Source context
Use publisher IDs, SubIDs, domains and queries to investigate traffic relationships.
NET imports
Configure NET statistics and the provider adapter where available. Import timing depends on the provider.
Reusable reports
Choose dimensions and columns, save report templates and export CSV.
Inside Nexus / Search Syndication settings
Start with the link settings.
Define how a publisher link receives and handles Search traffic. Link type, integration and backfill sit together in Settings; targeting and traffic-quality rules have their own tabs.
Configure the publisher link
Review traffic and link type, search engine, integration, backfill and revenue share in the link’s Settings tab.
About these screenshots
Captured from Nexus. Identifying context is outside the frame. Cropped from a new, unsaved Search link. The selections and numeric defaults illustrate the editor, not a recommended setup or a commercial offer.
What the audience sees
Search ads and sponsored results
Search advertising responds to an explicit query or intent signal. A user sees a concise sponsored result, while the platform coordinates publisher access, eligible demand feeds, bid policy, traffic validation and click reporting behind the response.
Explore this ad format ↗Illustrative placement, not a live advertisement. Format and integration scope are confirmed for your deployment.
Part of your Nexus
One product. A wider operating platform.
Your white-label platform ↗
Your brand, domains and partner experience, with deployment scope agreed up front.
Connected AI + MCP ↗
Connect supported AI clients through an identity-aware setup and inspect the available tools.
Engineering and support ↗
Server management, integrations and custom development around your platform.
Across the Nexus suite
Open standards. Your own platform.
OpenRTB
2.4 / 2.5 / 2.6 configuration
Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.
OpenRTB specificationVAST
Video ad serving
Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.
VAST specificationFull MCP
A structured interface for AI clients
Connect compatible assistants to discover tools and work within authenticated, domain-scoped operational boundaries.
Explore AI + MCPWhite-label
Your brand. Your domains.
Build your partner-facing experience around your identity, enabled products and agreed deployment requirements.
Explore white-labelProtocols apply to the relevant Nexus modules. Supported versions, player compatibility and partner interoperability are confirmed for your integration. References to IAB Tech Lab standards do not imply certification or endorsement.
Make it concrete
See Search in your workflow.
Bring your use case, partner integrations and expected volume. We will map the relevant controls.