Appearance
Push notifications
Push notifications are short ads that appear on your subscribers' computers and phones — like app notifications — even when your site isn't open. Visitors only receive them after they agree to subscribe, and every notification you deliver can earn revenue.
How it works
- A visitor arrives on your site and is asked whether they want notifications (see Subscribe prompts).
- If they allow it, they become a subscriber of your placement.
- From then on, dlserve sends them relevant ads as notifications, within the limits you set. When a subscriber clicks one, the advertiser's page opens.
With Audience targeting switched on, dlserve spaces out (or skips) notifications to subscribers who aren't responding; it never sends anyone more than your limits. New placements start with it off.
Set it up
- Go to Placements and click New placement. Choose Web push for a website, give it a name and a website URL, and save. (For a placement you already have, open the row menu (⋮) and choose Settings to change those.) To start from an existing placement instead, open its row menu (⋮) and choose Clone: the copy keeps every setting and ad format, starts with no subscribers, and gets its own install code, so install it like a new placement.
- Open the row menu (⋮) on the placement and choose Formats.
- On the Push notifications tab, make sure the switch is on, then work through its three blocks:
- Asking visitors — how and when visitors are asked to subscribe.
- Sending hours & limits — when subscribers may be sent notifications, how many, and whether Smart send timing picks the best hours for them.
- Audience targeting — how often less-engaged subscribers hear from you.
- Click Save changes, then open the Get Code action on your placement's row and follow both install steps — including hosting your service worker.
Setting up without push. A placement can run in-page notifications, pop ads and exit-intent ads with Push notifications off. The onboarding wizard asks first, with Collect push subscribers: leave it off and there is no sw.js to host, and the install check looks for the snippet alone. You can switch push on later — see When you turn it back on.
Where the prompt appears
Under Asking visitors you can choose where the subscribe prompt sits. The two position choices show when your placement asks with a soft-ask (Soft-ask, then browser prompt or Soft-ask + bell button).
- Position on desktop — Auto (recommended), one of the four corners, a bar across the top or bottom, a card centred at the top or bottom (Top (centred card) or Bottom (centred card)), or the center of the screen.
- Position on phones — Auto (recommended), top, bottom or center. Leave it on Same as desktop and the closest spot is used: any top position becomes the top, any bottom position the bottom.
In-page notifications move aside on their own, so they never sit on top of the prompt or the bell button, even in the same corner.
If something on your page, such as a full-screen popup, hides the prompt, pick a different position. Visitors can't answer a prompt they can't see.
Auto position
New placements start on Auto (recommended). Instead of guessing which spot works best on your site, Auto tests it on real visitors:
- What is tested. On computers, the four corners. On phones, top against bottom. Each visitor sees the same spot on every page, so the prompt never jumps around.
- How it picks. The winner is the spot where the most visitors turn notifications on in their browser for each time the prompt is shown. It picks a winner once it has about a week of data, enough visitors in every spot and a clear leader, and stops after 28 days at the latest. Clicks on the prompt's Allow button only count at the 28-day mark, to break a near tie.
- Small sites. If there aren't enough visitors for a clear winner, Auto keeps its default spot (Bottom right on computers, Bottom on phones) and says so under the position choice.
- Re-checks. About every 90 days Auto tests again, because sites and their other ads change.
- Overriding it. Pick a specific position at any time to stop the test and keep that spot. Choose Auto (recommended) again to restart it.
Under the position choice you can always see where the test stands: how many days it has run, which spot won, or that there isn't enough traffic yet.
Turn subscriber collection on or off
The switch is in Placements → row menu (⋮) → Formats → the Push notifications tab.
Turning it off stops your site asking new visitors to subscribe. Nothing else changes:
- Your existing subscribers keep receiving pushes — your scheduled sends, your campaigns and your test sends all carry on exactly as before. No subscriber is removed, and nobody loses their history.
- Your other ad formats keep running. In-page notifications, pop ads and exit-intent ads are not affected.
- Sending hours & limits and Audience targeting stay editable, because they still govern the subscribers you kept. Only Asking visitors is greyed out until you switch collection back on.
Keep sw.js on your site. It is what delivers notifications to the subscribers you already have — see Hosting your service worker.
Changes reach your site within a few minutes. A visitor whose browser loaded your page just before the change may still be asked once in those minutes — the subscription is refused either way and nobody new is recorded.
While collection is off, your Overview and your Subscribers report say so above their numbers, and the placement's row in Placements carries a Not collecting label.
When you turn it back on
Collection resumes on the next page view. The subscribers you kept are the same people with the same engagement history — nothing was reset while collection was off, so your reports stay continuous.
If you set this placement up without push notifications, host sw.js now — see Hosting your service worker. Until it's there, visitors can agree to subscribe but nothing is recorded.
Sending hours & limits
In Formats → the Push notifications tab → Sending hours & limits you control:
| Rule | What it does |
|---|---|
| Placement timezone | The clock we fall back to when we don't know a subscriber's own timezone — their sending hours, daily limit and delivery schedule are counted in it. Recurring campaigns run on this clock for everyone. |
| Sending hours | Off by default, so notifications can go out at any time of day (24/7). Tick Limit sending hours to choose a From / To range, counted in each subscriber's own local time. |
| Daily maximum | A hard cap on notifications per subscriber per day. With Audience targeting on, dlserve may send fewer, based on how engaged the subscriber is. |
| Minimum gap | A subscriber never gets two notifications closer together than this. |
| Smart send timing | Sends each subscriber's daily notifications at the best hours of their day. See Smart send timing. |
| Sub ID | Optional traffic-source label sent with every push ad request and used in your reports. Empty = your site's domain. See Traffic sources. |
Sending hours
Sending hours are the part of the day when dlserve may send automated ads to your subscribers.
By default there are none: Limit sending hours is unticked and notifications can go out at any time of day (24/7). Your daily maximum and minimum gap still apply.
Tick Limit sending hours to send only between a From and a To time. When you tick it the range starts at 09:00 – 21:00, and you can change it.
The hours are measured in each subscriber's own local time. With 09:00 – 21:00, someone in New York gets notifications between 9am and 9pm New York time, and someone in Los Angeles between 9am and 9pm Los Angeles time. If we don't know a subscriber's timezone yet, we use the placement's timezone instead.
Your delivery schedules follow the same clock. A delivery set to go out at 9:00 AM reaches each subscriber at 9:00 AM where they are, so the send rolls across timezones through the day. Subscribers whose timezone we don't know get it at 9:00 AM in your placement's timezone. If a schedule falls outside your sending hours — say 11:00 PM with hours of 09:00 – 21:00 — nothing goes out at all, so keep the two in step.
The end time is the moment sending stops: 09:00 – 21:00 means the last notification can go out at 20:59. To send until midnight, set To to 00:00: 18:00 – 00:00 covers the rest of the day.
Hours can't run past midnight. Apart from a 00:00 end, the end has to be later than the start, so 22:00 – 07:00 isn't accepted — a range like that would mean "no hours at all" and your placement would stop sending.
Your daily maximum is counted over the same local day, so it resets at midnight in the subscriber's own timezone — or in your placement's timezone when we don't know theirs.
Campaigns you schedule yourself are not affected — see Campaigns.
Smart send timing
Formats → the Push notifications tab → Sending hours & limits → Smart send timing.
Each subscriber's daily limit starts again at midnight in their own time. Without smart timing, their notifications go out at the first deliveries of the day, often in the middle of the night when few people are looking. With Smart send timing on, dlserve sends them at the best hours left in each subscriber's day instead.
How it picks the hours. From recent notifications across dlserve, it learns at which hours of the day people click most, and what ads pay at each hour in the subscriber's country. Hours are counted in each subscriber's own local time. It also learns at which hours ads are available for your subscribers' country, and doesn't hold a notification back for hours when ads rarely show. Each person's best hours shift a little from day to day, so people who haven't clicked yet are tried at different good times. On about one day in ten, a subscriber gets random hours within your sending hours instead, so the timing keeps learning.
What stays the same:
- The same number of notifications per day. Your Max notifications per user per day still sets it. When few hours of the day are left, the remaining notifications go out anyway.
- Your rules still apply. Smart timing only chooses when, within your Sending hours. It never sends outside them, never sooner than Minimum minutes between notifications, and never to anyone Audience targeting would skip.
- Campaigns still go out at the time you pick.
- Windows app placements don't use it: your app fetches its ads itself.
The comparison group. To measure whether it helps, half of your subscribers keep today's timing for now. They are picked at random and stay in the same group, so the two groups can be compared fairly: clicks per notification, and earnings per subscriber per day. After a few weeks, the comparison group shrinks to a small share.
Switch it on or off. In Formats → the Push notifications tab → Sending hours & limits, switch Smart send timing off (or on) and click Save changes. The change takes effect within about an hour. Placements that already existed when it launched have it on; new placements start with it off. In Placements, a placement with it on shows Smart timing next to its sending hours.
Audience targeting
Formats → the Push notifications tab → Audience targeting.
Every push subscriber gets an engagement score from 0 to 100, refreshed every hour from their recent clicks. With Audience targeting switched on, less-engaged subscribers get their ad notifications spaced further apart, or fewer of them, or none at all below a minimum score you set. It never sends anyone more than your own limits, and it never sends sooner than your own gap. New placements start with it off.
| Setting | What it does |
|---|---|
| Audience targeting | On: each subscriber's limits follow their engagement level (below). Off: every subscriber gets your placement's limits, whatever their score. |
| Minimum engagement score | Subscribers scoring under this get no ad notifications from this placement. 0 skips nobody. Only applies with Audience targeting on. |
How the score is made
About once an hour, from three things:
- How often they clicked the notifications they were shown in the last 7 days. This counts most.
- How many days since their last click.
- A small boost in their first week, so new subscribers get notifications before there is click data.
Being shown notifications without clicking slowly lowers the score; one click raises it sharply. Typical scores: never clicked, about 15–24; new this week, about 44; clicked this week, about 50–90.
The four levels
Each level has its own limits. Your placement's own Max notifications per user per day and Minimum minutes between notifications still win whenever they are stricter: a level can only lower your daily maximum and lengthen your gap.
| Level | Engagement score | Who's typically here | Most per day, by default | Least time between, by default |
|---|---|---|---|---|
| Low | under 25 | Haven't clicked in a while, or never have | 5 | 190 min |
| Medium | 25–49 | New this week, or last clicked one to two weeks ago | 9 | 147 min |
| High | 50–74 | Clicked in the last week or two | 13 | 110 min |
| Premium | 75 and up | Clicked in the last few days | 17 | 61 min |
| No current score | — | Brand-new subscribers before their first score, and people with no recent activity | your limits | your limits |
With the default 3 notifications a day, every level's daily maximum is above yours, so every level gets up to 3 a day: what targeting changes is the spacing, plus who the minimum score skips.
Example
A placement sends 3 a day, at least 60 minutes apart, on an hourly delivery, with Audience targeting on and a Minimum engagement score of 0.
- Dana clicked yesterday, so her score is about 87 (Premium). She gets up to 3 a day, at least 61 minutes apart: about every 2 hours on hourly delivery.
- Ben subscribed two months ago and never clicked, so his score is about 24 (Low). He still gets up to 3 a day, but at least 190 minutes apart: about every 4 hours.
- Raise the Minimum engagement score to 25 and Ben stops getting ad notifications. Dana is not affected, and neither is a brand-new subscriber (about 44).
- Switch Audience targeting off and Dana and Ben are treated the same: up to 3 a day, at least 60 minutes apart.
How to tune it
- Start with it on and the minimum at 0. Nobody is skipped; less-engaged subscribers are just spaced further apart.
- To send less to people who don't respond, raise the Minimum engagement score. 25 skips people who haven't clicked in a couple of weeks, but not new subscribers.
- To send less to everyone, lower Max notifications per user per day or raise Minimum minutes between notifications in Sending hours & limits.
- Changes apply from the next scheduled delivery. Scores refresh every hour.
These settings only apply to automated sends. Campaigns go to the audience you pick and ignore the engagement score.
Good to know
- On some devices the notification is prepared when it arrives, so the offer is current when you see it. Keep your
sw.jsup to date to get this. - Subscribers must opt in — nobody receives push notifications without allowing them in their browser.
- Android app placements are capped at 2 notifications per day.
- Android devices that don't show notifications get an occasional check-in instead. When none of a device's last several notifications was shown or clicked (usually because notifications are turned off for your app), dlserve sends it one notification every few days rather than its full schedule, until one is shown or clicked again. Your Sent count goes down by those skipped sends; devices that show notifications are not affected, and nobody stops receiving notifications altogether.
- Android app placements need your app's App bundle ID (for example
com.example.app) in the placement's Settings — ad partners see it as the site your ads run on. - iPhone and iPad Safari don't support web push, so those visitors can't subscribe. You can still earn from them with in-page notifications.
- Windows app placements work differently: see Windows app ads.
- You can also send your own messages to your subscribers with campaigns.