NEXUSAD PLATFORM
Sign inBook a demo

Publisher operations

Give every publisher a clear place in your network.

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.

Book a guided walkthrough ↗Explore the capabilities ↓
  1. 01Publisher website
  2. 02Approval & integration
  3. 03Subscription rules
  4. 04Activity & reporting

Inside the workflow

The controls behind your daily workflow.

Explore the settings and reports behind the headline, then review the configuration your deployment needs.

01

Website administration

Manage the publisher, website name, URL, description and account status. Approval and suspension controls make the status of a website explicit.

02

Welcome notifications

Configure a welcome notification with a title, destination link and message text. Treat the notification content as part of the publisher experience.

03

Subscription behavior

Set the subscription trigger, time frame, delay and prompt behavior. Advanced options include persistence until a click, where configured for the integration.

04

Postbacks and redirects

Configure a subscription postback and the redirects associated with subscribed and not-subscribed outcomes. Validate the destination and integration before launch.

05

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.

06

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.

Inside the operation

Explore Publisher operations in operation.

Choose a stage to see its controls. This is a workflow explanation; explore the actual platform in a demo.

Publisher operationsWorkflow
01 / Publisher propertyWebsiteOwnership · status
02 / NexusConfigure
  • Approval
  • Subscription rules
  • Postbacks
03 / Delivery serviceIntegrationEndpoint · Push URL
Possible outcomes
SubscribedorNot subscribed
04 / REVIEWRequests · Valid requests · Errors
Define the experience

Configure notification text, subscription prompts, redirects and postback destinations.

  • Prompts
  • Redirects
  • Postbacks
A subscriber record is not proof of delivery or monetization. Browser permission and validated integration are required.Workflow illustration, not a live account. 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.

See it with your team.

Bring your operating requirements. We will walk through the current interface and the relevant configuration, integrations and reporting controls.

Book a demo ↗

A day in the platform

From setup to a decision.

A practical workflow for your publisher operation, with the relevant controls at each step.

  1. 01

    Register the website

    Associate the site with its publisher and review its URL, description and account status.

  2. 02

    Define the experience

    Configure notification text, subscription prompts, redirects and postback destinations.

  3. 03

    Validate the integration

    Confirm the delivery service and Push URL are configured, then test the approved integration in a controlled environment.

  4. 04

    Review the activity

    Inspect subscriber records and publisher statistics before adjusting the site’s configuration.

Reporting that fits the channel

Compare traffic, quality and commercial results.

Keep delivery, traffic quality and commercial results in context. Available dimensions depend on the selected report.

Explore reporting & data freshness ↗

Performance indicators

  • Requests
  • Valid requests
  • Errors
  • Initializations
  • Subscribers
  • Impressions
  • Clicks
  • Invalid clicks
  • Closed
  • CTR
  • CPC
  • Revenue

Ways to break it down

Publisher account · Country · Operating system · Browser

Deployment scope. 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.

Know before you launch

Useful distinctions.
Clear expectations.

Good operations start with a shared understanding of what is configured, what is measured and what needs validation.

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.

The connected operation

Keep the rest of the workflow in view.

01 / Operations

Reporting & reconciliation

Channel metrics, source breakdowns and partner NET figures — explained in their own context.

Explore the workflow ↗02 / Operations

Push Subscribers & publishers

Direct publisher websites, subscription settings, subscriber inventory and reporting.

Explore the workflow ↗03 / Operations

Advertiser self-serve

Multi-format direct campaigns, CPC and CPM buying, funds, account balance and reporting.

Explore the workflow ↗

See it with your team

Build a better publisher workflow.

Walk through website onboarding, subscription configuration and reporting with your team’s operating requirements in view.

Plan your demo ↗