Skip to content

FAQ ​

What data does dlserve collect from my visitors? ​

When a visitor subscribes to your push notifications (in an Android app: when the app first registers the device; in a Windows app: when the person's PC first registers), we store:

  • Their push subscription (web) or push token (Android app): the address we deliver notifications to.
  • Their IP address, and the country and region derived from it.
  • Their browser's user agent. In an Android app: the device model, Android version, app version and the user agent of the device's built-in browser component.
  • Their language and time zone.
  • A random subscriber ID, when they subscribed, and when they were last active.
  • Which ads they were sent, shown and clicked.
  • Your click ID (postback_id), External ID and tags, if you pass them to us.

In a Windows app, we store a random install ID, the Windows version, your app's name and version, the default browser, the language and time zone, the IP address with its country and region, how and when the person was asked about ads, and when ads started. Each ad request shares the IP address, a browser user agent built from the default browser and the Windows version, the language, the random ID, when ads started and your app's website address with our advertising partners. When an ad shows, the app also loads its picture and reports the impression from our advertising partners' servers, which see the IP address, the app's name and version and the Windows version. The app's first check, to see whether ads are available, carries no ID.

Every ad request sends the subscriber's IP address, user agent, language, random subscriber ID and subscription time, with your site address or app ID (and your click ID, if you pass one), to our advertising partners. They use it to choose the ad and to check that views and clicks are genuine. In-page, pop and exit-intent ads send the visitor's IP address, user agent, language and page address in the same way, whether or not the visitor has subscribed.

We do not collect email addresses, names, precise GPS location, or browsing history. Records of individual events are deleted after 90 days. The privacy policy template explains all of this to your visitors in plain words.

Do you support iOS Safari? ​

Not yet. Windows desktop apps are supported (Windows 10 version 1809 and newer, and Windows 11), see the Windows SDK. 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:

  • For push notifications and pop ads, the ad fetch is a server-to-server call from our delivery infrastructure; the browser never sees it. In-page and exit-intent ads are fetched by the browser from our concealed subdomain.
  • Windows apps talk only to t.dlserve.ai and xml-v4.dlserve.ai (ad pictures and the impression hop). Clicks go through t.dlserve.ai.
  • 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 our image host, xml-v4.dlserve.ai.

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)

Here sends is the push notifications shown in the month. Ads in your Windows apps are left out of it.

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 placement? ​

Each placement is one site (or one Android or Windows app). If you run more than one site, create a separate placement for each domain:

  1. Go to Publishing → Placements and click New placement.
  2. Pick the placement type, name it, enter the second site's URL and save. For a web placement the Match my site step opens next, so the subscribe prompt fits the new site.
  3. Install the new placement's code on the second site (its row menu → Get Code, or Get SDK for an app). Do not reuse another placement's code — the placement ID is tied to its site URL and delivery will break.

Clone in a placement's row menu starts the new placement from an existing one's settings; it still needs its own code installed.

Each placement has its own reporting, subscriber base, and subscribe-prompt 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.