{"name":"Nexus","category":"AI-native AdTech infrastructure","heritage":"Nexus Soft AdTech engineering since 2004","website":"https://www.nexus-soft.org","mcp":"https://www.nexus-soft.org/mcp","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. Keep publisher integration details and feed eligibility understandable. 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. 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: Configure UID macros and image or iframe sync URLs. Review synced requests, win rate, impressions, revenue, spend and NET metrics. 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."},"platformSolutions":[{"slug":"xml-ad-network","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"],"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"],"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","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","Use advertiser accounts, campaign budgets, schedules, creatives, moderation and supported targeting. Define the self-service experience and permissions for your brand."],["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":["direct-link-ads","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":"Manage publisher websites, browser subscriptions and notification delivery. Connect the website and delivery services, 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."}],"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 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":"OpenRTB native integration pattern","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":"Feed routing, source controls, quality rules and click / commercial reports for compatible partners.","requires":"A permitted publisher implementation and suitable demand. Browser restrictions determine window behavior; CPV describes the pricing model, not the creative."},"availability":"Nexus Soft heritage; available as custom deployment scope","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":"Search / feed components and source rules for supported contextual and domain traffic integrations.","requires":"Approved publisher domains, a landing or result renderer and compatible demand that accepts the supplied context."},"availability":"Search and feed workflow; deployment-specific","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":"Publisher websites, subscription workflows and Web Push subscription / delivery components.","requires":"Browser permission, service-worker integration, valid subscriptions and the configured notification-delivery service."},"availability":"Publisher subscription workflow; 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 and offer tracking","category":"Performance traffic","definition":"A direct link is a tracked URL that routes a visitor to an eligible offer or campaign destination. It defines a traffic path rather than a visual creative. Nexus CPA click routing and conversion processing can connect that visit to an advertiser-reported outcome.","deployment":{"kind":"Tracking path","solution":"affiliate-tracking-platform","nexus":"Offer destination routing, tracked clicks, conversion matching and postback / payout processing.","requires":"Approved traffic sources, a working offer destination and advertiser conversion integration. A link does not itself create a popunder."},"availability":"Tracked offer destinations and deployment-specific campaign integrations","placements":["Approved publisher links and calls to action","Offer promotions using an agreed traffic source"],"buyingModels":["CPA for an accepted conversion event","Fixed or revenue-share offer payouts"],"targeting":["Supported offer geo and device rules","Publisher approval and offer eligibility","Click and conversion caps"],"metrics":[{"name":"Clicks","definition":"Track visits entering the configured offer route."},{"name":"Conversions","definition":"Match reported outcomes to the original click ID and apply validation."},{"name":"Payouts","definition":"Review recorded partner earnings under the configured offer terms."}],"deliveryFlow":["Publisher click","Tracking identifier","Eligible offer destination","Conversion postback","Validation & payout"]}},"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":"Publisher websites expose account status, approval, suspension, subscription behavior, notification content, postbacks and redirects. Subscriber inventory and publisher reports expose activity and revenue fields. Subscription delivery requires a configured service endpoint and validated website integration.","advertiserOperations":"Campaign configuration includes CPV bid, daily and total budgets, schedule, frequency cap, conversion-tracking switch and audience/source lists. Creative records include advertiser, campaign, status, dimensions, click URL, impression pixel and asset. CPA offers have separate payout, conversion-window, approval and cap controls.","contextualAndDomains":"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."},"operations":{"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":"Find the signal behind the total.","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."]],"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":"Manage publisher websites, approvals, subscription settings, subscriber activity and reporting in Nexus. Explore the workflow and integration requirements.","eyebrow":"Publisher operations","title":"Give every publisher a clear place in your network.","lead":"Manage publisher websites, approval status, subscription settings and performance in a connected workflow. Keep the commercial relationship separate from the delivery and integration details your operations team needs.","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."],["Subscriber 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":"Explore Nexus campaign budgets, schedules, audience rules and source lists, plus creative assets, click URLs, dimensions and impression tracking.","eyebrow":"Campaigns & creatives","title":"Make the setup as clear as the objective.","lead":"Give operators a structured way to configure campaigns, define their audience and manage creative assets. Bring budgets, scheduling, traffic eligibility and tracking fields into the same planning conversation.","accent":"campaign","configurationView":true,"visual":["Campaign objective","Budget & audience","Creative & tracking","Delivery review"],"capabilities":[["Commercial boundaries","The campaign editor exposes a CPV bid, daily and total budgets, frequency capping and a conversion-tracking switch. These are campaign controls, not a universal billing model for every Nexus product."],["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."]],"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":"Campaign and creative fields depend on the selected workflow. Tracking URLs, creative acceptance and conversion recording need integration testing; the presence of a field does not guarantee acceptance by an external partner.","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."}},"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."},"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."}