dlserve docs

Appearance

Integration guide ​

Getting dlserve running on your site takes about five minutes. You'll sign up, create a channel, drop in a one-line snippet, and verify the install. After that, subscribers start flowing in automatically whenever visitors grant the browser push permission.

Step 1 — Sign up ​

Create your account at https://app.dlserve.ai/auth/signup. Enter your name, email address, and a password. Click Create account.

You'll receive a verification email within a few seconds. The link in that email is valid for 24 hours. Click it to confirm your address — without verification your account is read-only.

Step 2 — Create your first channel ​

A channel maps to a single website origin (e.g. https://example.com). After email verification the onboarding wizard opens automatically. If you skip it, you can create a channel any time from Channels → New channel in the dashboard.

Wizard step 1 — Channel details

  • Name — a human-readable label you'll see in reports (e.g. "Example Blog").

  • Origin URL — the exact origin of your site including the protocol and any port. No trailing slash. Example: https://example.com.

  • Opt-in strategy — controls when the browser permission prompt appears:

    • Immediate — prompt fires as soon as the page loads (highest opt-in rate; some browsers may flag as aggressive).
    • Soft-ask first — show a custom bell widget first; prompt fires only after the visitor clicks "Allow" on your widget.
    • Delayed — wait N seconds or until the visitor has scrolled a set percentage before prompting.

    For most publishers, Soft-ask first strikes the best balance between conversion rate and browser-friendliness. You can change this at any time without touching your snippet.

Wizard step 2 — Copy your snippet

Once your channel is saved, the wizard shows your personalised install snippet. It is a single <script> tag with your channel ID baked into the URL.

html
<script src="https://cdn.dlserve.ai/sdk/ch_xxxxxxxxxxxxxxxx.js" async></script>

Place this tag inside the <head> of every page on your site — or in a tag manager if you use one. Position doesn't matter relative to other scripts because of the async attribute, but <head> placement is recommended so the SDK loads as early as possible.

Example <head> with the snippet in place:

html
<!DOCTYPE html>
<html lang="en">
<head>
  <meta charset="UTF-8" />
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
  <title>My site</title>
  <!-- dlserve web-push SDK — one line, that's it -->
  <script src="https://cdn.dlserve.ai/sdk/ch_xxxxxxxxxxxxxxxx.js" async></script>
</head>
<body>
  <!-- your content -->
</body>
</html>

Replace ch_xxxxxxxxxxxxxxxx with the channel ID shown in your dashboard. Every channel has a unique ID — do not share a snippet between two different sites.

Wizard step 3 — Verify the install

After you click Verify, the dashboard pings your origin and checks that:

  1. The snippet is reachable in your HTML (<script> tag present and loading from cdn.dlserve.ai).
  2. The service worker endpoint (/sw/<channelId>.js) returns a valid response from our API.

Both checks must pass before the channel becomes active. If either check fails, see Troubleshooting for the most common causes and fixes.

What happens after install ​

Once the channel is active, visitors who land on your site and grant the browser permission prompt are recorded as subscribers. The SDK handles the entire permission flow — you don't need to write any JavaScript.

The dlserve delivery pipeline then:

  1. Fetches push ads from our ad source on your behalf (server-to-server — the ad provider's domain never appears in your visitors' browser traffic).
  2. Routes the push message through our delivery infrastructure to the subscriber's browser push endpoint.
  3. Tracks delivery, click, and conversion events and makes them available in your reports.

Your visitors see a push notification from your site's name and icon, not from any ad network.

When does the first push arrive? ​

Expect the first push notifications to land roughly 24–48 hours after your first subscribers are collected. The delay exists because:

  • The ad source's fill rate depends on the subscriber's geography and time-of-day window.
  • Our scoring service needs a small number of opt-in signals before it's confident about send timing.

Once the pipeline is warmed up, deliveries run continuously during the time windows your subscribers have historically engaged.

How visitors opt out ​

Subscribers can stop notifications any time without contacting you:

  • Click the bell widget on your site (if you chose Soft-ask) and toggle off.
  • Go to browser settings → Notifications, find your site, and change to "Block" or "Ask".

When a subscriber opts out, dlserve marks the endpoint as unsubscribed and removes their push identifiers within 30 days. You don't need to do anything.

Next: Identify your subscribers to attach your own user IDs and tags, API reference for programmatic access, or FAQ for common questions.