{"name":"Nexus","category":"AI-native AdTech infrastructure","heritage":"Nexus Soft AdTech engineering since 2004","website":"https://admin.nexus-soft.org","mcp":"https://admin.nexus-soft.org/mcp","products":{"search":"PPC search syndication with multi-feed orchestration, intent routing, minimum/maximum/custom bid policy, publisher limits, traffic validation, direct advertiser workflows and provider-level reporting.","feeds":"XML and JSON normalization, feed profiles, parser and timeout policy, parallel eligible-feed routing, affiliate permissions, QPS, caps and feed-health diagnostics.","rtb":"OpenRTB request validation, supply policy, QPS governance, demand routing, auction visibility and PMP-compatible flows.","video":"VAST delivery and diagnostics across web, app and CTV with demand-chain and commercial visibility.","cpa":"CPA, CPI and CPL campaigns, mobile targeting, postbacks, event attribution, click or conversion caps, partner payouts and API integration patterns."},"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.","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.","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.","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.","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.","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.","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.","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.","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.","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.","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"]}},"operatingCapabilities":{"trafficQuality":"Explainable IP and subnet rules, banned-domain checks, referrer and iframe policy, bot and proxy signals, IP-change and duplicate controls, blocked-traffic outcomes and trusted-partner exceptions where supported by the connected engine.","feedAndBidManagement":"Provider parser contracts, result limits, timeouts, eligible targets, feed profiles, per-feed limits, minimum/maximum/custom bids, publisher-specific ranges and controlled parallel feed routing.","partnerOperations":"Partner approval, account levels, suspension, traffic-type permissions, feed profiles, QPS, caps, balances and governed payout workflows.","advertiserOperations":"Authorized advertiser access, campaign moderation, minimum bids, catch-all or fallback campaigns, advanced targeting and detailed campaign evidence.","contextualAndDomains":"Approved publisher sites, contextual keyword and category policy, domain-parking connections, controlled landing templates and source-to-feed reporting.","customEngineering":"Requirements-led AdTech product development, partner and protocol integrations, operational dashboards, data services, infrastructure automation and MCP-enabled AI interfaces."},"security":"Public website, private workspace and MCP clients never receive database or Redis credentials. Nexus has no public registration or local password database: an administrator pre-provisions an exact business email, role and platform scope, and unknown Google identities fail closed. Verified Google authentication receives only 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. Google identity linking plus role, platform-scope and account-status changes revoke older sessions. System administrators require a current server-side session, admin role and exact email allowlist match and are strongly advised to enable 2FA. Platform credentials use explicit environment-secret references, inputs are bounded, outbound requests follow an SSRF-resistant DNS and TLS policy, and remote Redis access is limited to documented application hashes."}