Skip to content

Architecture

Understanding how Atheon differs from traditional ad networks is key to a successful integration.

The Problem with Traditional Ads

Traditional ad networks rely on Client-Side Decisioning.

  1. Your site loads.
  2. An iframe script runs in the browser.
  3. It bids, fetches an image, and forces your content to jump around ("Layout Shift") to make room for a banner.
  4. This ruins the user experience, especially in an immersive AI interfaces.

The Atheon Solution: Server-Side Decisioning

Atheon moves the heavy lifting to the server. We call this our Hybrid Architecture.

flowchart TD
    User[User] -->|Asks a question| Frontend[Frontend]

    %% Logic Layer (Server-Side)
    Frontend -->|User Query| Backend[Backend]
    Backend -->|User Query + LLM Response| Atheon[Atheon Services]

    Atheon -->|Intent analysis and ad injection| Backend
    Backend -->|Single text string: Answer + Ad| Frontend

    %% Presentation Layer (Client-Side)
    Frontend -->|Render via Markdown or HTML| UI[Rendered Content]
    UI -->|Wrapped in atheon-container| Container[Atheon Container]

    Container -->|Scroll visibility triggers| Analytics[Impression Analytics]

1. The Logic Layer (Server-Side)

When your user asks a question, your backend calls the Atheon Services before returning the response to the user.

  • Input: User Query + LLM Response.
  • Process: Atheon analyzes the intent and injects a relevant text-based ad unit directly into the content stream.
  • Output: A single string of text containing both your answer and the ad.

2. The Presentation Layer (Client-Side)

Your frontend receives the text just like any other message. There is no heavy ad script blocking the thread.

  • Rendering: You display the text using your standard Markdown or HTML renderer.
  • Analytics: You wrap the text in our <atheon-container>. This component watches the scroll position and reports an "Impression" only when the ad is actually readable by the user.

Why this matters

  • Zero Layout Shift: The ad is part of the text. It flows naturally.
  • Privacy First: PII is scrubbed on your server before it reaches us. We target based on intent, not user cookies.
  • Ad Block Resistant: Because the content is delivered from your own domain's backend API, it is resilient to standard cosmetic filtering.