Appearance
Windows app ads
Windows app ads are ads that appear as Windows notifications from your desktop app, while your app is running. You add the dlserve SDK to your app once (see the Windows SDK guide), then manage everything else from Placements in the dashboard.
What your users see
- A normal Windows notification with your app's name and icon.
- The ad's title and text, sometimes a picture, and the label Ad.
- No buttons and no sound.
- It disappears after about 25 seconds.
- A click opens the ad in the person's default browser.
When ads show
An ad shows only when all of these are true:
- The placement is Live and not Paused by dlserve.
- Your app is running and installed on the PC.
- The person hasn't turned ads off, and Windows notifications are on for your app.
- The person's country is one of your Countries.
- It is inside your Sending hours and under Max ads per user per day.
- The Minimum minutes between ads have passed since the last ad.
- At least 60 minutes have passed since their computer started getting ads.
- The PC isn't in full screen, in a presentation, on the locked screen or in Do Not Disturb.
- There is an ad available for that person.
Ads also wait through the first hour after a new Windows user account first signs in. The SDK never shows two ads less than 10 minutes apart.
Asking users
Whether people are asked before ads start depends on your Consent mode and where the person is. See Windows placement settings for the setting.
| Your Consent mode | Who sees a question | Everyone else |
|---|---|---|
| Ask in regions on dlserve's consent list (default) | The dialog, for people in the countries below | No question. Ads start quietly. |
| Show a one-time notice outside dlserve's consent list | The dialog, for people in the countries below | A one-time notice. With When to ask set to Only when my app calls ShowConsent, it waits for that call |
| Ask everyone before showing ads | The dialog, for everyone | Not applicable. Everyone is asked. |
The SDK always shows the dialog for people in the places on dlserve's list: the European Union, Iceland, Liechtenstein, Norway, the United Kingdom, Switzerland, Brazil and Quebec. Where the country can't be worked out, test devices are asked and live ads don't show. It also shows the dialog when the PC's own region settings (home region, time zone or regional format) point to one of those countries. Quebec is decided from the IP address only. This list is kept by dlserve and is how the SDK behaves. It is not legal advice, and it can change.
With After N minutes in the app (the default for new placements, 5 minutes), the question comes N minutes after the app starts. With Only when my app calls ShowConsent, the dialog and the notice wait until your app calls it, and nobody who would see either gets ads until then. After you make Consent mode stricter, your app should call ShowConsent again so people get the new question. See Windows placement settings.
The dialog asks: Allow your app to show ads as Windows notifications?
Up to 2 ads a day, labelled "Ad", only while your app is open. We use your IP address, a random install ID and basic device and app info to choose ads, and share them with our advertising partners. You can turn ads off in your app's settings.
The buttons are Allow and No thanks. Pressing Enter, or closing the dialog, counts as No thanks.
The notice says your app shows ads:
Your app shows up to 2 ads a day as Windows notifications, labelled "Ad", only while it's open. We use your IP address, a random install ID and basic device and app info to choose ads, and share them with our advertising partners.
The buttons are OK and Turn off ads. Pressing Enter, or closing the notice, counts as OK.
Both show your app's name from its Installed apps entry (cut to 40 bytes, so fewer characters for non-Latin names). If the name has anything but letters, digits, spaces and - ' & + ( ) _, such as a dot or a comma, they say "this app" instead. They also show your Max ads per user per day, and never less than 1. When you fill in Privacy policy URL (optional) with a link that starts with https://, a Privacy policy link appears at the bottom. The wording is in English and can't be changed.
If you make the Consent mode stricter, people who already get ads stop getting them until they answer the new question. The new question appears N minutes after the app starts with After N minutes in the app, or when your app calls ShowConsent with Only when my app calls ShowConsent (a one-time notice shows by itself when the app starts).
How users turn ads off
- Your app's ads setting. Your app must have one (see the SDK guide). Turning ads off stops them and removes any ad on screen.
- No thanks on the dialog, or Turn off ads on the notice.
- Windows notification settings for your app. This also stops the ads, but it mutes your app's own notifications too.
Once ads are off, the SDK never turns them back on by itself. Only the person, or your app when the person asks, can.
Testing and Live
- A new Windows placement starts in Testing. Only test devices get ads, and only test ads. Any PC that runs your app while the placement is in Testing becomes a test device, up to 10.
- Choose Go live from the placement's row menu (⋮) any time. Real ads then run for the Countries you set.
- Back to testing puts it back.
- Go live before you release your app, so new installs aren't test devices.
The SDK guide shows how to send yourself a test ad with Send test ad.
Paused by dlserve
If dlserve pauses a placement, a red Paused by dlserve badge appears next to it. Ads stop at each app's next check, within about 15 minutes. Contact support to find out why and to get it resumed. After the pause is lifted, ads come back the next time the app starts, or within about a day.
In your reports and payments
- Windows ads count under Push in Reportings. The By platform tab has a Windows row. See What your report numbers mean.
- Their revenue counts in your gross revenue.
- Windows ads don't count toward the minimum guarantee. See How payments work.
What data is used
For each install, with the person's answer where the app asked, dlserve stores:
- A random install ID, and a random subscriber ID linked to it.
- The IP address, and the country and region worked out from it.
- The Windows version, and your app's name and version.
- The default web browser, the language and the time zone.
- Whether ads are on, the answer to the question, when it was given and which version of the text was shown.
- When ads started, and when the app last checked in.
- Which ads were sent, shown, skipped, closed or clicked.
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. Each ad request shares the IP address, a browser user agent built from the default browser and Windows version, the language, the random ID, when ads started, and your app's website address with our advertising partners. The very first check an app makes carries no ID. Your users should be told about this in your app's privacy policy: use the privacy policy template.
Related: Windows placement settings, Windows SDK guide, Requirements and risks, What your report numbers mean.