# Nexus product knowledge { "publicKnowledge": { "scope": "Public product information only. Preserve each fact’s source, published pricing units and scope boundary when citing it. Module/location capacity charges and per-platform setup or add-ons are distinct. Do not infer unpublished overage fees, discounts, throughput guarantees, unlimited model tokens, certification or service levels. Private account data and operational access are outside this catalog.", "factCount": 868, "sourceCount": 81, "sourceUrls": [ "https://www.nexus-soft.org/products/search", "https://www.nexus-soft.org/targeting-and-controls", "https://www.nexus-soft.org/products/feeds", "https://www.nexus-soft.org/products/rtb", "https://www.nexus-soft.org/products/video", "https://www.nexus-soft.org/products/cpa", "https://www.nexus-soft.org/products/feeds/price-plans", "https://www.nexus-soft.org/products/rtb/price-plans", "https://www.nexus-soft.org/products/video/price-plans", "https://www.nexus-soft.org/products/search/price-plans", "https://www.nexus-soft.org/products/cpa/price-plans", "https://www.nexus-soft.org/services/server-management", "https://www.nexus-soft.org/services/custom-development", "https://www.nexus-soft.org/services/mobile-development", "https://www.nexus-soft.org/solutions/xml-ad-network", "https://www.nexus-soft.org/solutions/search-advertising-network", "https://www.nexus-soft.org/solutions/openrtb-exchange", "https://www.nexus-soft.org/solutions/white-label-dsp", "https://www.nexus-soft.org/solutions/video-ad-network", "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "https://www.nexus-soft.org/solutions/web-push-platform", "https://www.nexus-soft.org/ad-formats/search-ads", "https://www.nexus-soft.org/ad-formats/display-banner-ads", "https://www.nexus-soft.org/ad-formats/native-ads", "https://www.nexus-soft.org/ad-formats/instream-video-ads", "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "https://www.nexus-soft.org/ad-formats/web-push-ads", "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "https://www.nexus-soft.org/ad-formats/direct-link-ads", "https://www.nexus-soft.org/reporting", "https://www.nexus-soft.org/publisher-platform", "https://www.nexus-soft.org/campaign-management", "https://www.nexus-soft.org/integrations", "https://www.nexus-soft.org/resources/what-is-openrtb", "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "https://www.nexus-soft.org/resources/qps-governance", "https://www.nexus-soft.org/resources/supply-quality-filtering", "https://www.nexus-soft.org/resources/xml-feed-monetization", "https://www.nexus-soft.org/resources/xml-vs-json-feeds", "https://www.nexus-soft.org/resources/affiliate-subid-tracking", "https://www.nexus-soft.org/resources/duplicate-request-protection", "https://www.nexus-soft.org/resources/vast-video-advertising", "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "https://www.nexus-soft.org/resources/web-app-ctv-video", "https://www.nexus-soft.org/resources/mcp-for-adtech", "https://www.nexus-soft.org/resources/connect-ai-client-to-nexus", "https://www.nexus-soft.org/resources/mcp-security-model", "https://www.nexus-soft.org/resources/ai-ready-adtech-checklist", "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "https://www.nexus-soft.org/resources/white-label-adtech-platform", "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "https://www.nexus-soft.org/resources/legacy-adtech-migration", "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "https://www.nexus-soft.org/resources/click-fraud-filters-adtech", "https://www.nexus-soft.org/resources/feed-bid-limit-management", "https://www.nexus-soft.org/resources/publisher-member-management-adtech", "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "https://www.nexus-soft.org/resources/contextual-ads-domain-parking", "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "https://www.nexus-soft.org/docs", "https://www.nexus-soft.org/docs/mcp/quickstart", "https://www.nexus-soft.org/docs/mcp/tools", "https://www.nexus-soft.org/docs/mcp/resources", "https://www.nexus-soft.org/docs/mcp/security", "https://www.nexus-soft.org/services/custom-adtech-development", "https://www.nexus-soft.org/services/adtech-infrastructure-management", "https://www.nexus-soft.org/technology", "https://www.nexus-soft.org/white-label", "https://www.nexus-soft.org/", "https://www.nexus-soft.org/ai-mcp", "https://www.nexus-soft.org/deployment", "https://www.nexus-soft.org/products", "https://www.nexus-soft.org/legal/terms", "https://www.nexus-soft.org/legal/privacy", "https://www.nexus-soft.org/contact" ], "facts": [ { "id": "product.search.overview", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication", "text": "Connect provider feeds to publisher links, set search caps and revenue-share rules, and understand the results by keyword, domain and traffic source." }, { "id": "product.search.capability.0", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Provider feed setup", "text": "Configure the advertiser, search engine, provider URL, search cap and revenue share. Keep NET reporting settings with the feed they describe." }, { "id": "product.search.capability.1", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Publisher link management", "text": "Assign feeds to a publisher link and configure integration type, traffic type, backfill and commercial settings in one resource editor." }, { "id": "product.search.capability.2", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Keyword handling", "text": "Define keyword and domain rules, use keyword-replacement controls at feed level, and carry query and SubID context through supported URL macros." }, { "id": "product.search.capability.3", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Environment targeting", "text": "Configure countries, operating systems, browsers and browser versions, devices and domains at the relevant feed or link level." }, { "id": "product.search.capability.4", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Traffic-quality controls", "text": "Set applicable referrer, IP, datacenter, crawler, VPN and proxy policies. Review errors alongside traffic and financial indicators." }, { "id": "product.search.capability.5", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search-specific reports", "text": "Compare searches, monetized traffic, visitors, unique IPs, cost, revenue, EPC, RPM, profit and ROI. Switch to Keyword List or Keyword Count views." }, { "id": "product.search.control.0", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search caps", "text": "Set feed and publisher-link caps separately. Operating limits are not commercial plan entitlements." }, { "id": "product.search.control.1", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Revenue share", "text": "Keep provider and publisher commercial terms attached to the corresponding resource." }, { "id": "product.search.control.2", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Backfill", "text": "Configure publisher-link backfill as part of the integration." }, { "id": "product.search.control.3", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Source context", "text": "Use publisher IDs, SubIDs, domains and queries to investigate traffic relationships." }, { "id": "product.search.control.4", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "NET imports", "text": "Configure NET statistics and the provider adapter where available. Import timing depends on the provider." }, { "id": "product.search.control.5", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Reusable reports", "text": "Choose dimensions and columns, save report templates and export CSV." }, { "id": "product.search.workflow.0", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Connect a provider", "text": "Choose the search engine and feed URL, then configure commercial and reporting settings." }, { "id": "product.search.workflow.1", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Build the publisher link", "text": "Assign eligible feeds and define the integration, search cap and backfill rules." }, { "id": "product.search.workflow.2", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Set traffic eligibility", "text": "Review country, browser, device, domain and keyword controls." }, { "id": "product.search.workflow.3", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Investigate the outcome", "text": "Compare monetized searches, EPC, RPM and profit by source or keyword." }, { "id": "product.search.metrics", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Reporting metrics", "text": "Searches; Monetized; Unique IPs; Visitors; Coverage; Clicks; Cost; Revenue; EPC; RPM; Profit; ROI" }, { "id": "product.search.dimensions", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Reporting dimensions", "text": "Publisher / link; Feed; Country; OS / browser; Device; Domain; Keyword list; Keyword count" }, { "id": "product.search.contract", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Integration contracts", "text": "Search-engine selection; Provider URL macros; NET reporting configuration" }, { "id": "product.search.fit", "kind": "product", "url": "https://www.nexus-soft.org/products/search", "topics": [ "products", "product.search" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Who it is for", "text": "Search networks; Feed aggregators; Publisher networks" }, { "id": "product.search.targeting.0", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Countries, OS, devices", "text": "Feed settings" }, { "id": "product.search.targeting.1", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Browser / version", "text": "Browser + version" }, { "id": "product.search.targeting.2", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Domains / source IDs", "text": "Link + feed rules" }, { "id": "product.search.targeting.3", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Applications", "text": "Integration-specific" }, { "id": "product.search.targeting.4", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Specialized targeting", "text": "Keywords + replacement" }, { "id": "product.search.targeting.5", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.search", "targeting" ], "boundary": "Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "sourceTitle": "Search Syndication", "title": "Search Syndication: Operating limits", "text": "Search caps + RevShare" }, { "id": "product.feeds.overview", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds", "text": "Connect publisher accounts with demand feeds. Configure targeting, minimum bids, QPS and click limits, then compare publisher-side and feed-side results." }, { "id": "product.feeds.capability.0", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Publisher-to-feed mapping", "text": "Choose demand feeds for each affiliate account. XML direct links are supported for publisher traffic and configured demand destinations. Popunder JS is available with script, frequency and delay settings. Keep source controls in place; browser restrictions still determine window behavior." }, { "id": "product.feeds.capability.1", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Provider configuration", "text": "Set provider and feed type, image and icon requirements, SubID handling, result count and timeout." }, { "id": "product.feeds.capability.2", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Detailed targeting", "text": "Configure countries, operating systems, browsers, devices, domains, carriers, keywords and subscriber age." }, { "id": "product.feeds.capability.3", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Bids, limits and expiry", "text": "Set minimum bid, maximum requests and QPS, daily budget, click limits, clicks per IP or IP + user-agent, and result expiry." }, { "id": "product.feeds.capability.4", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Quality policy", "text": "Configure duplicate, fast-click, JavaScript, cookie, referrer, user-agent, iframe and headless-browser checks alongside network-risk categories." }, { "id": "product.feeds.capability.5", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Reports from both sides", "text": "Review requests, coverage, valid and invalid clicks, revenue, NET metrics and profit. Configure provider NET imports separately from traffic reporting." }, { "id": "product.feeds.control.0", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Commercial limits", "text": "Define minimum bid, daily budget and revenue-share configuration at feed level." }, { "id": "product.feeds.control.1", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Request capacity", "text": "Bound requests and QPS independently from pricing-plan allowances." }, { "id": "product.feeds.control.2", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Repeated clicks", "text": "Configure limits per IP and IP + user-agent, duplicate policy and result expiry." }, { "id": "product.feeds.control.3", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Subscriber context", "text": "Use subscriber-age and carrier targeting where the feed provides those signals." }, { "id": "product.feeds.control.4", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Publisher handling", "text": "Configure backfill, postback and invalid-traffic handling in the affiliate editor." }, { "id": "product.feeds.control.5", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "NET imports", "text": "Select the provider API adapter, update days, SubID import behavior and timeout." }, { "id": "product.feeds.workflow.0", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Set up the affiliate", "text": "Define the publisher account, integration and traffic-handling settings." }, { "id": "product.feeds.workflow.1", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Configure demand", "text": "Add provider settings, commercial limits, targeting and quality rules." }, { "id": "product.feeds.workflow.2", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Assign the relationship", "text": "Map selected feeds to the affiliate account." }, { "id": "product.feeds.workflow.3", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "Compare both sides", "text": "Review affiliate and feed reports by SubID, country, browser and domain." }, { "id": "product.feeds.metrics", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Reporting metrics", "text": "Requests; Valid requests; Errors; Coverage; Clicks; Invalid clicks; NET clicks; CPC; NET CPC; Revenue; NET revenue; Profit" }, { "id": "product.feeds.dimensions", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Reporting dimensions", "text": "Affiliate; Feed; SubID; Country; OS; Browser; Domain" }, { "id": "product.feeds.contract", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Integration contracts", "text": "Provider feed adapters; Publisher integration endpoints; Configurable NET imports" }, { "id": "product.feeds.fit", "kind": "product", "url": "https://www.nexus-soft.org/products/feeds", "topics": [ "products", "product.feeds" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Who it is for", "text": "Affiliate networks; Publishers; Demand aggregators" }, { "id": "product.feeds.targeting.0", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Countries, OS, devices", "text": "Feed targets" }, { "id": "product.feeds.targeting.1", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Browser / version", "text": "Browser selection" }, { "id": "product.feeds.targeting.2", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Domains / source IDs", "text": "Domains + SubID" }, { "id": "product.feeds.targeting.3", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Applications", "text": "Integration-specific" }, { "id": "product.feeds.targeting.4", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Specialized targeting", "text": "Carrier + subscriber age" }, { "id": "product.feeds.targeting.5", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.feeds", "targeting" ], "boundary": "Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "sourceTitle": "XML / JSON feeds", "title": "XML / JSON feeds: Operating limits", "text": "QPS + bid + clicks + budget" }, { "id": "product.rtb.overview", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB", "text": "Manage exchange and demand connections with OpenRTB version selection, bid floors, targeting and partner grants. Keep auction and financial signals in the same operating view." }, { "id": "product.rtb.capability.0", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Exchange configuration", "text": "Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection. Prebid.js and Prebid Server integrations are available now; configure compatible adapters, endpoints and inventory for your deployment." }, { "id": "product.rtb.capability.1", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Demand delivery controls", "text": "Configure DSP type, timeout, traffic types, Gzip and demand-side QPS. Keep NET import settings with the demand resource." }, { "id": "product.rtb.capability.2", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Inventory targeting", "text": "Use country, OS, browser, device, ad size, application and bundle controls, with inventory and video-type settings on demand." }, { "id": "product.rtb.capability.3", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Partner grants", "text": "Set Allowed Demands for an exchange and Allowed Exchanges for demand. Define trading relationships explicitly." }, { "id": "product.rtb.capability.4", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Floors and quality filters", "text": "Configure bid floors, exchange maximum bid, network-risk rules and SSP, site, publisher, domain or creative lists." }, { "id": "product.rtb.capability.5", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Cookie sync and reporting", "text": "Cookie sync is available now. Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics. Cookie sync has its own partner and browser requirements, separate from the Prebid integration setup." }, { "id": "product.rtb.control.0", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Version and auction", "text": "Select OpenRTB version and auction settings for the partner connection." }, { "id": "product.rtb.control.1", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Bid boundaries", "text": "Configure floors and exchange maximum bid separately from demand QPS and timeout." }, { "id": "product.rtb.control.2", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Supply context", "text": "Use SSP, Site/App ID, Publisher ID, domains and app bundles." }, { "id": "product.rtb.control.3", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Demand exclusions", "text": "Manage supported domain, inventory and creative-ID lists." }, { "id": "product.rtb.control.4", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Delivery settings", "text": "Configure notifications, supply-chain settings and third-party pixel limits." }, { "id": "product.rtb.control.5", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Financial visibility", "text": "Review revenue, NET revenue, spend, NET spend and profit alongside delivery." }, { "id": "product.rtb.workflow.0", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Register supply", "text": "Configure the exchange adapter, OpenRTB version and commercial rules." }, { "id": "product.rtb.workflow.1", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Connect demand", "text": "Set demand targeting, bid floors, QPS and timeout." }, { "id": "product.rtb.workflow.2", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Grant partner access", "text": "Define which exchange and demand resources may work together." }, { "id": "product.rtb.workflow.3", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "Review the auction path", "text": "Inspect requests, errors, win rate, impressions and NET financial indicators." }, { "id": "product.rtb.metrics", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Reporting metrics", "text": "Requests; Errors; Synced requests; NURL / BURL / LURL; Impressions; Win %; Conversions; Revenue; NET revenue; Spend; NET spend; Profit" }, { "id": "product.rtb.dimensions", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Reporting dimensions", "text": "Exchange; Site ID; Publisher ID; Size; Country; OS / browser; Device; Connection / carrier; Domain; Bundle" }, { "id": "product.rtb.contract", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Integration contracts", "text": "OpenRTB version selection; Supply / demand grants; Cookie-sync settings" }, { "id": "product.rtb.fit", "kind": "product", "url": "https://www.nexus-soft.org/products/rtb", "topics": [ "products", "product.rtb" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Who it is for", "text": "Ad exchanges; SSPs; Demand teams" }, { "id": "product.rtb.targeting.0", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Countries, OS, devices", "text": "Exchange + demand" }, { "id": "product.rtb.targeting.1", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Browser / version", "text": "Browser selection" }, { "id": "product.rtb.targeting.2", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Domains / source IDs", "text": "Site / publisher / domain" }, { "id": "product.rtb.targeting.3", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Applications", "text": "Bundle + app name" }, { "id": "product.rtb.targeting.4", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Specialized targeting", "text": "Ad size + inventory type" }, { "id": "product.rtb.targeting.5", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.rtb", "targeting" ], "boundary": "Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "sourceTitle": "OpenRTB", "title": "OpenRTB: Operating limits", "text": "Floors + QPS + timeout" }, { "id": "product.video.overview", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video", "text": "Manage publisher channels and demand tags in a dedicated VAST workspace. Configure environments, pricing and delivery limits, then follow video events from Started to Completed." }, { "id": "product.video.capability.0", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Publisher channels", "text": "Configure publisher, price type, CPM, floor, required fields and the web, app or CTV environment." }, { "id": "product.video.capability.1", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Demand tag management", "text": "Keep advertiser, source, tag type, timeout and delivery settings together. Tag configuration offers VAST, Audio and RTB options." }, { "id": "product.video.capability.2", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Application-level targeting", "text": "Configure countries, operating systems, ad sizes, languages, bundle IDs and application names." }, { "id": "product.video.capability.3", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Delivery limits", "text": "Set applicable hourly and daily revenue, request and impression limits. Demand tags add maximum QPS and scheduled-delivery controls." }, { "id": "product.video.capability.4", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Channel and tag grants", "text": "Assign allowed tags to a channel and allowed channels to a tag. Keep publisher integration and host configuration separate from demand." }, { "id": "product.video.capability.5", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Video-specific reporting", "text": "Inspect VAST URI validity, errors, fill, impressions and revenue. Review Started, First Quartile, Midpoint, Third Quartile and Completed." }, { "id": "product.video.control.0", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Environment", "text": "Select web, app or CTV and configure the required request fields." }, { "id": "product.video.control.1", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Commercial setup", "text": "Set publisher price type, CPM and floor, with demand-tag CPM configured independently." }, { "id": "product.video.control.2", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Traffic policy", "text": "Configure network-risk and applicable referrer, IP and user-agent matching checks." }, { "id": "product.video.control.3", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Expiry and limits", "text": "Control impression expiry, QPS and hourly or daily limits." }, { "id": "product.video.control.4", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Delivery context", "text": "Configure tracking pixels and scheduled delivery on demand tags." }, { "id": "product.video.control.5", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Playback evidence", "text": "Review URI validity, invalid impressions, fill and completion events." }, { "id": "product.video.workflow.0", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Create the channel", "text": "Define publisher, pricing, environment and integration fields." }, { "id": "product.video.workflow.1", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Configure the tag", "text": "Set demand source, timeout, targeting and delivery limits." }, { "id": "product.video.workflow.2", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Connect eligible demand", "text": "Grant access between channels and tags." }, { "id": "product.video.workflow.3", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "Follow video events", "text": "Review request and URI errors alongside fill, revenue and completion." }, { "id": "product.video.metrics", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Reporting metrics", "text": "Requests; Tag requests; Errors; Valid / invalid URI; Impressions; Fill %; Revenue; Publisher CPM; Started; First quartile; Midpoint; Completed" }, { "id": "product.video.dimensions", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Reporting dimensions", "text": "Channel / tag; Country; OS; App bundle; Application; Environment; Device / size" }, { "id": "product.video.contract", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Integration contracts", "text": "VAST channel / tag workflow; Web / App / CTV configuration; Playback event reports" }, { "id": "product.video.fit", "kind": "product", "url": "https://www.nexus-soft.org/products/video", "topics": [ "products", "product.video" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Who it is for", "text": "Video publishers; CTV operators; Ad networks" }, { "id": "product.video.targeting.0", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Countries, OS, devices", "text": "Channel + tag" }, { "id": "product.video.targeting.1", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Browser / version", "text": "Integration-specific" }, { "id": "product.video.targeting.2", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Domains / source IDs", "text": "Channel / app context" }, { "id": "product.video.targeting.3", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Applications", "text": "Bundle + app name" }, { "id": "product.video.targeting.4", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Specialized targeting", "text": "Language + environment" }, { "id": "product.video.targeting.5", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.video", "targeting" ], "boundary": "VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "sourceTitle": "VAST video", "title": "VAST video: Operating limits", "text": "CPM + QPS + hourly/daily caps" }, { "id": "product.cpa.overview", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL", "text": "Operate performance offers with fixed-price or revenue-share payouts, targeting, conversion windows and caps. Bring publisher access, creatives and conversion reporting into one workflow." }, { "id": "product.cpa.capability.0", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Offer workspace", "text": "Manage advertiser and offer references, preview and tracking URLs, images, descriptions, restrictions and expiry." }, { "id": "product.cpa.capability.1", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Payout configuration", "text": "Configure fixed-price or revenue-share terms, currency and advertiser/publisher payouts. Event categories include installation, registration, sales, subscription and in-app events." }, { "id": "product.cpa.capability.2", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Conversion rules and caps", "text": "Set conversion windows, pending or multiple-conversion controls, daily/monthly clicks, conversions and revenue, plus minimum/maximum CR." }, { "id": "product.cpa.capability.3", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Eligibility and access", "text": "Configure approval and terms requirements, private offers and publisher visibility. Keep these separate from delivery targeting." }, { "id": "product.cpa.capability.4", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Targeting and traffic filters", "text": "Use country, OS version, browser, device, connection and carrier context. Configure SubID, domain and IP-range allowlists and blocklists." }, { "id": "product.cpa.capability.5", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Creatives and performance", "text": "Organize offer creatives and publisher-cap records. Review click context, valid/invalid conversions, advertiser/publisher payouts, profit, CR, CPC and RPC." }, { "id": "product.cpa.control.0", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Commercial models", "text": "Keep fixed payout and revenue-share rules explicit." }, { "id": "product.cpa.control.1", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Conversion window", "text": "Define the window and pending/multiple-conversion policy. Validate attribution during integration." }, { "id": "product.cpa.control.2", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Volume limits", "text": "Set daily and monthly click, conversion and revenue boundaries." }, { "id": "product.cpa.control.3", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Private access", "text": "Require approval or terms and control publisher visibility." }, { "id": "product.cpa.control.4", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Source rules", "text": "Use SubID, domain and IP-range lists and invalid-traffic redirects." }, { "id": "product.cpa.control.5", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Click diagnostics", "text": "Inspect click ID, offer, publisher, source, SubID, environment, errors and payouts." }, { "id": "product.cpa.workflow.0", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Define the offer", "text": "Add tracking destination, event category, payout and terms." }, { "id": "product.cpa.workflow.1", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Set eligibility and caps", "text": "Configure targeting, conversion windows and daily or monthly limits." }, { "id": "product.cpa.workflow.2", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Organize publisher access", "text": "Use approvals, private-offer settings and creatives." }, { "id": "product.cpa.workflow.3", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "Review performance", "text": "Inspect clicks, conversions and both sides of the payout." }, { "id": "product.cpa.metrics", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Reporting metrics", "text": "Clicks; Unique clicks; Invalid clicks; Conversions; Invalid conversions; Advertiser payout; Publisher payout; Profit; CR; CPC; RPC" }, { "id": "product.cpa.dimensions", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Reporting dimensions", "text": "Publisher / offer; Advertiser; Source / SubID; Country / city; OS / browser; Device; Connection / carrier; Currency" }, { "id": "product.cpa.contract", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Integration contracts", "text": "Fixed / revenue-share payouts; Offer tracking URLs; Conversion reporting" }, { "id": "product.cpa.fit", "kind": "product", "url": "https://www.nexus-soft.org/products/cpa", "topics": [ "products", "product.cpa" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Who it is for", "text": "Performance networks; Agencies; Direct advertisers" }, { "id": "product.cpa.targeting.0", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Countries, OS, devices", "text": "Offer targets" }, { "id": "product.cpa.targeting.1", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Browser / version", "text": "Browser + OS versions" }, { "id": "product.cpa.targeting.2", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Domains / source IDs", "text": "SubID / domain / IP lists" }, { "id": "product.cpa.targeting.3", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Applications", "text": "App ID + offer context" }, { "id": "product.cpa.targeting.4", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Specialized targeting", "text": "Connection + carrier" }, { "id": "product.cpa.targeting.5", "kind": "product", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "products", "product.cpa", "targeting" ], "boundary": "Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery.", "sourceTitle": "CPA / CPI / CPL", "title": "CPA / CPI / CPL: Operating limits", "text": "Payout + daily/monthly caps" }, { "id": "quality.control.0", "kind": "policy", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "targeting", "quality" ], "boundary": "Controls apply in the relevant resource editors. No filter guarantees perfect detection.", "title": "Network signals", "text": "Datacenter, crawler, attack-source, fake-crawler, Tor, scraper, VPN and proxy categories are available in the relevant resource editors." }, { "id": "quality.control.1", "kind": "policy", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "targeting", "quality" ], "boundary": "Controls apply in the relevant resource editors. No filter guarantees perfect detection.", "title": "Request consistency", "text": "XML controls include duplicate/fast clicks, JavaScript, cookies, referrer, user-agent, iframe and headless-browser checks." }, { "id": "quality.control.2", "kind": "policy", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "targeting", "quality" ], "boundary": "Controls apply in the relevant resource editors. No filter guarantees perfect detection.", "title": "Explicit exceptions", "text": "Use supported source, domain, publisher, creative and IP lists to express policy at the correct resource level." }, { "id": "quality.control.3", "kind": "policy", "url": "https://www.nexus-soft.org/targeting-and-controls", "topics": [ "targeting", "quality" ], "boundary": "Controls apply in the relevant resource editors. No filter guarantees perfect detection.", "title": "Evidence after configuration", "text": "Review invalid traffic and error dimensions alongside delivery and financial indicators. No filter guarantees perfect detection." }, { "id": "pricing.product.feeds.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/feeds/price-plans", "topics": [ "pricing", "product.feeds" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "XML / JSON feeds pricing", "title": "XML / JSON feeds: published capacity price", "text": "XML / JSON feeds costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.product.rtb.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/rtb/price-plans", "topics": [ "pricing", "product.rtb" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "OpenRTB pricing", "title": "OpenRTB: published capacity price", "text": "OpenRTB costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.product.video.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/video/price-plans", "topics": [ "pricing", "product.video" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "VAST Video pricing", "title": "VAST Video: published capacity price", "text": "VAST Video costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations." }, { "id": "pricing.product.search.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "product.search" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "Search Syndication pricing", "title": "Search Syndication: published capacity price", "text": "Search Syndication costs $500 per month for each block of 100,000 searches per day. Minimum capacity and increments are 100,000 daily searches; the price is monthly, not a daily fee." }, { "id": "pricing.product.cpa.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/cpa/price-plans", "topics": [ "pricing", "product.cpa" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "CPA / CPI / CPL pricing", "title": "CPA / CPI / CPL: published capacity price", "text": "CPA / CPI / CPL costs $500 per month for each block of 100,000 incoming clicks per day. Minimum capacity and increments are 100,000 daily incoming clicks; the price is monthly, not a daily fee or a charge per conversion." }, { "id": "pricing.question.0", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "How is monthly capacity priced?", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." }, { "id": "pricing.question.1", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I share QPS capacity across modules or locations?", "text": "Each selected XML / JSON, OpenRTB or VAST Video module has a minimum of 1,000 incoming QPS in every selected location, increasing in steps of 1,000. Modules and locations are billed separately; their capacity blocks cannot be pooled. Available locations are US, EU, Asia; US is the default for a new configuration. Select each location at most once within a module. Search and CPA each use one daily-capacity selection per platform." }, { "id": "pricing.question.2", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Is outgoing QPS charged?", "text": "For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing." }, { "id": "pricing.question.3", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I increase or decrease QPS during the month?", "text": "QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge." }, { "id": "pricing.question.4", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I run more than one platform?", "text": "You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform." }, { "id": "pricing.question.5", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Do the prices include hosting, white-label and taxes?", "text": "Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "pricing.question.6", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Is the setup fee monthly or per module?", "text": "Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator." }, { "id": "pricing.question.7", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Does external MCP integration cost extra?", "text": "Nexus integration through external MCP is free. Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization. External MCP integration is separate from the paid in-platform AI add-on." }, { "id": "pricing.question.8", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "When does the free add-on month start?", "text": "Additional Fraud Filters, Test links and In-platform AI each have a free first month beginning when that add-on is activated, not when an account is registered. Capacity charges and setup are not part of this free trial. After-trial prices show the ongoing rates; this calculator does not activate an add-on, create a checkout or imply automatic charging." }, { "id": "pricing.question.9", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "What if I need an SLA, a discount or an overage agreement?", "text": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order." }, { "id": "pricing.question.10", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Do Basic, Professional and Premium plans still define the prices?", "text": "Published prices now use the capacity blocks above instead of Basic, Professional and Premium plan labels. Choose the actual modules and capacities; those old labels do not define additional numerical allowances." }, { "id": "pricing.question.11", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "How do I calculate the total for one platform?", "text": "Select modules, capacity in each QPS location and optional add-ons in the calculator. It sums the independently priced blocks and charges each add-on once per platform. The ongoing monthly total includes add-ons at their published rates. The first-month estimate excludes their free activation month and adds the one-time platform setup fee. The estimate assumes the selected add-ons are activated together; an enquiry does not create an order or automatic charge." }, { "id": "pricing.question.12", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "What is the daily click limit for XML / JSON feeds and OpenRTB?", "text": "XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.rule.billing", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Monthly capacity pricing", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." }, { "id": "pricing.rule.incoming", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Incoming QPS is the billing basis", "text": "For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing." }, { "id": "pricing.rule.locations", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Each QPS module and location is separate", "text": "Each selected XML / JSON, OpenRTB or VAST Video module has a minimum of 1,000 incoming QPS in every selected location, increasing in steps of 1,000. Modules and locations are billed separately; their capacity blocks cannot be pooled. Available locations are US, EU, Asia; US is the default for a new configuration. Select each location at most once within a module. Search and CPA each use one daily-capacity selection per platform." }, { "id": "pricing.rule.changes", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Change QPS capacity when you need to", "text": "QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge." }, { "id": "pricing.rule.platforms", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Separate platforms are billed separately", "text": "You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform." }, { "id": "pricing.rule.included", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Final prices include hosting and white-label", "text": "Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "pricing.rule.setup", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "One-time platform setup", "text": "Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator." }, { "id": "pricing.rule.mcp", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Free Nexus MCP integration", "text": "Nexus integration through external MCP is free. Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization. External MCP integration is separate from the paid in-platform AI add-on." }, { "id": "pricing.rule.trials", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "First month free for all three add-ons", "text": "Additional Fraud Filters, Test links and In-platform AI each have a free first month beginning when that add-on is activated, not when an account is registered. Capacity charges and setup are not part of this free trial. After-trial prices show the ongoing rates; this calculator does not activate an add-on, create a checkout or imply automatic charging." }, { "id": "pricing.rule.custom", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Confirm requirements outside this tariff", "text": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order." }, { "id": "pricing.rule.dailyclicks", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Daily click limits for XML / JSON and OpenRTB", "text": "XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.addon.fraud-filters", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.fraud-filters" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Additional Fraud Filters", "text": "Additional traffic-quality checks beyond the standard platform filters: datacenters, known attack sources, Tor, VPN, crawlers and fake crawlers, web scrapers and proxies. These checks do not guarantee detection of all invalid traffic. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.fraud-filters.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.fraud-filters" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Additional Fraud Filters: included features", "text": "Datacenter and known attack-source checks; Tor, VPN and proxy checks; Crawler, fake-crawler and web-scraper checks" }, { "id": "pricing.addon.test-links", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.test-links" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Test links", "text": "Inspect the final URL, redirect chain, redirect timing and screenshot for a test link. Select the referrer, country, device profile and browser engine for the test. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.test-links.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.test-links" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Test links: included features", "text": "Final URL, redirect chain and timing; Screenshot of the tested destination; Selectable referrer, country, device profile and browser engine" }, { "id": "pricing.addon.platform-ai", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.platform-ai" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "In-platform AI", "text": "AI inside your Nexus platform, with model usage included in the add-on price. This tariff is for AI inside a customer's platform, not the public product guide on this website. The add-on is billed once per platform, not separately for each module or location. $500 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.platform-ai.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.platform-ai" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "In-platform AI: included features", "text": "AI inside your platform; Model usage included; One add-on charge per platform" }, { "id": "service.server-management.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Server management", "text": "We help operate web servers, databases, DNS and load-balanced environments. Start with an existing system or a new deployment; agree on the systems, responsibilities and support coverage before work begins." }, { "id": "service.server-management.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Setup & configuration", "text": "Web servers, DNS, mail services and load balancing, configured for the agreed environment." }, { "id": "service.server-management.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Maintenance & performance", "text": "Server updates, troubleshooting and tuning for the services carrying your workload." }, { "id": "service.server-management.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Security & access", "text": "Security reviews, firewall configuration and server-side hardening." }, { "id": "service.server-management.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Databases & caching", "text": "Administration for MySQL, PostgreSQL, MongoDB and Redis, according to your stack." }, { "id": "service.server-management.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Backups & recovery", "text": "Backup configuration, restoration and recovery planning." }, { "id": "service.server-management.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Hosting migrations", "text": "Plan the destination, data transfer, validation and cutover for a server move." }, { "id": "service.server-management.context", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Server management: information to bring", "text": "Your current hosting and server roles; The recurring issue or upcoming infrastructure change; Required coverage and maintenance windows" }, { "id": "service.custom-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Custom software development", "text": "When an off-the-shelf product does not fit, we define the workflow, design the system, implement it and test it against agreed acceptance criteria. Work can start with a bounded project or an ongoing development engagement." }, { "id": "service.custom-development.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Requirements & architecture", "text": "Map user journeys, system boundaries and the interfaces the software needs." }, { "id": "service.custom-development.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Applications & interfaces", "text": "Build web applications and operational interfaces around your workflows." }, { "id": "service.custom-development.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "API & data integration", "text": "Connect applications through agreed APIs, data formats and database contracts." }, { "id": "service.custom-development.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Platform extensions", "text": "Adapt existing components and integrate new functionality into the wider system." }, { "id": "service.custom-development.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Testing & acceptance", "text": "Validate components and integrations, then review the complete system against the specification." }, { "id": "service.custom-development.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Maintenance & evolution", "text": "Define the support, documentation and follow-up work needed after delivery." }, { "id": "service.custom-development.context", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Custom software development: information to bring", "text": "The workflow and users you want to support; Existing applications and integration requirements; Scope, priorities and acceptance criteria" }, { "id": "service.mobile-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Mobile application development", "text": "We help shape mobile products through prototyping, interface design, iterative development and testing. Native, cross-platform or web-based delivery is selected around the project requirements rather than assumed in advance." }, { "id": "service.mobile-development.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Product & UX design", "text": "Clarify the essential tasks, map user journeys and prototype the experience." }, { "id": "service.mobile-development.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Delivery approach", "text": "Compare native, cross-platform and web-based options for the intended devices." }, { "id": "service.mobile-development.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Connected services", "text": "Integrate mobile workflows with the application and cloud services they depend on." }, { "id": "service.mobile-development.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Incremental development", "text": "Prioritize useful features and review working iterations with your team." }, { "id": "service.mobile-development.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Quality & feedback", "text": "Test releases and use customer feedback to guide the next iteration." }, { "id": "service.mobile-development.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Project engagement", "text": "Discuss fixed-scope, ongoing team or time-and-material arrangements." }, { "id": "service.mobile-development.context", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Mobile application development: information to bring", "text": "Your audience and their most important tasks; Target devices and existing backend services; Release priorities and available project scope" }, { "id": "solution.xml-ad-network.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network", "text": "Run an XML / JSON feed monetization platform. Connect advertiser feeds, assign them to publishers and control how traffic is filtered, routed and monetized. Scope: Existing module workflow" }, { "id": "solution.xml-ad-network.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: audience and goal", "text": "Feed operators, traffic networks and monetization teams. Connect traffic sources to advertiser feeds" }, { "id": "solution.xml-ad-network.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: modules", "text": "XML / JSON; Advertiser self-serve" }, { "id": "solution.xml-ad-network.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: workflow", "text": "Publisher request; Filters & limits; Eligible advertiser feeds; Click & revenue reports" }, { "id": "solution.xml-ad-network.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "Partner connections", "text": "Manage advertiser feeds and publisher mappings. Connect each source to the demand and commercial terms you choose." }, { "id": "solution.xml-ad-network.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "Traffic decisions", "text": "Configure bids, QPS, click limits, budgets and supported geo, device, domain and sub-ID rules. Inspect rejected traffic instead of treating every request as sellable." }, { "id": "solution.xml-ad-network.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "Revenue visibility", "text": "Review feed and affiliate statistics. Compare local results with imported partner NET figures and use the XML dashboard to investigate differences." }, { "id": "solution.xml-ad-network.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: prerequisite", "text": "Publisher traffic and advertiser feed agreements" }, { "id": "solution.xml-ad-network.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: prerequisite", "text": "Request parameters, response formats and tracking contracts for each partner" }, { "id": "solution.xml-ad-network.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: prerequisite", "text": "Traffic volumes, quality policy and reporting responsibilities" }, { "id": "solution.xml-ad-network.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "topics": [ "solutions", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "XML ad network", "title": "XML ad network: illustrative workflow", "text": "A traffic network connects several publisher sources to selected advertiser feeds, caps each source and compares partner-reported revenue with its own recorded clicks." }, { "id": "solution.search-advertising-network.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication", "text": "Run a search syndication platform. Connect search providers to publisher links, apply keyword and traffic rules and compare searches, clicks and partner results. Scope: Existing module workflow" }, { "id": "solution.search-advertising-network.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: audience and goal", "text": "Search publishers, syndication businesses and search-feed operators. Monetize search intent" }, { "id": "solution.search-advertising-network.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: modules", "text": "Search Syndication" }, { "id": "solution.search-advertising-network.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: workflow", "text": "Search query; Publisher link & rules; Search provider response; Searches, clicks & NET results" }, { "id": "solution.search-advertising-network.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Provider and publisher setup", "text": "Configure search provider feeds, publisher links and revenue-share settings around the traffic relationships you operate." }, { "id": "solution.search-advertising-network.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search-specific controls", "text": "Use supported keyword, geographic and device targeting, request filters and search caps. Review controls per provider instead of assuming identical behavior across feeds." }, { "id": "solution.search-advertising-network.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Comparable reports", "text": "Inspect searches and clicks by link, publisher, advertiser and feed. Separate local activity from NET figures received from partners." }, { "id": "solution.search-advertising-network.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: prerequisite", "text": "Approved search demand providers and publisher traffic" }, { "id": "solution.search-advertising-network.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: prerequisite", "text": "Search query and tracking parameters supported by each feed" }, { "id": "solution.search-advertising-network.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: prerequisite", "text": "Revenue-share agreements and traffic acceptance rules" }, { "id": "solution.search-advertising-network.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "topics": [ "solutions", "solution.search-advertising-network", "product.search" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search Syndication", "title": "Search Syndication: illustrative workflow", "text": "A publisher runs a search experience, sends eligible queries to its connected providers and reviews which links generate accepted searches and paid clicks." }, { "id": "solution.openrtb-exchange.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub", "text": "Operate the connection between programmatic supply and demand. Manage exchanges, demand access, inventory rules and trading reports from the OpenRTB workspace. Scope: Existing module workflow" }, { "id": "solution.openrtb-exchange.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: audience and goal", "text": "Programmatic networks, exchanges and supply aggregators. Connect supply and demand partners" }, { "id": "solution.openrtb-exchange.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: modules", "text": "OpenRTB" }, { "id": "solution.openrtb-exchange.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: workflow", "text": "Supply bid request; Inventory & traffic checks; Eligible demand / campaigns; Response & event reporting" }, { "id": "solution.openrtb-exchange.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "Trading relationships", "text": "Configure exchange and demand connections. Explicitly control which demand can receive traffic from each exchange." }, { "id": "solution.openrtb-exchange.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "Inventory and routing policy", "text": "Use supported inventory, geo, device, domain and app rules, QPS controls and partner-specific settings to qualify requests." }, { "id": "solution.openrtb-exchange.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "Operational reporting", "text": "Review requests, valid requests, impressions, clicks, revenue, spend and profit. Investigate traffic errors alongside trading results." }, { "id": "solution.openrtb-exchange.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: prerequisite", "text": "Supply and demand endpoint access plus trading agreements" }, { "id": "solution.openrtb-exchange.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: prerequisite", "text": "A tested OpenRTB contract for formats, events and partner requirements" }, { "id": "solution.openrtb-exchange.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: prerequisite", "text": "Capacity, timeout, filtering and commercial settings" }, { "id": "solution.openrtb-exchange.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "topics": [ "solutions", "solution.openrtb-exchange", "product.rtb" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "OpenRTB exchange & traffic hub", "title": "OpenRTB exchange & traffic hub: illustrative workflow", "text": "An operator connects a new supply partner, enables selected demand connections for that exchange and investigates request quality and trading performance in one workspace." }, { "id": "solution.white-label-dsp.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment", "text": "Build a demand-side platform around Nexus campaign management and the RTB runtime. Define advertiser campaigns, creatives, targeting and the supply connections they can buy from. Scope: Integration-scoped deployment" }, { "id": "solution.white-label-dsp.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: audience and goal", "text": "Advertiser-facing networks, agencies and custom AdTech businesses. Run an advertiser buying platform" }, { "id": "solution.white-label-dsp.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: modules", "text": "OpenRTB; Advertiser self-serve" }, { "id": "solution.white-label-dsp.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: workflow", "text": "Advertiser campaign; Creative, targeting & budget; Connected RTB supply; Impression, click & spend reports" }, { "id": "solution.white-label-dsp.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "Advertiser workflows", "text": "Give direct advertisers a self-serve workspace for multi-format campaigns, CPC and CPM buying, creatives, targeting, budgets, funds and account balances. Configure eligible supply, access and funding methods for your deployment; campaign media spend is separate from platform capacity charges." }, { "id": "solution.white-label-dsp.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "Buying runtime", "text": "The RTB runtime includes direct-campaign selection as well as external demand connections. Scope supply endpoints, frequency controls and supported creative delivery paths before launch." }, { "id": "solution.white-label-dsp.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "Brand and engineering", "text": "Combine white-label configuration with custom development where the buying workflow needs additional integrations, user journeys or reporting." }, { "id": "solution.white-label-dsp.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: prerequisite", "text": "The exchanges or supply partners you want to buy from" }, { "id": "solution.white-label-dsp.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: prerequisite", "text": "Creative review, targeting, budget and event requirements" }, { "id": "solution.white-label-dsp.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: prerequisite", "text": "A defined advertiser UX and a delivery plan for additional integrations" }, { "id": "solution.white-label-dsp.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "topics": [ "solutions", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "DSP Deployment", "title": "DSP Deployment: illustrative workflow", "text": "An agency wants a branded buying interface for a defined group of advertisers and supply partners. Nexus supplies campaign and RTB components; the required buying workflow is validated and completed during implementation." }, { "id": "solution.video-ad-network.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network", "text": "Build a video monetization platform around channels and VAST tags. Connect publisher inventory to eligible demand and inspect delivery, errors and partner results. Scope: Existing module workflow" }, { "id": "solution.video-ad-network.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: audience and goal", "text": "Video networks, publishers and video monetization teams. Connect video inventory to VAST demand" }, { "id": "solution.video-ad-network.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: modules", "text": "VAST Video" }, { "id": "solution.video-ad-network.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: workflow", "text": "Player / channel request; Eligibility & limits; Selected VAST tag; Playback events & reports" }, { "id": "solution.video-ad-network.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Channels and demand", "text": "Organize publisher channels and video tags, with the partner relationships and eligibility settings needed for each connection." }, { "id": "solution.video-ad-network.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video controls", "text": "Configure supported targeting, request filters and traffic limits. Keep player requirements and tag compatibility part of the integration checklist." }, { "id": "solution.video-ad-network.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Delivery investigation", "text": "Inspect video statistics and error reports to understand which requests progress to delivery and which fail along the VAST path." }, { "id": "solution.video-ad-network.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: prerequisite", "text": "A compatible publisher player or delivery integration" }, { "id": "solution.video-ad-network.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: prerequisite", "text": "VAST demand tags and publisher / demand agreements" }, { "id": "solution.video-ad-network.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: prerequisite", "text": "Playback-event, consent and error-reporting requirements" }, { "id": "solution.video-ad-network.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/video-ad-network", "topics": [ "solutions", "solution.video-ad-network", "product.video" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Video ad network", "title": "Video ad network: illustrative workflow", "text": "A video network maps publisher channels to selected VAST demand tags and checks delivery and errors before expanding the eligible traffic." }, { "id": "solution.affiliate-tracking-platform.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform", "text": "Run an offer-based CPA tracking platform. Connect publishers to offers, track clicks and reported conversions, apply caps and manage fixed or revenue-share payouts. Scope: Existing module workflow" }, { "id": "solution.affiliate-tracking-platform.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: audience and goal", "text": "Affiliate networks, offer owners and performance teams. Track clicks, conversions and partner payouts" }, { "id": "solution.affiliate-tracking-platform.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: modules", "text": "CPA" }, { "id": "solution.affiliate-tracking-platform.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: workflow", "text": "Publisher tracking link; Offer & landing page; Conversion / postback; Validation & payout reporting" }, { "id": "solution.affiliate-tracking-platform.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Offer management", "text": "Configure offers, publisher approvals, supported geo and device targeting, conversion windows and commercial terms." }, { "id": "solution.affiliate-tracking-platform.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Conversion tracking", "text": "Match advertiser-reported conversion events to the original click ID. Define the accepted event and postback behavior before counting outcomes." }, { "id": "solution.affiliate-tracking-platform.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Commercial controls", "text": "Use caps and fixed or revenue-share payouts. Review offer and publisher reports to see where valid or invalid conversions and partner earnings come from." }, { "id": "solution.affiliate-tracking-platform.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: prerequisite", "text": "Offers, landing pages and approved traffic sources" }, { "id": "solution.affiliate-tracking-platform.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: prerequisite", "text": "A working advertiser conversion / postback integration" }, { "id": "solution.affiliate-tracking-platform.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: prerequisite", "text": "The payable event, validation rules, caps and payout terms" }, { "id": "solution.affiliate-tracking-platform.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "topics": [ "solutions", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Affiliate & conversion tracking platform", "title": "Affiliate & conversion tracking platform: illustrative workflow", "text": "A network gives an approved publisher an offer link, receives a conversion postback and applies the configured payout after the event satisfies the agreed rules." }, { "id": "solution.web-push-platform.overview", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform", "text": "Use the available Push Subscribers module for direct publishers. Manage websites, browser subscriptions and notification delivery, then review subscriber activity and notification results. Scope: Delivery integration required" }, { "id": "solution.web-push-platform.audience", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: audience and goal", "text": "Publisher networks and browser-notification operators. Manage subscribed browser audiences" }, { "id": "solution.web-push-platform.modules", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: modules", "text": "Push Subscribers & publishers" }, { "id": "solution.web-push-platform.workflow", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: workflow", "text": "Website permission; Browser subscription; Configured push delivery; Subscriber & event reports" }, { "id": "solution.web-push-platform.capability.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Publisher setup", "text": "Organize publisher websites, subscription information and notification content in the publisher workflow." }, { "id": "solution.web-push-platform.capability.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Browser delivery", "text": "Nexus includes browser subscription and service-worker integration plus Web Push delivery code. Deployment requires the configured delivery services and valid subscriptions." }, { "id": "solution.web-push-platform.capability.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Audience reporting", "text": "Review subscriber activity, impressions, clicks and revenue where supported by the configured publisher and delivery integration." }, { "id": "solution.web-push-platform.requirement.0", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: prerequisite", "text": "A compatible website integration and service worker" }, { "id": "solution.web-push-platform.requirement.1", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: prerequisite", "text": "User permission and valid browser push subscriptions" }, { "id": "solution.web-push-platform.requirement.2", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: prerequisite", "text": "Delivery-service configuration, notification content and unsubscribe handling" }, { "id": "solution.web-push-platform.example", "kind": "solution", "url": "https://www.nexus-soft.org/solutions/web-push-platform", "topics": [ "solutions", "solution.web-push-platform", "product.publisher" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push publisher platform", "title": "Web Push publisher platform: illustrative workflow", "text": "A publisher connects its website, collects browser subscriptions from consenting visitors and reviews subscriber activity while the configured push service handles notification delivery." }, { "id": "format.search-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads and sponsored results", "text": "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." }, { "id": "format.search-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: Nexus components", "text": "Search provider feeds, publisher links, keyword and traffic rules, search caps and reporting." }, { "id": "format.search-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: required integration", "text": "Approved demand provider access, a search placement and compatible query / click parameters." }, { "id": "format.search-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: Placements", "text": "Search result pages; Publisher search boxes; Comparison and directory experiences; Contextual keyword pages" }, { "id": "format.search-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: Buying models", "text": "CPC — cost per click; Revenue-share or publisher payout; Provider bid and custom publisher range" }, { "id": "format.search-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: Targeting", "text": "Keyword or query intent; Country and region; Browser, OS and device; Publisher, placement and sub-ID; Supported partner-specific parameters" }, { "id": "format.search-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: Delivery flow", "text": "User query; Request and quality policy; Eligible demand feeds; Ranked sponsored results; Click and reconciliation" }, { "id": "format.search-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "CTR", "text": "Clicks ÷ delivered sponsored results" }, { "id": "format.search-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "RPC", "text": "Revenue generated per click" }, { "id": "format.search-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Coverage", "text": "Requests that return eligible results" }, { "id": "format.search-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "NET", "text": "Provider-reported commercial result" }, { "id": "format.search-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Is a search ad the same as a display banner?", "text": "No. Search ads respond to explicit query intent and are commonly delivered as structured text results. Display banners occupy a visual placement and are usually bought by impression or click." }, { "id": "format.search-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Can multiple demand feeds answer one request?", "text": "Yes, when the deployment supports multi-feed routing. Eligibility, timeout, ranking, deduplication and commercial policy still need deterministic rules." }, { "id": "format.search-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Which traffic controls matter most?", "text": "Publisher identity, request repetition, IP or network policy, referrer context, QPS, caps and partner-specific quality rules are common operating boundaries." }, { "id": "format.search-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "What the user sees", "text": "A search ad usually contains a title, destination or display URL and short description. It should be distinguishable from organic content while remaining closely related to the submitted query." }, { "id": "format.search-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "How delivery works", "text": "The publisher sends a structured request. Nexus validates identity and request context, applies limits and quality rules, selects eligible feeds, normalizes their responses and returns controlled results inside the delivery window." }, { "id": "format.search-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "What operators control", "text": "Feed profiles, minimum or maximum bids, custom publisher ranges, result limits, timeouts, allowed targets, QPS and blocked-result policy determine which commercial path can answer." }, { "id": "format.search-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Where value is won or lost", "text": "A high headline bid is not automatically the best route. Coverage, response latency, click quality, provider deductions and partner-level performance must be visible together." }, { "id": "format.search-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: what it looks like", "text": "A sponsored result next to a search query. Placement: Search results & partner search pages. Reach people already looking for a product or service." }, { "id": "format.search-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/search-ads", "topics": [ "formats", "format.search-ads", "solution.search-advertising-network", "product.search" ], "boundary": "Core Nexus Search workflow. Approved demand provider access, a search placement and compatible query / click parameters. This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "sourceTitle": "Search ads", "title": "Search ads: illustrative example", "text": "A person searches for running shoes and sees a relevant sponsored result." }, { "id": "format.display-banner-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banner advertising", "text": "Display banners are visual ad units placed inside a page or application layout. They are familiar and scalable, but effective delivery still depends on creative dimensions, placement context, viewability, frequency and transparent supply paths." }, { "id": "format.display-banner-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: Nexus components", "text": "Banner creative paths, campaign controls and supported OpenRTB supply / demand connections." }, { "id": "format.display-banner-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: required integration", "text": "A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied." }, { "id": "format.display-banner-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: Placements", "text": "Page header and leaderboard; Sidebar and medium rectangle; In-content display slot; Mobile web or in-app banner" }, { "id": "format.display-banner-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: Buying models", "text": "CPM — cost per thousand impressions; CPC — cost per click; Fixed-price or direct placement" }, { "id": "format.display-banner-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: Targeting", "text": "Geography; Site, app and placement; Device, OS and browser; Schedule and frequency; Audience or first-party segments when supplied lawfully" }, { "id": "format.display-banner-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: Delivery flow", "text": "Available placement; Ad request; Eligibility or auction; Creative response; Impression and click events" }, { "id": "format.display-banner-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Impressions", "text": "Counted ad deliveries" }, { "id": "format.display-banner-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Viewability", "text": "Opportunity to be seen" }, { "id": "format.display-banner-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "CTR", "text": "Clicks ÷ impressions" }, { "id": "format.display-banner-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "eCPM", "text": "Revenue normalized per thousand impressions" }, { "id": "format.display-banner-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Which banner size is best?", "text": "There is no universal best size. Use the sizes supported by the target inventory and prepare responsive or multiple creative variants without sacrificing load performance." }, { "id": "format.display-banner-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "What is the difference between CPM and eCPM?", "text": "CPM is a buying price per thousand impressions. eCPM normalizes actual spend or revenue so performance across different pricing models can be compared." }, { "id": "format.display-banner-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Does an impression mean the banner was seen?", "text": "Not necessarily. An impression records delivery; viewability adds evidence that enough of the creative entered the visible viewport for a defined period." }, { "id": "format.display-banner-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "What the user sees", "text": "A rectangular creative appears inside the surrounding page or application. Common units include leaderboards, medium rectangles and mobile banners, with responsive or HTML5 variants adapting to available space." }, { "id": "format.display-banner-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "How delivery works", "text": "The placement sends context such as size, environment and publisher identity. Eligible campaigns or bidders respond, the winning creative is returned and impression, viewability and click events are recorded." }, { "id": "format.display-banner-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Creative requirements", "text": "Dimensions, file weight, destination URL, animation behavior, fallback assets and secure delivery must match the placement contract. A visually strong banner that cannot render quickly still loses value." }, { "id": "format.display-banner-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Operator watchouts", "text": "Hidden placements, excessive refresh, domain or app misrepresentation, poor viewability and uncontrolled frequency can inflate delivery without producing useful attention." }, { "id": "format.display-banner-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: what it looks like", "text": "An image or HTML creative inside a reserved ad space. Placement: Websites & supported app inventory. Build awareness or send visitors to a landing page." }, { "id": "format.display-banner-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/display-banner-ads", "topics": [ "formats", "format.display-banner-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "OpenRTB-connected and deployment-specific inventory. A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Display banners", "title": "Display banners: illustrative example", "text": "A publisher places a banner beside an article without covering the content." }, { "id": "format.native-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native advertising", "text": "Native advertising is assembled from components—headline, image, description, brand and call to action—so the publisher can render it in the visual language of the surrounding product. The format should feel coherent without disguising that it is paid placement." }, { "id": "format.native-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: Nexus components", "text": "Native ads for direct advertisers through campaign and creative management, alongside native creative selection and supported programmatic partner connections." }, { "id": "format.native-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: required integration", "text": "A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear." }, { "id": "format.native-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: Placements", "text": "Editorial recommendation feed; In-feed mobile card; Sponsored content module; Commerce or discovery widget" }, { "id": "format.native-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: Buying models", "text": "CPM; CPC; CPA or downstream outcome where tracking supports it" }, { "id": "format.native-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: Targeting", "text": "Publisher and content category; Placement and device; Geography and language; Audience context supplied by the publisher; Frequency and schedule" }, { "id": "format.native-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: Delivery flow", "text": "Native placement request; Asset and policy validation; Bid or campaign selection; Publisher-side rendering; Engagement and conversion" }, { "id": "format.native-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Viewable impressions", "text": "Visible native deliveries" }, { "id": "format.native-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "CTR", "text": "Visits generated by the unit" }, { "id": "format.native-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Engaged sessions", "text": "Useful post-click visits" }, { "id": "format.native-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Conversion rate", "text": "Validated outcomes ÷ eligible visits" }, { "id": "format.native-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Does native advertising hide that it is an ad?", "text": "It should not. Native design matches the experience, but clear sponsored or advertising disclosure is essential for user trust and policy compliance." }, { "id": "format.native-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Who renders the final creative?", "text": "The publisher or application normally assembles supplied assets according to its native template and the technical contract used by the integration." }, { "id": "format.native-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Why can native traffic quality differ by placement?", "text": "A recommendation widget, editorial feed and mobile card create different user expectations. Placement-level reporting helps separate genuine interest from accidental or misleading engagement." }, { "id": "format.native-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "What the user sees", "text": "A card or content unit aligned with the surrounding feed: image, title, short description, sponsor name and an advertising disclosure. The publisher controls final rendering inside the declared asset contract." }, { "id": "format.native-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "How it differs from a banner", "text": "A banner arrives as a finished visual. A native response supplies structured assets that are composed by the publisher, allowing the unit to fit different screen and content layouts." }, { "id": "format.native-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "What quality means", "text": "The creative promise should match the landing experience, disclosure should remain visible and the placement should not imitate an editorial control or system notification." }, { "id": "format.native-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "What to measure", "text": "CTR alone can reward curiosity without value. Combine delivery and click metrics with engaged sessions, downstream events, source quality and placement-level performance." }, { "id": "format.native-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: what it looks like", "text": "A clearly labeled sponsored card that fits the surrounding content. Placement: Content feeds & recommendation areas. Introduce a relevant offer in a familiar reading experience." }, { "id": "format.native-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/native-ads", "topics": [ "formats", "format.native-ads", "solution.openrtb-exchange", "product.rtb" ], "boundary": "Native ads for direct advertisers and supported OpenRTB native integrations. A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear. An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "sourceTitle": "Native ads", "title": "Native ads: illustrative example", "text": "A sponsored travel article appears among editorial recommendations, with an advertising label." }, { "id": "format.instream-video-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video advertising", "text": "In-stream video advertising plays inside a video player before, during or after the requested content. The viewer experience depends on more than the media file: VAST metadata, wrapper depth, player capability, duration and tracking must work as one delivery chain." }, { "id": "format.instream-video-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: Nexus components", "text": "Video channels, VAST tags, eligibility settings and video delivery / error reporting." }, { "id": "format.instream-video-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: required integration", "text": "A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration." }, { "id": "format.instream-video-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: Placements", "text": "Pre-roll before content; Mid-roll break; Post-roll after content; Live-stream ad break" }, { "id": "format.instream-video-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: Buying models", "text": "CPM; vCPM or viewable delivery; CPV or completed-view model" }, { "id": "format.instream-video-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: Targeting", "text": "Content and channel; Device and player environment; Geography and language; Duration and creative compatibility; Ad-break position and frequency" }, { "id": "format.instream-video-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: Delivery flow", "text": "Player ad break; VAST request; Demand and wrapper chain; Compatible media selection; Playback and tracking events" }, { "id": "format.instream-video-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Start rate", "text": "Playback starts ÷ valid responses" }, { "id": "format.instream-video-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Completion rate", "text": "Completed views ÷ starts" }, { "id": "format.instream-video-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Quartiles", "text": "25%, 50%, 75% and complete events" }, { "id": "format.instream-video-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Error rate", "text": "VAST or player failures ÷ attempts" }, { "id": "format.instream-video-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "What is the difference between pre-roll and mid-roll?", "text": "Pre-roll plays before requested content. Mid-roll appears during content at a defined break and therefore needs especially careful frequency and viewer-experience policy." }, { "id": "format.instream-video-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Does a VAST response guarantee playback?", "text": "No. It provides a delivery contract, but the player must still resolve wrappers, select compatible media, load the asset and emit valid playback events." }, { "id": "format.instream-video-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Which metric matters beyond impressions?", "text": "Starts, quartile progress, completion, error rate and playback latency explain whether delivered responses became real viewing opportunities." }, { "id": "format.instream-video-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "What the user sees", "text": "A video creative plays inside the same player used for content. It may be skippable or non-skippable depending on the placement, creative and publisher policy." }, { "id": "format.instream-video-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "How VAST fits", "text": "VAST describes media assets, impression tracking, click destinations, errors and playback events. A wrapper may point to another VAST response, creating additional demand hops and latency." }, { "id": "format.instream-video-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Why compatibility matters", "text": "Container, codec, bitrate, aspect ratio, duration and secure media delivery must be compatible with the player and environment. A valid XML response can still fail at playback." }, { "id": "format.instream-video-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "Operator watchouts", "text": "Wrapper loops, excessive depth, slow media, unsupported codecs, duplicate tracking and unrealistic timeout budgets are common sources of lost video opportunities." }, { "id": "format.instream-video-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: what it looks like", "text": "A video ad before, during or after another video. Placement: Compatible video players. Reach viewers inside a video-watching session." }, { "id": "format.instream-video-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/instream-video-ads", "topics": [ "formats", "format.instream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Core Nexus VAST workflow. A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "In-stream video", "title": "In-stream video: illustrative example", "text": "A short ad plays before a publisher’s news video. Player capabilities determine playback and skip behavior." }, { "id": "format.outstream-video-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video advertising", "text": "Outstream video creates a player-like placement inside non-video content. The unit commonly opens or begins muted when it enters view and pauses or collapses when the user moves away, making viewability and interaction policy central to the format." }, { "id": "format.outstream-video-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: Nexus components", "text": "The Video module connects eligible channels and VAST demand tags." }, { "id": "format.outstream-video-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: required integration", "text": "An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone." }, { "id": "format.outstream-video-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: Placements", "text": "In-article unit; In-feed video card; Sticky or floating player; Native video placement" }, { "id": "format.outstream-video-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: Buying models", "text": "CPM; vCPM; CPV or completed view" }, { "id": "format.outstream-video-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: Targeting", "text": "Page and content context; Placement position; Device and browser capability; Geography and language; Viewability and frequency rules" }, { "id": "format.outstream-video-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: Delivery flow", "text": "Page or feed loads; Unit enters viewport; VAST response resolves; Muted playback begins; Pause, completion or interaction" }, { "id": "format.outstream-video-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Viewable starts", "text": "Starts while the unit is viewable" }, { "id": "format.outstream-video-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Completion rate", "text": "Completed plays ÷ starts" }, { "id": "format.outstream-video-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Viewable time", "text": "Duration meeting viewability conditions" }, { "id": "format.outstream-video-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Interaction rate", "text": "Clicks or controls used ÷ starts" }, { "id": "format.outstream-video-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Does outstream require existing video content?", "text": "No. It creates a video advertising placement inside non-video page or feed content." }, { "id": "format.outstream-video-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Why does outstream often start muted?", "text": "Browser autoplay policies and user-experience expectations generally make muted, viewport-aware playback the safer default." }, { "id": "format.outstream-video-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Is a sticky video always outstream?", "text": "Not necessarily. Sticky describes placement behavior. Both content video and outstream units can become sticky, so reporting should preserve the actual inventory type." }, { "id": "format.outstream-video-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "What the user sees", "text": "A video unit appears between paragraphs, inside a feed or as a controlled floating placement. It is separate from publisher video content and should not unexpectedly dominate the experience." }, { "id": "format.outstream-video-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "How it starts", "text": "An integration observes when the unit becomes viewable, requests or resolves eligible video demand and begins playback according to browser and publisher policy—commonly muted." }, { "id": "format.outstream-video-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Experience controls", "text": "Viewport thresholds, pause behavior, close controls, sticky positioning, sound activation, frequency and maximum footprint determine whether the format remains useful rather than intrusive." }, { "id": "format.outstream-video-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "What to investigate", "text": "A high start count with low viewable time or completion can indicate placement behavior, slow creative loading, scroll patterns or a mismatch between format and content." }, { "id": "format.outstream-video-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: what it looks like", "text": "A standalone video unit inside a page or content feed. Placement: Articles & feed placements. Add video inventory without needing a main editorial video." }, { "id": "format.outstream-video-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/outstream-video-ads", "topics": [ "formats", "format.outstream-video-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST integration pattern; deployment-specific. An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "Outstream video", "title": "Outstream video: illustrative example", "text": "A video unit appears between paragraphs. Playback rules depend on the player and placement." }, { "id": "format.ctv-ott-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV and OTT advertising", "text": "CTV advertising reaches streaming content on connected televisions and TV-like devices. It uses familiar video concepts, but living-room viewing, device fragmentation, ad pods and limited click interaction create a distinct operating environment." }, { "id": "format.ctv-ott-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: Nexus components", "text": "Video channel, tag and traffic-control components for an agreed delivery configuration." }, { "id": "format.ctv-ott-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: required integration", "text": "Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation." }, { "id": "format.ctv-ott-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: Placements", "text": "Streaming pre-roll; Mid-roll ad pod; FAST channel break; OTT application inventory" }, { "id": "format.ctv-ott-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: Buying models", "text": "CPM; Completed-view pricing; Programmatic guaranteed or private deal" }, { "id": "format.ctv-ott-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: Targeting", "text": "App, channel and content genre; Device type and operating system; Geography; Ad pod position; Publisher-provided household or first-party segments" }, { "id": "format.ctv-ott-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: Delivery flow", "text": "Streaming ad break; CTV opportunity; Eligible video demand; Ad pod assembly; Playback and completion evidence" }, { "id": "format.ctv-ott-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Completion rate", "text": "Completed views ÷ starts" }, { "id": "format.ctv-ott-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Reach", "text": "Estimated unique exposed households or devices" }, { "id": "format.ctv-ott-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Frequency", "text": "Average exposures per addressable unit" }, { "id": "format.ctv-ott-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Pod position", "text": "Performance by slot inside an ad break" }, { "id": "format.ctv-ott-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "What is the difference between CTV and OTT?", "text": "OTT describes content delivered over the internet. CTV describes the television devices and applications where much of that content is viewed; the terms overlap but are not identical." }, { "id": "format.ctv-ott-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Why is CTR less useful for CTV?", "text": "Television viewing does not naturally involve clicking. Completion, reach, frequency and downstream measurement are usually more informative." }, { "id": "format.ctv-ott-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "What is an ad pod?", "text": "A pod is a sequence of multiple ads inside one content break. Position, duration and competitive separation influence the viewer experience." }, { "id": "format.ctv-ott-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "What the viewer sees", "text": "A full-screen video ad appears before or during streamed programming, usually without the immediate click behavior of web advertising. Creative quality and repetition are highly visible on a television screen." }, { "id": "format.ctv-ott-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "How delivery differs", "text": "CTV can use client-side or server-side ad insertion. Device, application, content, pod and media compatibility signals influence whether demand is eligible and whether playback evidence is available." }, { "id": "format.ctv-ott-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Creative and pod policy", "text": "Duration, aspect ratio, bitrate, codec and loudness must fit the environment. Pod position and competitive-separation rules help avoid repeated brands or inappropriate sequencing." }, { "id": "format.ctv-ott-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "Measurement reality", "text": "Completion is strong but not equivalent to attention or incremental reach. Teams need consistent device or household methodology, frequency controls and clear separation of delivered, started and completed events." }, { "id": "format.ctv-ott-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: what it looks like", "text": "A video advertisement in a connected-TV or streaming experience. Placement: Supported TV apps & streaming inventory. Reach viewers on the large screen through compatible supply." }, { "id": "format.ctv-ott-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/ctv-ott-ads", "topics": [ "formats", "format.ctv-ott-ads", "solution.video-ad-network", "product.video" ], "boundary": "VAST and OpenRTB-connected deployment pattern. Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation. VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "sourceTitle": "CTV / OTT", "title": "CTV / OTT: illustrative example", "text": "A streaming application inserts an ad break using the delivery integration supported by that publisher." }, { "id": "format.interstitial-rich-media-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial and rich media advertising", "text": "Interstitial and rich media formats use more screen space or interaction than a standard banner. They can communicate complex creative ideas, but they also require stricter timing, close controls, performance and frequency policy." }, { "id": "format.interstitial-rich-media-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: Nexus components", "text": "Campaign and programmatic components for supported creative and inventory contracts." }, { "id": "format.interstitial-rich-media-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: required integration", "text": "A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied." }, { "id": "format.interstitial-rich-media-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: Placements", "text": "Between page or app states; Expandable display placement; In-banner video or interaction; Mobile full-screen unit" }, { "id": "format.interstitial-rich-media-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: Buying models", "text": "CPM; CPC; Engagement or CPA model when events are validated" }, { "id": "format.interstitial-rich-media-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: Targeting", "text": "App or site placement; Device and orientation; Geography and language; Session stage and schedule; Frequency and recency" }, { "id": "format.interstitial-rich-media-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: Delivery flow", "text": "Eligible transition; Frequency check; Creative load; Visible or interactive state; Close, click or conversion event" }, { "id": "format.interstitial-rich-media-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Viewable impressions", "text": "Visible full or expanded units" }, { "id": "format.interstitial-rich-media-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Engagement rate", "text": "Qualified interactions ÷ impressions" }, { "id": "format.interstitial-rich-media-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Close rate", "text": "Dismissals ÷ impressions" }, { "id": "format.interstitial-rich-media-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Conversion rate", "text": "Validated outcomes ÷ eligible visits" }, { "id": "format.interstitial-rich-media-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "What makes rich media different from a normal banner?", "text": "Rich media introduces more advanced motion, media or interaction, such as expansion, in-banner video or interactive elements." }, { "id": "format.interstitial-rich-media-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "When should an interstitial appear?", "text": "At a natural transition—such as between content or application states—subject to publisher policy and frequency limits." }, { "id": "format.interstitial-rich-media-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Why is close rate important?", "text": "A very high close rate may reveal poor timing, excessive frequency, irrelevant targeting or a creative that blocks the user’s intended task." }, { "id": "format.interstitial-rich-media-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "What the user sees", "text": "An interstitial occupies most or all of the screen at a natural transition. Rich media may expand, animate, play media or expose interactive controls inside a display placement." }, { "id": "format.interstitial-rich-media-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Why timing matters", "text": "A transition unit should appear at a predictable break rather than interrupting an active task. Preloading and rendering performance reduce blank states and accidental interaction." }, { "id": "format.interstitial-rich-media-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Required controls", "text": "A visible close action, bounded duration, mobile-safe layout, sound policy, frequency cap and creative weight limit protect the experience." }, { "id": "format.interstitial-rich-media-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "How to interpret engagement", "text": "Interaction can indicate interest, but it can also reveal confusing controls. Compare engagement with close rate, post-click behavior, placement, device and creative variant." }, { "id": "format.interstitial-rich-media-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: what it looks like", "text": "A larger interactive or full-screen unit with a clear close control. Placement: Natural transitions in web or app content. Create a high-impact message while respecting user navigation." }, { "id": "format.interstitial-rich-media-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/interstitial-rich-media-ads", "topics": [ "formats", "format.interstitial-rich-media-ads", "solution.white-label-dsp", "product.rtb", "product.advertiser" ], "boundary": "Deployment-specific campaign and OpenRTB format. A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied. DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "sourceTitle": "Interstitial & rich media", "title": "Interstitial & rich media: illustrative example", "text": "An interstitial appears between app screens, with an obvious way to close it and continue." }, { "id": "format.popunder-cpv-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder and CPV advertising", "text": "A popunder opens a destination in a secondary browser context behind the active page. The user typically encounters it after closing or moving away from the original window, which makes source transparency, browser behavior, timing and frequency essential." }, { "id": "format.popunder-cpv-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: Nexus components", "text": "Popunder JS support is available in the XML / JSON module, with publisher script, frequency and delay configuration, feed routing, source controls and click / commercial reports." }, { "id": "format.popunder-cpv-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: required integration", "text": "A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative." }, { "id": "format.popunder-cpv-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: Placements", "text": "Publisher page interaction; Direct-link campaign; Feed-backed destination; Multi-site rotation where explicitly configured" }, { "id": "format.popunder-cpv-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: Buying models", "text": "CPV — cost per valid view; CPM in some supply contracts; Campaign-specific bid or publisher payout" }, { "id": "format.popunder-cpv-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: Targeting", "text": "Country and region; Browser and operating system; Device class; Publisher, site and source; Time and frequency" }, { "id": "format.popunder-cpv-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: Delivery flow", "text": "Publisher interaction; Eligibility and cap check; Destination selection; Secondary window opens; View and outcome tracking" }, { "id": "format.popunder-cpv-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Valid views", "text": "Accepted destination opens" }, { "id": "format.popunder-cpv-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Unique rate", "text": "Unique users or devices ÷ views" }, { "id": "format.popunder-cpv-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Frequency", "text": "Views per user or device" }, { "id": "format.popunder-cpv-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Post-view outcome", "text": "Validated action after exposure" }, { "id": "format.popunder-cpv-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "What does CPV mean?", "text": "Cost per view charges for an accepted view or opened destination according to the campaign and supply contract. The exact validity rules must be defined." }, { "id": "format.popunder-cpv-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "How is popunder different from popup?", "text": "A popup appears above or in front of the active window. A popunder opens behind it and is usually encountered later." }, { "id": "format.popunder-cpv-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Why are frequency caps essential?", "text": "Repeated interruption quickly damages user experience and can inflate volume without producing additional campaign value." }, { "id": "format.popunder-cpv-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "What the user sees", "text": "The original page remains active while a second destination opens behind it. Because the experience is interruption-based, placement consent and predictable behavior matter more than raw delivery volume." }, { "id": "format.popunder-cpv-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "How delivery is governed", "text": "Publisher identity, browser capability, campaign eligibility, direct-link or feed response, time caps and per-user frequency determine whether an opportunity should open." }, { "id": "format.popunder-cpv-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Quality and fraud controls", "text": "Repeated opens, automation, hidden windows, blocked or unsupported browser behavior, misleading sources and excessive frequency can distort a CPV campaign." }, { "id": "format.popunder-cpv-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "When it is appropriate", "text": "Popunder can support direct-response campaigns with broad reach, but it is not a universal substitute for intent, native or video formats. Brand requirements, browser policy and user experience must be evaluated explicitly." }, { "id": "format.popunder-cpv-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: what it looks like", "text": "A separate landing-page window opened behind the active page, where permitted. Placement: Eligible partner inventory. Deliver a landing-page visit under explicit traffic-quality rules." }, { "id": "format.popunder-cpv-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/popunder-cpv-ads", "topics": [ "formats", "format.popunder-cpv-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Popunder JS support is available in the XML / JSON module. A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Popunder / CPV", "title": "Popunder / CPV: illustrative example", "text": "An eligible user action can trigger a partner landing page. Browser policies, consent and frequency limits constrain delivery." }, { "id": "format.mobile-performance-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile CPA, CPI and CPL advertising", "text": "Mobile performance advertising pays for a defined outcome rather than exposure alone. The ad can use several creative formats; what defines the model is the validated event—an action, installation, lead, sale or deployment-specific conversion." }, { "id": "format.mobile-performance-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: Nexus components", "text": "CPA offers, publisher access, conversion windows, caps, click-ID tracking and fixed or revenue-share payouts." }, { "id": "format.mobile-performance-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: required integration", "text": "An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied." }, { "id": "format.mobile-performance-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: Placements", "text": "Mobile web campaign; In-app inventory; Offer or comparison page; Affiliate and performance source" }, { "id": "format.mobile-performance-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: Buying models", "text": "CPA — cost per action; CPI — cost per install; CPL — cost per lead; CPS — cost per sale where agreed" }, { "id": "format.mobile-performance-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: Targeting", "text": "Country and region; Mobile OS and version; Device class or supported brand; Publisher and sub-ID; Schedule, click and conversion caps" }, { "id": "format.mobile-performance-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: Delivery flow", "text": "Partner click; Targeted offer or store; User completes event; Postback validation; Attribution, reporting and payout" }, { "id": "format.mobile-performance-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Conversion rate", "text": "Validated outcomes ÷ eligible clicks" }, { "id": "format.mobile-performance-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "CPA", "text": "Spend ÷ validated actions" }, { "id": "format.mobile-performance-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Install rate", "text": "Validated installs ÷ clicks" }, { "id": "format.mobile-performance-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "ROAS", "text": "Attributed value ÷ spend" }, { "id": "format.mobile-performance-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Is CPA an ad format?", "text": "Strictly, CPA is a pricing and optimization model. It can use search, display, native or video creatives, but clients often evaluate it as a distinct performance channel." }, { "id": "format.mobile-performance-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "What is a postback?", "text": "A server-to-server notification that reports a conversion event and the identifiers needed to connect it to an earlier click or campaign." }, { "id": "format.mobile-performance-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "What is the difference between CPI and CPL?", "text": "CPI pays for a validated application installation. CPL pays for an accepted lead, such as a completed and qualified form." }, { "id": "format.mobile-performance-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "What the user sees", "text": "The creative may be a banner, native card, search result or video. It directs the user to an application store, form, purchase flow or other destination tied to a defined outcome." }, { "id": "format.mobile-performance-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "How the outcome is validated", "text": "The configured advertiser or measurement integration reports a conversion with identifiers that connect it to the original click. Confirm the event, identifier and postback contract before launch." }, { "id": "format.mobile-performance-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "How caps protect campaigns", "text": "Click and conversion caps by day, month, offer or partner help control budget and prevent one source from consuming an allocation before quality is understood." }, { "id": "format.mobile-performance-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "What operators reconcile", "text": "Click records, sub-ID context, duplicate policy, attribution windows, advertiser approvals, partner payouts and reversals must lead to one defensible outcome count." }, { "id": "format.mobile-performance-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: what it looks like", "text": "A mobile offer that leads to an install, registration or other defined action. Placement: Mobile web & app acquisition campaigns. Measure a business outcome rather than a click alone." }, { "id": "format.mobile-performance-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/mobile-performance-ads", "topics": [ "formats", "format.mobile-performance-ads", "solution.affiliate-tracking-platform", "product.cpa" ], "boundary": "Core Nexus CPA workflow. An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied. Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "sourceTitle": "Mobile performance", "title": "Mobile performance: illustrative example", "text": "An app promotion links a user to the store. An approved conversion event is reported back through the agreed integration." }, { "id": "format.contextual-domain-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual advertising and domain monetization", "text": "Contextual and domain advertising derive intent from a page, site or domain rather than a conventional user search. The operating challenge is to preserve the source, extracted context and selected demand route so relevance and quality remain explainable." }, { "id": "format.contextual-domain-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: Nexus components", "text": "Contextual ads for direct advertisers, plus Search / XML feed components and source rules for contextual and domain traffic integrations." }, { "id": "format.contextual-domain-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: required integration", "text": "Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context." }, { "id": "format.contextual-domain-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: Placements", "text": "Contextual unit inside an article; Site-specific recommendation module; Parked-domain landing template; Category or keyword results page" }, { "id": "format.contextual-domain-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: Buying models", "text": "CPC; Revenue share; CPM for supported display inventory" }, { "id": "format.contextual-domain-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: Targeting", "text": "Approved site or domain; Keyword and category; Geography and language; Device and browser; Publisher, placement and feed profile" }, { "id": "format.contextual-domain-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: Delivery flow", "text": "Page or domain context; Keyword and category policy; Eligible feed selection; Rendered ads or landing template; Click and source reporting" }, { "id": "format.contextual-domain-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Coverage", "text": "Contexts that return eligible demand" }, { "id": "format.contextual-domain-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "CTR", "text": "Clicks ÷ delivered results" }, { "id": "format.contextual-domain-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "RPC", "text": "Revenue per accepted click" }, { "id": "format.contextual-domain-ads.metric.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Source quality", "text": "Performance by site, domain or keyword" }, { "id": "format.contextual-domain-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Is contextual advertising based on personal identity?", "text": "It can operate from page and content context without requiring a personal identity. Exact data use depends on the integration, consent and applicable policy." }, { "id": "format.contextual-domain-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "What is domain parking?", "text": "Connecting an otherwise undeveloped domain to a controlled landing experience that can provide navigation, contextual links and advertising results." }, { "id": "format.contextual-domain-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Why must sites and domains be approved?", "text": "Approval establishes inventory ownership, expected content, allowed templates and the source identity needed for quality and commercial reporting." }, { "id": "format.contextual-domain-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "What the user sees", "text": "On a content page, relevant sponsored units appear near the article or topic. On a parked domain, a controlled landing template organizes category or keyword links and advertising results." }, { "id": "format.contextual-domain-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "How context is created", "text": "Approved site configuration, page metadata, extracted terms, site-specific keywords, categories and defaults can contribute to the request sent to eligible demand." }, { "id": "format.contextual-domain-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "How domain parking works", "text": "An approved domain connects through nameserver or redirect patterns to a selected landing template. Domain ownership, template, keywords, categories and demand path remain operator-controlled." }, { "id": "format.contextual-domain-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Quality boundary", "text": "Extracted terms are signals, not guaranteed user intent. Reporting should preserve the source site or domain, applied context, selected feed and delivered result." }, { "id": "format.contextual-domain-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: what it looks like", "text": "An offer selected using page, keyword or domain context. Placement: Contextual pages & domain traffic. Match eligible demand to what the visitor is reading or visiting." }, { "id": "format.contextual-domain-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/contextual-domain-ads", "topics": [ "formats", "format.contextual-domain-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Contextual ads for direct advertisers, plus Search and XML feed workflows. Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Contextual & domain", "title": "Contextual & domain: illustrative example", "text": "A page about travel presents eligible travel-related demand using the context supplied by the partner." }, { "id": "format.web-push-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push notifications", "text": "Web Push is a notification delivered through a browser push service after a visitor subscribes. It uses a browser subscription and service worker rather than an ad slot inside the current page. Nexus includes publisher subscription workflows and Web Push delivery components." }, { "id": "format.web-push-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: Nexus components", "text": "The available Push Subscribers module for direct publishers, with website management, subscriber inventory, subscription workflows and Web Push delivery components." }, { "id": "format.web-push-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: required integration", "text": "Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service." }, { "id": "format.web-push-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: Placements", "text": "Browser / operating-system notification surfaces on supported devices; Publisher websites for subscription collection" }, { "id": "format.web-push-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: Buying models", "text": "Partner-agreed impression or click pricing; Outcome tracking only with a connected conversion integration" }, { "id": "format.web-push-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: Targeting", "text": "Subscribed publisher audience; Supported publisher and delivery-service rules; Browser eligibility and subscription status" }, { "id": "format.web-push-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: Delivery flow", "text": "Visitor permission; Browser subscription; Configured notification; Push-service delivery; Subscriber & event reports" }, { "id": "format.web-push-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Subscribers", "text": "Track subscription activity and the audience available to the configured service." }, { "id": "format.web-push-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Impressions & clicks", "text": "Review notification events supported by the delivery integration; sending is not proof that a user saw an ad." }, { "id": "format.web-push-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Revenue", "text": "Compare the commercial results recorded for the connected publisher operation." }, { "id": "format.web-push-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Does Web Push require permission?", "text": "Yes. Browser notification permission and a valid push subscription are required. A site visit alone does not authorize notifications." }, { "id": "format.web-push-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Can I use every browser or device?", "text": "No universal delivery guarantee is implied. Confirm browser support, website integration and delivery-service requirements for your audience." }, { "id": "format.web-push-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Does Nexus include the delivery workflow?", "text": "Nexus has browser subscription, service-worker and Web Push delivery components. The delivery service must be configured and tested for your deployment." }, { "id": "format.web-push-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "What the visitor sees", "text": "A notification with the content and controls permitted by their browser and operating system. Browser policy determines whether, when and how it is displayed." }, { "id": "format.web-push-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "What Nexus manages", "text": "Publisher websites, subscriptions and notification-related configuration, with delivery code that must be connected and configured for the deployment." }, { "id": "format.web-push-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "What must be in place", "text": "A compatible website integration, service worker, browser permission, delivery credentials and valid subscriptions. Adding a website to the admin is not sufficient by itself." }, { "id": "format.web-push-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "What this is not", "text": "An in-page push ad stays within a webpage and does not use a Web Push subscription. Native mobile application push also needs a different integration." }, { "id": "format.web-push-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: what it looks like", "text": "A browser notification sent to a visitor who subscribed. Placement: Supported browser / operating-system notifications. Reach a subscribed publisher audience through a configured delivery service." }, { "id": "format.web-push-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/web-push-ads", "topics": [ "formats", "format.web-push-ads", "solution.web-push-platform", "product.publisher" ], "boundary": "Push Subscribers is available for direct publishers; configured delivery integration required. Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service. Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "sourceTitle": "Web Push", "title": "Web Push: illustrative example", "text": "A visitor grants notification permission on a publisher website. Later, a notification from that publisher can appear through the configured browser push service." }, { "id": "format.in-page-push-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page push placements", "text": "In-page push is a notification-style ad rendered inside a webpage. Despite its name, it is not a browser push notification: it does not use a browser push subscription or service-worker delivery. Nexus has selected provider adapters that distinguish Push and InPage demand." }, { "id": "format.in-page-push-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: Nexus components", "text": "Selected provider feed adapters with separate Push and InPage modes." }, { "id": "format.in-page-push-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: required integration", "text": "A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget." }, { "id": "format.in-page-push-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: Placements", "text": "Notification-style units inside compatible publisher websites; Provider-supported in-page inventory" }, { "id": "format.in-page-push-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: Buying models", "text": "Provider-agreed click or impression pricing; Downstream conversion reporting where integrated" }, { "id": "format.in-page-push-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: Targeting", "text": "Request fields accepted by the provider; Supported source, geo and device controls; Placement and partner traffic policies" }, { "id": "format.in-page-push-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: Delivery flow", "text": "Publisher placement; Supported feed request; Eligible provider response; On-page rendering; Click & partner reports" }, { "id": "format.in-page-push-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Requests", "text": "Requests sent to the selected in-page demand integration." }, { "id": "format.in-page-push-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Clicks", "text": "Clicks recorded through the configured tracking path." }, { "id": "format.in-page-push-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Partner results", "text": "Revenue and NET figures where provided by the partner reporting contract." }, { "id": "format.in-page-push-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Is this the same as Web Push?", "text": "No. In-page push is displayed inside a webpage. Web Push is delivered through a browser push service to a subscribed user." }, { "id": "format.in-page-push-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Does it require browser notification permission?", "text": "It does not use the browser notification permission flow. Privacy, consent and advertising-policy requirements still depend on the data and placement used." }, { "id": "format.in-page-push-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "Will any XML feed work?", "text": "No. A supported provider adapter and compatible publisher placement are required. Confirm the provider’s in-page mode and tracking contract." }, { "id": "format.in-page-push-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "What the visitor sees", "text": "An ad styled like a small notification card inside the webpage. Its exact position, creative and dismiss behavior depend on the publisher renderer." }, { "id": "format.in-page-push-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "What Nexus connects", "text": "Selected feed adapters support an InPage mode separately from Push. The provider configuration and accepted traffic contract determine the available demand." }, { "id": "format.in-page-push-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "What you need to supply", "text": "A compatible publisher placement and renderer, a supported provider account and agreed request and tracking parameters." }, { "id": "format.in-page-push-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "What is not included automatically", "text": "The feed adapter does not prove that a universal Nexus in-page widget is included. Scope the rendering integration before launch." }, { "id": "format.in-page-push-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: what it looks like", "text": "A notification-style ad card displayed inside a webpage. Placement: Compatible publisher webpage placements. Monetize an on-page placement using a supported in-page demand provider." }, { "id": "format.in-page-push-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/in-page-push-ads", "topics": [ "formats", "format.in-page-push-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Selected feed adapters and compatible publisher placements. A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "In-page Push", "title": "In-page Push: illustrative example", "text": "A small sponsored card appears within a publisher page. It uses the webpage renderer, not the visitor’s browser notification subscription." }, { "id": "format.direct-link-ads.overview", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct links for XML traffic", "text": "A direct link routes publisher traffic through the XML / JSON module to a configured demand destination. It defines a traffic path rather than a visual creative. Source rules, destination configuration and click reporting remain part of the XML workflow." }, { "id": "format.direct-link-ads.nexus", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: Nexus components", "text": "Direct link support is available in the XML / JSON module, with publisher traffic routing, configured demand destinations, source controls and click reporting." }, { "id": "format.direct-link-ads.requirements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: required integration", "text": "Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path." }, { "id": "format.direct-link-ads.placements", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: Placements", "text": "Approved publisher links and calls to action; Configured XML demand destinations using agreed traffic sources" }, { "id": "format.direct-link-ads.buyingmodels", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: Buying models", "text": "Partner-agreed XML traffic commercial terms; Platform capacity is billed separately under the XML plan" }, { "id": "format.direct-link-ads.targeting", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: Targeting", "text": "Supported XML country and device rules; Publisher approval and feed eligibility; Request and click controls" }, { "id": "format.direct-link-ads.flow", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: Delivery flow", "text": "Publisher link; XML routing; Eligible demand; Configured destination; Click & source reporting" }, { "id": "format.direct-link-ads.metric.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Requests", "text": "Inspect traffic entering the configured XML route." }, { "id": "format.direct-link-ads.metric.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Clicks", "text": "Review clicks associated with the publisher and demand source." }, { "id": "format.direct-link-ads.metric.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Revenue", "text": "Compare recorded XML results and configured partner reporting." }, { "id": "format.direct-link-ads.question.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Is a direct link an ad format?", "text": "Strictly, it is a delivery and tracking path. It is included in this guide because operators commonly evaluate direct-link traffic as a channel." }, { "id": "format.direct-link-ads.question.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Is this the CPA module?", "text": "No. Direct Link is an XML / JSON capability. The separate CPA module manages offers, conversion events, postbacks and payout rules; those do not define XML direct-link pricing or routing." }, { "id": "format.direct-link-ads.question.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Is a link enough to start delivery?", "text": "No. Configure approved publisher traffic, compatible XML demand and a working destination before activating the traffic path." }, { "id": "format.direct-link-ads.section.0", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "What the visitor sees", "text": "The original publisher link or creative, followed by the configured demand destination. The link does not define the visual design of either page." }, { "id": "format.direct-link-ads.section.1", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "How Nexus tracks the result", "text": "The XML route keeps the publisher, demand and destination context with the recorded traffic. Use the XML reports to review clicks and commercial results." }, { "id": "format.direct-link-ads.section.2", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "What must be agreed", "text": "Allowed publisher sources, XML demand configuration, destination behavior and partner commercial terms." }, { "id": "format.direct-link-ads.section.3", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope. Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct link is not popunder", "text": "A direct link does not itself open a background browser window. Popunder behavior requires a separate permitted placement and browser-compatible implementation." }, { "id": "format.direct-link-ads.appearance", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: what it looks like", "text": "A publisher link routed through XML demand to a configured destination. Placement: Approved links and calls to action. Route publisher traffic through the XML / JSON module and inspect click results." }, { "id": "format.direct-link-ads.example", "kind": "format", "url": "https://www.nexus-soft.org/ad-formats/direct-link-ads", "topics": [ "formats", "format.direct-link-ads", "solution.xml-ad-network", "product.feeds", "product.advertiser" ], "boundary": "Direct link support is available in the XML / JSON module. Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path. XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "sourceTitle": "Direct Link", "title": "Direct Link: illustrative example", "text": "A visitor follows an approved publisher link. The configured XML demand route selects a destination, while the platform records the traffic and click reporting context." }, { "id": "guide.reporting.overview", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Reporting & reconciliation", "text": "A request, a reported impression and a partner-confirmed result are different things. Nexus gives each channel its own reporting vocabulary, with breakdowns that help you investigate traffic, delivery and commercial performance." }, { "id": "guide.reporting.capability.0", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Channel-specific measures", "text": "Search coverage, XML valid requests, RTB win rate, video completion and CPA conversions answer different questions. Work with the measures relevant to the product you operate." }, { "id": "guide.reporting.capability.1", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Dimensions with a purpose", "text": "Investigate results by the source and request attributes available in each report. The breakdown may be a search keyword, an RTB bundle or a video application environment." }, { "id": "guide.reporting.capability.2", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Partner NET reporting", "text": "Search, XML and RTB administration expose partner NET reporting fields. Configure the supported provider adapter and its update settings before comparing local and partner-reported results." }, { "id": "guide.reporting.capability.3", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Your working report", "text": "Report templates and a column chooser let operators arrange the available fields for their routine analysis. CSV export is available in the reporting interface." }, { "id": "guide.reporting.capability.4", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "A separate financial overview", "text": "The financial dashboard provides background snapshots on a five-minute cycle. It is an overview, not a promise that every partner feed or channel metric refreshes at that interval." }, { "id": "guide.reporting.capability.5", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "From exceptions to investigation", "text": "Requests with errors, invalid traffic and differences between local and NET figures give the team a starting point. Review the relevant partner and configuration before changing delivery rules." }, { "id": "guide.reporting.workflow.0", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Start with the question", "text": "Choose the channel and report: publisher, affiliate, feed, exchange, demand, video or offer performance." }, { "id": "guide.reporting.workflow.1", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Set the context", "text": "Select the period, relevant account or source and the available report dimensions." }, { "id": "guide.reporting.workflow.2", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Inspect the difference", "text": "Compare volume, delivery and commercial fields. Keep local counts and partner NET figures distinct." }, { "id": "guide.reporting.workflow.3", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Keep a useful view", "text": "Arrange columns, use a report template or export the available report for further analysis." }, { "id": "guide.reporting.definition.0", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Local versus NET", "text": "Local figures describe the platform’s recorded activity. NET fields are the corresponding measures obtained through a configured partner reporting integration. Do not treat the two as interchangeable." }, { "id": "guide.reporting.definition.1", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Coverage versus conversion", "text": "Coverage describes a delivery-related measure in a channel report. A conversion represents an outcome in the performance workflow. Read them in their own product context." }, { "id": "guide.reporting.definition.2", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Useful comparisons", "text": "Compare like-for-like periods, partners, currencies and report dimensions. Confirm the provider update window before investigating a discrepancy." }, { "id": "guide.reporting.definition.3", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Illustrative reconciliation: 120 versus 114 clicks", "text": "For a fictional completed reporting period, suppose the local report shows 120 clicks and the partner NET report shows 114. The absolute difference is 6; using the local count as the explicitly chosen denominator, 6 / 120 × 100 = 5%. This is sample arithmetic, not a customer result, an acceptable discrepancy threshold or a Nexus metric formula. Record which count is the denominator when sharing the comparison." }, { "id": "guide.reporting.definition.4", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "First align the comparison", "text": "Check the same start/end times and timezone, the same affiliate or publisher link, the same feed and source breakdown, and the same validity or acceptance scope. Check whether the provider has finished reporting that period. For money, also align currency and gross/net or revenue-share treatment. A date label alone is not proof that two exports describe the same activity." }, { "id": "guide.reporting.definition.5", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Then isolate the remaining difference", "text": "Break the fictional six-click gap down by the dimensions available in the relevant report. If it concentrates in one feed or SubID, inspect that connection and its import settings. If the partner period is incomplete, wait for its agreed update window before drawing a conclusion. Retain separate local and partner values; replacing one with the other hides the evidence needed to resolve the mismatch." }, { "id": "guide.reporting.definition.6", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Do not turn a count gap into an invoice claim", "text": "A click discrepancy does not directly establish a revenue discrepancy. Price models, accepted events, adjustments and commercial terms can differ. Likewise, NET is a provider-reporting label here, not a universal accounting definition of profit. Keep a record of the report filters, update timestamp, expected adjustment process and responsible partner contact before deciding which figure governs settlement." }, { "id": "guide.reporting.definition.7", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Make the investigation repeatable", "text": "Choose the needed columns and available dimensions, save a report view or export CSV, and record the comparison assumptions alongside the evidence. Investigate representative accepted and rejected samples through the approved integration process where aggregate reports are insufficient. A useful resolution explains the source of the difference and the next check; it does not silently change traffic rules just to make two totals agree." }, { "id": "guide.reporting.metrics", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Reporting & reconciliation: metrics", "text": "Requests; Valid / invalid traffic; Clicks; Revenue; Cost / spend; Profit; Partner NET" }, { "id": "guide.reporting.dimensions", "kind": "guide", "url": "https://www.nexus-soft.org/reporting", "topics": [ "guides", "guide.reporting" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "sourceTitle": "Reporting & reconciliation", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Search metrics and NET import boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "XML affiliate, feed and provider reporting" }, { "url": "https://www.nexus-soft.org/products/rtb", "title": "RTB local and partner NET reporting" } ], "title": "Reporting & reconciliation: dimensions", "text": "Channel-specific reports; Date range; Account / partner; Source identifiers; Traffic attributes" }, { "id": "guide.publisher-platform.overview", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Publisher operations", "text": "Push Subscribers is available for direct publishers. Manage publisher websites, approvals, browser subscriptions, subscriber inventory and performance in a connected workflow. Keep commercial relationships separate from delivery configuration." }, { "id": "guide.publisher-platform.capability.0", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Website administration", "text": "Manage the publisher, website name, URL, description and account status. Approval and suspension controls make the status of a website explicit." }, { "id": "guide.publisher-platform.capability.1", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Welcome notifications", "text": "Configure a welcome notification with a title, destination link and message text. Treat the notification content as part of the publisher experience." }, { "id": "guide.publisher-platform.capability.2", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Subscription behavior", "text": "Set the subscription trigger, time frame, delay and prompt behavior. Advanced options include persistence until a click, where configured for the integration." }, { "id": "guide.publisher-platform.capability.3", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Postbacks and redirects", "text": "Configure a subscription postback and the redirects associated with subscribed and not-subscribed outcomes. Validate the destination and integration before launch." }, { "id": "guide.publisher-platform.capability.4", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Push Subscribers inventory", "text": "Inspect first and last activity, website and source identifiers, country, language, browser, OS and subscription status. The inventory also exposes impression, click and revenue fields." }, { "id": "guide.publisher-platform.capability.5", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Publisher reporting", "text": "Review request validity, initialization, subscriber activity, impressions, clicks, closed notifications and revenue. Break down the available reports by account, country, OS and browser." }, { "id": "guide.publisher-platform.workflow.0", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Register the website", "text": "Associate the site with its publisher and review its URL, description and account status." }, { "id": "guide.publisher-platform.workflow.1", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Define the experience", "text": "Configure notification text, subscription prompts, redirects and postback destinations." }, { "id": "guide.publisher-platform.workflow.2", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Validate the integration", "text": "Confirm the delivery service and Push URL are configured, then test the approved integration in a controlled environment." }, { "id": "guide.publisher-platform.workflow.3", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Review the activity", "text": "Inspect subscriber records and publisher statistics before adjusting the site’s configuration." }, { "id": "guide.publisher-platform.definition.0", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Before a site goes live", "text": "Confirm ownership and approval, the service URL, subscription behavior, notification content and valid callback destinations." }, { "id": "guide.publisher-platform.definition.1", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Before sending notifications", "text": "Check the audience and permission model, supported browsers and delivery configuration. A subscriber record alone is not a delivery guarantee." }, { "id": "guide.publisher-platform.definition.2", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Before publishing a case study", "text": "Use approved, anonymized reporting and explain the period and measurement method. Customer identities and live subscriber endpoints should remain private." }, { "id": "guide.publisher-platform.metrics", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Publisher operations: metrics", "text": "Requests; Valid requests; Errors; Initializations; Subscribers; Impressions; Clicks; Invalid clicks; Closed; CTR; CPC; Revenue" }, { "id": "guide.publisher-platform.dimensions", "kind": "guide", "url": "https://www.nexus-soft.org/publisher-platform", "topics": [ "guides", "guide.publisher-platform" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "sourceTitle": "Publisher operations", "title": "Publisher operations: dimensions", "text": "Publisher account; Country; Operating system; Browser" }, { "id": "guide.campaign-management.overview", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Advertiser self-serve", "text": "Bring display, native, contextual, video, popunder and push campaigns together. Direct advertisers manage creatives, targeting, budgets, funds and account balance in a self-serve workspace, with reporting across their configured delivery channels." }, { "id": "guide.campaign-management.capability.0", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "CPC and CPM buying", "text": "Buy traffic by click with CPC or by thousand impressions with CPM. Popunder workflows also expose CPV bidding. Set the bid, daily and total budgets, frequency cap and schedule for the selected campaign type. Campaign media spend is separate from the Nexus platform subscription and its capacity-based pricing." }, { "id": "guide.campaign-management.capability.1", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Delivery schedule", "text": "Configure the campaign’s schedule alongside its budget and audience. Review the intended delivery window before activating a campaign." }, { "id": "guide.campaign-management.capability.2", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Detailed audience selection", "text": "Define geographic, operating system, browser and browser-version targeting. Use the available campaign fields to narrow the traffic that matches the objective." }, { "id": "guide.campaign-management.capability.3", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Source-level controls", "text": "Manage IP, domain, publisher, SubID, keyword and feed eligibility with the available allowlists and blocklists. Source controls make exclusions explicit." }, { "id": "guide.campaign-management.capability.4", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Creative inventory", "text": "Browse creative records with their advertiser, campaign, type, status and dimensions. Keep the asset associated with the campaign it belongs to." }, { "id": "guide.campaign-management.capability.5", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Creative content and tracking", "text": "The creative editor separates basic information, tracking and media. Configure the name, status, width, height, click URL, impression pixel and asset as required by the format." }, { "id": "guide.campaign-management.capability.6", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Self-serve funds and balance", "text": "Direct advertisers can manage funds and view their account balance in the advertiser workspace, alongside their campaigns and reports. Available funding methods and payment-provider setup are configured for the deployment; no particular gateway or instant settlement is implied." }, { "id": "guide.campaign-management.capability.7", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Formats and delivery channels", "text": "Run direct campaigns with display and HTML banners, native and contextual ads, video, popunder, Web Push and in-page push. Connect eligible traffic through Push delivery, XML / JSON feeds and OpenRTB. The creative format defines the experience; the delivery integration connects it to compatible publisher inventory." }, { "id": "guide.campaign-management.workflow.0", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Set the campaign boundaries", "text": "Define the bid, daily and total budget, frequency cap and schedule for the campaign." }, { "id": "guide.campaign-management.workflow.1", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Choose the eligible audience", "text": "Select request attributes and source lists, then review the exclusions with your operations team." }, { "id": "guide.campaign-management.workflow.2", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Prepare the creative", "text": "Associate the asset with its advertiser and campaign. Check dimensions, click URL and impression tracking." }, { "id": "guide.campaign-management.workflow.3", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Validate before scaling", "text": "Run a controlled delivery check and use the relevant channel reports to review traffic and outcomes." }, { "id": "guide.campaign-management.definition.0", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Campaign versus offer", "text": "A campaign defines an advertising setup and audience. The CPA offer workflow has its own payout models, conversion events, caps and publisher-access settings." }, { "id": "guide.campaign-management.definition.1", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Creative versus ad format", "text": "An asset and its tracking fields belong to the creative. The ad format determines how the placement is presented and which delivery integration it needs." }, { "id": "guide.campaign-management.definition.2", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Configuration versus outcome", "text": "Budgets, schedules and targeting define intended behavior. Confirm delivery and partner reporting with controlled traffic before committing to performance expectations." }, { "id": "guide.campaign-management.metrics", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Advertiser self-serve: metrics", "text": "Campaign status; Advertiser; Creative type; Width / height; Click URL; Impression pixel" }, { "id": "guide.campaign-management.dimensions", "kind": "guide", "url": "https://www.nexus-soft.org/campaign-management", "topics": [ "guides", "guide.campaign-management" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "sourceTitle": "Advertiser self-serve", "title": "Advertiser self-serve: dimensions", "text": "Country; Operating system; Browser / version; IP / domain; Publisher / SubID; Keyword / feed" }, { "id": "integration.traffic-delivery.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.traffic-delivery" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Schemas, URLs, timeouts, result limits and eligible routes are explicitly configured.", "sourceTitle": "Nexus integrations", "title": "Traffic & delivery", "text": "Move advertising opportunities and responses through the protocol each channel expects." }, { "id": "integration.traffic-delivery.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.traffic-delivery" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Schemas, URLs, timeouts, result limits and eligible routes are explicitly configured.", "sourceTitle": "Nexus integrations", "title": "Traffic & delivery: integration interfaces", "text": "XML and JSON feeds; HTTP service APIs; OpenRTB endpoints; Prebid.js and Prebid Server; Cookie sync; VAST demand and delivery; Popunder JS; Direct links" }, { "id": "integration.traffic-delivery.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.traffic-delivery" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Schemas, URLs, timeouts, result limits and eligible routes are explicitly configured.", "sourceTitle": "Nexus integrations", "title": "Traffic & delivery: data in contract", "text": "Requests, targeting context, bid or result data, delivery status and protocol errors." }, { "id": "integration.traffic-delivery.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.traffic-delivery" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Schemas, URLs, timeouts, result limits and eligible routes are explicitly configured.", "sourceTitle": "Nexus integrations", "title": "Traffic & delivery: integration requirements", "text": "Schemas, URLs, timeouts, result limits and eligible routes are explicitly configured." }, { "id": "integration.data-reporting.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.data-reporting" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Connections are source-qualified, credentials stay server-side and returned data is bounded.", "sourceTitle": "Nexus integrations", "title": "Data & reporting", "text": "Connect commercial records and operational evidence without making the browser a database client." }, { "id": "integration.data-reporting.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.data-reporting" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Connections are source-qualified, credentials stay server-side and returned data is bounded.", "sourceTitle": "Nexus integrations", "title": "Data & reporting: integration interfaces", "text": "MongoDB; MySQL; TimescaleDB / PostgreSQL; External reporting services" }, { "id": "integration.data-reporting.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.data-reporting" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Connections are source-qualified, credentials stay server-side and returned data is bounded.", "sourceTitle": "Nexus integrations", "title": "Data & reporting: data in contract", "text": "Platform records, aggregated statistics, partner mappings and approved reporting dimensions." }, { "id": "integration.data-reporting.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.data-reporting" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Connections are source-qualified, credentials stay server-side and returned data is bounded.", "sourceTitle": "Nexus integrations", "title": "Data & reporting: integration requirements", "text": "Connections are source-qualified, credentials stay server-side and returned data is bounded." }, { "id": "integration.realtime-infrastructure.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.realtime-infrastructure" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Only documented Redis records are in contract; unrelated keys and queues remain outside it.", "sourceTitle": "Nexus integrations", "title": "Realtime infrastructure", "text": "Reach the fast-changing state used by delivery services while keeping key access deliberately narrow." }, { "id": "integration.realtime-infrastructure.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.realtime-infrastructure" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Only documented Redis records are in contract; unrelated keys and queues remain outside it.", "sourceTitle": "Nexus integrations", "title": "Realtime infrastructure: integration interfaces", "text": "Redis application hashes; Tenant load balancers; QPS and rate controls; Service health state" }, { "id": "integration.realtime-infrastructure.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.realtime-infrastructure" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Only documented Redis records are in contract; unrelated keys and queues remain outside it.", "sourceTitle": "Nexus integrations", "title": "Realtime infrastructure: data in contract", "text": "Approved application configuration, limits, availability and safe operational status." }, { "id": "integration.realtime-infrastructure.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.realtime-infrastructure" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Only documented Redis records are in contract; unrelated keys and queues remain outside it.", "sourceTitle": "Nexus integrations", "title": "Realtime infrastructure: integration requirements", "text": "Only documented Redis records are in contract; unrelated keys and queues remain outside it." }, { "id": "integration.identity-operations.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.identity-operations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Registration grants no platform access or administrator role; protected requests re-check current account status, role and assigned scope.", "sourceTitle": "Nexus integrations", "title": "Identity & operations", "text": "Give people and connected platforms the correct scope before any privileged workflow begins." }, { "id": "integration.identity-operations.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.identity-operations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Registration grants no platform access or administrator role; protected requests re-check current account status, role and assigned scope.", "sourceTitle": "Nexus integrations", "title": "Identity & operations: integration interfaces", "text": "Email/password and Google member registration; Google-only administrator sign-in; SMTP or Resend account email; Platform-level assignments; Audit events" }, { "id": "integration.identity-operations.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.identity-operations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Registration grants no platform access or administrator role; protected requests re-check current account status, role and assigned scope.", "sourceTitle": "Nexus integrations", "title": "Identity & operations: data in contract", "text": "Verified identity, role, platform scope, session state and bounded administrative evidence." }, { "id": "integration.identity-operations.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.identity-operations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Registration grants no platform access or administrator role; protected requests re-check current account status, role and assigned scope.", "sourceTitle": "Nexus integrations", "title": "Identity & operations: integration requirements", "text": "Registration grants no platform access or administrator role; protected requests re-check current account status, role and assigned scope." }, { "id": "integration.performance-tracking.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.performance-tracking", "product.cpa", "postback" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Accepted fields, event ownership, retry behaviour and deduplication rules are agreed in advance.", "sourceTitle": "Nexus integrations", "title": "Performance tracking", "text": "Join an acquisition event to the offer, source and partner economics responsible for it." }, { "id": "integration.performance-tracking.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.performance-tracking", "product.cpa", "postback" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Accepted fields, event ownership, retry behaviour and deduplication rules are agreed in advance.", "sourceTitle": "Nexus integrations", "title": "Performance tracking: integration interfaces", "text": "Server-to-server postbacks; Conversion identifiers; Campaign and offer APIs; External tracking services" }, { "id": "integration.performance-tracking.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.performance-tracking", "product.cpa", "postback" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Accepted fields, event ownership, retry behaviour and deduplication rules are agreed in advance.", "sourceTitle": "Nexus integrations", "title": "Performance tracking: data in contract", "text": "Click identifiers, event names, conversion values, status and reconciliation context." }, { "id": "integration.performance-tracking.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.performance-tracking", "product.cpa", "postback" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Accepted fields, event ownership, retry behaviour and deduplication rules are agreed in advance.", "sourceTitle": "Nexus integrations", "title": "Performance tracking: integration requirements", "text": "Accepted fields, event ownership, retry behaviour and deduplication rules are agreed in advance." }, { "id": "integration.ai-discovery.overview", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.ai-discovery", "mcp" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Public discovery does not expose customer credentials, arbitrary queries or privileged writes.", "sourceTitle": "Nexus integrations", "title": "AI & developer discovery", "text": "Expose stable public product knowledge and documented interfaces to software clients." }, { "id": "integration.ai-discovery.interfaces", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.ai-discovery", "mcp" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Public discovery does not expose customer credentials, arbitrary queries or privileged writes.", "sourceTitle": "Nexus integrations", "title": "AI & developer discovery: integration interfaces", "text": "OpenAPI document; Streamable HTTP MCP; llms.txt discovery; Typed tools and resources" }, { "id": "integration.ai-discovery.data", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.ai-discovery", "mcp" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Public discovery does not expose customer credentials, arbitrary queries or privileged writes.", "sourceTitle": "Nexus integrations", "title": "AI & developer discovery: data in contract", "text": "Product capabilities, schemas, format guidance and bounded solution-discovery context." }, { "id": "integration.ai-discovery.requirements", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations", "integration.ai-discovery", "mcp" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery. Public discovery does not expose customer credentials, arbitrary queries or privileged writes.", "sourceTitle": "Nexus integrations", "title": "AI & developer discovery: integration requirements", "text": "Public discovery does not expose customer credentials, arbitrary queries or privileged writes." }, { "id": "integration.workflow.01", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Integration workflow: Contract", "text": "Define owner, direction, authentication, schema, volume range and expected response." }, { "id": "integration.workflow.02", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Integration workflow: Sample", "text": "Use representative payloads with secrets and personal data removed or safely substituted." }, { "id": "integration.workflow.03", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Integration workflow: Connect", "text": "Configure the endpoint, source, credentials reference and tenant policy server-side." }, { "id": "integration.workflow.04", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Integration workflow: Exercise", "text": "Test valid, empty, slow, malformed, duplicate and unavailable-path behaviour." }, { "id": "integration.workflow.05", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Integration workflow: Reconcile", "text": "Confirm which metrics, logs, errors and commercial records prove correct operation." }, { "id": "integration.readiness.0", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Ownership", "text": "Named technical and commercial owners on both sides of the connection." }, { "id": "integration.readiness.1", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Direction", "text": "A clear record of what Nexus sends, receives, stores and never exposes." }, { "id": "integration.readiness.2", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Authentication", "text": "Documented credential type, rotation owner and safe secret reference." }, { "id": "integration.readiness.3", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Capacity", "text": "Expected and maximum request ranges, timeout budget, caps and retry policy." }, { "id": "integration.readiness.4", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Failure", "text": "Agreed behaviour for empty data, partial response, dependency failure and recovery." }, { "id": "integration.readiness.5", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "These are supported integration families, not a promise that every external product connects without design work. Exact schemas, versions and ownership are confirmed during discovery.", "sourceTitle": "Nexus integrations", "title": "Evidence", "text": "The fields and reports used to validate delivery and reconcile partner totals." }, { "id": "integration.available.cookie-sync", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Partner configuration and browser cookie restrictions still apply. Cookie sync and Prebid are separate integrations, each with its own configuration requirements.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-10", "title": "Cookie sync: available now", "text": "Cookie sync is available now in OpenRTB. Configure UID macros and image or iframe sync URLs, then review synced requests in RTB reporting." }, { "id": "integration.available.prebid", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Confirm the supported versions, bidder adapter, endpoint configuration and inventory formats for your deployment. Partner access and commercial agreements are configured separately; availability is not a guarantee of compatibility with every adapter or demand partner.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-11", "title": "Prebid.js and Prebid Server: available now", "text": "Prebid.js and Prebid Server integrations are available now for Nexus OpenRTB. Connect header-bidding workflows to your configured RTB supply and demand setup." }, { "id": "integration.available.popunder-js", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Use a permitted publisher placement and suitable demand. Confirm the script version and any provider licensing requirements for the deployment. Browser restrictions determine whether and how a secondary window can open; support is not a browser-bypass guarantee.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-10", "title": "Popunder JS: available now", "text": "Popunder JS support is available now in the XML / JSON module, with publisher script configuration, frequency and delay settings, feed routing and source controls." }, { "id": "integration.available.direct-link", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Use approved traffic sources, configured XML demand and a working destination. A direct link does not itself create a popunder. Do not assume CPA conversion or payout rules apply to XML direct links.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-10", "title": "Direct links: available now", "text": "Direct link support is available now in the XML / JSON module. Route publisher traffic through the configured XML demand and destination workflow, with source controls and click reporting. This is an XML capability, not the CPA offer module." }, { "id": "integration.available.direct-advertisers", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Funding methods and payment-provider configuration depend on the deployment. Funds and balance management do not imply a particular payment gateway, instant settlement or public access to account balances.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-10", "title": "Advertiser self-serve: available now", "text": "Advertiser self-serve is available now for direct advertisers. Advertisers can manage their campaigns, creatives, targeting, budgets, funds and account balance in the advertiser workspace, with reporting and operator-defined access." }, { "id": "integration.available.advertiser-formats", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "CPC and CPM describe media buying, not the Nexus capacity subscription. XML / JSON and OpenRTB are delivery integrations, not creative formats. Match each campaign to compatible inventory, creative assets, tracking and, where required, a player or publisher renderer. Web Push requires permission and valid subscriptions.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-11", "title": "Multi-format direct campaigns: available now", "text": "Multi-format direct campaigns are available now for direct advertisers: display and HTML banners, native and contextual ads, video, popunder, Web Push and in-page push. Manage CPC (cost per click) and CPM (cost per thousand impressions) buying models, with delivery across Push, XML / JSON and OpenRTB traffic. Campaigns, creatives, targeting and budgets stay in the advertiser workspace." }, { "id": "integration.available.push-subscribers", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "Web Push requires browser permission, valid subscriptions and configured website and delivery services. It is distinct from an in-page push ad; a publisher record alone does not enable delivery.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-10", "title": "Push Subscribers: available now", "text": "The Push Subscribers module is available now for direct publishers. Manage publisher websites, browser subscriptions, subscriber inventory, subscription settings and notification activity with publisher reporting." }, { "id": "integration.roadmap.scope", "kind": "guide", "url": "https://www.nexus-soft.org/integrations", "topics": [ "guides", "integrations" ], "boundary": "This is a development target, not a guaranteed delivery date or an SLA. Confirm release status, supported versions and the exact integration scope before planning a launch. The broader goal is full support for the planned modules and integrations; it is not a promise to support every third-party product or arbitrary requested feature.", "sourceTitle": "Nexus integrations", "lastModified": "2026-09-11", "title": "Development plan and release scope", "text": "Prebid.js and Prebid Server, cookie sync, Popunder JS, XML direct links, multi-format direct campaigns, advertiser self-serve and Push Subscribers are already available. The remaining planned modules and integrations are in development, with a target of 10 December 2026 under the plan confirmed on 10 September 2026. Ask the team to confirm whether another specific missing feature is in scope and when it will be available." }, { "id": "resource.what-is-openrtb.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/what-is-openrtb", "topics": [ "resources", "resource.what-is-openrtb", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is OpenRTB? A practical guide for AdTech operators", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB configuration and reporting scope" }, { "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "title": "Request, response and selected-bid definitions" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6 protocol specification" } ], "title": "What is OpenRTB? A practical guide for AdTech operators", "text": "OpenRTB is an open protocol for exchanging bid requests and bid responses between advertising systems. The protocol defines the message contract; a production platform still needs routing, validation, capacity controls, reporting and commercial policy." }, { "id": "resource.what-is-openrtb.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/what-is-openrtb", "topics": [ "resources", "resource.what-is-openrtb", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is OpenRTB? A practical guide for AdTech operators", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB configuration and reporting scope" }, { "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "title": "Request, response and selected-bid definitions" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6 protocol specification" } ], "title": "The request lifecycle", "text": "A publisher or SSP creates a bid request describing an impression opportunity. An exchange or routing layer validates it, selects eligible demand endpoints and waits within a bounded auction window. DSPs return bids, the auction chooses an eligible result and the delivery path records notices and outcomes. Supply request validation Demand endpoint selection Auction timeout boundary Bid and win visibility" }, { "id": "resource.what-is-openrtb.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/what-is-openrtb", "topics": [ "resources", "resource.what-is-openrtb", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is OpenRTB? A practical guide for AdTech operators", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB configuration and reporting scope" }, { "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "title": "Request, response and selected-bid definitions" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6 protocol specification" } ], "title": "What the protocol does not solve", "text": "OpenRTB does not decide which commercial relationships are valid, how much QPS a partner may send, which filters protect inventory or how operators investigate loss reasons. Those responsibilities belong to the platform operating around the bidstream." }, { "id": "resource.what-is-openrtb.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/what-is-openrtb", "topics": [ "resources", "resource.what-is-openrtb", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is OpenRTB? A practical guide for AdTech operators", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB configuration and reporting scope" }, { "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "title": "Request, response and selected-bid definitions" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6 protocol specification" } ], "title": "How Nexus approaches OpenRTB", "text": "Nexus places tenant configuration, demand routes, QPS governance, endpoint mappings and operational visibility around the auction service. The objective is a bidstream commercial and technical teams can reason about together." }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "SSP vs DSP vs ad exchange: choosing the operation you need", "text": "Start with who you serve and which decision you need to control. A publisher needs a route to eligible demand. An advertiser needs a way to buy suitable opportunities. A network connecting the two needs partner access, trading rules and comparable reports. These responsibilities can share infrastructure, but they are different operating products." }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Supply-side platform", "text": "An SSP represents publisher inventory and helps connect available opportunities to buyers. In a deployment discussion, identify the publisher or supply relationship, the inventory allowed into the system and the downstream parties eligible to receive it. Access to a protocol endpoint does not by itself establish the commercial right to trade that inventory. Publisher integration Inventory policy Supply quality Outbound QPS" }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Demand-side platform", "text": "A DSP serves advertiser buying requirements: which campaign may buy, from which supply, under which targeting, budget, creative and measurement rules. Nexus describes its DSP option as an integration-scoped combination of campaign management and the RTB runtime. The advertiser interface, bidding strategies, attribution, billing and specific exchange access must be validated separately. Campaign eligibility Audience and context Budget control Bid decision" }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Ad exchange", "text": "An exchange connects supply and demand relationships and applies the agreed trading rules. The Nexus exchange workflow exposes exchange connections, demand connections, demand grants, inventory rules and trading reports. The OpenRTB protocol standardizes communication between inventory suppliers and buyers; it does not supply publisher contracts, demand relationships or an advertiser business model." }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Illustrative decision: exchange or DSP?", "text": "Imagine a network with two approved supply partners and three contracted demand endpoints. Its first need is to decide which demand may receive each source and investigate traffic and trading results: begin with exchange scope. If its customers instead need to create campaigns, upload creatives and buy from a defined set of exchanges, begin with DSP scope. These fictional partner counts describe a planning exercise, not a Nexus customer or included partner bundle. Exchange brief: supply access, demand grants, supported formats and reporting ownership. DSP brief: advertiser workflow, campaigns, creative review, buying connections and event definitions. Combined brief: document both roles and the boundary between the campaign and trading workflows." }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Validate the message and timing contract", "text": "The IAB OpenRTB 2.6 specification defines tmax as the time the exchange allows for receiving bids, including network latency. That deadline is an input to integration design, not a Nexus speed guarantee. Agree on the protocol version, required context, creative formats, no-bid behavior, delivery events and expected response timing with each partner. Test representative accepted, rejected, slow and unavailable paths before increasing traffic. Record the fields the supply actually sends and those the buyer requires. Keep bid responses, delivery events and commercial reconciliation as separate checkpoints. Treat a version selector as configuration evidence; confirm interoperability with partner tests." }, { "id": "resource.ssp-vs-dsp-vs-ad-exchange.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange", "topics": [ "resources", "resource.ssp-vs-dsp-vs-ad-exchange", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "SSP vs DSP vs ad exchange: choosing the operation you need", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "Nexus DSP deployment scope" }, { "url": "https://www.nexus-soft.org/solutions/openrtb-exchange", "title": "Nexus exchange workflow and prerequisites" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB Tech Lab OpenRTB 2.6: introduction and BidRequest definition" } ], "title": "Bring one concrete workflow to evaluation", "text": "A useful evaluation begins with a redacted traffic example, the partners already available to you, the first supported format and the operator who will investigate failures. Ask to follow that example through configuration and reporting. For a DSP, also show the intended advertiser journey. This reveals integration work and missing responsibilities earlier than comparing a long list of product labels." }, { "id": "resource.openrtb-request-lifecycle.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "topics": [ "resources", "resource.openrtb-request-lifecycle", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "The OpenRTB request lifecycle from supply to win notice", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB controls and report boundaries" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Keep local, partner and delivery figures separate" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB OpenRTB 2.6: no-bid responses, auction timing and win notices" } ], "title": "The OpenRTB request lifecycle from supply to win notice", "text": "A request lifecycle is more useful than a feature checklist because it shows where latency, filtering, commercial rules and failures enter the system." }, { "id": "resource.openrtb-request-lifecycle.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "topics": [ "resources", "resource.openrtb-request-lifecycle", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "The OpenRTB request lifecycle from supply to win notice", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB controls and report boundaries" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Keep local, partner and delivery figures separate" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB OpenRTB 2.6: no-bid responses, auction timing and win notices" } ], "title": "Receive and validate", "text": "The supply request must be structurally valid and acceptable to tenant policy before it consumes downstream capacity. Invalid or unsupported opportunities should produce understandable outcomes. Contract validation Required context Inventory policy Source identification" }, { "id": "resource.openrtb-request-lifecycle.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "topics": [ "resources", "resource.openrtb-request-lifecycle", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "The OpenRTB request lifecycle from supply to win notice", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB controls and report boundaries" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Keep local, partner and delivery figures separate" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB OpenRTB 2.6: no-bid responses, auction timing and win notices" } ], "title": "Select and route", "text": "Eligible demand endpoints are chosen using availability, capacity, configured policy and the request context supported by the connected auction service." }, { "id": "resource.openrtb-request-lifecycle.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "topics": [ "resources", "resource.openrtb-request-lifecycle", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "The OpenRTB request lifecycle from supply to win notice", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB controls and report boundaries" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Keep local, partner and delivery figures separate" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB OpenRTB 2.6: no-bid responses, auction timing and win notices" } ], "title": "Observe the outcome", "text": "Response rate, bid rate, auction result, timeout and notice behavior create the operational evidence needed to tune routes and partner expectations." }, { "id": "resource.openrtb-request-lifecycle.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/openrtb-request-lifecycle", "topics": [ "resources", "resource.openrtb-request-lifecycle", "cluster.programmatic" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "The OpenRTB request lifecycle from supply to win notice", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/core-features", "title": "Nexus OpenRTB controls and report boundaries" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Keep local, partner and delivery figures separate" }, { "url": "https://github.com/InteractiveAdvertisingBureau/openrtb2.x/blob/main/2.6.md", "title": "IAB OpenRTB 2.6: no-bid responses, auction timing and win notices" } ], "title": "Worked example: follow requests without counting them twice", "text": "Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. Start with an authored batch of 1,000 incoming requests: 80 invalid, 120 not eligible for the selected routes and 800 routed. Assume one impression opportunity per incoming request, two eligible demand endpoints per routed request and at most one acceptable bid per partner response. The 1,600 outgoing attempts yield 940 explicit no-bid responses, 420 acceptable bid responses, 160 timeouts and 80 invalid responses. Separately, 320 of the 800 routed auctions have a selected bid and 480 do not. These are synthetic worksheet categories, not a Nexus export schema or measured outcomes. 420 / 1,600 = 26.25% acceptable bids per outgoing attempt; 320 / 800 = 40% selected bids per routed auction. These are not CTR or delivered fill. No elapsed time establishes QPS; selection proves neither delivery nor revenue. The two-endpoint assumption is not a routing guarantee or an included demand bundle. Prebid integration and a commercial relationship with a buyer are not established by this example." }, { "id": "resource.qps-governance.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "QPS governance for advertising infrastructure", "text": "Queries per second is not only a server metric. In AdTech it is also a contractual and commercial boundary between supply, routing infrastructure and demand." }, { "id": "resource.qps-governance.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "Why one global limit is insufficient", "text": "Search and XML workloads have different request shapes, economics and delivery paths. Nexus therefore models independent channel QPS values and supports member-level QPS structures for XML operations. Platform boundary Channel boundary Member boundary Service capacity" }, { "id": "resource.qps-governance.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "Caps versus QPS", "text": "QPS limits instantaneous rate. A cap limits volume over a longer operating or commercial period. Both may be required to prevent a fast source from consuming an entire allocation." }, { "id": "resource.qps-governance.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "Governed configuration", "text": "Nexus keeps limits in validated tenant configuration and approved runtime records rather than exposing Redis or service credentials to the browser." }, { "id": "resource.qps-governance.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "Illustrative incoming and outgoing traffic", "text": "Suppose 1,000 incoming requests per second are each routed to two eligible partners, producing 2,000 outgoing requests per second. This is illustrative arithmetic, not a customer result, a routing promise or a performance benchmark. Nexus prices the incoming QPS, not the sum of incoming and outgoing traffic. For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing. Check each partner’s own rate limits and integration contract before increasing fan-out." }, { "id": "resource.qps-governance.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/qps-governance", "topics": [ "resources", "resource.qps-governance", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "QPS governance for advertising infrastructure", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML incoming QPS and daily click capacity" }, { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "OpenRTB module and location limits" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Video capacity scope" } ], "title": "Daily clicks are a separate capacity limit", "text": "For XML and OpenRTB, 1,000 incoming QPS allows a maximum of 10,000,000 clicks per day; 2,000 QPS allows 20,000,000. Each module and each location has its own limit. Unused capacity in one location does not cover another. This XML/RTB daily click rule is not a Video plan limit. XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "resource.supply-quality-filtering.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/supply-quality-filtering", "topics": [ "resources", "resource.supply-quality-filtering", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Supply quality filtering without a black box", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus request-context targeting and traffic-quality boundaries" }, { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Video channel controls and deployment limitations" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed eligibility, repetition and request limits" } ], "title": "Supply quality filtering without a black box", "text": "A filter should have an owner, an input signal and an explainable result. An unexplained rejection rule makes partner support and commercial reconciliation unnecessarily difficult." }, { "id": "resource.supply-quality-filtering.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/supply-quality-filtering", "topics": [ "resources", "resource.supply-quality-filtering", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Supply quality filtering without a black box", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus request-context targeting and traffic-quality boundaries" }, { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Video channel controls and deployment limitations" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed eligibility, repetition and request limits" } ], "title": "Available request context", "text": "Nexus models referrer, language, user-agent and sub-ID participation in XML request workflows. The connected engine determines how enabled signals are enforced. Referrer Language User agent Sub-ID" }, { "id": "resource.supply-quality-filtering.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/supply-quality-filtering", "topics": [ "resources", "resource.supply-quality-filtering", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Supply quality filtering without a black box", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus request-context targeting and traffic-quality boundaries" }, { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Video channel controls and deployment limitations" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed eligibility, repetition and request limits" } ], "title": "Environment controls", "text": "The Video channel editor groups network-risk controls for datacenters, crawlers, Tor, VPN and proxy traffic. Other modules expose their own environment checks; the configuration guide below explains Video channel policy, not iframe filtering or a universal policy for every module." }, { "id": "resource.supply-quality-filtering.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/supply-quality-filtering", "topics": [ "resources", "resource.supply-quality-filtering", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Supply quality filtering without a black box", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus request-context targeting and traffic-quality boundaries" }, { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Video channel controls and deployment limitations" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed eligibility, repetition and request limits" } ], "title": "Repetition controls", "text": "Duplicate-request policy, IP request ceilings and global maximum requests help protect delivery from repeated or excessive behavior." }, { "id": "resource.xml-feed-monetization.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "XML feed monetization: build and validate an ad-network workflow", "text": "An XML ad network connects publisher traffic with agreed advertiser feeds. The operating challenge is to make each relationship explicit: which source may request results, which demand may answer, what context must survive the connection, which limits apply and how both parties will measure the outcome. XML describes a data format; it does not establish a universal feed schema or guarantee demand access." }, { "id": "resource.xml-feed-monetization.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Start with the publisher and demand contract", "text": "List the approved publisher source and the advertiser feed it will use. Agree on required request context, result fields, click tracking, timeouts and reporting responsibility before connecting them. Nexus provides affiliate integration settings, provider/feed configuration and explicit affiliate-to-feed assignments. A provider name or XML URL is not proof that an adapter accepts every variation of that provider’s response. Publisher identity and source/SubID conventions. Provider response fields, image/icon requirements, result count and timeout. Commercial agreement, accepted traffic types and reporting update window." }, { "id": "resource.xml-feed-monetization.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Illustrative mapping: one source, two feeds", "text": "Suppose publisher Cedar has two sources, search-panel and news-widget. Feed A accepts the approved search traffic; Feed B has a separately agreed contextual integration. Write those relationships into a planning matrix before configuration. Mapping a feed to Cedar does not automatically prove that every Cedar source is eligible. Check the available resource-level targeting and the provider contract for each path. These names are fictional planning labels, not real integrations or Nexus API parameters. Cedar / search-panel → Feed A → agreed search response and click contract. Cedar / news-widget → Feed B → separately validated contextual delivery. Unexpected source → investigate identity and eligibility before enabling demand." }, { "id": "resource.xml-feed-monetization.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Separate eligibility, rate and commercial limits", "text": "Nexus XML feed editors expose geographic, device, domain, keyword, carrier and subscriber-age targeting where the integration supplies the relevant context. Limits include maximum requests/QPS, daily budget, click ceilings, repeated-click rules and result expiry. These controls answer different questions. A rate limit bounds request flow, a click cap bounds counted activity and a budget constrains the commercial allocation. Their configured values are not a published hosting-capacity guarantee." }, { "id": "resource.xml-feed-monetization.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Exercise the route before increasing traffic", "text": "Use synthetic or appropriately redacted samples to check a valid response, an empty response, malformed data, a timeout and a repeated click. For each case, agree on the expected result and the report or integration log that will demonstrate it. Inspect provider settings and affiliate mapping independently. Confirm parser behavior, tracking and fallback handling with the actual adapter; this guide does not define a copy-and-paste production request. Valid path: the intended source reaches the approved feed with required context intact. Empty or slow path: the agreed response and any configured backfill can be explained. Invalid or repeated activity: the selected controls are tested with both legitimate and rejected samples." }, { "id": "resource.xml-feed-monetization.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Read both sides of the reporting relationship", "text": "Begin with the same date range, affiliate, feed and available SubID or domain breakdown. Compare requests, valid requests, errors, coverage, clicks and revenue before looking at imported NET fields. Nexus exposes affiliate-side and feed-side reports and separate provider NET import settings. A difference may reflect timing, attribution, filtering or scope; it is not sufficient evidence of fraud or a billing error." }, { "id": "resource.xml-feed-monetization.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "A useful handover has explicit acceptance checks", "text": "Document who owns each connection, which samples passed, which limits were agreed, the provider update window and the escalation path for a mismatch. Keep pending integrations and unsupported placements visible. Pop, contextual and push delivery require their corresponding provider and delivery setup; enabling XML alone does not enable every advertising format. Bring the first source and demand agreement to discovery so the initial network can be scoped concretely." }, { "id": "resource.xml-feed-monetization.section.6", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Illustrative capacity across two locations", "text": "For one platform with XML at 1,000 incoming QPS in US and 2,000 in EU, with no optional add-ons, capacity costs $1,500 per month. The first full month totals $3,000, including the one-time $1,500 platform setup. This is an illustrative configuration, not a customer result or a traffic guarantee. US: $500/month; maximum 10,000,000 clicks/day. EU: $1,000/month; maximum 20,000,000 clicks/day. These are separate location limits, not a shared 30-million-click pool. RTB, Video, Search and CPA receive no capacity from this XML allocation; each selected module is priced separately. Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised. The example assumes unchanged capacity for a full month. QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge." }, { "id": "resource.xml-feed-monetization.section.7", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-feed-monetization", "topics": [ "resources", "resource.xml-feed-monetization", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML feed monetization: build and validate an ad-network workflow", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "XML location pricing and daily click limits" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Nexus XML feed controls and reporting" }, { "url": "https://www.nexus-soft.org/solutions/xml-ad-network", "title": "XML network scope and prerequisites" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local and partner NET reconciliation" } ], "title": "Worked example: when clicks change the XML allocation", "text": "Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. For a synthetic planning day, assume US peaks at 760 incoming QPS with 11,200,000 clicks, and EU peaks at 1,350 incoming QPS with 8,400,000 clicks. Starting with US 1,000 / EU 2,000 QPS costs $1,500/month, but US exceeds its separate daily click allowance. US 2,000 / EU 2,000 QPS satisfies both planning inputs at $2,000/month. These are independently priced locations on one XML platform, not pooled capacity or measured customer traffic. At the full-month rates, one $1,500 platform setup fee makes the initial first month $3,000 and the revised first month $3,500; no add-ons. Hosting, white-label and taxes are included. The daily click limit currently triggers no automatic action; arrange a capacity increase. Meeting these authored planning inputs is not a throughput, availability or traffic guarantee. Outgoing QPS is not added to the incoming-QPS bill; technical and partner limits still apply." }, { "id": "resource.xml-vs-json-feeds.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-vs-json-feeds", "topics": [ "resources", "resource.xml-vs-json-feeds", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML vs JSON advertising feeds", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/integrations", "title": "Nexus integration contracts and partner compatibility checks" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Provider configuration and affiliate feed mapping" }, { "url": "https://www.w3.org/TR/xml/", "title": "W3C XML 1.0: document syntax, not an advertising feed schema" }, { "url": "https://www.rfc-editor.org/info/rfc8259/", "title": "IETF RFC 8259: JSON data interchange format" } ], "title": "XML vs JSON advertising feeds", "text": "XML and JSON can carry equivalent business information, but their schemas, parsing behavior and partner conventions differ. The platform should isolate those differences from downstream commercial logic." }, { "id": "resource.xml-vs-json-feeds.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-vs-json-feeds", "topics": [ "resources", "resource.xml-vs-json-feeds", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML vs JSON advertising feeds", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/integrations", "title": "Nexus integration contracts and partner compatibility checks" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Provider configuration and affiliate feed mapping" }, { "url": "https://www.w3.org/TR/xml/", "title": "W3C XML 1.0: document syntax, not an advertising feed schema" }, { "url": "https://www.rfc-editor.org/info/rfc8259/", "title": "IETF RFC 8259: JSON data interchange format" } ], "title": "XML feeds", "text": "XML remains common in search and affiliate advertising because it supports established schemas and broad partner compatibility. It can also introduce inconsistent nesting and field conventions. Established partner contracts Explicit document structure Schema variation" }, { "id": "resource.xml-vs-json-feeds.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-vs-json-feeds", "topics": [ "resources", "resource.xml-vs-json-feeds", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML vs JSON advertising feeds", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/integrations", "title": "Nexus integration contracts and partner compatibility checks" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Provider configuration and affiliate feed mapping" }, { "url": "https://www.w3.org/TR/xml/", "title": "W3C XML 1.0: document syntax, not an advertising feed schema" }, { "url": "https://www.rfc-editor.org/info/rfc8259/", "title": "IETF RFC 8259: JSON data interchange format" } ], "title": "JSON feeds", "text": "JSON is compact and natural for API-oriented services, but a JSON response is not automatically standardized. Field names and commercial semantics still require a contract." }, { "id": "resource.xml-vs-json-feeds.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/xml-vs-json-feeds", "topics": [ "resources", "resource.xml-vs-json-feeds", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "XML vs JSON advertising feeds", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/integrations", "title": "Nexus integration contracts and partner compatibility checks" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Provider configuration and affiliate feed mapping" }, { "url": "https://www.w3.org/TR/xml/", "title": "W3C XML 1.0: document syntax, not an advertising feed schema" }, { "url": "https://www.rfc-editor.org/info/rfc8259/", "title": "IETF RFC 8259: JSON data interchange format" } ], "title": "Normalization as the boundary", "text": "Nexus exposes provider feed configuration and affiliate-to-feed mappings. Schema conversion, parser behavior and response compatibility must be confirmed for each partner integration; they should not be inferred from the presence of an XML or JSON URL." }, { "id": "resource.affiliate-subid-tracking.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/affiliate-subid-tracking", "topics": [ "resources", "resource.affiliate-subid-tracking", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Affiliate sub-ID tracking and partner-level traffic analysis", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher account and source-management context" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML integration settings and SubID reporting controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Compare source dimensions using consistent reporting definitions" } ], "title": "Affiliate sub-ID tracking and partner-level traffic analysis", "text": "A single affiliate or member may aggregate many traffic sources. Without a sub-ID contract, poor and strong sources collapse into the same reporting row." }, { "id": "resource.affiliate-subid-tracking.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/affiliate-subid-tracking", "topics": [ "resources", "resource.affiliate-subid-tracking", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Affiliate sub-ID tracking and partner-level traffic analysis", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher account and source-management context" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML integration settings and SubID reporting controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Compare source dimensions using consistent reporting definitions" } ], "title": "Preserve source context", "text": "Nexus can require or preserve sub-ID context in XML request configuration. Naming and allowed values should be agreed with the partner before launch. Source Placement Campaign reference Partner-defined segment" }, { "id": "resource.affiliate-subid-tracking.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/affiliate-subid-tracking", "topics": [ "resources", "resource.affiliate-subid-tracking", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Affiliate sub-ID tracking and partner-level traffic analysis", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher account and source-management context" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML integration settings and SubID reporting controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Compare source dimensions using consistent reporting definitions" } ], "title": "Apply policy at the correct level", "text": "Member limits protect the account boundary while sub-ID reporting helps operators investigate quality and performance beneath it." }, { "id": "resource.affiliate-subid-tracking.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/affiliate-subid-tracking", "topics": [ "resources", "resource.affiliate-subid-tracking", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Affiliate sub-ID tracking and partner-level traffic analysis", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher account and source-management context" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML integration settings and SubID reporting controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Compare source dimensions using consistent reporting definitions" } ], "title": "Avoid identity ambiguity", "text": "Sub-IDs should not be treated as authenticated identity. They are request context and must be validated and interpreted within the partner contract." }, { "id": "resource.duplicate-request-protection.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/duplicate-request-protection", "topics": [ "resources", "resource.duplicate-request-protection", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Duplicate request protection for feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus repetition, source and traffic-control scope" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Feed click, request and expiry configuration" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Distinguish request rate from volume caps" } ], "title": "Duplicate request protection for feed traffic", "text": "Duplicate traffic can consume QPS, create repeated results and make partner reconciliation difficult. The correct response depends on request identity and the commercial agreement." }, { "id": "resource.duplicate-request-protection.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/duplicate-request-protection", "topics": [ "resources", "resource.duplicate-request-protection", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Duplicate request protection for feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus repetition, source and traffic-control scope" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Feed click, request and expiry configuration" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Distinguish request rate from volume caps" } ], "title": "Define a duplicate", "text": "A duplicate rule needs a time window and a stable request signature. Overly broad matching can suppress legitimate repeat intent; overly narrow matching protects nothing. Source context Query or intent IP and user agent Time window" }, { "id": "resource.duplicate-request-protection.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/duplicate-request-protection", "topics": [ "resources", "resource.duplicate-request-protection", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Duplicate request protection for feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus repetition, source and traffic-control scope" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Feed click, request and expiry configuration" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Distinguish request rate from volume caps" } ], "title": "Layer the controls", "text": "Global duplicate policy can be combined with IP request ceilings, member QPS and maximum-request boundaries." }, { "id": "resource.duplicate-request-protection.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/duplicate-request-protection", "topics": [ "resources", "resource.duplicate-request-protection", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Duplicate request protection for feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus repetition, source and traffic-control scope" }, { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "Feed click, request and expiry configuration" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Distinguish request rate from volume caps" } ], "title": "Keep the outcome explainable", "text": "Operators need to distinguish filtered duplicates from upstream errors, empty demand and capacity rejection." }, { "id": "resource.vast-video-advertising.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-video-advertising", "topics": [ "resources", "resource.vast-video-advertising", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is VAST video advertising?", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video controls and delivery boundaries" }, { "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "title": "Wrapper diagnosis and document-versus-playback scope" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: inline ads, wrappers, media and tracking" } ], "title": "What is VAST video advertising?", "text": "VAST is a contract between an ad-serving response and a video player. It describes creatives, tracking and additional demand hops, but it does not guarantee successful playback." }, { "id": "resource.vast-video-advertising.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-video-advertising", "topics": [ "resources", "resource.vast-video-advertising", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is VAST video advertising?", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video controls and delivery boundaries" }, { "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "title": "Wrapper diagnosis and document-versus-playback scope" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: inline ads, wrappers, media and tracking" } ], "title": "VAST response", "text": "A response may contain an inline creative or a wrapper that points to another VAST document. Each hop adds dependencies, tracking and potential latency. Inline creative Wrapper URI Media files Tracking events" }, { "id": "resource.vast-video-advertising.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-video-advertising", "topics": [ "resources", "resource.vast-video-advertising", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is VAST video advertising?", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video controls and delivery boundaries" }, { "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "title": "Wrapper diagnosis and document-versus-playback scope" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: inline ads, wrappers, media and tracking" } ], "title": "Delivery environments", "text": "Web, mobile applications and connected TV devices have different player capabilities and inventory context. Environment policy should be explicit." }, { "id": "resource.vast-video-advertising.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-video-advertising", "topics": [ "resources", "resource.vast-video-advertising", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "What is VAST video advertising?", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video controls and delivery boundaries" }, { "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "title": "Wrapper diagnosis and document-versus-playback scope" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: inline ads, wrappers, media and tracking" } ], "title": "Nexus operating model", "text": "Nexus connects VAST service endpoints, tenant modules, delivery diagnostics and commercial visibility inside the same control plane." }, { "id": "resource.vast-wrapper-diagnostics.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "topics": [ "resources", "resource.vast-wrapper-diagnostics", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "VAST wrapper diagnostics and timeout analysis", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video delivery and reporting boundaries" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Test Links scope and optional add-ons" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: wrapper references and error categories" } ], "title": "VAST wrapper diagnostics and timeout analysis", "text": "A video opportunity can fail at any demand hop, during media selection or inside the player. A useful diagnostic path preserves enough context to locate that boundary." }, { "id": "resource.vast-wrapper-diagnostics.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "topics": [ "resources", "resource.vast-wrapper-diagnostics", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "VAST wrapper diagnostics and timeout analysis", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video delivery and reporting boundaries" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Test Links scope and optional add-ons" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: wrapper references and error categories" } ], "title": "Follow the wrapper chain", "text": "Operators should see the sequence of wrapper URLs, response status and time spent at each hop. Wrapper depth Endpoint response Elapsed time Final creative" }, { "id": "resource.vast-wrapper-diagnostics.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "topics": [ "resources", "resource.vast-wrapper-diagnostics", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "VAST wrapper diagnostics and timeout analysis", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video delivery and reporting boundaries" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Test Links scope and optional add-ons" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: wrapper references and error categories" } ], "title": "Classify errors", "text": "Transport failures, malformed VAST, unsupported media and player errors are different problems and should not share one generic failure label." }, { "id": "resource.vast-wrapper-diagnostics.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "topics": [ "resources", "resource.vast-wrapper-diagnostics", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "VAST wrapper diagnostics and timeout analysis", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video delivery and reporting boundaries" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Test Links scope and optional add-ons" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: wrapper references and error categories" } ], "title": "Protect the playback window", "text": "Timeouts must reflect the user experience and the remaining delivery budget, not only the preference of an upstream demand partner." }, { "id": "resource.vast-wrapper-diagnostics.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/vast-wrapper-diagnostics", "topics": [ "resources", "resource.vast-wrapper-diagnostics", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "VAST wrapper diagnostics and timeout analysis", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video/core-features", "title": "Nexus Video delivery and reporting boundaries" }, { "url": "https://www.nexus-soft.org/products/video/price-plans", "title": "Test Links scope and optional add-ons" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: wrapper references and error categories" } ], "title": "Worked example: isolate wrapper document latency", "text": "Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. This synthetic manual worksheet follows three fictional VAST documents at example.com: start.xml, partner.xml and creative.xml. Authored sequential fetch durations of 90, 140 and 220 ms add to 450 ms. Against an illustrative 1,000 ms document-resolution budget, that leaves 550 ms before parsing, media download and player work. A slow variant changes the last fetch to 820 ms: total 1,050 ms, 50 ms above the same assumed budget. These are not measured requests, live VAST endpoints or a Nexus latency promise. A VAST wrapper is not an HTTP redirect. Test Links exposes HTTP redirect chains, final URL, timing and screenshots; this worksheet does not establish VAST parsing or successful playback. The example.com addresses are inert labels, not links to execute. The 1,000 ms budget is an explicit educational assumption, not a product default, SLA or recommendation for every player." }, { "id": "resource.web-app-ctv-video.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/web-app-ctv-video", "topics": [ "resources", "resource.web-app-ctv-video", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Web, app and CTV video inventory: operational differences", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video", "title": "Nexus video environments and integration scope" }, { "url": "https://www.nexus-soft.org/solutions/video-ad-network", "title": "Video network requirements and partner dependencies" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: player support and media-file requirements" } ], "title": "Web, app and CTV video inventory: operational differences", "text": "A single VAST workflow can serve multiple environments, but a production platform should not pretend their device, identity and playback behavior is identical." }, { "id": "resource.web-app-ctv-video.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/web-app-ctv-video", "topics": [ "resources", "resource.web-app-ctv-video", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Web, app and CTV video inventory: operational differences", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video", "title": "Nexus video environments and integration scope" }, { "url": "https://www.nexus-soft.org/solutions/video-ad-network", "title": "Video network requirements and partner dependencies" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: player support and media-file requirements" } ], "title": "Web video", "text": "Browser and page context are available, but autoplay policy, iframe placement and browser support can affect playback. Browser context Page placement Autoplay policy" }, { "id": "resource.web-app-ctv-video.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/web-app-ctv-video", "topics": [ "resources", "resource.web-app-ctv-video", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Web, app and CTV video inventory: operational differences", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video", "title": "Nexus video environments and integration scope" }, { "url": "https://www.nexus-soft.org/solutions/video-ad-network", "title": "Video network requirements and partner dependencies" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: player support and media-file requirements" } ], "title": "Mobile application video", "text": "App inventory depends on SDK or player integration and application/device context that differs from browser requests." }, { "id": "resource.web-app-ctv-video.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/web-app-ctv-video", "topics": [ "resources", "resource.web-app-ctv-video", "cluster.video" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Web, app and CTV video inventory: operational differences", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/video", "title": "Nexus video environments and integration scope" }, { "url": "https://www.nexus-soft.org/solutions/video-ad-network", "title": "Video network requirements and partner dependencies" }, { "url": "https://iabtechlab.com/wp-content/uploads/2022/09/VAST_4.3.pdf", "title": "IAB Tech Lab VAST 4.3: player support and media-file requirements" } ], "title": "Connected TV", "text": "CTV has long-form viewing contexts, device fragmentation and strict media compatibility needs. Environment-aware policy prevents inappropriate demand paths." }, { "id": "resource.mcp-for-adtech.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "MCP for AdTech: making advertising infrastructure understandable to AI", "text": "Model Context Protocol (MCP) connects AI applications to server capabilities. Nexus public MCP helps clients find product facts and plan deployments; it does not connect advertiser accounts, reveal live reports or authorize campaign changes." }, { "id": "resource.mcp-for-adtech.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Choose the right connection", "text": "Use https://www.nexus-soft.org/mcp for read-only public product discovery over Streamable HTTP. Private operational connections have separate authorization; their tools depend on the server, modules and identity. Website registration does not grant administrator rights or platform assignments. Public discovery: products, pricing scope, formats and integration requirements. Private operations: verify server, identity, platform scope and permitted action. Never send passwords, tokens, personal endpoints or customer exports to public discovery." }, { "id": "resource.mcp-for-adtech.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Understand tools, resources and prompts", "text": "MCP distinguishes callable tools, readable resources and reusable prompt templates. Nexus offers get_product_capabilities and paginated get_public_knowledge search, plus nexus://products/catalog and nexus://knowledge/public resources. The solution-discovery prompt helps plan a deployment; it does not create infrastructure. Use advertised input schemas rather than guessing dashboard fields." }, { "id": "resource.mcp-for-adtech.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Initialize, discover, then request information", "text": "Start with initialize to negotiate version and capabilities, then notifications/initialized. Discover capabilities through tools/list, resources/list and prompts/list. The specifications below explain this sequence. A referenced version is not a claim that every optional MCP feature is implemented by Nexus or supported by every client. Confirm client transport support and use the canonical HTTPS endpoint. Inspect capabilities and schemas before calling tools. Handle protocol and tool errors; a failed call proves no capability." }, { "id": "resource.mcp-for-adtech.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Illustrative discovery: planning an XML network", "text": "With publisher traffic and advertiser agreements in place, inspect get_product_capabilities for feeds. Use get_public_knowledge to find XML mapping, limits and reporting guidance, then compare sources and scope before requesting a deployment recommendation. This is a planning example, not a recorded customer session or provider test. Ask which XML controls exist and what the provider must confirm. Expect sourced capabilities and outstanding integration questions. Do not expect a created feed, changed budget or private report." }, { "id": "resource.mcp-for-adtech.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Treat operational access as a separate decision", "text": "For an operational connection, discover its own tools and permissions. Before sensitive changes, inspect targets and proposed values and obtain the required approval. Descriptions and read-only hints are not authorization controls. Public Nexus tools expose no arbitrary database queries, Redis access or code execution." }, { "id": "resource.mcp-for-adtech.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Keep the answer connected to evidence", "text": "Nexus public facts come from the website’s product, service and resource content, with source pages and scope boundaries. Separate educational examples from verified controls and deployment commitments. MCP does not eliminate model mistakes, prove partner compatibility or promise autonomous optimization. Ask Nexus to validate undocumented requirements." }, { "id": "resource.mcp-for-adtech.section.6", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Free external MCP versus in-platform AI", "text": "Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization." }, { "id": "resource.mcp-for-adtech.section.7", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Additional Fraud Filters", "text": "$100 per month per platform, with one free month from activation. Additional traffic-quality checks beyond the standard platform filters: datacenters, known attack sources, Tor, VPN, crawlers and fake crawlers, web scrapers and proxies. These checks do not guarantee detection of all invalid traffic. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "resource.mcp-for-adtech.section.8", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "Test links", "text": "$100 per month per platform, with one free month from activation. Inspect the final URL, redirect chain, redirect timing and screenshot for a test link. Select the referrer, country, device profile and browser engine for the test. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "resource.mcp-for-adtech.section.9", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-for-adtech", "topics": [ "resources", "resource.mcp-for-adtech", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "MCP for AdTech: making advertising infrastructure understandable to AI", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/rtb/price-plans", "title": "Free external MCP and optional in-platform add-ons" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Nexus public discovery and connected operational scope" }, { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus Streamable HTTP connection and discovery steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP and private infrastructure boundary" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/lifecycle", "title": "MCP specification: initialization and capability negotiation" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/server/tools", "title": "MCP specification: tool schemas, errors and security considerations" } ], "title": "In-platform AI", "text": "$500 per month per platform, with one free month from activation. AI inside your Nexus platform, with model usage included in the add-on price. This tariff is for AI inside a customer's platform, not the public product guide on this website. The add-on is billed once per platform, not separately for each module or location. $500 per month; the first month is free from add-on activation." }, { "id": "resource.connect-ai-client-to-nexus.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/connect-ai-client-to-nexus", "topics": [ "resources", "resource.connect-ai-client-to-nexus", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "How an AI client connects to Nexus MCP", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus public MCP connection and initialization steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/tools", "title": "Public tool names, inputs and response scope" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Public discovery and separately authorized operational connections" } ], "title": "How an AI client connects to Nexus MCP", "text": "A compatible client connects to the public MCP endpoint, initializes a protocol session and discovers the tools, resources and prompts advertised by the server." }, { "id": "resource.connect-ai-client-to-nexus.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/connect-ai-client-to-nexus", "topics": [ "resources", "resource.connect-ai-client-to-nexus", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "How an AI client connects to Nexus MCP", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus public MCP connection and initialization steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/tools", "title": "Public tool names, inputs and response scope" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Public discovery and separately authorized operational connections" } ], "title": "Connection endpoint", "text": "The Nexus MCP endpoint is available at /mcp and uses Streamable HTTP. Production clients should use the canonical HTTPS domain. Initialize List capabilities Call approved tool Read structured result" }, { "id": "resource.connect-ai-client-to-nexus.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/connect-ai-client-to-nexus", "topics": [ "resources", "resource.connect-ai-client-to-nexus", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "How an AI client connects to Nexus MCP", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus public MCP connection and initialization steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/tools", "title": "Public tool names, inputs and response scope" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Public discovery and separately authorized operational connections" } ], "title": "Discovery before action", "text": "Clients should inspect tool schemas rather than guessing parameter names or scraping button labels from the website." }, { "id": "resource.connect-ai-client-to-nexus.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/connect-ai-client-to-nexus", "topics": [ "resources", "resource.connect-ai-client-to-nexus", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "How an AI client connects to Nexus MCP", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Nexus public MCP connection and initialization steps" }, { "url": "https://www.nexus-soft.org/docs/mcp/tools", "title": "Public tool names, inputs and response scope" }, { "url": "https://www.nexus-soft.org/ai-mcp", "title": "Public discovery and separately authorized operational connections" } ], "title": "Bounded capability", "text": "Public MCP tools focus on product understanding and solution design. Connected operational deployments expose their own tools behind authentication, domain scope and server-side authorization. Available actions depend on the selected server, enabled capabilities and account permissions." }, { "id": "resource.mcp-security-model.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-security-model", "topics": [ "resources", "resource.mcp-security-model", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Nexus MCP security model", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP security and private-access boundaries" }, { "url": "https://www.nexus-soft.org/security", "title": "Nexus account, tenant and infrastructure controls" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization", "title": "MCP authorization specification; deployment support must be checked separately" } ], "title": "Nexus MCP security model", "text": "AI-native does not mean giving a model unrestricted database or Redis access. It means presenting a deliberate application contract that an AI client can understand." }, { "id": "resource.mcp-security-model.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-security-model", "topics": [ "resources", "resource.mcp-security-model", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Nexus MCP security model", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP security and private-access boundaries" }, { "url": "https://www.nexus-soft.org/security", "title": "Nexus account, tenant and infrastructure controls" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization", "title": "MCP authorization specification; deployment support must be checked separately" } ], "title": "Public knowledge boundary", "text": "Product overview, targeting controls and deployment guidance can be public because the same information is visible in product documentation. Typed inputs Read-oriented outputs No arbitrary database query" }, { "id": "resource.mcp-security-model.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-security-model", "topics": [ "resources", "resource.mcp-security-model", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Nexus MCP security model", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP security and private-access boundaries" }, { "url": "https://www.nexus-soft.org/security", "title": "Nexus account, tenant and infrastructure controls" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization", "title": "MCP authorization specification; deployment support must be checked separately" } ], "title": "Application authorization", "text": "Connected operational deployments apply authenticated roles, tenant boundaries and server-side authorization. Their rate limits, approval requirements and audit capabilities depend on the exposed tool and deployment policy. Public product tools do not grant access to private operations." }, { "id": "resource.mcp-security-model.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mcp-security-model", "topics": [ "resources", "resource.mcp-security-model", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Nexus MCP security model", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Nexus public MCP security and private-access boundaries" }, { "url": "https://www.nexus-soft.org/security", "title": "Nexus account, tenant and infrastructure controls" }, { "url": "https://modelcontextprotocol.io/specification/2025-11-25/basic/authorization", "title": "MCP authorization specification; deployment support must be checked separately" } ], "title": "Infrastructure isolation", "text": "Redis and database credentials remain inside server-side connection managers. Approved Redis access is limited to keys derived from configured services." }, { "id": "resource.ai-ready-adtech-checklist.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ai-ready-adtech-checklist", "topics": [ "resources", "resource.ai-ready-adtech-checklist", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AI-ready AdTech platform checklist", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Discover the configured public MCP capability contract" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Public knowledge versus authenticated operational permissions" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Broader platform acceptance questions" } ], "title": "AI-ready AdTech platform checklist", "text": "A chat interface is not an integration contract. An AI-ready platform needs structured knowledge, discoverable operations, bounded permissions and outputs that operators can verify." }, { "id": "resource.ai-ready-adtech-checklist.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ai-ready-adtech-checklist", "topics": [ "resources", "resource.ai-ready-adtech-checklist", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AI-ready AdTech platform checklist", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Discover the configured public MCP capability contract" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Public knowledge versus authenticated operational permissions" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Broader platform acceptance questions" } ], "title": "Knowledge", "text": "Publish stable product definitions, route-specific documentation, schemas and explicit limitations. Product catalog Glossary API schemas Versioned documentation" }, { "id": "resource.ai-ready-adtech-checklist.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ai-ready-adtech-checklist", "topics": [ "resources", "resource.ai-ready-adtech-checklist", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AI-ready AdTech platform checklist", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Discover the configured public MCP capability contract" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Public knowledge versus authenticated operational permissions" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Broader platform acceptance questions" } ], "title": "Operations", "text": "Expose typed tools with narrow responsibilities instead of generic code or database execution." }, { "id": "resource.ai-ready-adtech-checklist.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ai-ready-adtech-checklist", "topics": [ "resources", "resource.ai-ready-adtech-checklist", "cluster.ai + mcp" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AI-ready AdTech platform checklist", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "title": "Discover the configured public MCP capability contract" }, { "url": "https://www.nexus-soft.org/docs/mcp/security", "title": "Public knowledge versus authenticated operational permissions" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Broader platform acceptance questions" } ], "title": "Governance", "text": "Apply authentication, tenant authorization, rate limits, auditability and human approval to sensitive write operations." }, { "id": "resource.build-vs-buy-adtech.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Build vs buy an AdTech platform", "text": "Start with the operating decision you need to own: accepting a publisher, routing a request, enforcing a commercial limit or reconciling a partner report. Compare ways to deliver that same workflow using the same traffic assumptions. A feature list or monthly software price alone cannot describe the engineering, partner and support work required to operate it." }, { "id": "resource.build-vs-buy-adtech.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Build internally", "text": "Building can fit when the workflow itself is a competitive advantage and your team can own its maintenance. Estimate the work after the first successful request: partner adapters, access control, reporting definitions, incident response, upgrades and operator tools. Name the people who will maintain each part when a partner changes its response or a key engineer is unavailable. Internal ownership gives design freedom; it does not remove delivery or operational dependencies. What behavior must be unique, and what can follow an existing contract? Who owns protocol changes, security fixes and production support? Which acceptance checks demonstrate the complete workflow, including failure paths?" }, { "id": "resource.build-vs-buy-adtech.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Buy disconnected tools", "text": "A specialist tool can fit a clearly bounded requirement. Check the interfaces between tools as carefully as their individual features: which system owns publisher identity, caps, accepted events and final statements? Ask for sample exports and error cases before committing. A lower subscription may still leave your team maintaining adapters and investigating differences between reports. Compare replacement and exit effort as well as initial connection work. List the source of truth for accounts, configuration and financial records. Confirm export formats, retention and access to records after the contract ends. Assign responsibility when two connected systems disagree." }, { "id": "resource.build-vs-buy-adtech.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Build on Nexus", "text": "Nexus provides Search, XML/JSON feeds, OpenRTB, Video and CPA modules with shared operating controls. Evaluate the module that fits the first workflow, then identify the integrations and custom work needed around it. A compatible protocol does not supply demand contracts or guarantee every partner adapter. Use the deployment and product pages to distinguish available controls from items that need agreement, implementation or an acceptance test." }, { "id": "resource.build-vs-buy-adtech.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Compare costs over one agreed planning period", "text": "Use the same period and workload for each option. Record initial implementation and migration, recurring platform charges, your own engineering and operations time, separately contracted partner services, and eventual transition costs. Keep one-time and recurring amounts separate. For Nexus, use the current pricing calculator: capacity is scoped by module and, for incoming QPS, by location. Published hosting, white-label and applicable taxes are already included; do not add them again. Custom work or an SLA requires an explicit agreement. Initial work: requirements, adapters, configuration, test cases, migration and training. Recurring work: the quoted platform scope, internal staffing and any separately required third-party services. Change and exit: future integrations, data exports, contractual notice and migration responsibilities. Use your own amounts and assumptions; this worksheet does not predict savings or return on investment." }, { "id": "resource.build-vs-buy-adtech.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/build-vs-buy-adtech", "topics": [ "resources", "resource.build-vs-buy-adtech", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Build vs buy an AdTech platform", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus deployment models, phases and scope boundaries" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Current shared capacity calculator and commercial inclusions" }, { "url": "https://www.nexus-soft.org/services/custom-development", "title": "Separately scoped custom development and acceptance" }, { "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "title": "Product, integration and operating checks" } ], "title": "Turn the comparison into a pilot decision", "text": "For an illustrative evaluation, choose one approved publisher source and one compatible demand route. Document an accepted request, an ineligible request, an empty response and a timeout, then identify the report that explains each result. Agree on who can configure the route and who can stop the test. Score each option against these same requirements, marking untested items as open. Expand only after the responsible teams accept the evidence; no fixed launch date or production performance follows from this example. Record the required outcome, its evidence, its owner and any unresolved dependency. Carry the selected module, capacity assumptions and integration list into the pricing enquiry." }, { "id": "resource.white-label-adtech-platform.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "White-label AdTech platform architecture", "text": "A white-label platform needs a clear agreement about what your customers see and what your team operates. Start with the audience, the revenue workflow and the branded surfaces they will use. Domain names and a logo are one part of the brief; partner access, traffic contracts, reporting and support responsibilities determine whether the service is ready for use." }, { "id": "resource.white-label-adtech-platform.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "Tenant identity", "text": "Nexus platform configuration includes a domain, description, status and public URLs. Prepare a branding inventory for the agreed deployment: public site, member or partner workspace, authentication pages, notifications and any documents or reports customers receive. Confirm each surface in the proposal and preview it before launch. White-label branding is included in the published platform tariff; a requested workflow or interface extension may require separately agreed development. Supply approved names, logos, domain ownership and the intended audience for each surface. Assign responsibility for DNS, certificates, email sender configuration and renewal. Confirm which templates and interfaces are included, and which require additional work." }, { "id": "resource.white-label-adtech-platform.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "Module composition", "text": "Choose modules by the transaction you need to operate. Search handles search-provider and publisher-link workflows; XML/JSON feeds handle feed and affiliate mappings; OpenRTB handles programmatic request paths; Video uses VAST delivery contracts; CPA handles offers and conversion-related workflows. Define the publisher and advertiser experience separately. A branded platform does not automatically include every ad format, buying strategy, payment integration or demand relationship. Map each promised customer workflow to a module and a confirmed integration. Keep incoming QPS capacity separate for each applicable module and location. For Search and CPA, use the published daily search or incoming-click capacity units." }, { "id": "resource.white-label-adtech-platform.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "Private infrastructure", "text": "Nexus keeps database, Redis and private-service configuration behind authenticated server workflows. A brand or domain is not an authorization boundary by itself. Establish the accounts and roles required for your deployment, confirm which platform each account can access, and test that another platform or an unauthorized role cannot read its records. Agree on credential ownership, operational access and recovery responsibilities without exposing secrets in the branding brief." }, { "id": "resource.white-label-adtech-platform.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "Agree on commercial and support ownership", "text": "State who approves publishers, contracts with demand partners, investigates traffic-quality disputes and reconciles local and partner reports. Define support contacts, escalation, maintenance communication and any required service commitment in the agreement. The published price includes hosting, white-label branding and applicable taxes, but it is not a universal SLA or a promise of traffic, revenue or access to a named advertising partner. Identify the owner of customer terms, privacy information and operational support. Specify report definitions, currencies, timezones and partner update delays. Confirm export, retention and transition requirements before onboarding customers." }, { "id": "resource.white-label-adtech-platform.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/white-label-adtech-platform", "topics": [ "resources", "resource.white-label-adtech-platform", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "White-label AdTech platform architecture", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/white-label", "title": "Nexus branded-platform scope and operator responsibilities" }, { "url": "https://www.nexus-soft.org/products", "title": "The five Nexus modules and their operating workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Included branding, hosting and pricing scope" }, { "url": "https://www.nexus-soft.org/security", "title": "Authenticated access and private infrastructure boundaries" }, { "url": "https://www.nexus-soft.org/deployment", "title": "Deployment design, validation and operational handover" } ], "title": "Accept the complete branded journey", "text": "Use an illustrative test account with prepared data to follow the agreed journey from entry and sign-in to its assigned workflow, report and support path. Check the correct identity on each surface and exercise denied access as well as a successful operation. Validate actual request and response behavior with the configured partner. Record outstanding items before launch; a preview or screenshot demonstrates a visible interface, not traffic delivery or financial performance. Verify domain, certificate, links, approved branding and the configured notification path. Confirm account scope, permitted actions and the explanation of report values. Record acceptance evidence, unresolved integrations and the owner of the launch decision." }, { "id": "resource.adtech-platform-evaluation-checklist.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "AdTech platform evaluation checklist", "text": "A strong evaluation follows a request from source to commercial outcome. Feature counts alone do not reveal hidden integration work or operational boundaries." }, { "id": "resource.adtech-platform-evaluation-checklist.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Traffic and products", "text": "List active channels, request formats, partner volumes, QPS, caps and expected expansion. Search Feeds OpenRTB Video CPA" }, { "id": "resource.adtech-platform-evaluation-checklist.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Controls and evidence", "text": "Identify which system owns targeting, filters, routes, commercial terms and the reporting used for reconciliation." }, { "id": "resource.adtech-platform-evaluation-checklist.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Security and deployment", "text": "Confirm tenant isolation, credential boundaries, roles, audit events, production validation and failure behavior." }, { "id": "resource.adtech-platform-evaluation-checklist.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Choose the module from the operating workflow", "text": "Choose Search for query/feed and publisher-link operations; XML for publisher-to-feed mapping and feed controls; OpenRTB for supply/demand bid routing; Video for VAST delivery; and CPA for offers, incoming clicks, postbacks and conversions. A response encoded as XML or JSON does not by itself determine which product you need. Validate the actual partner workflow. XML / JSON feeds: $500/month per 1,000 incoming QPS in each location. OpenRTB: $500/month per 1,000 incoming QPS in each location. VAST Video: $500/month per 1,000 incoming QPS in each location. Search Syndication: $500/month per 100,000 searches per day. CPA / CPI / CPL: $500/month per 100,000 incoming clicks per day." }, { "id": "resource.adtech-platform-evaluation-checklist.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Compare a complete platform quote", "text": "State the module, each QPS location, the required daily volume and the optional add-ons. Compare the same incoming-only measurement and period across quotes. Do not assume a competitor uses a particular charging rule without checking its terms. You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform. Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator. Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "resource.adtech-platform-evaluation-checklist.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist", "topics": [ "resources", "resource.adtech-platform-evaluation-checklist", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "AdTech platform evaluation checklist", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products", "title": "Nexus revenue-engine workflows" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Multi-module pricing calculator and platform scope" }, { "url": "https://www.nexus-soft.org/products/search/price-plans", "title": "Search daily search capacity" }, { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "CPA daily incoming click capacity" } ], "title": "Changing capacity during the month", "text": "QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge. Confirm the effective date of a capacity change when comparing a partial-month invoice with a full-month estimate." }, { "id": "resource.legacy-adtech-migration.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Migrating from fragmented or legacy AdTech services", "text": "Define the first traffic path to move and the evidence that will show it works. A migration must preserve more than a reachable endpoint: partner identities, request fields, accepted events, reporting periods and operating responsibilities all need an agreed destination. This guide is a planning framework; migration scope, tools, downtime and recovery depend on the actual systems and partner contracts." }, { "id": "resource.legacy-adtech-migration.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Inventory the current path", "text": "Trace one source through its endpoint, parser, routing rules, delivery or tracking events and reports. List dependent databases, caches, scheduled imports and external callbacks, with a responsible owner for each. Record identifiers, field types, timezones, currencies and retention needs. Keep credentials in their approved secret store; an inventory should reference their owner and purpose rather than copy their values into a shared document. Traffic contracts: required fields, accepted sources, timeouts, limits and response semantics. Data contracts: account and partner mappings, historical records, exports and reporting definitions. Operations: service URLs, DNS ownership, dependencies, maintenance contacts and change windows." }, { "id": "resource.legacy-adtech-migration.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Choose the first boundary", "text": "Select a source or channel whose eligibility, volume and commercial responsibility can be bounded. Identify how traffic will reach the destination and how it can return to the previous path. Confirm provider approval and compatibility before moving requests. A Nexus module does not imply a ready-made importer for an arbitrary legacy database; field mapping, adapters and historical-data migration require explicit scope and validation. Name the traffic cohort, destination, partner approvals and cutover owner. Mark dependencies that must move together and those that can remain temporarily. Agree on a stop condition and the person authorized to act on it." }, { "id": "resource.legacy-adtech-migration.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Validate before expansion", "text": "Rehearse with synthetic or appropriately redacted samples. Cover valid and invalid requests, absent demand, timeouts, repeated tracking events and permission failures. Compare reports for the same cohort, period and definitions; local counts and partner NET imports may update at different times. Do not duplicate live auctions, clicks or billable events merely to compare systems. Any replay or parallel observation needs an agreed method that avoids double delivery and accounting. Document the expected outcome and evidence for each test case. Reconcile missing, duplicated and late events before accepting the sample. Treat interface availability and successful HTTP responses as partial checks, not complete delivery evidence." }, { "id": "resource.legacy-adtech-migration.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Cut over with a bounded observation window", "text": "Where the routing and partner setup allow it, begin with a limited traffic cohort and observe it before increasing exposure. Agree on the measurements and tolerances in advance: request errors, timeouts, accepted outcomes and reporting discrepancies for that cohort. Google’s SRE canary guidance explains this general release technique; it is not evidence that Nexus supplies automatic traffic splitting or rollback for your deployment. If traffic cannot be divided safely, agree on a maintenance window and a different acceptance plan. Capture the active configuration and approved destination before the switch. Keep the earlier path available for the agreed recovery window when technically feasible. Compare like-for-like traffic and account for partner reporting delay before increasing exposure." }, { "id": "resource.legacy-adtech-migration.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Plan rollback separately from data recovery", "text": "Write down the exact trigger, decision owner and steps to restore the previous traffic route. Also determine what happens to records created after cutover: changing routing alone does not undo new conversions, payments, configuration changes or data transformations. Test backup restoration and any reconciliation procedure before depending on them. Agree on acceptable data loss and recovery time for this migration; this guide provides no default guarantee of zero downtime or reversible database changes. Check that the previous service still accepts the required contracts and configuration. Decide whether writes must pause and how new, pending and late records will be reconciled. Keep recovery artifacts protected and record the outcome of the rehearsal." }, { "id": "resource.legacy-adtech-migration.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/legacy-adtech-migration", "topics": [ "resources", "resource.legacy-adtech-migration", "cluster.platform strategy" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Migrating from fragmented or legacy AdTech services", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/deployment", "title": "Nexus discovery, integration, validation and launch responsibilities" }, { "url": "https://www.nexus-soft.org/services/server-management", "title": "Scoped migration, backup and recovery services" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Partner contracts, data boundaries and failure handling" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Local, partner and delivery reconciliation definitions" }, { "url": "https://sre.google/workbook/canarying-releases/", "title": "Google SRE: canary evaluation principles, not a Nexus feature guarantee" } ], "title": "Close the handover before retiring the old path", "text": "For an illustrative XML migration, the handover might name one publisher source, its approved demand feed, the retained SubID convention and the reports used to compare accepted clicks. Add the actual observation period, discrepancies and sign-off owners when evidence exists. Retire the earlier endpoint only after callbacks, partner imports, access, retention and recovery needs have been resolved. These are planning steps, not a recorded customer migration or an included fixed-price service. Confirm operational contacts, monitoring ownership and the escalation procedure. Preserve required historical records and remove obsolete access through the agreed process. Bring the dependency inventory and acceptance criteria to a scoped deployment or migration enquiry." }, { "id": "resource.ppc-search-syndication-platform.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Search Syndication: feeds, publishers and commercial control", "text": "Search syndication connects a publisher’s search experience to approved advertising demand. The useful starting point is one query from one source: identify the publisher link, the eligible provider feed, the request context and the reports that will explain the result. Nexus supplies operating software; provider access, traffic approval and commercial agreements remain separate requirements." }, { "id": "resource.ppc-search-syndication-platform.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Connect supply to multiple demand feeds", "text": "Keep provider feeds and publisher links as distinct records. The provider feed holds the advertiser, search engine, feed URL, search cap, revenue share and NET reporting settings. The publisher link selects feeds and holds its own integration type, cap, backfill and commercial settings. Before connecting either, confirm the provider’s actual request and response contract and the traffic approved for it. Affiliate and direct-publisher access XML and JSON provider contracts Feed assignment and eligibility Provider-specific integration validation" }, { "id": "resource.ppc-search-syndication-platform.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Define publisher-link eligibility", "text": "Use the Search link Targets tab to choose which sub-IDs, domains and keywords are eligible for that link. Feed-level keyword replacement and provider settings are separate controls. Check country, browser/version and device requirements in the relevant editor rather than assuming link and feed fields are interchangeable. The adjacent configuration guide explains the relationship; it does not apply or recommend traffic settings." }, { "id": "resource.ppc-search-syndication-platform.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Illustrative trace: preserve the original source", "text": "Imagine a fictional publisher, Cedar, sending the query hiking boots from its mobile-search source. In a planning record, keep the publisher link, SubID, original query, selected provider and any configured keyword transformation together. Confirm which URL macros the provider supports and test the transmitted values. These labels are explanatory; they are not a live request, a Nexus parameter schema or permission to send traffic to a search provider. Original intent: hiking boots from Cedar / mobile-search. Eligibility check: the configured link, domain, keyword and device rules. Demand check: the assigned provider and its accepted traffic contract. Outcome check: response, local searches/clicks and later partner-reported figures." }, { "id": "resource.ppc-search-syndication-platform.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Make commercial policy explicit", "text": "Search feed and link editors expose revenue-share and search-cap settings. A publisher-link cap and a provider-feed cap protect different relationships; document which resource owns each value. XML feeds have separate minimum-bid, QPS, click and budget controls. Do not copy an XML limit checklist onto Search or interpret a configured traffic limit as a plan entitlement. Agree on the meaning and reset behavior of each cap during validation." }, { "id": "resource.ppc-search-syndication-platform.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Diagnose an empty result in a useful order", "text": "Start with the selected link and source context, then inspect feed assignment, targeting, traffic-quality rules, caps and provider availability. Distinguish an intentionally ineligible query from an integration error or an eligible query with no demand. Test the configured backfill path independently. Increasing a cap cannot fix a malformed provider request, and changing keyword rules without preserving the original query can make later investigation harder. Check one known eligible sample and one intentionally ineligible sample. Exercise an empty response and a provider failure with agreed expected outcomes. Record the relevant settings and report filters so another operator can repeat the investigation." }, { "id": "resource.ppc-search-syndication-platform.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Reconcile technical and commercial evidence", "text": "Review the same date range, publisher/link and feed before comparing searches, monetized activity, clicks, revenue and partner NET results. Use Keyword List or Keyword Count and available domain/device breakdowns to localize a difference. NET import timing and metric definitions depend on the provider. A local search, a monetized result and a paid click are different observations; confirm the denominator of EPC, RPM and coverage with the report definition before presenting them as a business result." }, { "id": "resource.ppc-search-syndication-platform.section.6", "kind": "resource", "url": "https://www.nexus-soft.org/resources/ppc-search-syndication-platform", "topics": [ "resources", "resource.ppc-search-syndication-platform", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Search Syndication: feeds, publishers and commercial control", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search", "title": "Nexus Search feed and publisher-link capabilities" }, { "url": "https://www.nexus-soft.org/solutions/search-advertising-network", "title": "Search network requirements" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Reporting definitions and update boundaries" } ], "title": "Scope the first launch around evidence", "text": "Bring one approved provider, one publisher traffic pattern, the supported query/tracking contract and a target reporting question to the evaluation. Agree on integration tests, commercial ownership and the handover process before expansion. The goal of the first walkthrough is to show that the team can explain a traffic path and its outcome, not to infer guaranteed demand or revenue from a configured feed." }, { "id": "resource.click-fraud-filters-adtech.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/click-fraud-filters-adtech", "topics": [ "resources", "resource.click-fraud-filters-adtech", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Click fraud filters for PPC and feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus traffic-quality signals and enforcement scope" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Standard controls and the optional Additional Fraud Filters add-on" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Investigate source discrepancies without inferring fraud from totals alone" } ], "title": "Click fraud filters for PPC and feed traffic", "text": "Traffic protection is most useful when every rule has a known input, scope and outcome. A generic fraud score cannot replace the operational controls needed to investigate a publisher, feed or source." }, { "id": "resource.click-fraud-filters-adtech.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/click-fraud-filters-adtech", "topics": [ "resources", "resource.click-fraud-filters-adtech", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Click fraud filters for PPC and feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus traffic-quality signals and enforcement scope" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Standard controls and the optional Additional Fraud Filters add-on" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Investigate source discrepancies without inferring fraud from totals alone" } ], "title": "Layer deterministic controls", "text": "IP and subnet policy, banned-domain checks, referrer validation, iframe rules and request-rate boundaries provide explainable first-line protection. They can be applied globally or, where the connected engine supports it, scoped to a particular feed. IP and subnet policy Domain and referrer checks Iframe and environment rules QPS, caps and duplicate controls" }, { "id": "resource.click-fraud-filters-adtech.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/click-fraud-filters-adtech", "topics": [ "resources", "resource.click-fraud-filters-adtech", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Click fraud filters for PPC and feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus traffic-quality signals and enforcement scope" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Standard controls and the optional Additional Fraud Filters add-on" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Investigate source discrepancies without inferring fraud from totals alone" } ], "title": "Add behavioral and network signals", "text": "Bot confidence, anonymous or transparent proxy indicators, unexpected IP changes and source inconsistencies can contribute additional evidence. Detection strength should be tuned against false positives rather than treated as a universal maximum setting." }, { "id": "resource.click-fraud-filters-adtech.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/click-fraud-filters-adtech", "topics": [ "resources", "resource.click-fraud-filters-adtech", "cluster.traffic controls" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Click fraud filters for PPC and feed traffic", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/targeting-and-controls", "title": "Nexus traffic-quality signals and enforcement scope" }, { "url": "https://www.nexus-soft.org/products/feeds/price-plans", "title": "Standard controls and the optional Additional Fraud Filters add-on" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Investigate source discrepancies without inferring fraud from totals alone" } ], "title": "Preserve an operator decision path", "text": "Trusted-partner exceptions, blocked-traffic outcomes and human-verification steps need an audit trail. Operators should be able to explain whether traffic was rejected by identity, environment, repetition, capacity or quality policy." }, { "id": "resource.feed-bid-limit-management.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/feed-bid-limit-management", "topics": [ "resources", "resource.feed-bid-limit-management", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Feed, bid and limit management for search advertising", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed bid, request, budget and click-limit controls" }, { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Separate Search provider and publisher-link settings" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Capacity units and independently scoped limits" } ], "title": "Feed, bid and limit management for search advertising", "text": "Demand feeds do not have identical schemas, response times, commercial terms or traffic acceptance. Treating them as interchangeable endpoints hides the decisions that determine margin and delivery quality." }, { "id": "resource.feed-bid-limit-management.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/feed-bid-limit-management", "topics": [ "resources", "resource.feed-bid-limit-management", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Feed, bid and limit management for search advertising", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed bid, request, budget and click-limit controls" }, { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Separate Search provider and publisher-link settings" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Capacity units and independently scoped limits" } ], "title": "Configure the feed contract", "text": "Each connection needs an understood parser, timeout, result limit, eligible targets and commercial behavior. Reusable feed profiles help teams apply a tested operating pattern across approved partners. Parser and schema Timeout boundary Result limit Allowed targets" }, { "id": "resource.feed-bid-limit-management.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/feed-bid-limit-management", "topics": [ "resources", "resource.feed-bid-limit-management", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Feed, bid and limit management for search advertising", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed bid, request, budget and click-limit controls" }, { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Separate Search provider and publisher-link settings" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Capacity units and independently scoped limits" } ], "title": "Define eligible feed traffic", "text": "Use the XML feed Targets tab for geographic, device, browser, domain, carrier, keyword and subscriber-age criteria. Match the enabled criteria to the request context and traffic contract supported by that provider." }, { "id": "resource.feed-bid-limit-management.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/feed-bid-limit-management", "topics": [ "resources", "resource.feed-bid-limit-management", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Feed, bid and limit management for search advertising", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed bid, request, budget and click-limit controls" }, { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Separate Search provider and publisher-link settings" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Capacity units and independently scoped limits" } ], "title": "Control bids and volume at the right level", "text": "Platform ceilings protect infrastructure, feed limits protect provider contracts and publisher ranges protect commercial relationships. Individual exceptions should be deliberate, bounded and visible to the team responsible for reconciliation." }, { "id": "resource.feed-bid-limit-management.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/feed-bid-limit-management", "topics": [ "resources", "resource.feed-bid-limit-management", "cluster.feeds" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Feed, bid and limit management for search advertising", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/feeds/core-features", "title": "XML feed bid, request, budget and click-limit controls" }, { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Separate Search provider and publisher-link settings" }, { "url": "https://www.nexus-soft.org/resources/qps-governance", "title": "Capacity units and independently scoped limits" } ], "title": "Route in parallel without losing governance", "text": "Parallel provider requests can improve coverage, but only when they remain inside latency, QPS and eligibility boundaries. The response path still needs deterministic ranking, deduplication, error classification and reporting." }, { "id": "resource.publisher-member-management-adtech.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/publisher-member-management-adtech", "topics": [ "resources", "resource.publisher-member-management-adtech", "cluster.partner operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Publisher and affiliate management for AdTech platforms", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher onboarding, accounts and operating permissions" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Publisher-to-feed relationships and reporting" }, { "url": "https://www.nexus-soft.org/security", "title": "Role, access and protected-data boundaries" } ], "title": "Publisher and affiliate management for AdTech platforms", "text": "A partner portal is not only a registration screen. It is the boundary where identity, traffic permissions, feed access, commercial terms and operational support meet." }, { "id": "resource.publisher-member-management-adtech.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/publisher-member-management-adtech", "topics": [ "resources", "resource.publisher-member-management-adtech", "cluster.partner operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Publisher and affiliate management for AdTech platforms", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher onboarding, accounts and operating permissions" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Publisher-to-feed relationships and reporting" }, { "url": "https://www.nexus-soft.org/security", "title": "Role, access and protected-data boundaries" } ], "title": "Approve access deliberately", "text": "Applications can be reviewed before activation, assigned an account level and connected only to the traffic types and feed profiles appropriate to the agreement. Signup date, source IP and account context provide useful review evidence. Approval and rejection Account levels Traffic-type permissions Feed profiles" }, { "id": "resource.publisher-member-management-adtech.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/publisher-member-management-adtech", "topics": [ "resources", "resource.publisher-member-management-adtech", "cluster.partner operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Publisher and affiliate management for AdTech platforms", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher onboarding, accounts and operating permissions" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Publisher-to-feed relationships and reporting" }, { "url": "https://www.nexus-soft.org/security", "title": "Role, access and protected-data boundaries" } ], "title": "Respond without destroying history", "text": "Suspension should stop or restrict traffic while preserving the account, configuration and evidence required to resolve a problem. Search by identity, level or active feed helps operators find the relevant relationship quickly." }, { "id": "resource.publisher-member-management-adtech.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/publisher-member-management-adtech", "topics": [ "resources", "resource.publisher-member-management-adtech", "cluster.partner operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Publisher and affiliate management for AdTech platforms", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher onboarding, accounts and operating permissions" }, { "url": "https://www.nexus-soft.org/products/feeds", "title": "Publisher-to-feed relationships and reporting" }, { "url": "https://www.nexus-soft.org/security", "title": "Role, access and protected-data boundaries" } ], "title": "Separate payout workflow from delivery", "text": "Balances, payout requests, processing periods, minimum thresholds and fees belong to a controlled financial workflow. Exact payment methods and legal requirements depend on the deployment and commercial agreement." }, { "id": "resource.direct-advertiser-campaign-management.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Direct advertiser campaign management inside an AdTech platform", "text": "Direct campaigns connect an advertiser, budget, audience and creatives to agreed inventory. Nexus provides campaign and creative editors; delivery depends on the channel and integration. Configure the workflow, then validate its outcomes." }, { "id": "resource.direct-advertiser-campaign-management.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Set the commercial and scheduling boundaries", "text": "The reviewed editor exposes a CPV bid, daily and total budgets, frequency capping, a conversion-tracking switch and scheduling. Inventory includes all-campaign and pending-approval views. Fields and billing models are workflow-specific, not universal across Search, Video, RTB and CPA. Name the advertiser, permitted users and approval owner. Set commercial limits and the delivery window. Define the tracking objective and accepted event." }, { "id": "resource.direct-advertiser-campaign-management.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Target with supported request evidence", "text": "Target geography, operating systems, browsers and versions. Available source allowlists and blocklists cover IP ranges, domains, publisher IDs, SubIDs, keywords and feeds. Check that the integration supplies the required context and how missing fields are handled. Targeting does not replace publisher approval of creatives or traffic." }, { "id": "resource.direct-advertiser-campaign-management.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Prepare the creative and its measurement path", "text": "Creative records identify advertiser, campaign, type, status and dimensions. The editor separates basic details, tracking and media: width, height, click URL, impression pixel and asset. Match the format and supply requirements. A tracking URL or conversion switch is configuration evidence, not proof of delivered, attributed or accepted events." }, { "id": "resource.direct-advertiser-campaign-management.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Illustrative acceptance check: one campaign, one source", "text": "For fictional Spring Demo, agree on one source, creative, target country and bounded test allocation. Exercise eligible, excluded-source and out-of-schedule requests against the delivery and reporting path. This is a test plan, not a Nexus API request, a customer result or a budget-enforcement guarantee under concurrent traffic. Eligible: verify creative, destination and recorded events. Excluded or out of schedule: check rule enforcement. Budget or frequency boundary: agree on counting and timing, then test. Missing event: investigate integration and reporting before changing commercial records." }, { "id": "resource.direct-advertiser-campaign-management.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Campaign management is not the whole DSP", "text": "DSP Deployment is an integration-scoped combination of campaigns and the RTB runtime. Validate supply access, creative acceptance, advertiser experience, automated bidding, attribution and billing separately; an editor provides no universal exchange access. CPA offers are also a distinct workflow with conversion windows, payout models, caps and publisher permissions." }, { "id": "resource.direct-advertiser-campaign-management.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/direct-advertiser-campaign-management", "topics": [ "resources", "resource.direct-advertiser-campaign-management", "cluster.campaign operations" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Direct advertiser campaign management inside an AdTech platform", "lastModified": "2026-09-09", "sourceReferences": [ { "url": "https://www.nexus-soft.org/campaign-management", "title": "Nexus campaign budgets, targeting, creatives and tracking fields" }, { "url": "https://www.nexus-soft.org/solutions/white-label-dsp", "title": "DSP deployment components and integration requirements" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Separate CPA offer, conversion-window and payout controls" }, { "url": "https://www.nexus-soft.org/reporting", "title": "Nexus local and partner reporting definitions" } ], "title": "Hand over an observable workflow", "text": "Keep configuration, approved creatives and test results together. Compare channel reports using the same period, advertiser and campaign; distinguish local activity from partner results and their update timing. Assign creative review, event investigation and spend reconciliation. Use the Nexus demo to confirm modules and outstanding integration work." }, { "id": "resource.contextual-ads-domain-parking.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/contextual-ads-domain-parking", "topics": [ "resources", "resource.contextual-ads-domain-parking", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Contextual advertising and domain parking operations", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Search context, provider routing and reporting controls" }, { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher sources, account approval and configured access" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Validate contextual and domain integrations with the actual provider" } ], "title": "Contextual advertising and domain parking operations", "text": "Contextual and domain traffic both begin with page or domain context rather than a conventional search box. Sustainable monetization requires explicit ownership of the source, extracted intent and final demand route." }, { "id": "resource.contextual-ads-domain-parking.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/contextual-ads-domain-parking", "topics": [ "resources", "resource.contextual-ads-domain-parking", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Contextual advertising and domain parking operations", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Search context, provider routing and reporting controls" }, { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher sources, account approval and configured access" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Validate contextual and domain integrations with the actual provider" } ], "title": "Operate contextual publisher inventory", "text": "Publishers register approved sites and placements, while operators moderate eligibility and define how keywords are selected. Page metadata, site-specific terms, categories and defaults can contribute context when the integration supports them. Site approval Placement or banner configuration Keyword and category policy Feed eligibility" }, { "id": "resource.contextual-ads-domain-parking.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/contextual-ads-domain-parking", "topics": [ "resources", "resource.contextual-ads-domain-parking", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Contextual advertising and domain parking operations", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Search context, provider routing and reporting controls" }, { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher sources, account approval and configured access" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Validate contextual and domain integrations with the actual provider" } ], "title": "Manage parked domains as inventory", "text": "A parking workflow connects approved domains through nameserver or redirect patterns to controlled landing templates. Domain ownership, template selection, keywords and categories should remain visible to both support and commercial teams." }, { "id": "resource.contextual-ads-domain-parking.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/contextual-ads-domain-parking", "topics": [ "resources", "resource.contextual-ads-domain-parking", "cluster.search advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Contextual advertising and domain parking operations", "lastModified": "2026-09-14", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/search/core-features", "title": "Search context, provider routing and reporting controls" }, { "url": "https://www.nexus-soft.org/publisher-platform", "title": "Publisher sources, account approval and configured access" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Validate contextual and domain integrations with the actual provider" } ], "title": "Keep intent and delivery explainable", "text": "Extracted keywords are inputs, not guaranteed user intent. Reporting should distinguish the source domain or site, applied context, selected feed and delivered result so quality issues can be investigated rather than averaged away." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.overview", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Mobile performance platform for CPA, CPI and CPL campaigns", "text": "A performance offer needs an agreed outcome before it needs traffic. An installation, registration, approved lead and purchase are different events with different acceptance rules. Nexus exposes offer configuration, conversion windows, approval controls, caps and reporting; the actual tracking and postback contract must be validated with the partners involved." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.0", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Support outcome-based price models", "text": "Define the accepted event, the evidence required to accept it and when it becomes payable. Nexus offer settings include fixed-price or revenue-share terms, currency, advertiser and publisher payouts, event category and conversion-window controls. An event received from an advertiser is not automatically a settled publisher payment. Agree on pending, rejected and repeated-event handling before a source is approved. Offer identity, tracking destination and accepted event. Conversion window and pending/multiple-conversion policy. Advertiser payout, publisher payout, currency and reconciliation responsibility." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.1", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Apply offer and partner boundaries", "text": "Publisher access, traffic eligibility and caps are separate controls. Nexus exposes private offers, approval and terms requirements alongside geographic, device, carrier, SubID, domain and IP-range targeting. Daily and monthly limits can apply to clicks, conversions and revenue. A publisher who can see an offer is not thereby eligible for every traffic source, and an available cap does not override an offer’s conversion rules." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.2", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Illustrative postback: follow one event", "text": "In a fictional test, click demo-click-17 belongs to offer sample-install and publisher Cedar. The advertiser later reports event demo-event-42 as an installation. The integration test should verify the click-to-offer relationship, the agreed event, the conversion window and the resulting report state. These labels are illustrative records, not Nexus field names, endpoint parameters or a production API example. Use the actual partner contract to construct a request. Known click + accepted event + valid timing → check the configured acceptance or pending outcome. Unknown click or wrong offer → check the agreed rejection or investigation path. Same event delivered again → verify the agreed repeat-event behavior before counting it twice." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.3", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Test retries and conversion windows independently", "text": "A repeated delivery of one event is different from a second legitimate event on the same click. Document the event identifier, allowed event types and the intended multiple-conversion policy. Exercise an on-time event, an event outside the window, a delayed retry and a temporary endpoint failure. Authentication, acknowledgement, retry limits and duplicate handling are integration requirements to verify, not guarantees inferred from the presence of a postback URL." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.4", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Check the cap boundary before launch", "text": "For an illustrative test allocation of ten accepted events per day, prepare cases just below, at and above the agreed boundary. Confirm which status counts toward the cap, the timezone used for the reset and what happens to a late event or concurrent arrival. Ten is a fictional test value, not a recommended offer setting or included Nexus quota. Validate the implemented behavior with the configured offer and partner before routing production traffic." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.5", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Reconcile conversions with the commercial record", "text": "Use the same offer, publisher, period, currency and acceptance status on both sides. Nexus reports include valid/invalid conversions, advertiser and publisher payouts, profit and source details. Investigate a missing event by its click and event context before changing a payout. A useful handover records the sample cases, their expected outcomes, the reporting window and who resolves disagreements. No example in this guide is a customer result or an attribution guarantee." }, { "id": "resource.mobile-performance-platform-cpa-cpi-cpl.section.6", "kind": "resource", "url": "https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl", "topics": [ "resources", "resource.mobile-performance-platform-cpa-cpi-cpl", "cluster.performance advertising" ], "boundary": "Educational guide, not proof that every described capability is implemented or enabled in every Nexus deployment. Confirm the relevant product and integration scope.", "sourceTitle": "Mobile performance platform for CPA, CPI and CPL campaigns", "lastModified": "2026-09-10", "sourceReferences": [ { "url": "https://www.nexus-soft.org/products/cpa/price-plans", "title": "Monthly charges for daily incoming click capacity" }, { "url": "https://www.nexus-soft.org/products/cpa", "title": "Nexus offer, conversion-window, cap and payout controls" }, { "url": "https://www.nexus-soft.org/solutions/affiliate-tracking-platform", "title": "Tracking deployment requirements" }, { "url": "https://www.nexus-soft.org/integrations", "title": "Postback and integration contract checklist" } ], "title": "Platform capacity is not the offer payout", "text": "An illustrative CPA configuration with 200,000 incoming clicks per day costs $1,000 per month, or $2,500 for the first full month including platform setup, with no optional add-ons. This is not a price per day, per conversion or a publisher payout. It is not a customer result or a promise of conversions. Purchased daily incoming-click capacity and an offer’s conversion cap are different limits. The ten-event example above explains an offer workflow, not the purchased platform capacity. Search uses daily searches, not CPA clicks. Do not convert either daily volume into a QPS entitlement. Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "page.docs.overview", "kind": "guide", "url": "https://www.nexus-soft.org/docs", "topics": [ "documentation" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus technical documentation", "title": "Nexus technical documentation", "text": "Entry points for product, API, MCP, security and integration documentation." }, { "id": "page.docs.section.0", "kind": "guide", "url": "https://www.nexus-soft.org/docs", "topics": [ "documentation" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus technical documentation", "title": "Product documentation", "text": "Explore the public product catalog, targeting controls and deployment models. /products /targeting-and-controls /deployment" }, { "id": "page.docs.section.1", "kind": "guide", "url": "https://www.nexus-soft.org/docs", "topics": [ "documentation" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus technical documentation", "title": "Developer interfaces", "text": "Use machine-readable contracts and protocol documentation to understand public Nexus interfaces. /openapi.json /docs/mcp/quickstart /docs/mcp/tools /docs/mcp/resources /api/catalog" }, { "id": "page.docs.section.2", "kind": "guide", "url": "https://www.nexus-soft.org/docs", "topics": [ "documentation" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus technical documentation", "title": "Trust documentation", "text": "Review implemented security boundaries and responsible disclosure guidance. /security /.well-known/security.txt /legal/privacy" }, { "id": "page.docs.mcp.quickstart.overview", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP quickstart", "title": "Nexus MCP quickstart", "text": "Connect a compatible AI client to the Nexus Streamable HTTP MCP server." }, { "id": "page.docs.mcp.quickstart.section.0", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP quickstart", "title": "Endpoint", "text": "Use the canonical HTTPS `/mcp` URL. Initialize the MCP session, then ask the server to list its tools, resources and prompts. POST /mcp Content-Type: application/json Protocol negotiation" }, { "id": "page.docs.mcp.quickstart.section.1", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP quickstart", "title": "Discovery", "text": "Call `tools/list`, `resources/list` and `prompts/list` before using capabilities. Tool input schemas are the source of truth. get_nexus_overview get_product_capabilities get_ad_format_guide get_targeting_controls get_operating_capabilities recommend_deployment get_security_model get_public_knowledge" }, { "id": "page.docs.mcp.quickstart.section.2", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP quickstart", "title": "Safety", "text": "Public tools are read-oriented product discovery functions. They do not provide arbitrary database, Redis or code execution. Bounded inputs Structured outputs Server-side credentials" }, { "id": "page.docs.mcp.quickstart.section.3", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/quickstart", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP quickstart", "title": "Reference guides", "text": "Review the public tool reference and the resources and prompts guide before building a client workflow. Discover the current interfaces from the server at runtime. /docs/mcp/tools /docs/mcp/resources" }, { "id": "page.docs.mcp.tools.overview", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "Nexus MCP tools", "text": "Typed product, advertising-format, targeting, operating-capability and deployment operations exposed by the public Nexus MCP server." }, { "id": "page.docs.mcp.tools.section.0", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_nexus_overview", "text": "Returns the Nexus operating model, AdTech engineering context, revenue engines and AI-native platform overview." }, { "id": "page.docs.mcp.tools.section.1", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_product_capabilities", "text": "Accepts one of search, feeds, rtb, video or cpa and returns the relevant capability description." }, { "id": "page.docs.mcp.tools.section.2", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_ad_format_guide", "text": "Returns a structured guide to a selected ad format: definition, placements, buying models, targeting, metrics, delivery flow and deployment fit." }, { "id": "page.docs.mcp.tools.section.3", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_targeting_controls", "text": "Explains request context, quality filters, capacity, commercial policy and routing controls." }, { "id": "page.docs.mcp.tools.section.4", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_operating_capabilities", "text": "Returns structured knowledge about traffic quality, feed and bid management, partner operations, advertiser workflows, contextual and domain monetization, and custom engineering." }, { "id": "page.docs.mcp.tools.section.5", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "recommend_deployment", "text": "Accepts business model, channel selection and white-label preference to create a bounded initial deployment recommendation." }, { "id": "page.docs.mcp.tools.section.6", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_security_model", "text": "Describes Nexus authentication, authorization, data boundaries and remote infrastructure policy. It accepts no input fields and returns public security information, not access to a private deployment." }, { "id": "page.docs.mcp.tools.section.7", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/tools", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP tools", "title": "get_public_knowledge", "text": "Finds public product, pricing, service and deployment facts with exact source URLs and scope boundaries. Query is optional; omit it to browse with kind or topic filters and offset/limit pagination. It does not return private account data or perform operational actions." }, { "id": "page.docs.mcp.resources.overview", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/resources", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP resources and prompts", "title": "Nexus MCP resources and prompts", "text": "Stable knowledge and guided solution discovery for compatible AI clients." }, { "id": "page.docs.mcp.resources.section.0", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/resources", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP resources and prompts", "title": "Product catalog resource", "text": "`nexus://products/catalog` exposes five Nexus revenue engines, thirteen format and traffic-model guides, seven platform deployment recipes and operating knowledge for compatible AI clients." }, { "id": "page.docs.mcp.resources.section.1", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/resources", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP resources and prompts", "title": "Solution-discovery prompt", "text": "The prompt helps an AI client identify relevant products, formats, integrations, security boundaries and phased deployment without inventing customer metrics." }, { "id": "page.docs.mcp.resources.section.2", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/resources", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP resources and prompts", "title": "Version expectations", "text": "Clients should discover capabilities at runtime and avoid assuming that every future server version exposes the same tool list." }, { "id": "page.docs.mcp.resources.section.3", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/resources", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "Nexus MCP resources and prompts", "title": "Sourced public knowledge resource", "text": "`nexus://knowledge/public` returns the public fact corpus used by the website assistant as application/json, including product, pricing, service and deployment facts with source URLs and scope boundaries. Read it with resources/read; it does not expose private account or platform data." }, { "id": "page.docs.mcp.security.overview", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/security", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "MCP security and governance", "title": "MCP security and governance", "text": "Understand the boundary between public AI discovery and private Nexus infrastructure." }, { "id": "page.docs.mcp.security.section.0", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/security", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "MCP security and governance", "title": "Public discovery", "text": "Product descriptions and deployment guidance are intentionally public and match visible website content." }, { "id": "page.docs.mcp.security.section.1", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/security", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "MCP security and governance", "title": "Privileged operations", "text": "Any future write operation should require authenticated tenant context, authorization, rate limiting, audit records and appropriate human approval." }, { "id": "page.docs.mcp.security.section.2", "kind": "guide", "url": "https://www.nexus-soft.org/docs/mcp/security", "topics": [ "documentation", "mcp" ], "boundary": "Public documentation describes bounded discovery interfaces, not permission to access a private deployment.", "sourceTitle": "MCP security and governance", "title": "Infrastructure", "text": "Database and Redis credentials remain in backend connection managers. Public AI clients do not receive them." }, { "id": "page.services.custom-adtech-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "Custom AdTech software development", "text": "Extend Nexus or build a specialized advertising workflow with a team experienced in traffic platforms, partner integrations and high-volume web systems." }, { "id": "page.services.custom-adtech-development.section.0", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "When standard software is not enough", "text": "Advertising businesses often have distinctive supply contracts, commercial logic, reporting and infrastructure. Nexus Soft can define a bounded custom scope around those requirements instead of forcing them into a generic workflow." }, { "id": "page.services.custom-adtech-development.section.1", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "From requirements to production", "text": "The engagement begins with traffic paths, roles, data contracts, operating scenarios and acceptance criteria. Architecture, implementation, integration testing, system validation and production handover follow from that shared definition." }, { "id": "page.services.custom-adtech-development.section.2", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "AdTech integration depth", "text": "Custom work can cover XML and JSON feeds, partner APIs, OpenRTB services, VAST delivery, postbacks, dashboards, admin workflows, data services and infrastructure automation. Exact scope and supported protocols are confirmed during solution design." }, { "id": "page.services.custom-adtech-development.section.3", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "Flexible delivery model", "text": "A defined feature can be delivered as a scoped project, while evolving platforms may use a dedicated or mixed product-engineering model. Timeline, ownership, maintenance and support boundaries are documented before work begins." }, { "id": "page.services.custom-adtech-development.section.4", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "AI-native extension", "text": "New product knowledge and approved operations can also be exposed through Nexus MCP tools and resources, giving compatible AI clients a typed interface rather than requiring them to scrape a dashboard." }, { "id": "page.services.adtech-infrastructure-management.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "AdTech infrastructure management", "text": "Operational support for the servers, data services, security boundaries and delivery paths behind high-volume advertising systems." }, { "id": "page.services.adtech-infrastructure-management.section.0", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Reliability starts below the dashboard", "text": "Traffic routing depends on web services, databases, caches, DNS, load balancing, network policy and recoverable data. Nexus treats those dependencies as part of the operating system, not invisible hosting details." }, { "id": "page.services.adtech-infrastructure-management.section.1", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Proactive operations", "text": "Monitoring, performance tuning, security maintenance, backup design and recovery planning reduce avoidable failures. Production commitments and escalation procedures are defined for the actual deployment rather than implied by a generic website claim." }, { "id": "page.services.adtech-infrastructure-management.section.2", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Migration and scale", "text": "Infrastructure work can include new service setup, database or cache configuration, load-balancing patterns, hosting migration and troubleshooting across Linux or Windows environments." }, { "id": "page.services.adtech-infrastructure-management.section.3", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Protected configuration", "text": "Service credentials remain server-side. Platform administrators work through authenticated, bounded configuration workflows while public website and MCP discovery interfaces remain separated from private infrastructure." }, { "id": "standard.openrtb.overview", "kind": "policy", "url": "https://www.nexus-soft.org/technology", "topics": [ "standards", "product.rtb" ], "boundary": "Protocols 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.", "title": "IAB Tech Lab: OpenRTB", "text": "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." }, { "id": "standard.vast.overview", "kind": "policy", "url": "https://www.nexus-soft.org/technology", "topics": [ "standards", "product.video" ], "boundary": "Protocols 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.", "title": "IAB Tech Lab: VAST", "text": "Video ad serving. Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module." }, { "id": "white-label.capability.0", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your brand & domains", "text": "Present the platform under your own identity, with agreed branding and domain configuration. Your customers work with your business, not a generic shared marketplace." }, { "id": "white-label.capability.1", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your partner relationships", "text": "Organize supply, demand and operator access around the way your network works. Keep each account within its assigned platform scope." }, { "id": "white-label.capability.2", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your commercial rules", "text": "Configure supported bids, margins, caps and routing policies for each channel. Keep the delivery decisions connected to your business model." }, { "id": "white-label.capability.3", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your connected stack", "text": "Integrate feeds, OpenRTB, VAST, postbacks and APIs where supported. Add custom development when the standard workflow needs to go further." }, { "id": "white-label.capability.4", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your infrastructure model", "text": "Plan domains, services, data stores, monitoring and support responsibilities together. Choose the deployment scope before committing to a rollout." }, { "id": "white-label.capability.5", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label", "solutions", "products" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Your AI workflows", "text": "Full MCP support gives compatible AI clients a structured interface to Nexus. Connected operations retain identity, domain scope, permissions and audit history." }, { "id": "home.question.0", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "What is Nexus?", "text": "Nexus is configurable advertising technology for teams operating search, feeds, programmatic, video and performance businesses. It combines channel-specific services with platform configuration, partner access and operational administration. The deployment is assembled around your traffic, integrations and workflows." }, { "id": "home.question.1", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "Do I need all five products?", "text": "No. Start with the channel that fits your business: Search, XML / JSON feeds, OpenRTB, VAST video or CPA. Additional modules can be introduced as part of an agreed integration and rollout plan." }, { "id": "home.question.2", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "Can we use our own brand, domains and infrastructure?", "text": "Nexus supports white-label and tenant-aware configuration, including domains, service endpoints and platform-specific data sources. During discovery we agree which components Nexus operates, which remain in your environment and how they connect." }, { "id": "home.question.3", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "What does full MCP support mean in practice?", "text": "Nexus provides tools, resources and prompts over Model Context Protocol for compatible AI clients. Public discovery is read-only. Connected operational deployments add authenticated, domain-scoped administration, session and question history, tool diagnostics and policy-controlled workflows. Available actions depend on the connected MCP server and the identity’s permissions." }, { "id": "home.question.4", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "How is access to different platforms controlled?", "text": "Accounts receive explicit roles and platform assignments. Administrators manage platform configuration and MCP connections in a separate workspace. Protected operations are checked server-side; a shared domain or a copied URL does not grant access." }, { "id": "home.question.5", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "What should I bring to a demo?", "text": "Tell us which channels you operate, your current supply and demand integrations, approximate volume, required regions and the operational problem you want to solve. We can then walk through a relevant workflow and define scope, validation and commercial terms." }, { "id": "mcp.capability.0", "kind": "policy", "url": "https://www.nexus-soft.org/ai-mcp", "topics": [ "mcp" ], "boundary": "Public discovery is read-only. Authenticated operational actions depend on the connected MCP server and the identity’s permissions.", "title": "Multiple servers, one workspace", "text": "Register separate MCP deployments and select the server and domain before reviewing its operational context. Keep production and test environments distinct." }, { "id": "mcp.capability.1", "kind": "policy", "url": "https://www.nexus-soft.org/ai-mcp", "topics": [ "mcp" ], "boundary": "Public discovery is read-only. Authenticated operational actions depend on the connected MCP server and the identity’s permissions.", "title": "Questions, tools and diagnostics", "text": "Review session activity, question history, tool outcomes and latency. Inspect the evidence behind an interaction instead of relying on the final chat answer alone." }, { "id": "mcp.capability.2", "kind": "policy", "url": "https://www.nexus-soft.org/ai-mcp", "topics": [ "mcp" ], "boundary": "Public discovery is read-only. Authenticated operational actions depend on the connected MCP server and the identity’s permissions.", "title": "Governed actions and automation", "text": "Use the connected server’s approval, automation and audit capabilities. An AI request never replaces the server’s access checks or the deployment’s operating policy." }, { "id": "mcp.capability.3", "kind": "policy", "url": "https://www.nexus-soft.org/ai-mcp", "topics": [ "mcp" ], "boundary": "Public discovery is read-only. Authenticated operational actions depend on the connected MCP server and the identity’s permissions.", "title": "Learning with a review trail", "text": "Inspect learning proposals, supporting evidence and review outcomes where the remote server exposes them. Keep changes to operational guidance visible to administrators." }, { "id": "deployment.model.0", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Managed launch", "text": "A guided path for teams moving from fragmented workflows into their first connected Nexus revenue engine. Discovery and traffic mapping Partner and service integration Validation before production traffic Operational handover" }, { "id": "deployment.model.1", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Dedicated platform", "text": "A Nexus environment aligned to your domains, modules, connections and commercial operating model. Tenant-aware configuration Dedicated service connections Role-based workspaces Controlled infrastructure access" }, { "id": "deployment.model.2", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "White-label foundation", "text": "A branded product layer for AdTech businesses that need to serve their own operators, partners or customers. Custom product identity Tenant domains and modules Governed administration Composable revenue engines" }, { "id": "deployment.phase.01", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Discover", "text": "Map traffic sources, destinations, partner contracts, current services and the decisions that affect revenue." }, { "id": "deployment.phase.02", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Design", "text": "Define the tenant model, integration boundaries, channel modules, access roles and rollout milestones." }, { "id": "deployment.phase.03", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Connect", "text": "Configure approved APIs, feeds, data stores and delivery services through bounded server-side contracts." }, { "id": "deployment.phase.04", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Validate", "text": "Exercise routing, access, measurement and failure paths before moving agreed production traffic." }, { "id": "deployment.phase.05", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Operate", "text": "Give each team the correct workspace, visibility and escalation path for day-to-day decisions." }, { "id": "deployment.phase.06", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Expand", "text": "Add revenue engines, partners and automation without rebuilding the platform foundation." }, { "id": "policy.standards", "kind": "policy", "url": "https://www.nexus-soft.org/technology", "topics": [ "standards" ], "boundary": "Protocols 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.", "title": "Standards and interoperability", "text": "Protocols 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." }, { "id": "policy.overview", "kind": "policy", "url": "https://www.nexus-soft.org/", "topics": [ "overview" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "What is Nexus?", "text": "Nexus is configurable advertising technology for teams operating search, feeds, programmatic, video and performance businesses. It combines channel-specific services with platform configuration, partner access and operational administration. The deployment is assembled around your traffic, integrations and workflows." }, { "id": "policy.modules", "kind": "policy", "url": "https://www.nexus-soft.org/products", "topics": [ "overview", "products" ], "boundary": "The deployment is assembled around your traffic, integrations and workflows.", "title": "Do I need all five products?", "text": "No. Start with the channel that fits your business: Search, XML / JSON feeds, OpenRTB, VAST video or CPA. Additional modules can be introduced as part of an agreed integration and rollout plan." }, { "id": "policy.white-label", "kind": "policy", "url": "https://www.nexus-soft.org/white-label", "topics": [ "white-label" ], "boundary": "Agree on the exact branding, integrations and service scope before launch. Additional products, capacity and custom work are scoped separately.", "title": "Can we use our own brand, domains and infrastructure?", "text": "Nexus supports white-label and tenant-aware configuration, including domains, service endpoints and platform-specific data sources. During discovery we agree which components Nexus operates, which remain in your environment and how they connect." }, { "id": "policy.mcp", "kind": "policy", "url": "https://www.nexus-soft.org/ai-mcp", "topics": [ "mcp" ], "boundary": "Public discovery is read-only. Authenticated operational actions depend on the connected MCP server and the identity’s permissions.", "title": "What does full MCP support mean in practice?", "text": "Nexus provides tools, resources and prompts over Model Context Protocol for compatible AI clients. Public discovery is read-only. Connected operational deployments add authenticated, domain-scoped administration, session and question history, tool diagnostics and policy-controlled workflows. Available actions depend on the connected MCP server and the identity’s permissions. The public Streamable HTTP MCP endpoint is /mcp." }, { "id": "policy.accounts", "kind": "policy", "url": "https://www.nexus-soft.org/legal/terms", "topics": [ "accounts" ], "boundary": "Email registration and password recovery depend on configured email delivery. Creating an account does not grant platform access.", "title": "Member registration and administrator access", "text": "Members can register using a confirmed email and password or Google. Creating an account does not grant access to a platform or a paid service: a Nexus administrator assigns platform scope and permissions separately. Administrator access remains restricted to approved Google identities. Google sign-in is subject to Google’s applicable terms and privacy notice. Two-factor authentication is recommended but optional until you activate it. If you enable it, later sign-ins require an authenticator or recovery code. You must protect the authenticator device and recovery codes, must not share one-time codes, and should use a recovery code only when the enrolled authenticator is unavailable. Each recovery code works once." }, { "id": "policy.security", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "security" ], "boundary": "No internet service is risk-free. Public product information is not a certification or service-level commitment.", "title": "Security and data minimisation", "text": "Nexus supports member registration with a verified email and password or Google. Passwords are stored as salted scrypt hashes, never plaintext. Email verification and password reset use expiring, single-use links. Revocable opaque sessions use signed HTTP-only cookies; Google sign-in uses state and PKCE protection. Server-side role and platform assignment checks, credential-version checks, administrator allowlists, bounded inputs, trusted-origin checks, rate limits and security audit records protect access. Registration never grants platform access. No internet service is risk-free." }, { "id": "policy.pricing", "kind": "policy", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Monthly capacity pricing", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." }, { "id": "policy.contact", "kind": "policy", "url": "https://www.nexus-soft.org/contact", "topics": [ "contact" ], "boundary": "No credentials or production export are required. Do not submit secrets or confidential customer data.", "title": "Talk to Nexus", "text": "Use /contact for product questions, pricing, services, privacy or security enquiries. Visitors can use the form or select Show email on that page to reveal the team address. Direct visitors to this contact page rather than guessing or publishing an email address. Book a demo opens /contact?intent=demo; a meeting is arranged by email, not booked automatically. Useful context: channels and partner types in scope; representative request-volume range; current APIs, feeds, data stores or delivery services." }, { "id": "policy.deployment", "kind": "policy", "url": "https://www.nexus-soft.org/deployment", "topics": [ "deployment" ], "boundary": "Exact scope and timing depend on existing systems and partner readiness. These phases define the work without publishing fictional delivery promises.", "title": "Deployment models and production path", "text": "Managed launch; Dedicated platform; White-label foundation. Discover → Design → Connect → Validate → Operate → Expand." }, { "id": "privacy.ai-and-mcp.paragraph.0", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy", "mcp" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "AI assistant and MCP interfaces", "text": "The public MCP server exposes product documentation, structured advertising-format information and deployment guidance. It is not designed to receive personal data and its public tools do not provide arbitrary access to customer databases or credentials." }, { "id": "privacy.ai-and-mcp.paragraph.1", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy", "mcp" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "AI assistant and MCP interfaces", "text": "The website AI assistant selects answers from the Nexus public product knowledge base. Nexus processes the current question and bounded recent messages to identify context. When an OpenAI API connection is configured, we send the current question, inferred product context and candidate public facts to OpenAI to select supporting evidence; we do not send the complete conversation history in that provider request. The request disables response storage, which is not a promise of zero provider-side retention. Without that connection, the guide uses local knowledge selection." }, { "id": "privacy.ai-and-mcp.paragraph.2", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy", "mcp" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "AI assistant and MCP interfaces", "text": "The website application does not save a chat transcript in its database. Conversation state remains in the open page; provider-side security or service retention may apply to external requests. Do not submit personal, confidential, regulated or customer traffic data to the public assistant." }, { "id": "privacy.ai-and-mcp.paragraph.3", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy", "mcp" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "AI assistant and MCP interfaces", "text": "The public guide cannot approve accounts, award a contract, buy media, change a customer platform or make decisions with legal or similarly significant effects about you. Account permissions and platform requests are reviewed by administrators. Authentication and abuse controls may automatically deny a request; contact us if you believe access was blocked in error." }, { "id": "privacy.recipients.paragraph.0", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "Google Workspace is used for business email and the configured transactional SMTP relay. It processes recipient addresses and message content for registration confirmation, password reset and business correspondence. Account passwords are never included in those messages. Software support for an alternative mail provider does not mean your messages are sent to every supported provider." }, { "id": "privacy.recipients.paragraph.1", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "Website enquiries are saved in a protected administrator inbox. When email delivery is configured, the selected mail provider also processes the submitted business brief and your email address to notify the Nexus team inbox. Your email is used as Reply-To so the team can respond. Submitting the form does not automatically send an email to the visitor or book a meeting." }, { "id": "privacy.recipients.paragraph.2", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "Access inside Nexus Soft is limited to people who need the information for sales, support, account administration, security or legal responsibilities. Hosting and database operators process information needed to run the website and private workspaces. Configured monitoring services may receive sanitised technical error and security metadata; the application supports Loki for this purpose. Professional advisers or competent authorities may receive information needed for a specific legal matter. Provider access and processing locations must be covered by the relevant service arrangements." }, { "id": "privacy.recipients.paragraph.3", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "Google receives and returns authentication data when an authorised portal user chooses Google sign-in. OpenAI may process AI chat content only when the external AI connection is configured and you submit a question. We may disclose information where required by law or necessary to protect legal rights and service security." }, { "id": "privacy.recipients.paragraph.4", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "Google processes the limited public website analytics data described above only when Google Analytics 4 is configured and you consent to analytics. That analytics purpose is separate from Google sign-in and account email delivery. We do not send account User-IDs, form content or AI conversations to Google Analytics." }, { "id": "privacy.recipients.paragraph.5", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Recipients and service providers", "text": "We do not sell personal data collected through this corporate website." }, { "id": "privacy.cookies-and-storage.paragraph.0", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Cookies and browser storage", "text": "The site uses strictly necessary authentication cookies when you sign in and local browser storage to remember your privacy choice. Google Analytics 4 is an optional capability of the public website: it runs only when configured and after you give valid, current analytics consent. No Google analytics script or request is loaded before that consent." }, { "id": "privacy.cookies-and-storage.paragraph.1", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Cookies and browser storage", "text": "Analytics is excluded from administrator, member, authentication and API pages and from the administration hostname. Measurement uses canonical public page paths and predefined events, without URL query strings or fragments, form content, AI chat text or account User-IDs. Advertising features and Google Signals are disabled. Marketing tracking is not installed." }, { "id": "privacy.cookies-and-storage.paragraph.2", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Cookies and browser storage", "text": "After analytics consent, we can distinguish a small set of approved, non-personal campaign labels, such as a company email signature or demo follow-up, and an external referring origin without its path or query. This is website acquisition measurement, not email-open tracking, recipient identification or advertising profiling. Unknown campaign values are not forwarded. A short-lived record in the current browser tab helps preserve that source across public-page navigation; details and expiry are in the Cookie notice." }, { "id": "privacy.cookies-and-storage.paragraph.3", "kind": "policy", "url": "https://www.nexus-soft.org/legal/privacy", "topics": [ "privacy" ], "boundary": "This describes public-site processing. Customer deployment terms and configured providers may differ.", "title": "Cookies and browser storage", "text": "Analytics cookies are limited to the public website host, use path /, and expire after no more than 180 days without renewal on each visit. Cookie lifetimes and the privacy preference lifetime are separate from Google Analytics property data-retention settings. Full names, purposes and durations are listed in the Cookie notice." } ] }, "pricing": [ { "id": "pricing.product.feeds.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/feeds/price-plans", "topics": [ "pricing", "product.feeds" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "XML / JSON feeds pricing", "title": "XML / JSON feeds: published capacity price", "text": "XML / JSON feeds costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.product.rtb.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/rtb/price-plans", "topics": [ "pricing", "product.rtb" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "OpenRTB pricing", "title": "OpenRTB: published capacity price", "text": "OpenRTB costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations. Each 1,000 incoming QPS block has a maximum of 10,000,000 clicks per day for this module in this location; 2,000 incoming QPS allows a maximum of 20,000,000 clicks per day. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.product.video.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/video/price-plans", "topics": [ "pricing", "product.video" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "VAST Video pricing", "title": "VAST Video: published capacity price", "text": "VAST Video costs $500 per month for each block of 1,000 incoming QPS, separately for this module in each location. Minimum capacity and increments are 1,000 incoming QPS per location; capacity is not pooled across modules or locations." }, { "id": "pricing.product.search.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "product.search" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "Search Syndication pricing", "title": "Search Syndication: published capacity price", "text": "Search Syndication costs $500 per month for each block of 100,000 searches per day. Minimum capacity and increments are 100,000 daily searches; the price is monthly, not a daily fee." }, { "id": "pricing.product.cpa.rate", "kind": "pricing", "url": "https://www.nexus-soft.org/products/cpa/price-plans", "topics": [ "pricing", "product.cpa" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "sourceTitle": "CPA / CPI / CPL pricing", "title": "CPA / CPI / CPL: published capacity price", "text": "CPA / CPI / CPL costs $500 per month for each block of 100,000 incoming clicks per day. Minimum capacity and increments are 100,000 daily incoming clicks; the price is monthly, not a daily fee or a charge per conversion." }, { "id": "pricing.question.0", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "How is monthly capacity priced?", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." }, { "id": "pricing.question.1", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I share QPS capacity across modules or locations?", "text": "Each selected XML / JSON, OpenRTB or VAST Video module has a minimum of 1,000 incoming QPS in every selected location, increasing in steps of 1,000. Modules and locations are billed separately; their capacity blocks cannot be pooled. Available locations are US, EU, Asia; US is the default for a new configuration. Select each location at most once within a module. Search and CPA each use one daily-capacity selection per platform." }, { "id": "pricing.question.2", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Is outgoing QPS charged?", "text": "For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing." }, { "id": "pricing.question.3", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I increase or decrease QPS during the month?", "text": "QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge." }, { "id": "pricing.question.4", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Can I run more than one platform?", "text": "You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform." }, { "id": "pricing.question.5", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Do the prices include hosting, white-label and taxes?", "text": "Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "pricing.question.6", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Is the setup fee monthly or per module?", "text": "Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator." }, { "id": "pricing.question.7", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Does external MCP integration cost extra?", "text": "Nexus integration through external MCP is free. Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization. External MCP integration is separate from the paid in-platform AI add-on." }, { "id": "pricing.question.8", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "When does the free add-on month start?", "text": "Additional Fraud Filters, Test links and In-platform AI each have a free first month beginning when that add-on is activated, not when an account is registered. Capacity charges and setup are not part of this free trial. After-trial prices show the ongoing rates; this calculator does not activate an add-on, create a checkout or imply automatic charging." }, { "id": "pricing.question.9", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "What if I need an SLA, a discount or an overage agreement?", "text": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order." }, { "id": "pricing.question.10", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Do Basic, Professional and Premium plans still define the prices?", "text": "Published prices now use the capacity blocks above instead of Basic, Professional and Premium plan labels. Choose the actual modules and capacities; those old labels do not define additional numerical allowances." }, { "id": "pricing.question.11", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "How do I calculate the total for one platform?", "text": "Select modules, capacity in each QPS location and optional add-ons in the calculator. It sums the independently priced blocks and charges each add-on once per platform. The ongoing monthly total includes add-ons at their published rates. The first-month estimate excludes their free activation month and adds the one-time platform setup fee. The estimate assumes the selected add-ons are activated together; an enquiry does not create an order or automatic charge." }, { "id": "pricing.question.12", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "What is the daily click limit for XML / JSON feeds and OpenRTB?", "text": "XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.rule.billing", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Monthly capacity pricing", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." }, { "id": "pricing.rule.incoming", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Incoming QPS is the billing basis", "text": "For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing." }, { "id": "pricing.rule.locations", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Each QPS module and location is separate", "text": "Each selected XML / JSON, OpenRTB or VAST Video module has a minimum of 1,000 incoming QPS in every selected location, increasing in steps of 1,000. Modules and locations are billed separately; their capacity blocks cannot be pooled. Available locations are US, EU, Asia; US is the default for a new configuration. Select each location at most once within a module. Search and CPA each use one daily-capacity selection per platform." }, { "id": "pricing.rule.changes", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Change QPS capacity when you need to", "text": "QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge." }, { "id": "pricing.rule.platforms", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Separate platforms are billed separately", "text": "You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform." }, { "id": "pricing.rule.included", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Final prices include hosting and white-label", "text": "Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised." }, { "id": "pricing.rule.setup", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "One-time platform setup", "text": "Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator." }, { "id": "pricing.rule.mcp", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Free Nexus MCP integration", "text": "Nexus integration through external MCP is free. Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization. External MCP integration is separate from the paid in-platform AI add-on." }, { "id": "pricing.rule.trials", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "First month free for all three add-ons", "text": "Additional Fraud Filters, Test links and In-platform AI each have a free first month beginning when that add-on is activated, not when an account is registered. Capacity charges and setup are not part of this free trial. After-trial prices show the ongoing rates; this calculator does not activate an add-on, create a checkout or imply automatic charging." }, { "id": "pricing.rule.custom", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Confirm requirements outside this tariff", "text": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order." }, { "id": "pricing.rule.dailyclicks", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Daily click limits for XML / JSON and OpenRTB", "text": "XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus." }, { "id": "pricing.addon.fraud-filters", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.fraud-filters" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Additional Fraud Filters", "text": "Additional traffic-quality checks beyond the standard platform filters: datacenters, known attack sources, Tor, VPN, crawlers and fake crawlers, web scrapers and proxies. These checks do not guarantee detection of all invalid traffic. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.fraud-filters.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.fraud-filters" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Additional Fraud Filters: included features", "text": "Datacenter and known attack-source checks; Tor, VPN and proxy checks; Crawler, fake-crawler and web-scraper checks" }, { "id": "pricing.addon.test-links", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.test-links" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Test links", "text": "Inspect the final URL, redirect chain, redirect timing and screenshot for a test link. Select the referrer, country, device profile and browser engine for the test. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.test-links.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.test-links" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Test links: included features", "text": "Final URL, redirect chain and timing; Screenshot of the tested destination; Selectable referrer, country, device profile and browser engine" }, { "id": "pricing.addon.platform-ai", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.platform-ai" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "In-platform AI", "text": "AI inside your Nexus platform, with model usage included in the add-on price. This tariff is for AI inside a customer's platform, not the public product guide on this website. The add-on is billed once per platform, not separately for each module or location. $500 per month; the first month is free from add-on activation." }, { "id": "pricing.addon.platform-ai.features", "kind": "pricing", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing", "addon.platform-ai" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "In-platform AI: included features", "text": "AI inside your platform; Model usage included; One add-on charge per platform" }, { "id": "policy.pricing", "kind": "policy", "url": "https://www.nexus-soft.org/products/search/price-plans", "topics": [ "pricing" ], "boundary": "Contact Nexus for custom development, an SLA or commercial terms not stated here. No numerical discount or automatic overage rate is specified by this tariff. There are no hidden fees: any additional work must be priced and agreed upfront. Confirm any additional terms before ordering; a calculator enquiry does not place an order.", "title": "Monthly capacity pricing", "text": "All capacity blocks cost $500 per month in USD. XML / JSON feeds, OpenRTB and VAST Video use 1,000 incoming QPS blocks per module per location. Search uses 100,000 daily searches; CPA / CPI / CPL uses 100,000 daily incoming clicks. Daily capacity is billed monthly, not daily." } ], "services": [ { "id": "service.server-management.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Server management", "text": "We help operate web servers, databases, DNS and load-balanced environments. Start with an existing system or a new deployment; agree on the systems, responsibilities and support coverage before work begins." }, { "id": "service.server-management.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Setup & configuration", "text": "Web servers, DNS, mail services and load balancing, configured for the agreed environment." }, { "id": "service.server-management.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Maintenance & performance", "text": "Server updates, troubleshooting and tuning for the services carrying your workload." }, { "id": "service.server-management.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Security & access", "text": "Security reviews, firewall configuration and server-side hardening." }, { "id": "service.server-management.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Databases & caching", "text": "Administration for MySQL, PostgreSQL, MongoDB and Redis, according to your stack." }, { "id": "service.server-management.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Backups & recovery", "text": "Backup configuration, restoration and recovery planning." }, { "id": "service.server-management.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Hosting migrations", "text": "Plan the destination, data transfer, validation and cutover for a server move." }, { "id": "service.server-management.context", "kind": "service", "url": "https://www.nexus-soft.org/services/server-management", "topics": [ "services", "service.server-management" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Server management", "title": "Server management: information to bring", "text": "Your current hosting and server roles; The recurring issue or upcoming infrastructure change; Required coverage and maintenance windows" }, { "id": "service.custom-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Custom software development", "text": "When an off-the-shelf product does not fit, we define the workflow, design the system, implement it and test it against agreed acceptance criteria. Work can start with a bounded project or an ongoing development engagement." }, { "id": "service.custom-development.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Requirements & architecture", "text": "Map user journeys, system boundaries and the interfaces the software needs." }, { "id": "service.custom-development.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Applications & interfaces", "text": "Build web applications and operational interfaces around your workflows." }, { "id": "service.custom-development.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "API & data integration", "text": "Connect applications through agreed APIs, data formats and database contracts." }, { "id": "service.custom-development.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Platform extensions", "text": "Adapt existing components and integrate new functionality into the wider system." }, { "id": "service.custom-development.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Testing & acceptance", "text": "Validate components and integrations, then review the complete system against the specification." }, { "id": "service.custom-development.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Maintenance & evolution", "text": "Define the support, documentation and follow-up work needed after delivery." }, { "id": "service.custom-development.context", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-development", "topics": [ "services", "service.custom-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom software development", "title": "Custom software development: information to bring", "text": "The workflow and users you want to support; Existing applications and integration requirements; Scope, priorities and acceptance criteria" }, { "id": "service.mobile-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Mobile application development", "text": "We help shape mobile products through prototyping, interface design, iterative development and testing. Native, cross-platform or web-based delivery is selected around the project requirements rather than assumed in advance." }, { "id": "service.mobile-development.capability.0", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Product & UX design", "text": "Clarify the essential tasks, map user journeys and prototype the experience." }, { "id": "service.mobile-development.capability.1", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Delivery approach", "text": "Compare native, cross-platform and web-based options for the intended devices." }, { "id": "service.mobile-development.capability.2", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Connected services", "text": "Integrate mobile workflows with the application and cloud services they depend on." }, { "id": "service.mobile-development.capability.3", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Incremental development", "text": "Prioritize useful features and review working iterations with your team." }, { "id": "service.mobile-development.capability.4", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Quality & feedback", "text": "Test releases and use customer feedback to guide the next iteration." }, { "id": "service.mobile-development.capability.5", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Project engagement", "text": "Discuss fixed-scope, ongoing team or time-and-material arrangements." }, { "id": "service.mobile-development.context", "kind": "service", "url": "https://www.nexus-soft.org/services/mobile-development", "topics": [ "services", "service.mobile-development" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Mobile application development", "title": "Mobile application development: information to bring", "text": "Your audience and their most important tasks; Target devices and existing backend services; Release priorities and available project scope" }, { "id": "page.services.custom-adtech-development.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "Custom AdTech software development", "text": "Extend Nexus or build a specialized advertising workflow with a team experienced in traffic platforms, partner integrations and high-volume web systems." }, { "id": "page.services.custom-adtech-development.section.0", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "When standard software is not enough", "text": "Advertising businesses often have distinctive supply contracts, commercial logic, reporting and infrastructure. Nexus Soft can define a bounded custom scope around those requirements instead of forcing them into a generic workflow." }, { "id": "page.services.custom-adtech-development.section.1", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "From requirements to production", "text": "The engagement begins with traffic paths, roles, data contracts, operating scenarios and acceptance criteria. Architecture, implementation, integration testing, system validation and production handover follow from that shared definition." }, { "id": "page.services.custom-adtech-development.section.2", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "AdTech integration depth", "text": "Custom work can cover XML and JSON feeds, partner APIs, OpenRTB services, VAST delivery, postbacks, dashboards, admin workflows, data services and infrastructure automation. Exact scope and supported protocols are confirmed during solution design." }, { "id": "page.services.custom-adtech-development.section.3", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "Flexible delivery model", "text": "A defined feature can be delivered as a scoped project, while evolving platforms may use a dedicated or mixed product-engineering model. Timeline, ownership, maintenance and support boundaries are documented before work begins." }, { "id": "page.services.custom-adtech-development.section.4", "kind": "service", "url": "https://www.nexus-soft.org/services/custom-adtech-development", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "Custom AdTech software development", "title": "AI-native extension", "text": "New product knowledge and approved operations can also be exposed through Nexus MCP tools and resources, giving compatible AI clients a typed interface rather than requiring them to scrape a dashboard." }, { "id": "page.services.adtech-infrastructure-management.overview", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "AdTech infrastructure management", "text": "Operational support for the servers, data services, security boundaries and delivery paths behind high-volume advertising systems." }, { "id": "page.services.adtech-infrastructure-management.section.0", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Reliability starts below the dashboard", "text": "Traffic routing depends on web services, databases, caches, DNS, load balancing, network policy and recoverable data. Nexus treats those dependencies as part of the operating system, not invisible hosting details." }, { "id": "page.services.adtech-infrastructure-management.section.1", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Proactive operations", "text": "Monitoring, performance tuning, security maintenance, backup design and recovery planning reduce avoidable failures. Production commitments and escalation procedures are defined for the actual deployment rather than implied by a generic website claim." }, { "id": "page.services.adtech-infrastructure-management.section.2", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Migration and scale", "text": "Infrastructure work can include new service setup, database or cache configuration, load-balancing patterns, hosting migration and troubleshooting across Linux or Windows environments." }, { "id": "page.services.adtech-infrastructure-management.section.3", "kind": "service", "url": "https://www.nexus-soft.org/services/adtech-infrastructure-management", "topics": [ "services" ], "boundary": "We agree on access, scope and acceptance before any work on your systems. Each service has its own agreed scope and commercial terms.", "sourceTitle": "AdTech infrastructure management", "title": "Protected configuration", "text": "Service credentials remain server-side. Platform administrators work through authenticated, bounded configuration workflows while public website and MCP discovery interfaces remain separated from private infrastructure." } ], "overview": "Nexus is an AI-native AdTech control plane from Nexus Soft, whose advertising-technology engineering history reaches back to 2004. It connects Search, XML/JSON feeds, OpenRTB, VAST Video and CPA while allowing products to run independently or share identity, tenant configuration, infrastructure and operational policy.", "products": { "search": "Connect provider feeds to publisher links, set search caps and revenue-share rules, and understand the results by keyword, domain and traffic source. Provider feed setup: Configure the advertiser, search engine, provider URL, search cap and revenue share. Keep NET reporting settings with the feed they describe. 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. Search feed and link controls differ. Provider integrations, NET import timing and metric definitions are confirmed during deployment.", "feeds": "Connect publisher accounts with demand feeds. Configure targeting, minimum bids, QPS and click limits, then compare publisher-side and feed-side results. Publisher-to-feed mapping: Choose demand feeds for each affiliate account. XML direct links are supported for publisher traffic and configured demand destinations. Popunder JS is available with script, frequency and delay settings. Keep source controls in place; browser restrictions still determine window behavior. Provider configuration: Set provider and feed type, image and icon requirements, SubID handling, result count and timeout. Detailed targeting: Configure countries, operating systems, browsers, devices, domains, carriers, keywords and subscriber age. Bids, limits and expiry: Set minimum bid, maximum requests and QPS, daily budget, click limits, clicks per IP or IP + user-agent, and result expiry. Quality policy: Configure duplicate, fast-click, JavaScript, cookie, referrer, user-agent, iframe and headless-browser checks alongside network-risk categories. Reports from both sides: Review requests, coverage, valid and invalid clicks, revenue, NET metrics and profit. Configure provider NET imports separately from traffic reporting. Adapter support and response formats are integration-specific. Traffic-quality rules do not guarantee detection of every invalid interaction.", "rtb": "Manage exchange and demand connections with OpenRTB version selection, bid floors, targeting and partner grants. Keep auction and financial signals in the same operating view. Exchange configuration: Configure adapter, OpenRTB version, revenue share, auction type, no-bid code and billing event for the supply connection. Prebid.js and Prebid Server integrations are available now; configure compatible adapters, endpoints and inventory for your deployment. Demand delivery controls: Configure DSP type, timeout, traffic types, Gzip and demand-side QPS. Keep NET import settings with the demand resource. Inventory targeting: Use country, OS, browser, device, ad size, application and bundle controls, with inventory and video-type settings on demand. Partner grants: Set Allowed Demands for an exchange and Allowed Exchanges for demand. Define trading relationships explicitly. Floors and quality filters: Configure bid floors, exchange maximum bid, network-risk rules and SSP, site, publisher, domain or creative lists. Cookie sync and reporting: Cookie sync is available now. Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics. Cookie sync has its own partner and browser requirements, separate from the Prebid integration setup. Protocol interoperability, partner-specific extensions and capacity targets are validated for your deployment. Version selection is not a certification claim.", "video": "Manage publisher channels and demand tags in a dedicated VAST workspace. Configure environments, pricing and delivery limits, then follow video events from Started to Completed. Publisher channels: Configure publisher, price type, CPM, floor, required fields and the web, app or CTV environment. Demand tag management: Keep advertiser, source, tag type, timeout and delivery settings together. Tag configuration offers VAST, Audio and RTB options. Application-level targeting: Configure countries, operating systems, ad sizes, languages, bundle IDs and application names. Delivery limits: Set applicable hourly and daily revenue, request and impression limits. Demand tags add maximum QPS and scheduled-delivery controls. Channel and tag grants: Assign allowed tags to a channel and allowed channels to a tag. Keep publisher integration and host configuration separate from demand. Video-specific reporting: Inspect VAST URI validity, errors, fill, impressions and revenue. Review Started, First Quartile, Midpoint, Third Quartile and Completed. VAST versions, player and SDK compatibility, device support and audio delivery are confirmed for the agreed integration—not assumed for every environment.", "cpa": "Operate performance offers with fixed-price or revenue-share payouts, targeting, conversion windows and caps. Bring publisher access, creatives and conversion reporting into one workflow. Offer workspace: Manage advertiser and offer references, preview and tracking URLs, images, descriptions, restrictions and expiry. Payout configuration: Configure fixed-price or revenue-share terms, currency and advertiser/publisher payouts. Event categories include installation, registration, sales, subscription and in-app events. Conversion rules and caps: Set conversion windows, pending or multiple-conversion controls, daily/monthly clicks, conversions and revenue, plus minimum/maximum CR. Eligibility and access: Configure approval and terms requirements, private offers and publisher visibility. Keep these separate from delivery targeting. Targeting and traffic filters: Use country, OS version, browser, device, connection and carrier context. Configure SubID, domain and IP-range allowlists and blocklists. Creatives and performance: Organize offer creatives and publisher-cap records. Review click context, valid/invalid conversions, advertiser/publisher payouts, profit, CR, CPC and RPC. Tracking and postback contracts, attribution rules and payout reconciliation must be validated with your partners before production delivery." }, "operations": { "reporting": { "lastModified": "2026-09-09", "sources": [ [ "/products/search", "Search metrics and NET import boundaries" ], [ "/products/feeds", "XML affiliate, feed and provider reporting" ], [ "/products/rtb", "RTB local and partner NET reporting" ] ], "seoDescription": "Explore Nexus channel reports, source breakdowns, partner NET metrics, templates and CSV export. Understand data freshness before comparing results.", "eyebrow": "Reporting & reconciliation", "title": "Reconcile local activity with partner NET reports.", "lead": "A request, a reported impression and a partner-confirmed result are different things. Nexus gives each channel its own reporting vocabulary, with breakdowns that help you investigate traffic, delivery and commercial performance.", "accent": "reporting", "visual": [ "Choose a channel", "Select a date range", "Break down the result", "Compare partner NET" ], "capabilities": [ [ "Channel-specific measures", "Search coverage, XML valid requests, RTB win rate, video completion and CPA conversions answer different questions. Work with the measures relevant to the product you operate." ], [ "Dimensions with a purpose", "Investigate results by the source and request attributes available in each report. The breakdown may be a search keyword, an RTB bundle or a video application environment." ], [ "Partner NET reporting", "Search, XML and RTB administration expose partner NET reporting fields. Configure the supported provider adapter and its update settings before comparing local and partner-reported results." ], [ "Your working report", "Report templates and a column chooser let operators arrange the available fields for their routine analysis. CSV export is available in the reporting interface." ], [ "A separate financial overview", "The financial dashboard provides background snapshots on a five-minute cycle. It is an overview, not a promise that every partner feed or channel metric refreshes at that interval." ], [ "From exceptions to investigation", "Requests with errors, invalid traffic and differences between local and NET figures give the team a starting point. Review the relevant partner and configuration before changing delivery rules." ] ], "workflow": [ [ "Start with the question", "Choose the channel and report: publisher, affiliate, feed, exchange, demand, video or offer performance." ], [ "Set the context", "Select the period, relevant account or source and the available report dimensions." ], [ "Inspect the difference", "Compare volume, delivery and commercial fields. Keep local counts and partner NET figures distinct." ], [ "Keep a useful view", "Arrange columns, use a report template or export the available report for further analysis." ] ], "metrics": [ "Requests", "Valid / invalid traffic", "Clicks", "Revenue", "Cost / spend", "Profit", "Partner NET" ], "dimensions": [ "Channel-specific reports", "Date range", "Account / partner", "Source identifiers", "Traffic attributes" ], "boundary": "Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "definitions": [ [ "Local versus NET", "Local figures describe the platform’s recorded activity. NET fields are the corresponding measures obtained through a configured partner reporting integration. Do not treat the two as interchangeable." ], [ "Coverage versus conversion", "Coverage describes a delivery-related measure in a channel report. A conversion represents an outcome in the performance workflow. Read them in their own product context." ], [ "Useful comparisons", "Compare like-for-like periods, partners, currencies and report dimensions. Confirm the provider update window before investigating a discrepancy." ], [ "Illustrative reconciliation: 120 versus 114 clicks", "For a fictional completed reporting period, suppose the local report shows 120 clicks and the partner NET report shows 114. The absolute difference is 6; using the local count as the explicitly chosen denominator, 6 / 120 × 100 = 5%. This is sample arithmetic, not a customer result, an acceptable discrepancy threshold or a Nexus metric formula. Record which count is the denominator when sharing the comparison." ], [ "First align the comparison", "Check the same start/end times and timezone, the same affiliate or publisher link, the same feed and source breakdown, and the same validity or acceptance scope. Check whether the provider has finished reporting that period. For money, also align currency and gross/net or revenue-share treatment. A date label alone is not proof that two exports describe the same activity." ], [ "Then isolate the remaining difference", "Break the fictional six-click gap down by the dimensions available in the relevant report. If it concentrates in one feed or SubID, inspect that connection and its import settings. If the partner period is incomplete, wait for its agreed update window before drawing a conclusion. Retain separate local and partner values; replacing one with the other hides the evidence needed to resolve the mismatch." ], [ "Do not turn a count gap into an invoice claim", "A click discrepancy does not directly establish a revenue discrepancy. Price models, accepted events, adjustments and commercial terms can differ. Likewise, NET is a provider-reporting label here, not a universal accounting definition of profit. Keep a record of the report filters, update timestamp, expected adjustment process and responsible partner contact before deciding which figure governs settlement." ], [ "Make the investigation repeatable", "Choose the needed columns and available dimensions, save a report view or export CSV, and record the comparison assumptions alongside the evidence. Investigate representative accepted and rejected samples through the approved integration process where aggregate reports are insufficient. A useful resolution explains the source of the difference and the next check; it does not silently change traffic rules just to make two totals agree." ] ], "closing": "Bring the report you wish you had.", "closingText": "We will map your questions to the available channel reports, provider integrations and any additional development required." }, "publisher-platform": { "seoDescription": "Use Nexus Push Subscribers for direct publishers: website approvals, browser subscriptions, subscriber inventory, notification activity and reporting.", "eyebrow": "Publisher operations", "title": "Give every publisher a clear place in your network.", "lead": "Push Subscribers is available for direct publishers. Manage publisher websites, approvals, browser subscriptions, subscriber inventory and performance in a connected workflow. Keep commercial relationships separate from delivery configuration.", "accent": "publisher", "visual": [ "Publisher website", "Approval & integration", "Subscription rules", "Activity & reporting" ], "capabilities": [ [ "Website administration", "Manage the publisher, website name, URL, description and account status. Approval and suspension controls make the status of a website explicit." ], [ "Welcome notifications", "Configure a welcome notification with a title, destination link and message text. Treat the notification content as part of the publisher experience." ], [ "Subscription behavior", "Set the subscription trigger, time frame, delay and prompt behavior. Advanced options include persistence until a click, where configured for the integration." ], [ "Postbacks and redirects", "Configure a subscription postback and the redirects associated with subscribed and not-subscribed outcomes. Validate the destination and integration before launch." ], [ "Push Subscribers inventory", "Inspect first and last activity, website and source identifiers, country, language, browser, OS and subscription status. The inventory also exposes impression, click and revenue fields." ], [ "Publisher reporting", "Review request validity, initialization, subscriber activity, impressions, clicks, closed notifications and revenue. Break down the available reports by account, country, OS and browser." ] ], "workflow": [ [ "Register the website", "Associate the site with its publisher and review its URL, description and account status." ], [ "Define the experience", "Configure notification text, subscription prompts, redirects and postback destinations." ], [ "Validate the integration", "Confirm the delivery service and Push URL are configured, then test the approved integration in a controlled environment." ], [ "Review the activity", "Inspect subscriber records and publisher statistics before adjusting the site’s configuration." ] ], "metrics": [ "Requests", "Valid requests", "Errors", "Initializations", "Subscribers", "Impressions", "Clicks", "Invalid clicks", "Closed", "CTR", "CPC", "Revenue" ], "dimensions": [ "Publisher account", "Country", "Operating system", "Browser" ], "boundary": "Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "definitions": [ [ "Before a site goes live", "Confirm ownership and approval, the service URL, subscription behavior, notification content and valid callback destinations." ], [ "Before sending notifications", "Check the audience and permission model, supported browsers and delivery configuration. A subscriber record alone is not a delivery guarantee." ], [ "Before publishing a case study", "Use approved, anonymized reporting and explain the period and measurement method. Customer identities and live subscriber endpoints should remain private." ] ], "closing": "Build a better publisher workflow.", "closingText": "Walk through website onboarding, subscription configuration and reporting with your team’s operating requirements in view." }, "campaign-management": { "seoDescription": "Run multi-format direct campaigns with CPC and CPM buying, Push, XML and OpenRTB delivery, self-serve budgets, creatives, funds and account balance.", "eyebrow": "Advertiser self-serve", "title": "More ways to reach audiences. One advertiser workspace.", "lead": "Bring display, native, contextual, video, popunder and push campaigns together. Direct advertisers manage creatives, targeting, budgets, funds and account balance in a self-serve workspace, with reporting across their configured delivery channels.", "accent": "campaign", "configurationView": true, "visual": [ "Campaign objective", "Budget & audience", "Creative & tracking", "Delivery review" ], "capabilities": [ [ "CPC and CPM buying", "Buy traffic by click with CPC or by thousand impressions with CPM. Popunder workflows also expose CPV bidding. Set the bid, daily and total budgets, frequency cap and schedule for the selected campaign type. Campaign media spend is separate from the Nexus platform subscription and its capacity-based pricing." ], [ "Delivery schedule", "Configure the campaign’s schedule alongside its budget and audience. Review the intended delivery window before activating a campaign." ], [ "Detailed audience selection", "Define geographic, operating system, browser and browser-version targeting. Use the available campaign fields to narrow the traffic that matches the objective." ], [ "Source-level controls", "Manage IP, domain, publisher, SubID, keyword and feed eligibility with the available allowlists and blocklists. Source controls make exclusions explicit." ], [ "Creative inventory", "Browse creative records with their advertiser, campaign, type, status and dimensions. Keep the asset associated with the campaign it belongs to." ], [ "Creative content and tracking", "The creative editor separates basic information, tracking and media. Configure the name, status, width, height, click URL, impression pixel and asset as required by the format." ], [ "Self-serve funds and balance", "Direct advertisers can manage funds and view their account balance in the advertiser workspace, alongside their campaigns and reports. Available funding methods and payment-provider setup are configured for the deployment; no particular gateway or instant settlement is implied." ], [ "Formats and delivery channels", "Run direct campaigns with display and HTML banners, native and contextual ads, video, popunder, Web Push and in-page push. Connect eligible traffic through Push delivery, XML / JSON feeds and OpenRTB. The creative format defines the experience; the delivery integration connects it to compatible publisher inventory." ] ], "workflow": [ [ "Set the campaign boundaries", "Define the bid, daily and total budget, frequency cap and schedule for the campaign." ], [ "Choose the eligible audience", "Select request attributes and source lists, then review the exclusions with your operations team." ], [ "Prepare the creative", "Associate the asset with its advertiser and campaign. Check dimensions, click URL and impression tracking." ], [ "Validate before scaling", "Run a controlled delivery check and use the relevant channel reports to review traffic and outcomes." ] ], "metrics": [ "Campaign status", "Advertiser", "Creative type", "Width / height", "Click URL", "Impression pixel" ], "dimensions": [ "Country", "Operating system", "Browser / version", "IP / domain", "Publisher / SubID", "Keyword / feed" ], "boundary": "Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "definitions": [ [ "Campaign versus offer", "A campaign defines an advertising setup and audience. The CPA offer workflow has its own payout models, conversion events, caps and publisher-access settings." ], [ "Creative versus ad format", "An asset and its tracking fields belong to the creative. The ad format determines how the placement is presented and which delivery integration it needs." ], [ "Configuration versus outcome", "Budgets, schedules and targeting define intended behavior. Confirm delivery and partner reporting with controlled traffic before committing to performance expectations." ] ], "closing": "Bring your next campaign workflow.", "closingText": "We will show how its audience, budget, assets and channel integration fit together in Nexus." } }, "platformSolutions": [ { "slug": "xml-ad-network", "seoTitle": "XML Ad Network Software — White-Label Platform | Nexus", "name": "XML ad network", "goal": "Connect traffic sources to advertiser feeds", "audience": "Feed operators, traffic networks and monetization teams", "summary": "Run an XML / JSON feed monetization platform. Connect advertiser feeds, assign them to publishers and control how traffic is filtered, routed and monetized.", "modules": [ "feeds", "advertiser" ], "capture": "feeds", "scope": "Existing module workflow", "workflow": [ "Publisher request", "Filters & limits", "Eligible advertiser feeds", "Click & revenue reports" ], "capabilities": [ [ "Partner connections", "Manage advertiser feeds and publisher mappings. Connect each source to the demand and commercial terms you choose." ], [ "Traffic decisions", "Configure bids, QPS, click limits, budgets and supported geo, device, domain and sub-ID rules. Inspect rejected traffic instead of treating every request as sellable." ], [ "Revenue visibility", "Review feed and affiliate statistics. Compare local results with imported partner NET figures and use the XML dashboard to investigate differences." ] ], "requirements": [ "Publisher traffic and advertiser feed agreements", "Request parameters, response formats and tracking contracts for each partner", "Traffic volumes, quality policy and reporting responsibilities" ], "boundary": "XML is a feed integration format, not a banner design. Pop, contextual and push traffic require the corresponding provider adapter and delivery setup; one XML feed does not automatically support every placement.", "formats": [ "contextual-domain-ads", "popunder-cpv-ads", "in-page-push-ads", "direct-link-ads" ], "example": "A traffic network connects several publisher sources to selected advertiser feeds, caps each source and compares partner-reported revenue with its own recorded clicks." }, { "slug": "search-advertising-network", "name": "Search Syndication", "goal": "Monetize search intent", "audience": "Search publishers, syndication businesses and search-feed operators", "summary": "Run a search syndication platform. Connect search providers to publisher links, apply keyword and traffic rules and compare searches, clicks and partner results.", "modules": [ "search" ], "capture": "search", "scope": "Existing module workflow", "workflow": [ "Search query", "Publisher link & rules", "Search provider response", "Searches, clicks & NET results" ], "capabilities": [ [ "Provider and publisher setup", "Configure search provider feeds, publisher links and revenue-share settings around the traffic relationships you operate." ], [ "Search-specific controls", "Use supported keyword, geographic and device targeting, request filters and search caps. Review controls per provider instead of assuming identical behavior across feeds." ], [ "Comparable reports", "Inspect searches and clicks by link, publisher, advertiser and feed. Separate local activity from NET figures received from partners." ] ], "requirements": [ "Approved search demand providers and publisher traffic", "Search query and tracking parameters supported by each feed", "Revenue-share agreements and traffic acceptance rules" ], "boundary": "This is software for a search advertising network, not an organic search engine or a reseller account for a particular search provider. Provider access and traffic approval remain separate commercial requirements.", "formats": [ "search-ads", "contextual-domain-ads" ], "example": "A publisher runs a search experience, sends eligible queries to its connected providers and reviews which links generate accepted searches and paid clicks." }, { "slug": "openrtb-exchange", "seoTitle": "OpenRTB Ad Exchange Software — White-Label Platform | Nexus", "name": "OpenRTB exchange & traffic hub", "goal": "Connect supply and demand partners", "audience": "Programmatic networks, exchanges and supply aggregators", "summary": "Operate the connection between programmatic supply and demand. Manage exchanges, demand access, inventory rules and trading reports from the OpenRTB workspace.", "modules": [ "rtb" ], "capture": "rtb", "scope": "Existing module workflow", "workflow": [ "Supply bid request", "Inventory & traffic checks", "Eligible demand / campaigns", "Response & event reporting" ], "capabilities": [ [ "Trading relationships", "Configure exchange and demand connections. Explicitly control which demand can receive traffic from each exchange." ], [ "Inventory and routing policy", "Use supported inventory, geo, device, domain and app rules, QPS controls and partner-specific settings to qualify requests." ], [ "Operational reporting", "Review requests, valid requests, impressions, clicks, revenue, spend and profit. Investigate traffic errors alongside trading results." ] ], "requirements": [ "Supply and demand endpoint access plus trading agreements", "A tested OpenRTB contract for formats, events and partner requirements", "Capacity, timeout, filtering and commercial settings" ], "boundary": "An exchange connects buying and selling parties; a DSP focuses on buying for advertisers. Nexus provides the RTB operating components, but does not include a ready-made marketplace of premium inventory or guaranteed demand.", "formats": [ "display-banner-ads", "native-ads", "instream-video-ads" ], "example": "An operator connects a new supply partner, enables selected demand connections for that exchange and investigates request quality and trading performance in one workspace." }, { "slug": "white-label-dsp", "name": "DSP Deployment", "goal": "Run an advertiser buying platform", "audience": "Advertiser-facing networks, agencies and custom AdTech businesses", "summary": "Build a demand-side platform around Nexus campaign management and the RTB runtime. Define advertiser campaigns, creatives, targeting and the supply connections they can buy from.", "modules": [ "rtb", "advertiser" ], "capture": "rtb", "scope": "Integration-scoped deployment", "workflow": [ "Advertiser campaign", "Creative, targeting & budget", "Connected RTB supply", "Impression, click & spend reports" ], "capabilities": [ [ "Advertiser workflows", "Give direct advertisers a self-serve workspace for multi-format campaigns, CPC and CPM buying, creatives, targeting, budgets, funds and account balances. Configure eligible supply, access and funding methods for your deployment; campaign media spend is separate from platform capacity charges." ], [ "Buying runtime", "The RTB runtime includes direct-campaign selection as well as external demand connections. Scope supply endpoints, frequency controls and supported creative delivery paths before launch." ], [ "Brand and engineering", "Combine white-label configuration with custom development where the buying workflow needs additional integrations, user journeys or reporting." ] ], "requirements": [ "The exchanges or supply partners you want to buy from", "Creative review, targeting, budget and event requirements", "A defined advertiser UX and a delivery plan for additional integrations" ], "boundary": "DSP means demand-side platform. This is an integration-scoped Nexus deployment, not a claim of a turnkey universal DSP. Automated bidding strategies, attribution models, billing and access to specific exchanges must be validated separately.", "formats": [ "display-banner-ads", "native-ads", "instream-video-ads" ], "example": "An agency wants a branded buying interface for a defined group of advertisers and supply partners. Nexus supplies campaign and RTB components; the required buying workflow is validated and completed during implementation." }, { "slug": "video-ad-network", "name": "Video ad network", "goal": "Connect video inventory to VAST demand", "audience": "Video networks, publishers and video monetization teams", "summary": "Build a video monetization platform around channels and VAST tags. Connect publisher inventory to eligible demand and inspect delivery, errors and partner results.", "modules": [ "video" ], "capture": "video", "scope": "Existing module workflow", "workflow": [ "Player / channel request", "Eligibility & limits", "Selected VAST tag", "Playback events & reports" ], "capabilities": [ [ "Channels and demand", "Organize publisher channels and video tags, with the partner relationships and eligibility settings needed for each connection." ], [ "Video controls", "Configure supported targeting, request filters and traffic limits. Keep player requirements and tag compatibility part of the integration checklist." ], [ "Delivery investigation", "Inspect video statistics and error reports to understand which requests progress to delivery and which fail along the VAST path." ] ], "requirements": [ "A compatible publisher player or delivery integration", "VAST demand tags and publisher / demand agreements", "Playback-event, consent and error-reporting requirements" ], "boundary": "VAST is a delivery protocol. In-stream, outstream and CTV are placement environments. CTV apps, SSAI, player behavior and certification are integration-specific; they are not supplied automatically by enabling the Video module.", "formats": [ "instream-video-ads", "outstream-video-ads", "ctv-ott-ads" ], "example": "A video network maps publisher channels to selected VAST demand tags and checks delivery and errors before expanding the eligible traffic." }, { "slug": "affiliate-tracking-platform", "name": "Affiliate & conversion tracking platform", "goal": "Track clicks, conversions and partner payouts", "audience": "Affiliate networks, offer owners and performance teams", "summary": "Run an offer-based CPA tracking platform. Connect publishers to offers, track clicks and reported conversions, apply caps and manage fixed or revenue-share payouts.", "modules": [ "cpa" ], "capture": "cpa", "scope": "Existing module workflow", "workflow": [ "Publisher tracking link", "Offer & landing page", "Conversion / postback", "Validation & payout reporting" ], "capabilities": [ [ "Offer management", "Configure offers, publisher approvals, supported geo and device targeting, conversion windows and commercial terms." ], [ "Conversion tracking", "Match advertiser-reported conversion events to the original click ID. Define the accepted event and postback behavior before counting outcomes." ], [ "Commercial controls", "Use caps and fixed or revenue-share payouts. Review offer and publisher reports to see where valid or invalid conversions and partner earnings come from." ] ], "requirements": [ "Offers, landing pages and approved traffic sources", "A working advertiser conversion / postback integration", "The payable event, validation rules, caps and payout terms" ], "boundary": "Tracking here means affiliate clicks, offer conversions and postbacks. It is not a blanket claim of multi-touch attribution, cross-device identity, an app measurement SDK or MMP certification. Install and lead tracking depend on the integrated conversion source.", "formats": [ "mobile-performance-ads" ], "example": "A network gives an approved publisher an offer link, receives a conversion postback and applies the configured payout after the event satisfies the agreed rules." }, { "slug": "web-push-platform", "name": "Web Push publisher platform", "goal": "Manage subscribed browser audiences", "audience": "Publisher networks and browser-notification operators", "summary": "Use the available Push Subscribers module for direct publishers. Manage websites, browser subscriptions and notification delivery, then review subscriber activity and notification results.", "modules": [ "publisher" ], "capture": "publisher-platform", "scope": "Delivery integration required", "workflow": [ "Website permission", "Browser subscription", "Configured push delivery", "Subscriber & event reports" ], "capabilities": [ [ "Publisher setup", "Organize publisher websites, subscription information and notification content in the publisher workflow." ], [ "Browser delivery", "Nexus includes browser subscription and service-worker integration plus Web Push delivery code. Deployment requires the configured delivery services and valid subscriptions." ], [ "Audience reporting", "Review subscriber activity, impressions, clicks and revenue where supported by the configured publisher and delivery integration." ] ], "requirements": [ "A compatible website integration and service worker", "User permission and valid browser push subscriptions", "Delivery-service configuration, notification content and unsubscribe handling" ], "boundary": "Web Push needs browser permission. It is different from an in-page push placement, which is an ad rendered within a webpage. Adding a publisher record alone does not activate notification delivery.", "formats": [ "web-push-ads" ], "example": "A publisher connects its website, collects browser subscriptions from consenting visitors and reviews subscriber activity while the configured push service handles notification delivery." } ], "standards": { "protocols": [ { "key": "openrtb", "organization": "IAB Tech Lab", "title": "OpenRTB", "subtitle": "2.4 / 2.5 / 2.6 configuration", "description": "Connect exchange and demand partners with version selection, auction settings, bid floors and timeouts in the RTB module.", "href": "https://iabtechlab.com/standards/openrtb/", "linkLabel": "OpenRTB specification" }, { "key": "vast", "organization": "IAB Tech Lab", "title": "VAST", "subtitle": "Video ad serving", "description": "Manage video channels and VAST tags. Review starts, quartiles, completions and URI diagnostics in the video module.", "href": "https://iabtechlab.com/standards/vast/", "linkLabel": "VAST specification" } ], "scope": "Protocols 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." }, "adFormats": { "search-ads": { "name": "Search ads and sponsored results", "category": "Intent advertising", "definition": "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.", "deployment": { "kind": "Ad format", "solution": "search-advertising-network", "nexus": "Search provider feeds, publisher links, keyword and traffic rules, search caps and reporting.", "requires": "Approved demand provider access, a search placement and compatible query / click parameters." }, "availability": "Core Nexus Search workflow", "placements": [ "Search result pages", "Publisher search boxes", "Comparison and directory experiences", "Contextual keyword pages" ], "buyingModels": [ "CPC — cost per click", "Revenue-share or publisher payout", "Provider bid and custom publisher range" ], "targeting": [ "Keyword or query intent", "Country and region", "Browser, OS and device", "Publisher, placement and sub-ID", "Supported partner-specific parameters" ], "metrics": [ { "name": "CTR", "definition": "Clicks ÷ delivered sponsored results" }, { "name": "RPC", "definition": "Revenue generated per click" }, { "name": "Coverage", "definition": "Requests that return eligible results" }, { "name": "NET", "definition": "Provider-reported commercial result" } ], "deliveryFlow": [ "User query", "Request and quality policy", "Eligible demand feeds", "Ranked sponsored results", "Click and reconciliation" ] }, "display-banner-ads": { "name": "Display banner advertising", "category": "Display advertising", "definition": "Display banners are visual ad units placed inside a page or application layout. They are familiar and scalable, but effective delivery still depends on creative dimensions, placement context, viewability, frequency and transparent supply paths.", "deployment": { "kind": "Ad format", "solution": "white-label-dsp", "nexus": "Banner creative paths, campaign controls and supported OpenRTB supply / demand connections.", "requires": "A compatible ad slot, creative dimensions and a tested impression and click integration. Creative authoring tools are not implied." }, "availability": "OpenRTB-connected and deployment-specific inventory", "placements": [ "Page header and leaderboard", "Sidebar and medium rectangle", "In-content display slot", "Mobile web or in-app banner" ], "buyingModels": [ "CPM — cost per thousand impressions", "CPC — cost per click", "Fixed-price or direct placement" ], "targeting": [ "Geography", "Site, app and placement", "Device, OS and browser", "Schedule and frequency", "Audience or first-party segments when supplied lawfully" ], "metrics": [ { "name": "Impressions", "definition": "Counted ad deliveries" }, { "name": "Viewability", "definition": "Opportunity to be seen" }, { "name": "CTR", "definition": "Clicks ÷ impressions" }, { "name": "eCPM", "definition": "Revenue normalized per thousand impressions" } ], "deliveryFlow": [ "Available placement", "Ad request", "Eligibility or auction", "Creative response", "Impression and click events" ] }, "native-ads": { "name": "Native advertising", "category": "Content-integrated advertising", "definition": "Native advertising is assembled from components—headline, image, description, brand and call to action—so the publisher can render it in the visual language of the surrounding product. The format should feel coherent without disguising that it is paid placement.", "deployment": { "kind": "Ad format", "solution": "openrtb-exchange", "nexus": "Native ads for direct advertisers through campaign and creative management, alongside native creative selection and supported programmatic partner connections.", "requires": "A matching native asset contract and publisher renderer. The partner determines how title, image, sponsor label and destination appear." }, "availability": "Native ads for direct advertisers and supported OpenRTB native integrations", "placements": [ "Editorial recommendation feed", "In-feed mobile card", "Sponsored content module", "Commerce or discovery widget" ], "buyingModels": [ "CPM", "CPC", "CPA or downstream outcome where tracking supports it" ], "targeting": [ "Publisher and content category", "Placement and device", "Geography and language", "Audience context supplied by the publisher", "Frequency and schedule" ], "metrics": [ { "name": "Viewable impressions", "definition": "Visible native deliveries" }, { "name": "CTR", "definition": "Visits generated by the unit" }, { "name": "Engaged sessions", "definition": "Useful post-click visits" }, { "name": "Conversion rate", "definition": "Validated outcomes ÷ eligible visits" } ], "deliveryFlow": [ "Native placement request", "Asset and policy validation", "Bid or campaign selection", "Publisher-side rendering", "Engagement and conversion" ] }, "instream-video-ads": { "name": "In-stream video advertising", "category": "Video advertising", "definition": "In-stream video advertising plays inside a video player before, during or after the requested content. The viewer experience depends on more than the media file: VAST metadata, wrapper depth, player capability, duration and tracking must work as one delivery chain.", "deployment": { "kind": "Video placement", "solution": "video-ad-network", "nexus": "Video channels, VAST tags, eligibility settings and video delivery / error reporting.", "requires": "A compatible content player and demand tag. Confirm VAST version, playback events and skip behavior with the integration." }, "availability": "Core Nexus VAST workflow", "placements": [ "Pre-roll before content", "Mid-roll break", "Post-roll after content", "Live-stream ad break" ], "buyingModels": [ "CPM", "vCPM or viewable delivery", "CPV or completed-view model" ], "targeting": [ "Content and channel", "Device and player environment", "Geography and language", "Duration and creative compatibility", "Ad-break position and frequency" ], "metrics": [ { "name": "Start rate", "definition": "Playback starts ÷ valid responses" }, { "name": "Completion rate", "definition": "Completed views ÷ starts" }, { "name": "Quartiles", "definition": "25%, 50%, 75% and complete events" }, { "name": "Error rate", "definition": "VAST or player failures ÷ attempts" } ], "deliveryFlow": [ "Player ad break", "VAST request", "Demand and wrapper chain", "Compatible media selection", "Playback and tracking events" ] }, "outstream-video-ads": { "name": "Outstream video advertising", "category": "Video advertising", "definition": "Outstream video creates a player-like placement inside non-video content. The unit commonly opens or begins muted when it enters view and pauses or collapses when the user moves away, making viewability and interaction policy central to the format.", "deployment": { "kind": "Video placement", "solution": "video-ad-network", "nexus": "The Video module connects eligible channels and VAST demand tags.", "requires": "An outstream player or renderer inside the publisher page. Playback and viewability measurement are not supplied by a VAST tag alone." }, "availability": "VAST integration pattern; deployment-specific", "placements": [ "In-article unit", "In-feed video card", "Sticky or floating player", "Native video placement" ], "buyingModels": [ "CPM", "vCPM", "CPV or completed view" ], "targeting": [ "Page and content context", "Placement position", "Device and browser capability", "Geography and language", "Viewability and frequency rules" ], "metrics": [ { "name": "Viewable starts", "definition": "Starts while the unit is viewable" }, { "name": "Completion rate", "definition": "Completed plays ÷ starts" }, { "name": "Viewable time", "definition": "Duration meeting viewability conditions" }, { "name": "Interaction rate", "definition": "Clicks or controls used ÷ starts" } ], "deliveryFlow": [ "Page or feed loads", "Unit enters viewport", "VAST response resolves", "Muted playback begins", "Pause, completion or interaction" ] }, "ctv-ott-ads": { "name": "CTV and OTT advertising", "category": "Connected television", "definition": "CTV advertising reaches streaming content on connected televisions and TV-like devices. It uses familiar video concepts, but living-room viewing, device fragmentation, ad pods and limited click interaction create a distinct operating environment.", "deployment": { "kind": "Viewing environment", "solution": "video-ad-network", "nexus": "Video channel, tag and traffic-control components for an agreed delivery configuration.", "requires": "Compatible connected-TV inventory, player or SSAI integration and event contracts. App SDKs and CTV certification require separate validation." }, "availability": "VAST and OpenRTB-connected deployment pattern", "placements": [ "Streaming pre-roll", "Mid-roll ad pod", "FAST channel break", "OTT application inventory" ], "buyingModels": [ "CPM", "Completed-view pricing", "Programmatic guaranteed or private deal" ], "targeting": [ "App, channel and content genre", "Device type and operating system", "Geography", "Ad pod position", "Publisher-provided household or first-party segments" ], "metrics": [ { "name": "Completion rate", "definition": "Completed views ÷ starts" }, { "name": "Reach", "definition": "Estimated unique exposed households or devices" }, { "name": "Frequency", "definition": "Average exposures per addressable unit" }, { "name": "Pod position", "definition": "Performance by slot inside an ad break" } ], "deliveryFlow": [ "Streaming ad break", "CTV opportunity", "Eligible video demand", "Ad pod assembly", "Playback and completion evidence" ] }, "interstitial-rich-media-ads": { "name": "Interstitial and rich media advertising", "category": "High-impact display", "definition": "Interstitial and rich media formats use more screen space or interaction than a standard banner. They can communicate complex creative ideas, but they also require stricter timing, close controls, performance and frequency policy.", "deployment": { "kind": "Placement family", "solution": "white-label-dsp", "nexus": "Campaign and programmatic components for supported creative and inventory contracts.", "requires": "A compatible publisher renderer or app integration with close controls and permitted creative behavior. A rich-media builder or template library is not implied." }, "availability": "Deployment-specific campaign and OpenRTB format", "placements": [ "Between page or app states", "Expandable display placement", "In-banner video or interaction", "Mobile full-screen unit" ], "buyingModels": [ "CPM", "CPC", "Engagement or CPA model when events are validated" ], "targeting": [ "App or site placement", "Device and orientation", "Geography and language", "Session stage and schedule", "Frequency and recency" ], "metrics": [ { "name": "Viewable impressions", "definition": "Visible full or expanded units" }, { "name": "Engagement rate", "definition": "Qualified interactions ÷ impressions" }, { "name": "Close rate", "definition": "Dismissals ÷ impressions" }, { "name": "Conversion rate", "definition": "Validated outcomes ÷ eligible visits" } ], "deliveryFlow": [ "Eligible transition", "Frequency check", "Creative load", "Visible or interactive state", "Close, click or conversion event" ] }, "popunder-cpv-ads": { "name": "Popunder and CPV advertising", "category": "Performance display", "definition": "A popunder opens a destination in a secondary browser context behind the active page. The user typically encounters it after closing or moving away from the original window, which makes source transparency, browser behavior, timing and frequency essential.", "deployment": { "kind": "Traffic placement", "solution": "xml-ad-network", "nexus": "Popunder JS support is available in the XML / JSON module, with publisher script, frequency and delay configuration, feed routing, source controls and click / commercial reports.", "requires": "A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative." }, "availability": "Popunder JS support is available in the XML / JSON module", "placements": [ "Publisher page interaction", "Direct-link campaign", "Feed-backed destination", "Multi-site rotation where explicitly configured" ], "buyingModels": [ "CPV — cost per valid view", "CPM in some supply contracts", "Campaign-specific bid or publisher payout" ], "targeting": [ "Country and region", "Browser and operating system", "Device class", "Publisher, site and source", "Time and frequency" ], "metrics": [ { "name": "Valid views", "definition": "Accepted destination opens" }, { "name": "Unique rate", "definition": "Unique users or devices ÷ views" }, { "name": "Frequency", "definition": "Views per user or device" }, { "name": "Post-view outcome", "definition": "Validated action after exposure" } ], "deliveryFlow": [ "Publisher interaction", "Eligibility and cap check", "Destination selection", "Secondary window opens", "View and outcome tracking" ] }, "mobile-performance-ads": { "name": "Mobile CPA, CPI and CPL advertising", "category": "Performance advertising", "definition": "Mobile performance advertising pays for a defined outcome rather than exposure alone. The ad can use several creative formats; what defines the model is the validated event—an action, installation, lead, sale or deployment-specific conversion.", "deployment": { "kind": "Outcome-based workflow", "solution": "affiliate-tracking-platform", "nexus": "CPA offers, publisher access, conversion windows, caps, click-ID tracking and fixed or revenue-share payouts.", "requires": "An advertiser conversion integration with an agreed event and postback contract. No mobile attribution SDK, MMP or cross-device model is implied." }, "availability": "Core Nexus CPA workflow", "placements": [ "Mobile web campaign", "In-app inventory", "Offer or comparison page", "Affiliate and performance source" ], "buyingModels": [ "CPA — cost per action", "CPI — cost per install", "CPL — cost per lead", "CPS — cost per sale where agreed" ], "targeting": [ "Country and region", "Mobile OS and version", "Device class or supported brand", "Publisher and sub-ID", "Schedule, click and conversion caps" ], "metrics": [ { "name": "Conversion rate", "definition": "Validated outcomes ÷ eligible clicks" }, { "name": "CPA", "definition": "Spend ÷ validated actions" }, { "name": "Install rate", "definition": "Validated installs ÷ clicks" }, { "name": "ROAS", "definition": "Attributed value ÷ spend" } ], "deliveryFlow": [ "Partner click", "Targeted offer or store", "User completes event", "Postback validation", "Attribution, reporting and payout" ] }, "contextual-domain-ads": { "name": "Contextual advertising and domain monetization", "category": "Context monetization", "definition": "Contextual and domain advertising derive intent from a page, site or domain rather than a conventional user search. The operating challenge is to preserve the source, extracted context and selected demand route so relevance and quality remain explainable.", "deployment": { "kind": "Contextual placement", "solution": "xml-ad-network", "nexus": "Contextual ads for direct advertisers, plus Search / XML feed components and source rules for contextual and domain traffic integrations.", "requires": "Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context." }, "availability": "Contextual ads for direct advertisers, plus Search and XML feed workflows", "placements": [ "Contextual unit inside an article", "Site-specific recommendation module", "Parked-domain landing template", "Category or keyword results page" ], "buyingModels": [ "CPC", "Revenue share", "CPM for supported display inventory" ], "targeting": [ "Approved site or domain", "Keyword and category", "Geography and language", "Device and browser", "Publisher, placement and feed profile" ], "metrics": [ { "name": "Coverage", "definition": "Contexts that return eligible demand" }, { "name": "CTR", "definition": "Clicks ÷ delivered results" }, { "name": "RPC", "definition": "Revenue per accepted click" }, { "name": "Source quality", "definition": "Performance by site, domain or keyword" } ], "deliveryFlow": [ "Page or domain context", "Keyword and category policy", "Eligible feed selection", "Rendered ads or landing template", "Click and source reporting" ] }, "web-push-ads": { "name": "Web Push notifications", "category": "Browser notifications", "definition": "Web Push is a notification delivered through a browser push service after a visitor subscribes. It uses a browser subscription and service worker rather than an ad slot inside the current page. Nexus includes publisher subscription workflows and Web Push delivery components.", "deployment": { "kind": "Browser notification", "solution": "web-push-platform", "nexus": "The available Push Subscribers module for direct publishers, with website management, subscriber inventory, subscription workflows and Web Push delivery components.", "requires": "Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service." }, "availability": "Push Subscribers is available for direct publishers; configured delivery integration required", "placements": [ "Browser / operating-system notification surfaces on supported devices", "Publisher websites for subscription collection" ], "buyingModels": [ "Partner-agreed impression or click pricing", "Outcome tracking only with a connected conversion integration" ], "targeting": [ "Subscribed publisher audience", "Supported publisher and delivery-service rules", "Browser eligibility and subscription status" ], "metrics": [ { "name": "Subscribers", "definition": "Track subscription activity and the audience available to the configured service." }, { "name": "Impressions & clicks", "definition": "Review notification events supported by the delivery integration; sending is not proof that a user saw an ad." }, { "name": "Revenue", "definition": "Compare the commercial results recorded for the connected publisher operation." } ], "deliveryFlow": [ "Visitor permission", "Browser subscription", "Configured notification", "Push-service delivery", "Subscriber & event reports" ] }, "in-page-push-ads": { "name": "In-page push placements", "category": "On-page advertising", "definition": "In-page push is a notification-style ad rendered inside a webpage. Despite its name, it is not a browser push notification: it does not use a browser push subscription or service-worker delivery. Nexus has selected provider adapters that distinguish Push and InPage demand.", "deployment": { "kind": "On-page placement", "solution": "xml-ad-network", "nexus": "Selected provider feed adapters with separate Push and InPage modes.", "requires": "A supported provider and compatible publisher renderer. This is not Web Push and does not imply a universal Nexus in-page widget." }, "availability": "Selected feed adapters and compatible publisher placements", "placements": [ "Notification-style units inside compatible publisher websites", "Provider-supported in-page inventory" ], "buyingModels": [ "Provider-agreed click or impression pricing", "Downstream conversion reporting where integrated" ], "targeting": [ "Request fields accepted by the provider", "Supported source, geo and device controls", "Placement and partner traffic policies" ], "metrics": [ { "name": "Requests", "definition": "Requests sent to the selected in-page demand integration." }, { "name": "Clicks", "definition": "Clicks recorded through the configured tracking path." }, { "name": "Partner results", "definition": "Revenue and NET figures where provided by the partner reporting contract." } ], "deliveryFlow": [ "Publisher placement", "Supported feed request", "Eligible provider response", "On-page rendering", "Click & partner reports" ] }, "direct-link-ads": { "name": "Direct links for XML traffic", "category": "Performance traffic", "definition": "A direct link routes publisher traffic through the XML / JSON module to a configured demand destination. It defines a traffic path rather than a visual creative. Source rules, destination configuration and click reporting remain part of the XML workflow.", "deployment": { "kind": "Tracking path", "solution": "xml-ad-network", "nexus": "Direct link support is available in the XML / JSON module, with publisher traffic routing, configured demand destinations, source controls and click reporting.", "requires": "Approved publisher traffic, configured XML demand and a working destination. A link does not itself create a popunder. CPA conversion and payout rules do not define this XML routing path." }, "availability": "Direct link support is available in the XML / JSON module", "placements": [ "Approved publisher links and calls to action", "Configured XML demand destinations using agreed traffic sources" ], "buyingModels": [ "Partner-agreed XML traffic commercial terms", "Platform capacity is billed separately under the XML plan" ], "targeting": [ "Supported XML country and device rules", "Publisher approval and feed eligibility", "Request and click controls" ], "metrics": [ { "name": "Requests", "definition": "Inspect traffic entering the configured XML route." }, { "name": "Clicks", "definition": "Review clicks associated with the publisher and demand source." }, { "name": "Revenue", "definition": "Compare recorded XML results and configured partner reporting." } ], "deliveryFlow": [ "Publisher link", "XML routing", "Eligible demand", "Configured destination", "Click & source reporting" ] } }, "operatingCapabilities": { "reporting": "A request, a reported impression and a partner-confirmed result are different things. Nexus gives each channel its own reporting vocabulary, with breakdowns that help you investigate traffic, delivery and commercial performance. Channel-specific measures: Search coverage, XML valid requests, RTB win rate, video completion and CPA conversions answer different questions. Work with the measures relevant to the product you operate. Dimensions with a purpose: Investigate results by the source and request attributes available in each report. The breakdown may be a search keyword, an RTB bundle or a video application environment. Partner NET reporting: Search, XML and RTB administration expose partner NET reporting fields. Configure the supported provider adapter and its update settings before comparing local and partner-reported results. Your working report: Report templates and a column chooser let operators arrange the available fields for their routine analysis. CSV export is available in the reporting interface. A separate financial overview: The financial dashboard provides background snapshots on a five-minute cycle. It is an overview, not a promise that every partner feed or channel metric refreshes at that interval. From exceptions to investigation: Requests with errors, invalid traffic and differences between local and NET figures give the team a starting point. Review the relevant partner and configuration before changing delivery rules. Report fields and dimensions vary by channel. Data freshness depends on the service and provider update settings. A difference in local and NET counts is not, by itself, evidence of fraud or a billing error.", "trafficQuality": "Network signals: Datacenter, crawler, attack-source, fake-crawler, Tor, scraper, VPN and proxy categories are available in the relevant resource editors. Request consistency: XML controls include duplicate/fast clicks, JavaScript, cookies, referrer, user-agent, iframe and headless-browser checks. Explicit exceptions: Use supported source, domain, publisher, creative and IP lists to express policy at the correct resource level. Evidence after configuration: Review invalid traffic and error dimensions alongside delivery and financial indicators. No filter guarantees perfect detection.", "feedAndBidManagement": "Search providers expose feed URLs, revenue share, search caps, targeting and NET reporting settings. XML feeds expose result limits, timeouts, minimum bids, QPS, click limits and daily budgets. Affiliate-to-feed mappings define access. Do not assume the same bid controls exist in every module.", "partnerOperations": "The Push Subscribers module is available now for direct publishers. Manage publisher websites, browser subscriptions, subscriber inventory, subscription settings and notification activity with publisher reporting. Web Push requires browser permission, valid subscriptions and configured website and delivery services. It is distinct from an in-page push ad; a publisher record alone does not enable delivery. Push Subscribers is available for direct publishers. Manage publisher websites, approvals, browser subscriptions, subscriber inventory and performance in a connected workflow. Keep commercial relationships separate from delivery configuration. Website administration: Manage the publisher, website name, URL, description and account status. Approval and suspension controls make the status of a website explicit. Welcome notifications: Configure a welcome notification with a title, destination link and message text. Treat the notification content as part of the publisher experience. Subscription behavior: Set the subscription trigger, time frame, delay and prompt behavior. Advanced options include persistence until a click, where configured for the integration. Postbacks and redirects: Configure a subscription postback and the redirects associated with subscribed and not-subscribed outcomes. Validate the destination and integration before launch. Push Subscribers inventory: Inspect first and last activity, website and source identifiers, country, language, browser, OS and subscription status. The inventory also exposes impression, click and revenue fields. Publisher reporting: Review request validity, initialization, subscriber activity, impressions, clicks, closed notifications and revenue. Break down the available reports by account, country, OS and browser. Subscription and notification delivery require a configured service endpoint and a validated website integration. Available controls do not remove browser restrictions, user permission requirements or the publisher’s consent responsibilities.", "advertiserOperations": "Advertiser self-serve is available now for direct advertisers. Advertisers can manage their campaigns, creatives, targeting, budgets, funds and account balance in the advertiser workspace, with reporting and operator-defined access. Funding methods and payment-provider configuration depend on the deployment. Funds and balance management do not imply a particular payment gateway, instant settlement or public access to account balances. Bring display, native, contextual, video, popunder and push campaigns together. Direct advertisers manage creatives, targeting, budgets, funds and account balance in a self-serve workspace, with reporting across their configured delivery channels. CPC and CPM buying: Buy traffic by click with CPC or by thousand impressions with CPM. Popunder workflows also expose CPV bidding. Set the bid, daily and total budgets, frequency cap and schedule for the selected campaign type. Campaign media spend is separate from the Nexus platform subscription and its capacity-based pricing. Delivery schedule: Configure the campaign’s schedule alongside its budget and audience. Review the intended delivery window before activating a campaign. Detailed audience selection: Define geographic, operating system, browser and browser-version targeting. Use the available campaign fields to narrow the traffic that matches the objective. Source-level controls: Manage IP, domain, publisher, SubID, keyword and feed eligibility with the available allowlists and blocklists. Source controls make exclusions explicit. Creative inventory: Browse creative records with their advertiser, campaign, type, status and dimensions. Keep the asset associated with the campaign it belongs to. Creative content and tracking: The creative editor separates basic information, tracking and media. Configure the name, status, width, height, click URL, impression pixel and asset as required by the format. Self-serve funds and balance: Direct advertisers can manage funds and view their account balance in the advertiser workspace, alongside their campaigns and reports. Available funding methods and payment-provider setup are configured for the deployment; no particular gateway or instant settlement is implied. Formats and delivery channels: Run direct campaigns with display and HTML banners, native and contextual ads, video, popunder, Web Push and in-page push. Connect eligible traffic through Push delivery, XML / JSON feeds and OpenRTB. The creative format defines the experience; the delivery integration connects it to compatible publisher inventory. Match the campaign to the inventory, creative specification and tracking contract. Video requires a compatible player; native and rich-media placements need a matching renderer. Web Push requires permission and valid subscriptions, unlike in-page push. Prebid.js and Prebid Server integrations are available; configure compatible versions, adapters and endpoints for the deployment.", "contextualAndDomains": "Multi-format direct campaigns are available now for direct advertisers: display and HTML banners, native and contextual ads, video, popunder, Web Push and in-page push. Manage CPC (cost per click) and CPM (cost per thousand impressions) buying models, with delivery across Push, XML / JSON and OpenRTB traffic. Campaigns, creatives, targeting and budgets stay in the advertiser workspace. CPC and CPM describe media buying, not the Nexus capacity subscription. XML / JSON and OpenRTB are delivery integrations, not creative formats. Match each campaign to compatible inventory, creative assets, tracking and, where required, a player or publisher renderer. Web Push requires permission and valid subscriptions. Search feeds expose keyword and keyword-replacement controls. Publisher search links support feed assignment, search type, backfill and source macros. Reporting includes domain, keyword-list and keyword-count dimensions. Domain-parking and landing-page integrations must be scoped and validated separately.", "customEngineering": "Requirements-led AdTech product development, partner and protocol integrations, operational dashboards, data services, infrastructure automation and MCP-enabled AI interfaces." }, "mcp": "Nexus exposes a Streamable HTTP MCP server at /mcp. AI clients can discover product knowledge, inspect capabilities and request deployment recommendations through typed, read-only tools.", "security": "Public website, member workspace and public MCP clients do not receive database or Redis credentials. Members can register with a confirmed email and password or explicitly choose Google registration. New accounts receive no platform assignments or administrator privileges; administrators assign platform access separately. Passwords use salted scrypt hashes. Email verification and password-reset tokens are stored as hashes, expire after 30 minutes and can be used only once. Transactional mail uses the configured SMTP relay or Resend; SMTP requires verified TLS, and configuration alone does not prove delivery. Google sign-in verifies email and subject binding with state and PKCE protection. A non-admin without an existing Nexus account must explicitly register; Google sign-in does not replace an existing password account. Successful password or Google sign-in first issues a separate 10-minute pre-auth challenge. Authenticator 2FA is recommended: an unenrolled account may explicitly continue with primary assurance, while an enrolled account must provide RFC 6238 TOTP or a single-use recovery code and cannot skip the factor. Unique TOTP seeds use AES-256-GCM encryption at rest, accepted counters block replay, attempts are throttled and ten 80-bit recovery codes are retained only as keyed hashes. Trusted-origin checks and current database roles protect private APIs. Viewers receive concise read-only data only for assigned platforms; managers receive safe operational detail for those assignments; administrators have global control. Password resets, Google identity binding and role, platform-scope or account-status changes invalidate older sessions. System administrator sign-in remains Google-only and requires a current server-side session, admin role and exact email allowlist match; administrators are strongly advised to enable 2FA. Platform credentials use explicit environment-secret references, inputs are bounded, agent requests follow an SSRF-resistant DNS and TLS policy, and remote Redis access is limited to documented application hashes.", "targeting": "Nexus models targeting and traffic policy through request context (referrer, language, user-agent and sub-ID), hosting and iframe filters, duplicate and IP request controls, Search/XML QPS and price/filter settings, global XML ceilings, per-member QPS and caps, OS/browser reporting flags, channel schedules and governed endpoint-to-server mappings. Exact enforcement depends on the connected revenue engine and enabled deployment configuration." } ## Operator knowledge ### What is OpenRTB? A practical guide for AdTech operators Understand the OpenRTB request lifecycle, supply and demand roles, auctions, QPS and the operational controls required around the protocol. OpenRTB is an open protocol for exchanging bid requests and bid responses between advertising systems. The protocol defines the message contract; a production platform still needs routing, validation, capacity controls, reporting and commercial policy. The request lifecycle: A publisher or SSP creates a bid request describing an impression opportunity. An exchange or routing layer validates it, selects eligible demand endpoints and waits within a bounded auction window. DSPs return bids, the auction chooses an eligible result and the delivery path records notices and outcomes. Supply request validation, Demand endpoint selection, Auction timeout boundary, Bid and win visibility What the protocol does not solve: OpenRTB does not decide which commercial relationships are valid, how much QPS a partner may send, which filters protect inventory or how operators investigate loss reasons. Those responsibilities belong to the platform operating around the bidstream. How Nexus approaches OpenRTB: Nexus places tenant configuration, demand routes, QPS governance, endpoint mappings and operational visibility around the auction service. The objective is a bidstream commercial and technical teams can reason about together. https://www.nexus-soft.org/resources/what-is-openrtb ### SSP vs DSP vs ad exchange: choosing the operation you need Compare SSP, DSP and OpenRTB exchange responsibilities, follow an illustrative buying decision and scope a Nexus deployment around actual partners and requirements. Start with who you serve and which decision you need to control. A publisher needs a route to eligible demand. An advertiser needs a way to buy suitable opportunities. A network connecting the two needs partner access, trading rules and comparable reports. These responsibilities can share infrastructure, but they are different operating products. Supply-side platform: An SSP represents publisher inventory and helps connect available opportunities to buyers. In a deployment discussion, identify the publisher or supply relationship, the inventory allowed into the system and the downstream parties eligible to receive it. Access to a protocol endpoint does not by itself establish the commercial right to trade that inventory. Publisher integration, Inventory policy, Supply quality, Outbound QPS Demand-side platform: A DSP serves advertiser buying requirements: which campaign may buy, from which supply, under which targeting, budget, creative and measurement rules. Nexus describes its DSP option as an integration-scoped combination of campaign management and the RTB runtime. The advertiser interface, bidding strategies, attribution, billing and specific exchange access must be validated separately. Campaign eligibility, Audience and context, Budget control, Bid decision Ad exchange: An exchange connects supply and demand relationships and applies the agreed trading rules. The Nexus exchange workflow exposes exchange connections, demand connections, demand grants, inventory rules and trading reports. The OpenRTB protocol standardizes communication between inventory suppliers and buyers; it does not supply publisher contracts, demand relationships or an advertiser business model. Illustrative decision: exchange or DSP?: Imagine a network with two approved supply partners and three contracted demand endpoints. Its first need is to decide which demand may receive each source and investigate traffic and trading results: begin with exchange scope. If its customers instead need to create campaigns, upload creatives and buy from a defined set of exchanges, begin with DSP scope. These fictional partner counts describe a planning exercise, not a Nexus customer or included partner bundle. Exchange brief: supply access, demand grants, supported formats and reporting ownership., DSP brief: advertiser workflow, campaigns, creative review, buying connections and event definitions., Combined brief: document both roles and the boundary between the campaign and trading workflows. Validate the message and timing contract: The IAB OpenRTB 2.6 specification defines tmax as the time the exchange allows for receiving bids, including network latency. That deadline is an input to integration design, not a Nexus speed guarantee. Agree on the protocol version, required context, creative formats, no-bid behavior, delivery events and expected response timing with each partner. Test representative accepted, rejected, slow and unavailable paths before increasing traffic. Record the fields the supply actually sends and those the buyer requires., Keep bid responses, delivery events and commercial reconciliation as separate checkpoints., Treat a version selector as configuration evidence; confirm interoperability with partner tests. Bring one concrete workflow to evaluation: A useful evaluation begins with a redacted traffic example, the partners already available to you, the first supported format and the operator who will investigate failures. Ask to follow that example through configuration and reporting. For a DSP, also show the intended advertiser journey. This reveals integration work and missing responsibilities earlier than comparing a long list of product labels. https://www.nexus-soft.org/resources/ssp-vs-dsp-vs-ad-exchange ### The OpenRTB request lifecycle from supply to win notice Trace OpenRTB requests from validation to reporting. Use a synthetic worked example to separate incoming requests, demand attempts, no-bids and selected bids. A request lifecycle is more useful than a feature checklist because it shows where latency, filtering, commercial rules and failures enter the system. Receive and validate: The supply request must be structurally valid and acceptable to tenant policy before it consumes downstream capacity. Invalid or unsupported opportunities should produce understandable outcomes. Contract validation, Required context, Inventory policy, Source identification Select and route: Eligible demand endpoints are chosen using availability, capacity, configured policy and the request context supported by the connected auction service. Observe the outcome: Response rate, bid rate, auction result, timeout and notice behavior create the operational evidence needed to tune routes and partner expectations. Worked example: follow requests without counting them twice: Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. Start with an authored batch of 1,000 incoming requests: 80 invalid, 120 not eligible for the selected routes and 800 routed. Assume one impression opportunity per incoming request, two eligible demand endpoints per routed request and at most one acceptable bid per partner response. The 1,600 outgoing attempts yield 940 explicit no-bid responses, 420 acceptable bid responses, 160 timeouts and 80 invalid responses. Separately, 320 of the 800 routed auctions have a selected bid and 480 do not. These are synthetic worksheet categories, not a Nexus export schema or measured outcomes. 420 / 1,600 = 26.25% acceptable bids per outgoing attempt; 320 / 800 = 40% selected bids per routed auction. These are not CTR or delivered fill. No elapsed time establishes QPS; selection proves neither delivery nor revenue., The two-endpoint assumption is not a routing guarantee or an included demand bundle. Prebid integration and a commercial relationship with a buyer are not established by this example. https://www.nexus-soft.org/resources/openrtb-request-lifecycle ### QPS governance for advertising infrastructure Learn how platform, channel, partner and endpoint limits protect infrastructure and commercial commitments. Queries per second is not only a server metric. In AdTech it is also a contractual and commercial boundary between supply, routing infrastructure and demand. Why one global limit is insufficient: Search and XML workloads have different request shapes, economics and delivery paths. Nexus therefore models independent channel QPS values and supports member-level QPS structures for XML operations. Platform boundary, Channel boundary, Member boundary, Service capacity Caps versus QPS: QPS limits instantaneous rate. A cap limits volume over a longer operating or commercial period. Both may be required to prevent a fast source from consuming an entire allocation. Governed configuration: Nexus keeps limits in validated tenant configuration and approved runtime records rather than exposing Redis or service credentials to the browser. Illustrative incoming and outgoing traffic: Suppose 1,000 incoming requests per second are each routed to two eligible partners, producing 2,000 outgoing requests per second. This is illustrative arithmetic, not a customer result, a routing promise or a performance benchmark. Nexus prices the incoming QPS, not the sum of incoming and outgoing traffic. For QPS-priced modules, capacity billing is based on incoming QPS. Outgoing QPS is unlimited for this billing calculation only; technical capacity, partner limits and configured operating caps still apply. This billing statement does not remove the separate daily click limits for XML / JSON feeds and OpenRTB. This does not redefine Search or CPA daily-capacity pricing., Check each partner’s own rate limits and integration contract before increasing fan-out. Daily clicks are a separate capacity limit: For XML and OpenRTB, 1,000 incoming QPS allows a maximum of 10,000,000 clicks per day; 2,000 QPS allows 20,000,000. Each module and each location has its own limit. Unused capacity in one location does not cover another. This XML/RTB daily click rule is not a Video plan limit. XML / JSON feeds and OpenRTB each have a maximum of 10,000,000 clicks per day for each 1,000 incoming QPS block, independently per module and per location. At 2,000 incoming QPS, that module in that location has a maximum of 20,000,000 clicks per day. These limits cannot be pooled across modules or locations. This daily click limit applies only to XML / JSON feeds and OpenRTB, not VAST Video; Search and CPA keep their separate daily-capacity pricing. This is a plan limit, not an automatic technical stop. Higher daily click volumes require a capacity increase. Reaching the limit currently triggers no automatic action; arrange the capacity change with Nexus. https://www.nexus-soft.org/resources/qps-governance ### Supply quality filtering without a black box Understand request-context, environment, duplicate and source controls used to protect advertising traffic. A filter should have an owner, an input signal and an explainable result. An unexplained rejection rule makes partner support and commercial reconciliation unnecessarily difficult. Available request context: Nexus models referrer, language, user-agent and sub-ID participation in XML request workflows. The connected engine determines how enabled signals are enforced. Referrer, Language, User agent, Sub-ID Environment controls: The Video channel editor groups network-risk controls for datacenters, crawlers, Tor, VPN and proxy traffic. Other modules expose their own environment checks; the configuration guide below explains Video channel policy, not iframe filtering or a universal policy for every module. Repetition controls: Duplicate-request policy, IP request ceilings and global maximum requests help protect delivery from repeated or excessive behavior. https://www.nexus-soft.org/resources/supply-quality-filtering ### XML feed monetization: build and validate an ad-network workflow Plan XML feed mapping, QPS, daily click limits and reporting. Compare a worked US/EU capacity example using published prices and clearly labeled test inputs. An XML ad network connects publisher traffic with agreed advertiser feeds. The operating challenge is to make each relationship explicit: which source may request results, which demand may answer, what context must survive the connection, which limits apply and how both parties will measure the outcome. XML describes a data format; it does not establish a universal feed schema or guarantee demand access. Start with the publisher and demand contract: List the approved publisher source and the advertiser feed it will use. Agree on required request context, result fields, click tracking, timeouts and reporting responsibility before connecting them. Nexus provides affiliate integration settings, provider/feed configuration and explicit affiliate-to-feed assignments. A provider name or XML URL is not proof that an adapter accepts every variation of that provider’s response. Publisher identity and source/SubID conventions., Provider response fields, image/icon requirements, result count and timeout., Commercial agreement, accepted traffic types and reporting update window. Illustrative mapping: one source, two feeds: Suppose publisher Cedar has two sources, search-panel and news-widget. Feed A accepts the approved search traffic; Feed B has a separately agreed contextual integration. Write those relationships into a planning matrix before configuration. Mapping a feed to Cedar does not automatically prove that every Cedar source is eligible. Check the available resource-level targeting and the provider contract for each path. These names are fictional planning labels, not real integrations or Nexus API parameters. Cedar / search-panel → Feed A → agreed search response and click contract., Cedar / news-widget → Feed B → separately validated contextual delivery., Unexpected source → investigate identity and eligibility before enabling demand. Separate eligibility, rate and commercial limits: Nexus XML feed editors expose geographic, device, domain, keyword, carrier and subscriber-age targeting where the integration supplies the relevant context. Limits include maximum requests/QPS, daily budget, click ceilings, repeated-click rules and result expiry. These controls answer different questions. A rate limit bounds request flow, a click cap bounds counted activity and a budget constrains the commercial allocation. Their configured values are not a published hosting-capacity guarantee. Exercise the route before increasing traffic: Use synthetic or appropriately redacted samples to check a valid response, an empty response, malformed data, a timeout and a repeated click. For each case, agree on the expected result and the report or integration log that will demonstrate it. Inspect provider settings and affiliate mapping independently. Confirm parser behavior, tracking and fallback handling with the actual adapter; this guide does not define a copy-and-paste production request. Valid path: the intended source reaches the approved feed with required context intact., Empty or slow path: the agreed response and any configured backfill can be explained., Invalid or repeated activity: the selected controls are tested with both legitimate and rejected samples. Read both sides of the reporting relationship: Begin with the same date range, affiliate, feed and available SubID or domain breakdown. Compare requests, valid requests, errors, coverage, clicks and revenue before looking at imported NET fields. Nexus exposes affiliate-side and feed-side reports and separate provider NET import settings. A difference may reflect timing, attribution, filtering or scope; it is not sufficient evidence of fraud or a billing error. A useful handover has explicit acceptance checks: Document who owns each connection, which samples passed, which limits were agreed, the provider update window and the escalation path for a mismatch. Keep pending integrations and unsupported placements visible. Pop, contextual and push delivery require their corresponding provider and delivery setup; enabling XML alone does not enable every advertising format. Bring the first source and demand agreement to discovery so the initial network can be scoped concretely. Illustrative capacity across two locations: For one platform with XML at 1,000 incoming QPS in US and 2,000 in EU, with no optional add-ons, capacity costs $1,500 per month. The first full month totals $3,000, including the one-time $1,500 platform setup. This is an illustrative configuration, not a customer result or a traffic guarantee. US: $500/month; maximum 10,000,000 clicks/day. EU: $1,000/month; maximum 20,000,000 clicks/day. These are separate location limits, not a shared 30-million-click pool., RTB, Video, Search and CPA receive no capacity from this XML allocation; each selected module is priced separately., Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised., The example assumes unchanged capacity for a full month. QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge. Worked example: when clicks change the XML allocation: Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. For a synthetic planning day, assume US peaks at 760 incoming QPS with 11,200,000 clicks, and EU peaks at 1,350 incoming QPS with 8,400,000 clicks. Starting with US 1,000 / EU 2,000 QPS costs $1,500/month, but US exceeds its separate daily click allowance. US 2,000 / EU 2,000 QPS satisfies both planning inputs at $2,000/month. These are independently priced locations on one XML platform, not pooled capacity or measured customer traffic. At the full-month rates, one $1,500 platform setup fee makes the initial first month $3,000 and the revised first month $3,500; no add-ons. Hosting, white-label and taxes are included. The daily click limit currently triggers no automatic action; arrange a capacity increase., Meeting these authored planning inputs is not a throughput, availability or traffic guarantee. Outgoing QPS is not added to the incoming-QPS bill; technical and partner limits still apply. https://www.nexus-soft.org/resources/xml-feed-monetization ### XML vs JSON advertising feeds Compare XML and JSON feed contracts, operational tradeoffs and normalization requirements. XML and JSON can carry equivalent business information, but their schemas, parsing behavior and partner conventions differ. The platform should isolate those differences from downstream commercial logic. XML feeds: XML remains common in search and affiliate advertising because it supports established schemas and broad partner compatibility. It can also introduce inconsistent nesting and field conventions. Established partner contracts, Explicit document structure, Schema variation JSON feeds: JSON is compact and natural for API-oriented services, but a JSON response is not automatically standardized. Field names and commercial semantics still require a contract. Normalization as the boundary: Nexus exposes provider feed configuration and affiliate-to-feed mappings. Schema conversion, parser behavior and response compatibility must be confirmed for each partner integration; they should not be inferred from the presence of an XML or JSON URL. https://www.nexus-soft.org/resources/xml-vs-json-feeds ### Affiliate sub-ID tracking and partner-level traffic analysis Use sub-identifiers to distinguish sources, placements and commercial performance beneath a partner account. A single affiliate or member may aggregate many traffic sources. Without a sub-ID contract, poor and strong sources collapse into the same reporting row. Preserve source context: Nexus can require or preserve sub-ID context in XML request configuration. Naming and allowed values should be agreed with the partner before launch. Source, Placement, Campaign reference, Partner-defined segment Apply policy at the correct level: Member limits protect the account boundary while sub-ID reporting helps operators investigate quality and performance beneath it. Avoid identity ambiguity: Sub-IDs should not be treated as authenticated identity. They are request context and must be validated and interpreted within the partner contract. https://www.nexus-soft.org/resources/affiliate-subid-tracking ### Duplicate request protection for feed traffic Why repeated advertising requests distort delivery, capacity and reporting—and how explicit controls reduce the impact. Duplicate traffic can consume QPS, create repeated results and make partner reconciliation difficult. The correct response depends on request identity and the commercial agreement. Define a duplicate: A duplicate rule needs a time window and a stable request signature. Overly broad matching can suppress legitimate repeat intent; overly narrow matching protects nothing. Source context, Query or intent, IP and user agent, Time window Layer the controls: Global duplicate policy can be combined with IP request ceilings, member QPS and maximum-request boundaries. Keep the outcome explainable: Operators need to distinguish filtered duplicates from upstream errors, empty demand and capacity rejection. https://www.nexus-soft.org/resources/duplicate-request-protection ### What is VAST video advertising? Understand VAST responses, wrappers, media assets, tracking and the controls around web, app and CTV delivery. VAST is a contract between an ad-serving response and a video player. It describes creatives, tracking and additional demand hops, but it does not guarantee successful playback. VAST response: A response may contain an inline creative or a wrapper that points to another VAST document. Each hop adds dependencies, tracking and potential latency. Inline creative, Wrapper URI, Media files, Tracking events Delivery environments: Web, mobile applications and connected TV devices have different player capabilities and inventory context. Environment policy should be explicit. Nexus operating model: Nexus connects VAST service endpoints, tenant modules, delivery diagnostics and commercial visibility inside the same control plane. https://www.nexus-soft.org/resources/vast-video-advertising ### VAST wrapper diagnostics and timeout analysis Trace VAST wrapper chains and timeout boundaries. Compare synthetic document-fetch timings without confusing HTTP redirects, media loading or player errors. A video opportunity can fail at any demand hop, during media selection or inside the player. A useful diagnostic path preserves enough context to locate that boundary. Follow the wrapper chain: Operators should see the sequence of wrapper URLs, response status and time spent at each hop. Wrapper depth, Endpoint response, Elapsed time, Final creative Classify errors: Transport failures, malformed VAST, unsupported media and player errors are different problems and should not share one generic failure label. Protect the playback window: Timeouts must reflect the user experience and the remaining delivery budget, not only the preference of an upstream demand partner. Worked example: isolate wrapper document latency: Synthetic worked example. All traffic counts and timings below are authored test inputs, not customer data, measured platform performance or promised results. This synthetic manual worksheet follows three fictional VAST documents at example.com: start.xml, partner.xml and creative.xml. Authored sequential fetch durations of 90, 140 and 220 ms add to 450 ms. Against an illustrative 1,000 ms document-resolution budget, that leaves 550 ms before parsing, media download and player work. A slow variant changes the last fetch to 820 ms: total 1,050 ms, 50 ms above the same assumed budget. These are not measured requests, live VAST endpoints or a Nexus latency promise. A VAST wrapper is not an HTTP redirect. Test Links exposes HTTP redirect chains, final URL, timing and screenshots; this worksheet does not establish VAST parsing or successful playback., The example.com addresses are inert labels, not links to execute. The 1,000 ms budget is an explicit educational assumption, not a product default, SLA or recommendation for every player. https://www.nexus-soft.org/resources/vast-wrapper-diagnostics ### Web, app and CTV video inventory: operational differences Compare delivery context, player constraints and policy needs across major video environments. A single VAST workflow can serve multiple environments, but a production platform should not pretend their device, identity and playback behavior is identical. Web video: Browser and page context are available, but autoplay policy, iframe placement and browser support can affect playback. Browser context, Page placement, Autoplay policy Mobile application video: App inventory depends on SDK or player integration and application/device context that differs from browser requests. Connected TV: CTV has long-form viewing contexts, device fragmentation and strict media compatibility needs. Environment-aware policy prevents inappropriate demand paths. https://www.nexus-soft.org/resources/web-app-ctv-video ### MCP for AdTech: making advertising infrastructure understandable to AI Understand Nexus public MCP discovery, tools, resources, connection steps and the separate permission boundary for private platform operations. Model Context Protocol (MCP) connects AI applications to server capabilities. Nexus public MCP helps clients find product facts and plan deployments; it does not connect advertiser accounts, reveal live reports or authorize campaign changes. Choose the right connection: Use https://www.nexus-soft.org/mcp for read-only public product discovery over Streamable HTTP. Private operational connections have separate authorization; their tools depend on the server, modules and identity. Website registration does not grant administrator rights or platform assignments. Public discovery: products, pricing scope, formats and integration requirements., Private operations: verify server, identity, platform scope and permitted action., Never send passwords, tokens, personal endpoints or customer exports to public discovery. Understand tools, resources and prompts: MCP distinguishes callable tools, readable resources and reusable prompt templates. Nexus offers get_product_capabilities and paginated get_public_knowledge search, plus nexus://products/catalog and nexus://knowledge/public resources. The solution-discovery prompt helps plan a deployment; it does not create infrastructure. Use advertised input schemas rather than guessing dashboard fields. Initialize, discover, then request information: Start with initialize to negotiate version and capabilities, then notifications/initialized. Discover capabilities through tools/list, resources/list and prompts/list. The specifications below explain this sequence. A referenced version is not a claim that every optional MCP feature is implemented by Nexus or supported by every client. Confirm client transport support and use the canonical HTTPS endpoint., Inspect capabilities and schemas before calling tools., Handle protocol and tool errors; a failed call proves no capability. Illustrative discovery: planning an XML network: With publisher traffic and advertiser agreements in place, inspect get_product_capabilities for feeds. Use get_public_knowledge to find XML mapping, limits and reporting guidance, then compare sources and scope before requesting a deployment recommendation. This is a planning example, not a recorded customer session or provider test. Ask which XML controls exist and what the provider must confirm., Expect sourced capabilities and outstanding integration questions., Do not expect a created feed, changed budget or private report. Treat operational access as a separate decision: For an operational connection, discover its own tools and permissions. Before sensitive changes, inspect targets and proposed values and obtain the required approval. Descriptions and read-only hints are not authorization controls. Public Nexus tools expose no arbitrary database queries, Redis access or code execution. Keep the answer connected to evidence: Nexus public facts come from the website’s product, service and resource content, with source pages and scope boundaries. Separate educational examples from verified controls and deployment commitments. MCP does not eliminate model mistakes, prove partner compatibility or promise autonomous optimization. Ask Nexus to validate undocumented requirements. Free external MCP versus in-platform AI: Connect your Nexus platform to ChatGPT and other compatible MCP clients with no Nexus integration fee. The paid in-platform AI add-on is not required. Third-party AI client subscriptions and AI provider fees are not included and may apply separately. Connection availability depends on your client, account and workspace settings; platform access still requires authorization. Additional Fraud Filters: $100 per month per platform, with one free month from activation. Additional traffic-quality checks beyond the standard platform filters: datacenters, known attack sources, Tor, VPN, crawlers and fake crawlers, web scrapers and proxies. These checks do not guarantee detection of all invalid traffic. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation. Test links: $100 per month per platform, with one free month from activation. Inspect the final URL, redirect chain, redirect timing and screenshot for a test link. Select the referrer, country, device profile and browser engine for the test. The add-on is billed once per platform, not separately for each module or location. $100 per month; the first month is free from add-on activation. In-platform AI: $500 per month per platform, with one free month from activation. AI inside your Nexus platform, with model usage included in the add-on price. This tariff is for AI inside a customer's platform, not the public product guide on this website. The add-on is billed once per platform, not separately for each module or location. $500 per month; the first month is free from add-on activation. https://www.nexus-soft.org/resources/mcp-for-adtech ### How an AI client connects to Nexus MCP A practical connection model for compatible AI clients using the Nexus Streamable HTTP MCP endpoint. A compatible client connects to the public MCP endpoint, initializes a protocol session and discovers the tools, resources and prompts advertised by the server. Connection endpoint: The Nexus MCP endpoint is available at /mcp and uses Streamable HTTP. Production clients should use the canonical HTTPS domain. Initialize, List capabilities, Call approved tool, Read structured result Discovery before action: Clients should inspect tool schemas rather than guessing parameter names or scraping button labels from the website. Bounded capability: Public MCP tools focus on product understanding and solution design. Connected operational deployments expose their own tools behind authentication, domain scope and server-side authorization. Available actions depend on the selected server, enabled capabilities and account permissions. https://www.nexus-soft.org/resources/connect-ai-client-to-nexus ### Nexus MCP security model How Nexus separates public product knowledge, authenticated operations and private infrastructure. AI-native does not mean giving a model unrestricted database or Redis access. It means presenting a deliberate application contract that an AI client can understand. Public knowledge boundary: Product overview, targeting controls and deployment guidance can be public because the same information is visible in product documentation. Typed inputs, Read-oriented outputs, No arbitrary database query Application authorization: Connected operational deployments apply authenticated roles, tenant boundaries and server-side authorization. Their rate limits, approval requirements and audit capabilities depend on the exposed tool and deployment policy. Public product tools do not grant access to private operations. Infrastructure isolation: Redis and database credentials remain inside server-side connection managers. Approved Redis access is limited to keys derived from configured services. https://www.nexus-soft.org/resources/mcp-security-model ### AI-ready AdTech platform checklist Evaluate whether an advertising platform is truly AI-operable or merely contains a chat widget. A chat interface is not an integration contract. An AI-ready platform needs structured knowledge, discoverable operations, bounded permissions and outputs that operators can verify. Knowledge: Publish stable product definitions, route-specific documentation, schemas and explicit limitations. Product catalog, Glossary, API schemas, Versioned documentation Operations: Expose typed tools with narrow responsibilities instead of generic code or database execution. Governance: Apply authentication, tenant authorization, rate limits, auditability and human approval to sensitive write operations. https://www.nexus-soft.org/resources/ai-ready-adtech-checklist ### Build vs buy an AdTech platform Compare building, buying and extending an AdTech platform with a practical cost worksheet, ownership checklist and a bounded pilot decision. Start with the operating decision you need to own: accepting a publisher, routing a request, enforcing a commercial limit or reconciling a partner report. Compare ways to deliver that same workflow using the same traffic assumptions. A feature list or monthly software price alone cannot describe the engineering, partner and support work required to operate it. Build internally: Building can fit when the workflow itself is a competitive advantage and your team can own its maintenance. Estimate the work after the first successful request: partner adapters, access control, reporting definitions, incident response, upgrades and operator tools. Name the people who will maintain each part when a partner changes its response or a key engineer is unavailable. Internal ownership gives design freedom; it does not remove delivery or operational dependencies. What behavior must be unique, and what can follow an existing contract?, Who owns protocol changes, security fixes and production support?, Which acceptance checks demonstrate the complete workflow, including failure paths? Buy disconnected tools: A specialist tool can fit a clearly bounded requirement. Check the interfaces between tools as carefully as their individual features: which system owns publisher identity, caps, accepted events and final statements? Ask for sample exports and error cases before committing. A lower subscription may still leave your team maintaining adapters and investigating differences between reports. Compare replacement and exit effort as well as initial connection work. List the source of truth for accounts, configuration and financial records., Confirm export formats, retention and access to records after the contract ends., Assign responsibility when two connected systems disagree. Build on Nexus: Nexus provides Search, XML/JSON feeds, OpenRTB, Video and CPA modules with shared operating controls. Evaluate the module that fits the first workflow, then identify the integrations and custom work needed around it. A compatible protocol does not supply demand contracts or guarantee every partner adapter. Use the deployment and product pages to distinguish available controls from items that need agreement, implementation or an acceptance test. Compare costs over one agreed planning period: Use the same period and workload for each option. Record initial implementation and migration, recurring platform charges, your own engineering and operations time, separately contracted partner services, and eventual transition costs. Keep one-time and recurring amounts separate. For Nexus, use the current pricing calculator: capacity is scoped by module and, for incoming QPS, by location. Published hosting, white-label and applicable taxes are already included; do not add them again. Custom work or an SLA requires an explicit agreement. Initial work: requirements, adapters, configuration, test cases, migration and training., Recurring work: the quoted platform scope, internal staffing and any separately required third-party services., Change and exit: future integrations, data exports, contractual notice and migration responsibilities., Use your own amounts and assumptions; this worksheet does not predict savings or return on investment. Turn the comparison into a pilot decision: For an illustrative evaluation, choose one approved publisher source and one compatible demand route. Document an accepted request, an ineligible request, an empty response and a timeout, then identify the report that explains each result. Agree on who can configure the route and who can stop the test. Score each option against these same requirements, marking untested items as open. Expand only after the responsible teams accept the evidence; no fixed launch date or production performance follows from this example. Record the required outcome, its evidence, its owner and any unresolved dependency., Carry the selected module, capacity assumptions and integration list into the pricing enquiry. https://www.nexus-soft.org/resources/build-vs-buy-adtech ### White-label AdTech platform architecture Plan a white-label AdTech platform with a branding checklist, module and partner requirements, access boundaries and practical launch acceptance checks. A white-label platform needs a clear agreement about what your customers see and what your team operates. Start with the audience, the revenue workflow and the branded surfaces they will use. Domain names and a logo are one part of the brief; partner access, traffic contracts, reporting and support responsibilities determine whether the service is ready for use. Tenant identity: Nexus platform configuration includes a domain, description, status and public URLs. Prepare a branding inventory for the agreed deployment: public site, member or partner workspace, authentication pages, notifications and any documents or reports customers receive. Confirm each surface in the proposal and preview it before launch. White-label branding is included in the published platform tariff; a requested workflow or interface extension may require separately agreed development. Supply approved names, logos, domain ownership and the intended audience for each surface., Assign responsibility for DNS, certificates, email sender configuration and renewal., Confirm which templates and interfaces are included, and which require additional work. Module composition: Choose modules by the transaction you need to operate. Search handles search-provider and publisher-link workflows; XML/JSON feeds handle feed and affiliate mappings; OpenRTB handles programmatic request paths; Video uses VAST delivery contracts; CPA handles offers and conversion-related workflows. Define the publisher and advertiser experience separately. A branded platform does not automatically include every ad format, buying strategy, payment integration or demand relationship. Map each promised customer workflow to a module and a confirmed integration., Keep incoming QPS capacity separate for each applicable module and location., For Search and CPA, use the published daily search or incoming-click capacity units. Private infrastructure: Nexus keeps database, Redis and private-service configuration behind authenticated server workflows. A brand or domain is not an authorization boundary by itself. Establish the accounts and roles required for your deployment, confirm which platform each account can access, and test that another platform or an unauthorized role cannot read its records. Agree on credential ownership, operational access and recovery responsibilities without exposing secrets in the branding brief. Agree on commercial and support ownership: State who approves publishers, contracts with demand partners, investigates traffic-quality disputes and reconciles local and partner reports. Define support contacts, escalation, maintenance communication and any required service commitment in the agreement. The published price includes hosting, white-label branding and applicable taxes, but it is not a universal SLA or a promise of traffic, revenue or access to a named advertising partner. Identify the owner of customer terms, privacy information and operational support., Specify report definitions, currencies, timezones and partner update delays., Confirm export, retention and transition requirements before onboarding customers. Accept the complete branded journey: Use an illustrative test account with prepared data to follow the agreed journey from entry and sign-in to its assigned workflow, report and support path. Check the correct identity on each surface and exercise denied access as well as a successful operation. Validate actual request and response behavior with the configured partner. Record outstanding items before launch; a preview or screenshot demonstrates a visible interface, not traffic delivery or financial performance. Verify domain, certificate, links, approved branding and the configured notification path., Confirm account scope, permitted actions and the explanation of report values., Record acceptance evidence, unresolved integrations and the owner of the launch decision. https://www.nexus-soft.org/resources/white-label-adtech-platform ### AdTech platform evaluation checklist A practical checklist covering products, targeting, integrations, security, operations, AI readiness and deployment. A strong evaluation follows a request from source to commercial outcome. Feature counts alone do not reveal hidden integration work or operational boundaries. Traffic and products: List active channels, request formats, partner volumes, QPS, caps and expected expansion. Search, Feeds, OpenRTB, Video, CPA Controls and evidence: Identify which system owns targeting, filters, routes, commercial terms and the reporting used for reconciliation. Security and deployment: Confirm tenant isolation, credential boundaries, roles, audit events, production validation and failure behavior. Choose the module from the operating workflow: Choose Search for query/feed and publisher-link operations; XML for publisher-to-feed mapping and feed controls; OpenRTB for supply/demand bid routing; Video for VAST delivery; and CPA for offers, incoming clicks, postbacks and conversions. A response encoded as XML or JSON does not by itself determine which product you need. Validate the actual partner workflow. XML / JSON feeds: $500/month per 1,000 incoming QPS in each location., OpenRTB: $500/month per 1,000 incoming QPS in each location., VAST Video: $500/month per 1,000 incoming QPS in each location., Search Syndication: $500/month per 100,000 searches per day., CPA / CPI / CPL: $500/month per 100,000 incoming clicks per day. Compare a complete platform quote: State the module, each QPS location, the required daily volume and the optional add-ons. Compare the same incoming-only measurement and period across quotes. Do not assume a competitor uses a particular charging rule without checking its terms. You can order any number of separate platforms. Each platform has its own capacity charges, selected add-ons and one-time setup fee. Each selected add-on is charged once per platform, not once per module or location. One calculator configuration represents one platform., Setup is $1,500 once per platform, not per month, module or location. It is separate from monthly capacity and add-on charges and is included once in the first-month total shown by the calculator., Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised. Changing capacity during the month: QPS capacity can be increased or decreased at any time in the published increments. Charges are prorated for the time each capacity is active. The calculator shows full-month rates, not a partial-period invoice or an automatic overage charge. Confirm the effective date of a capacity change when comparing a partial-month invoice with a full-month estimate. https://www.nexus-soft.org/resources/adtech-platform-evaluation-checklist ### Migrating from fragmented or legacy AdTech services Plan an AdTech migration with dependency mapping, reporting reconciliation, a bounded traffic cutover and an explicit rollback and data-recovery checklist. Define the first traffic path to move and the evidence that will show it works. A migration must preserve more than a reachable endpoint: partner identities, request fields, accepted events, reporting periods and operating responsibilities all need an agreed destination. This guide is a planning framework; migration scope, tools, downtime and recovery depend on the actual systems and partner contracts. Inventory the current path: Trace one source through its endpoint, parser, routing rules, delivery or tracking events and reports. List dependent databases, caches, scheduled imports and external callbacks, with a responsible owner for each. Record identifiers, field types, timezones, currencies and retention needs. Keep credentials in their approved secret store; an inventory should reference their owner and purpose rather than copy their values into a shared document. Traffic contracts: required fields, accepted sources, timeouts, limits and response semantics., Data contracts: account and partner mappings, historical records, exports and reporting definitions., Operations: service URLs, DNS ownership, dependencies, maintenance contacts and change windows. Choose the first boundary: Select a source or channel whose eligibility, volume and commercial responsibility can be bounded. Identify how traffic will reach the destination and how it can return to the previous path. Confirm provider approval and compatibility before moving requests. A Nexus module does not imply a ready-made importer for an arbitrary legacy database; field mapping, adapters and historical-data migration require explicit scope and validation. Name the traffic cohort, destination, partner approvals and cutover owner., Mark dependencies that must move together and those that can remain temporarily., Agree on a stop condition and the person authorized to act on it. Validate before expansion: Rehearse with synthetic or appropriately redacted samples. Cover valid and invalid requests, absent demand, timeouts, repeated tracking events and permission failures. Compare reports for the same cohort, period and definitions; local counts and partner NET imports may update at different times. Do not duplicate live auctions, clicks or billable events merely to compare systems. Any replay or parallel observation needs an agreed method that avoids double delivery and accounting. Document the expected outcome and evidence for each test case., Reconcile missing, duplicated and late events before accepting the sample., Treat interface availability and successful HTTP responses as partial checks, not complete delivery evidence. Cut over with a bounded observation window: Where the routing and partner setup allow it, begin with a limited traffic cohort and observe it before increasing exposure. Agree on the measurements and tolerances in advance: request errors, timeouts, accepted outcomes and reporting discrepancies for that cohort. Google’s SRE canary guidance explains this general release technique; it is not evidence that Nexus supplies automatic traffic splitting or rollback for your deployment. If traffic cannot be divided safely, agree on a maintenance window and a different acceptance plan. Capture the active configuration and approved destination before the switch., Keep the earlier path available for the agreed recovery window when technically feasible., Compare like-for-like traffic and account for partner reporting delay before increasing exposure. Plan rollback separately from data recovery: Write down the exact trigger, decision owner and steps to restore the previous traffic route. Also determine what happens to records created after cutover: changing routing alone does not undo new conversions, payments, configuration changes or data transformations. Test backup restoration and any reconciliation procedure before depending on them. Agree on acceptable data loss and recovery time for this migration; this guide provides no default guarantee of zero downtime or reversible database changes. Check that the previous service still accepts the required contracts and configuration., Decide whether writes must pause and how new, pending and late records will be reconciled., Keep recovery artifacts protected and record the outcome of the rehearsal. Close the handover before retiring the old path: For an illustrative XML migration, the handover might name one publisher source, its approved demand feed, the retained SubID convention and the reports used to compare accepted clicks. Add the actual observation period, discrepancies and sign-off owners when evidence exists. Retire the earlier endpoint only after callbacks, partner imports, access, retention and recovery needs have been resolved. These are planning steps, not a recorded customer migration or an included fixed-price service. Confirm operational contacts, monitoring ownership and the escalation procedure., Preserve required historical records and remove obsolete access through the agreed process., Bring the dependency inventory and acceptance criteria to a scoped deployment or migration enquiry. https://www.nexus-soft.org/resources/legacy-adtech-migration ### Search Syndication: feeds, publishers and commercial control Set up a search syndication workflow with separate provider feeds and publisher links, query and SubID context, traffic eligibility, search caps and NET reconciliation. Search syndication connects a publisher’s search experience to approved advertising demand. The useful starting point is one query from one source: identify the publisher link, the eligible provider feed, the request context and the reports that will explain the result. Nexus supplies operating software; provider access, traffic approval and commercial agreements remain separate requirements. Connect supply to multiple demand feeds: Keep provider feeds and publisher links as distinct records. The provider feed holds the advertiser, search engine, feed URL, search cap, revenue share and NET reporting settings. The publisher link selects feeds and holds its own integration type, cap, backfill and commercial settings. Before connecting either, confirm the provider’s actual request and response contract and the traffic approved for it. 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. Feed-level keyword replacement and provider settings are separate controls. Check country, browser/version and device requirements in the relevant editor rather than assuming link and feed fields are interchangeable. The adjacent configuration guide explains the relationship; it does not apply or recommend traffic settings. Illustrative trace: preserve the original source: Imagine a fictional publisher, Cedar, sending the query hiking boots from its mobile-search source. In a planning record, keep the publisher link, SubID, original query, selected provider and any configured keyword transformation together. Confirm which URL macros the provider supports and test the transmitted values. These labels are explanatory; they are not a live request, a Nexus parameter schema or permission to send traffic to a search provider. Original intent: hiking boots from Cedar / mobile-search., Eligibility check: the configured link, domain, keyword and device rules., Demand check: the assigned provider and its accepted traffic contract., Outcome check: response, local searches/clicks and later partner-reported figures. Make commercial policy explicit: Search feed and link editors expose revenue-share and search-cap settings. A publisher-link cap and a provider-feed cap protect different relationships; document which resource owns each value. XML feeds have separate minimum-bid, QPS, click and budget controls. Do not copy an XML limit checklist onto Search or interpret a configured traffic limit as a plan entitlement. Agree on the meaning and reset behavior of each cap during validation. Diagnose an empty result in a useful order: Start with the selected link and source context, then inspect feed assignment, targeting, traffic-quality rules, caps and provider availability. Distinguish an intentionally ineligible query from an integration error or an eligible query with no demand. Test the configured backfill path independently. Increasing a cap cannot fix a malformed provider request, and changing keyword rules without preserving the original query can make later investigation harder. Check one known eligible sample and one intentionally ineligible sample., Exercise an empty response and a provider failure with agreed expected outcomes., Record the relevant settings and report filters so another operator can repeat the investigation. Reconcile technical and commercial evidence: Review the same date range, publisher/link and feed before comparing searches, monetized activity, clicks, revenue and partner NET results. Use Keyword List or Keyword Count and available domain/device breakdowns to localize a difference. NET import timing and metric definitions depend on the provider. A local search, a monetized result and a paid click are different observations; confirm the denominator of EPC, RPM and coverage with the report definition before presenting them as a business result. Scope the first launch around evidence: Bring one approved provider, one publisher traffic pattern, the supported query/tracking contract and a target reporting question to the evaluation. Agree on integration tests, commercial ownership and the handover process before expansion. The goal of the first walkthrough is to show that the team can explain a traffic path and its outcome, not to infer guaranteed demand or revenue from a configured feed. https://www.nexus-soft.org/resources/ppc-search-syndication-platform ### Click fraud filters for PPC and feed traffic A practical model for bot, proxy, IP, domain, referrer, iframe and repeated-request controls without turning traffic quality into a black box. Traffic protection is most useful when every rule has a known input, scope and outcome. A generic fraud score cannot replace the operational controls needed to investigate a publisher, feed or source. Layer deterministic controls: IP and subnet policy, banned-domain checks, referrer validation, iframe rules and request-rate boundaries provide explainable first-line protection. They can be applied globally or, where the connected engine supports it, scoped to a particular feed. IP and subnet policy, Domain and referrer checks, Iframe and environment rules, QPS, caps and duplicate controls Add behavioral and network signals: Bot confidence, anonymous or transparent proxy indicators, unexpected IP changes and source inconsistencies can contribute additional evidence. Detection strength should be tuned against false positives rather than treated as a universal maximum setting. Preserve an operator decision path: Trusted-partner exceptions, blocked-traffic outcomes and human-verification steps need an audit trail. Operators should be able to explain whether traffic was rejected by identity, environment, repetition, capacity or quality policy. https://www.nexus-soft.org/resources/click-fraud-filters-adtech ### Feed, bid and limit management for search advertising How feed profiles, result limits, timeouts, allowed targets, custom bids and publisher exceptions create a controllable demand layer. Demand feeds do not have identical schemas, response times, commercial terms or traffic acceptance. Treating them as interchangeable endpoints hides the decisions that determine margin and delivery quality. Configure the feed contract: Each connection needs an understood parser, timeout, result limit, eligible targets and commercial behavior. Reusable feed profiles help teams apply a tested operating pattern across approved partners. Parser and schema, Timeout boundary, Result limit, Allowed targets Define eligible feed traffic: Use the XML feed Targets tab for geographic, device, browser, domain, carrier, keyword and subscriber-age criteria. Match the enabled criteria to the request context and traffic contract supported by that provider. Control bids and volume at the right level: Platform ceilings protect infrastructure, feed limits protect provider contracts and publisher ranges protect commercial relationships. Individual exceptions should be deliberate, bounded and visible to the team responsible for reconciliation. Route in parallel without losing governance: Parallel provider requests can improve coverage, but only when they remain inside latency, QPS and eligibility boundaries. The response path still needs deterministic ranking, deduplication, error classification and reporting. https://www.nexus-soft.org/resources/feed-bid-limit-management ### Publisher and affiliate management for AdTech platforms Design partner onboarding, account levels, access profiles, suspension, balances, caps and payout workflows around clear operating responsibility. A partner portal is not only a registration screen. It is the boundary where identity, traffic permissions, feed access, commercial terms and operational support meet. Approve access deliberately: Applications can be reviewed before activation, assigned an account level and connected only to the traffic types and feed profiles appropriate to the agreement. Signup date, source IP and account context provide useful review evidence. Approval and rejection, Account levels, Traffic-type permissions, Feed profiles Respond without destroying history: Suspension should stop or restrict traffic while preserving the account, configuration and evidence required to resolve a problem. Search by identity, level or active feed helps operators find the relevant relationship quickly. Separate payout workflow from delivery: Balances, payout requests, processing periods, minimum thresholds and fees belong to a controlled financial workflow. Exact payment methods and legal requirements depend on the deployment and commercial agreement. https://www.nexus-soft.org/resources/publisher-member-management-adtech ### Direct advertiser campaign management inside an AdTech platform Plan direct advertiser campaigns with budgets, schedules, audience rules, creative assets and tracking, and distinguish campaign setup from a DSP deployment. Direct campaigns connect an advertiser, budget, audience and creatives to agreed inventory. Nexus provides campaign and creative editors; delivery depends on the channel and integration. Configure the workflow, then validate its outcomes. Set the commercial and scheduling boundaries: The reviewed editor exposes a CPV bid, daily and total budgets, frequency capping, a conversion-tracking switch and scheduling. Inventory includes all-campaign and pending-approval views. Fields and billing models are workflow-specific, not universal across Search, Video, RTB and CPA. Name the advertiser, permitted users and approval owner., Set commercial limits and the delivery window., Define the tracking objective and accepted event. Target with supported request evidence: Target geography, operating systems, browsers and versions. Available source allowlists and blocklists cover IP ranges, domains, publisher IDs, SubIDs, keywords and feeds. Check that the integration supplies the required context and how missing fields are handled. Targeting does not replace publisher approval of creatives or traffic. Prepare the creative and its measurement path: Creative records identify advertiser, campaign, type, status and dimensions. The editor separates basic details, tracking and media: width, height, click URL, impression pixel and asset. Match the format and supply requirements. A tracking URL or conversion switch is configuration evidence, not proof of delivered, attributed or accepted events. Illustrative acceptance check: one campaign, one source: For fictional Spring Demo, agree on one source, creative, target country and bounded test allocation. Exercise eligible, excluded-source and out-of-schedule requests against the delivery and reporting path. This is a test plan, not a Nexus API request, a customer result or a budget-enforcement guarantee under concurrent traffic. Eligible: verify creative, destination and recorded events., Excluded or out of schedule: check rule enforcement., Budget or frequency boundary: agree on counting and timing, then test., Missing event: investigate integration and reporting before changing commercial records. Campaign management is not the whole DSP: DSP Deployment is an integration-scoped combination of campaigns and the RTB runtime. Validate supply access, creative acceptance, advertiser experience, automated bidding, attribution and billing separately; an editor provides no universal exchange access. CPA offers are also a distinct workflow with conversion windows, payout models, caps and publisher permissions. Hand over an observable workflow: Keep configuration, approved creatives and test results together. Compare channel reports using the same period, advertiser and campaign; distinguish local activity from partner results and their update timing. Assign creative review, event investigation and spend reconciliation. Use the Nexus demo to confirm modules and outstanding integration work. https://www.nexus-soft.org/resources/direct-advertiser-campaign-management ### Contextual advertising and domain parking operations How site approval, keyword extraction, categories, landing templates and feed routing support contextual and parked-domain monetization. Contextual and domain traffic both begin with page or domain context rather than a conventional search box. Sustainable monetization requires explicit ownership of the source, extracted intent and final demand route. Operate contextual publisher inventory: Publishers register approved sites and placements, while operators moderate eligibility and define how keywords are selected. Page metadata, site-specific terms, categories and defaults can contribute context when the integration supports them. Site approval, Placement or banner configuration, Keyword and category policy, Feed eligibility Manage parked domains as inventory: A parking workflow connects approved domains through nameserver or redirect patterns to controlled landing templates. Domain ownership, template selection, keywords and categories should remain visible to both support and commercial teams. Keep intent and delivery explainable: Extracted keywords are inputs, not guaranteed user intent. Reporting should distinguish the source domain or site, applied context, selected feed and delivered result so quality issues can be investigated rather than averaged away. https://www.nexus-soft.org/resources/contextual-ads-domain-parking ### Mobile performance platform for CPA, CPI and CPL campaigns Work through CPA, CPI and CPL offer setup, an illustrative conversion postback, repeated events, conversion windows, caps and advertiser/publisher payout reconciliation. A performance offer needs an agreed outcome before it needs traffic. An installation, registration, approved lead and purchase are different events with different acceptance rules. Nexus exposes offer configuration, conversion windows, approval controls, caps and reporting; the actual tracking and postback contract must be validated with the partners involved. Support outcome-based price models: Define the accepted event, the evidence required to accept it and when it becomes payable. Nexus offer settings include fixed-price or revenue-share terms, currency, advertiser and publisher payouts, event category and conversion-window controls. An event received from an advertiser is not automatically a settled publisher payment. Agree on pending, rejected and repeated-event handling before a source is approved. Offer identity, tracking destination and accepted event., Conversion window and pending/multiple-conversion policy., Advertiser payout, publisher payout, currency and reconciliation responsibility. Apply offer and partner boundaries: Publisher access, traffic eligibility and caps are separate controls. Nexus exposes private offers, approval and terms requirements alongside geographic, device, carrier, SubID, domain and IP-range targeting. Daily and monthly limits can apply to clicks, conversions and revenue. A publisher who can see an offer is not thereby eligible for every traffic source, and an available cap does not override an offer’s conversion rules. Illustrative postback: follow one event: In a fictional test, click demo-click-17 belongs to offer sample-install and publisher Cedar. The advertiser later reports event demo-event-42 as an installation. The integration test should verify the click-to-offer relationship, the agreed event, the conversion window and the resulting report state. These labels are illustrative records, not Nexus field names, endpoint parameters or a production API example. Use the actual partner contract to construct a request. Known click + accepted event + valid timing → check the configured acceptance or pending outcome., Unknown click or wrong offer → check the agreed rejection or investigation path., Same event delivered again → verify the agreed repeat-event behavior before counting it twice. Test retries and conversion windows independently: A repeated delivery of one event is different from a second legitimate event on the same click. Document the event identifier, allowed event types and the intended multiple-conversion policy. Exercise an on-time event, an event outside the window, a delayed retry and a temporary endpoint failure. Authentication, acknowledgement, retry limits and duplicate handling are integration requirements to verify, not guarantees inferred from the presence of a postback URL. Check the cap boundary before launch: For an illustrative test allocation of ten accepted events per day, prepare cases just below, at and above the agreed boundary. Confirm which status counts toward the cap, the timezone used for the reset and what happens to a late event or concurrent arrival. Ten is a fictional test value, not a recommended offer setting or included Nexus quota. Validate the implemented behavior with the configured offer and partner before routing production traffic. Reconcile conversions with the commercial record: Use the same offer, publisher, period, currency and acceptance status on both sides. Nexus reports include valid/invalid conversions, advertiser and publisher payouts, profit and source details. Investigate a missing event by its click and event context before changing a payout. A useful handover records the sample cases, their expected outcomes, the reporting window and who resolves disagreements. No example in this guide is a customer result or an attribution guarantee. Platform capacity is not the offer payout: An illustrative CPA configuration with 200,000 incoming clicks per day costs $1,000 per month, or $2,500 for the first full month including platform setup, with no optional add-ons. This is not a price per day, per conversion or a publisher payout. It is not a customer result or a promise of conversions. Purchased daily incoming-click capacity and an offer’s conversion cap are different limits. The ten-event example above explains an offer workflow, not the purchased platform capacity., Search uses daily searches, not CPA clicks. Do not convert either daily volume into a QPS entitlement., Published USD prices are final and include hosting, white-label branding and applicable taxes, with no hidden fees. Any additional work must be priced and agreed upfront. The in-platform AI add-on also includes model usage; no unlimited-token allowance is promised. https://www.nexus-soft.org/resources/mobile-performance-platform-cpa-cpi-cpl