dlserve docs

Appearance

FAQ ​

What data does dlserve collect from my visitors? ​

When a visitor opts in to push notifications we collect:

  • The push endpoint URL generated by their browser and the public encryption keys needed to deliver messages to it. We never see the device itself, any contacts, or any content the visitor enters on your site.
  • Approximate location (country and region) derived from their IP address at the moment of opt-in.
  • Browser and operating-system name.

We do not collect email addresses, names, precise GPS location, or browsing history. The push endpoint is an opaque token specific to your site — a subscriber on your site cannot be cross-referenced with a subscriber on another publisher's site.

Do you support iOS Safari? ​

Not yet. Apple's push platform (APNs) requires a separate integration that is outside the MVP scope. iOS Safari support is on the post-MVP roadmap. All major desktop browsers (Chrome, Edge, Firefox) and Android Chrome are supported today.

How is the ad source concealed from my visitors? ​

Every network request your visitors' browsers make goes to a dlserve-owned hostname — not to any upstream ad provider directly. Specifically:

  • The ad fetch is a server-to-server call from our delivery infrastructure; the browser never sees it.
  • Click and pixel tracking URLs proxy through t.<your-domain> before redirecting to the ad endpoint via our concealed subdomain.
  • Push notification image thumbnails load from xml-v4.dlserve.ai, a CNAME we control — the hostname itself does not reveal the upstream provider.

The net result: your subscribers' browser DevTools will show requests to dlserve-owned hosts only. No upstream ad-provider domain or branding is visible at any layer of the browser-observable network traffic.

When do payouts run? ​

Payouts run monthly, typically within the first five business days of the following month. Your earnings for a given month are calculated as:

payout = max(revenue × revenue_share_pct, sends / 1000 × min_cpm)

Both your revenue share percentage and your minimum CPM are set in your publisher agreement. The dashboard shows a running estimate in the Reports section throughout the month.

Can I block specific advertisers? ​

Advertiser-level blocking is not available in the current release. If you have a specific advertiser whose ads are a poor fit for your audience, contact your dlserve account representative — we can apply an exclusion manually on your behalf. Advertiser controls are on the post-MVP product roadmap.

How do I add a second channel? ​

Channels are one-to-one with site origins. If you run more than one site, create a separate channel for each domain:

  1. Go to Channels → New channel in the dashboard.
  2. Run through the same wizard you used for your first channel.
  3. Install the new snippet on the second site. Do not use a snippet from channel A on site B — the channel ID is tied to the origin URL and delivery will break.

Each channel has its own reporting, subscriber base, and opt-in strategy settings.

What if I want to migrate off dlserve? ​

You own your subscriber data. To request an export of your subscribers (push endpoints and associated metadata), contact your dlserve account representative. We provide the export in a standard JSON format that is compatible with other web-push delivery systems. There is no fee for data portability.

Is there a WordPress plugin? ​

There is no dedicated WordPress plugin yet, but the <script> snippet works on any WordPress site. The easiest way to add it is via a plugin that lets you inject code into <head>, such as:

  • Insert Headers and Footers (free, no coding required)
  • WPCode (free tier available)
  • Your theme's functions.php via wp_head action

Paste your snippet into the "header" section of whichever method you choose, save, and then run the verify step in the dlserve dashboard to confirm it loaded correctly.

Didn't find your answer? See Troubleshooting for common install problems, or reach out to your dlserve account representative.