PRODUCT BLUEPRINT / IN DEVELOPMENT

THE PLATFORM / CAPABILITIES

Control the system.
Keep the signal clear.

Explore the planned QLYNK Ads platform: approved-site controls, ad creative management, responsive placements, secure delivery, and clear measurement.

06

Planned capability areas

01

Focused private ecosystem

0

Claims of live ad serving

01
CONTROL / PLANNED

Publisher boundaries first.

Build around websites explicitly approved by the administrator. Hostname normalization, clear subdomain rules, and server-side site/unit checks are part of the planned access model.

  • Website allowlist and status controls
  • Explicit site-to-unit associations
  • Fail-closed behaviour for unapproved sites
02
CREATIVE / PLANNED

Manage the message and the media.

Organise image, GIF, and video creative alongside title, optional subtitle, destination, schedule, and lifecycle status. The first release is not intended to execute arbitrary HTML or JavaScript ads.

  • Draft, active, paused, and archived states
  • Validated media and destination URLs
  • Creative previews and practical fallbacks
03
PLACEMENT / PLANNED

Fit the space without losing the signal.

A single ad can render in more than one unit. Presentation is planned to respond to actual available dimensions instead of assuming every slot has the same space.

  • Wide, square, and vertical formats
  • Title + subtitle, title-only, and micro modes
  • A visible AD disclosure at every size
04
DELIVERY / PLANNED

An integration built for real pages.

A versioned SDK and isolated iframe delivery path are planned to support responsive rendering, lazy loading, duplicate-initialisation protection, and useful empty/error states.

  • Site and unit authorisation on the server
  • Isolated rendering with defensive defaults
  • Dismissal and frequency controls for supported overlays
05
MEASUREMENT / PLANNED

Events that can be explained.

The planned analytics model keeps impressions and clicks separate, attributes each event to its ad, unit, and site, and treats network type, bot classification, and legitimacy as different signals.

  • Distinct impression and click records
  • Date filters, breakdowns, and CTR
  • Unknown and uncertain classifications preserved
06
SECURITY / PLANNED

Guardrails around the moving parts.

Security controls are intended to be enforced by server-side checks, not by hiding buttons in a dashboard or relying on browser-origin headers alone.

  • Email/password plus authenticator TOTP
  • Revocable sessions and rate limits
  • Validated redirects, media, and event payloads

BUILT IN STAGES

The public foundation is here.
The product is still being built.

Feature descriptions are the intended direction, not a representation that these tools are currently available.