Appearance
Troubleshooting
If the verify-install step in the dashboard fails — or if you're seeing unexpected behaviour after a successful install — the failures below cover the most common causes and how to fix them.
Snippet not found in your HTML
The dashboard's verify step fetches your origin URL and looks for a <script> tag pointing to cdn.dlserve.ai. This check fails when the tag is missing or blocked.
Causes
- The snippet was not placed inside
<head>(or anywhere in the HTML document sent to the browser). - A Content Security Policy (CSP) header is blocking the external script before the browser executes it.
- The placement ID in your snippet does not match the placement you are verifying in the dashboard.
- The snippet is inside a tag manager that fires after our verification crawler has already left the page.
Fixes
- Confirm the placement ID. In the dashboard, Placements shows each placement's ID in the first column — click the copy icon next to it to copy the full ID. It must match the ID in your snippet's address,
https://cdn.dlserve.ai/sdk/<ID>.js, in your HTML source. - Add
cdn.dlserve.aito yourContent-Security-Policy'sscript-srcdirective:Content-Security-Policy: script-src 'self' https://cdn.dlserve.ai; - If you are using a tag manager, also add the snippet directly to the page's
<head>for the verify check, then you can move it back to the tag manager once the check passes.
Service worker not reachable
Push notifications need a small file, sw.js, at the top level of your own site: https://yoursite.com/sw.js. The snippet registers it from there. Browsers only accept a service worker from your own site, so it can't load from ours. If the browser can't register it, visitors can agree to notifications but never become subscribers. If you use a soft-ask, Allowed on Subscribers keeps growing while Subscribed stays at zero. Once enough visitors are affected, the dashboard shows a "Push setup isn't finished" notice for the placement and we email you.
Causes
sw.jshasn't been uploaded yet, or it sits in a folder (such as/js/sw.js) or under another name. The snippet only looks for/sw.jsat the root./sw.jsredirects to another address, such as a CDN or another path. Browsers refuse a service worker that redirects, even to a copy of the same file.- The file at
/sw.jsisn't this placement's: it's another placement'ssw.jsor a service worker your site already had. Download this placement's file again and put it there. If your site needs its own service worker at that address, contact support before replacing it. - Your server answers
/sw.jswith a web page instead of the file (for example your 404 page, or hosting that sends every unknown address to your home page), or sends it as something other than JavaScript. - Your site is served over HTTP, not HTTPS. Browsers only allow service workers on secure origins.
- A Content Security Policy (CSP) header blocks the service worker, or the subscription it sends to
t.dlserve.ai.
Fixes
- Go to Placements, open the row menu (⋮) on your placement and choose Get Code. Click Download sw.js and upload the file to the top level of your site.
- Open
https://yoursite.com/sw.jsin your browser. You should see JavaScript code, not a page from your site or an error. Your server must send it asContent-Type: application/javascript. - Ensure your entire site is served over HTTPS. Service workers are unconditionally blocked on plain HTTP (except
localhost). - If your site sets a
Content-Security-Policy, allow the service worker from your own site, the script it loads fromcdn.dlserve.aiand its connection tot.dlserve.ai. If the header is also sent withsw.js, the same line covers it:Content-Security-Policy: script-src 'self' https://cdn.dlserve.ai; worker-src 'self'; connect-src 'self' https://t.dlserve.ai; - In your browser's DevTools → Application → Service Workers, check for any registration error message and include it when contacting support.
Hosting your service worker walks through the setup step by step.
No subscribers after 24 hours
The snippet is on your site, but your subscriber count stays at zero.
Causes
- Push notifications is switched off for the placement, so visitors are never asked.
- The prompt waits too long (for example After 5 pageviews) and visitors leave before it appears.
- Visitors are dismissing the browser permission prompt (or their browser auto-blocks it due to a previous dismissal on your domain).
sw.jsisn't reachable on your site. See Service worker not reachable.- All of your traffic is from browsers or platforms that are not yet supported (e.g. iOS Safari).
Fixes
- Go to Placements → row menu (⋮) → Formats → the Push notifications tab and check that the switch is on. Then, under Asking visitors, set Trigger to an earlier option such as Instant (on page load) or After 2 pageviews. A soft-ask (
geunder When to ask for permission) usually converts better than the browser prompt alone. See Subscribe prompts. - If you use a soft-ask prompt, open Subscribers and compare Soft-ask shown with Allowed and Subscribed. If Soft-ask shown is zero, the prompt is not being triggered at all. If Allowed grows but Subscribed stays at zero, the browser can't register your service worker (see Service worker not reachable). If Allowed stays low, visitors are declining (Dismissed and Blocked show where). Open a day to see it hour by hour.
- Incompatible on Subscribers counts visitors whose browser can't receive web push. iOS visitors cannot subscribe until iOS Safari support is added.
Push notifications not arriving on Chrome
Subscribers are recorded but Chrome users report not receiving notifications.
Causes
- Chrome has revoked the push subscription on the device due to inactivity or a browser update.
- The FCM (Firebase Cloud Messaging) endpoint has expired and the service worker has not yet rotated it.
Fixes
- The service worker renews the subscription automatically when the browser rotates it, or on the subscriber's next visit to your site. A missed message is not resent, but the next scheduled delivery should arrive normally, within your placement's sending hours and limits.
- If the problem persists for more than an hour, open Subscribers, choose the placement and check Expired: it counts subscriptions the browser's push service has ended, which are no longer sent to. If Expired jumps suddenly, contact support with your placement ID (the ID column on Placements), the browser and the dates.
Push not arriving on Edge
Edge users report delayed or missing notifications.
Causes
- Microsoft's push service (WNS) can have transient delays of up to several hours, particularly during off-peak maintenance windows.
- WNS rate limits per endpoint can cause a backlog when a large batch is delivered simultaneously.
Fixes
- This is usually a transient condition. Ask the user to check again after a day — the notification commonly arrives with a delay rather than being dropped entirely.
- If the pattern is consistent over multiple days, contact your dlserve representative with the placement ID (the ID column on Placements) and approximate delivery times so we can cross-check against WNS error logs.
This is about browser push to Edge. Ads in your Windows app don't use Microsoft's push service. See Windows apps.
Windows apps
Your Windows app shows no ads, or Send test ad shows nothing. Start by turning on logging: set a log handler and start the SDK with logLevel set to info. See Logging. Then find your log line in the table.
| Log line or symptom | What it means | What to do |
|---|---|---|
Nothing in the log, and IsAvailable (dls_is_available() in C) is false or 0 | dlserve.dll is missing, blocked, the wrong bitness or an older version. Every call does nothing. | Put the DLL that matches your app (x64 or x86) where the SDK looks: next to the .exe, or in the x64 or x86 folder for .NET. Check that security software hasn't quarantined it, and that it is signed if your app is. |
this host stays dormant: elevated | The app runs as administrator. | Start the app as the signed-in user, not from an elevated installer. |
this host stays dormant: store_package | The app is a Microsoft Store package. | The SDK shows no ads in Store apps. |
this host stays dormant: old_os | Windows is older than 10 version 1809. | Nothing to fix. The SDK needs Windows 10 1809 or newer. |
this host stays dormant: another_instance | A second copy of the app is running in this Windows session. | Close the other copy. One copy per session fetches ads. |
child-directed app: ads stay off | Your code starts the SDK with childDirected set to true. GetState() shows dormantReason child_directed. | Remove it if your app isn't made for children. |
config: unknown app id; checking again in 24 h | The App ID doesn't match a placement. | Copy the App ID again from Get SDK and restart the app. |
placement is not enabled or not eligible; checking again in 24 h | The placement can't serve this PC. | Check the placement has fewer than 10 test devices while in Testing, that this PC's country is in Countries on a Live placement, and that it isn't Paused by dlserve. Restart the app to check again at once. |
register refused (403 test_device_limit) | The placement already has 10 test devices. | Use Go live, or turn ads off in the app on test PCs you no longer use. |
register refused (403 geo_unsupported) | The placement is Live and this PC's country isn't in Countries. | Change Countries in Settings, or test with a placement in Testing. |
register refused (404) | The placement can't be found or is Paused by dlserve. | Check the App ID. If the placement shows Paused by dlserve, contact support. |
registered (no_prompt, test device) on a Live placement | This PC counts as a test device: it has no Installed apps entry, or it registered while the placement was in Testing. | Make your installer create the entry. On a PC that registered in testing, turn ads off and on in the app. |
dormant start: ads were turned off earlier | The user, or your app, turned ads off. GetState() shows adsEnabled as false. | Turn ads on from your app's ads setting. See Add an ads on/off setting. |
ad dropped: toasts are off or busy right now | Windows held the ad: Do Not Disturb, full screen, a presentation, the locked screen, or notifications off for your app. | Turn notifications on for the app in Windows settings, leave full screen and send again. |
ad dropped: too soon after the last ad | Less than 10 minutes since the last real ad. | Wait. Test ads skip this check. |
impression not counted: Windows dismissed the toast at once | Windows hid the notification right away, usually because of Do Not Disturb. | Turn Do Not Disturb off. |
poll paused by the server | The placement is Paused by dlserve, or dlserve paused this SDK version. | Contact support. |
| No question appears | New placements ask After 5 minutes in the app by default, so nothing appears before then. If When to ask is Only when my app calls ShowConsent, the SDK waits for your code. With Show a one-time notice outside dlserve's consent list or Ask everyone before showing ads, the notice or question waits too, so those people get no ads. Outside the places on dlserve's consent list, the default Consent mode shows nothing and ads start quietly. | Call ShowConsent from your app, or set After N minutes in the app. See Asking users. |
| The dashboard says "No test devices yet" | No PC has registered yet. Where the SDK asks first, a PC registers only after the person answers Allow or OK. | Run the app, answer the question (call ShowConsent or turn your Show ads box on), then Send test ad again. |
| Send test ad shows nothing | Your PC isn't a test device, or the app isn't running with ads on. | Check the app is running, ads on and notifications on. Use Send test ad again. A missed test ad isn't resent. |
The Windows SDK guide walks through each step.
Still stuck? Email your dlserve account representative with your placement ID (the ID column on Placements), the browser and OS version where the problem occurs, and any error messages from DevTools → Console or Application → Service Workers.
For a Windows app, send the App ID, your app's version, the Windows version and the SDK log instead.