17 August 2026
The email that taught me web push exists
I did not take the meeting. I did take the channel seriously later. You already have a newsletter. The browser is sitting there.
I had not thought about it
Years before I started EngageNudge I was in Nordic newsrooms as a C-level tech manager. Web push was not on my list. Then a cold email arrived. An ad network wanted to put a script on the site and push ads at readers.
We said no. Obviously. I still remember the feeling of it. Someone had found a pipe I did not know was there.
I did not take a call. I looked the channel up. That is how I entered this category. I assume a lot of you entered it the same way, or have not entered it yet.
You already did the hard part once
A newsletter takes years. An address. A habit. An inbox that is tired. I am not against email. I use it. I am saying there is a second owned line that does not need an address, and most sites still have not built it.
The browser can ask, once, for permission. After that you can reach the person when something is actually worth it. No app store. No download. On the browsers that support it, including the iOS caveat everyone already knows about if they have tried.
The mistake I watched later
When a newsroom finally turns this on, the first instinct is to treat it like a second blast list. Every publish. Everyone. That is how you burn the thing before it has a chance.
I learned the channel from a mail I did not buy. I learned the damage from sitting next to a list that worked and still leaked. Those are different lessons. The first one is enough for this note.
If you have a newsletter and no browser audience, you are not late in some moral sense. You just have an unused pipe. I would rather you turn it on with judgment than turn it on like 2018 email.
I write more about the leak and the meeting you cannot win. This one is just the door. You built an email audience. Have you built a browser audience?
