How does this work from a technical perspective? Most browsers, if not all, require authorisation from the user before you can start sending push notifications, correct? When a user grants access, do they grant access to Aimtell or to the site implementing the Aimtell service?

It's an important difference, because the former would create a vendor lock-in for your customers preventing them from taking their 'subscribers' with them if they choose to move to a different service or a custom solution.

Curious to hear more! If there's no vendor lock-in I might be interested in using it for BetaList.

@marckohlbrugge: that's correct, all browsers require user authorization first. Essentially we are able to communicate to the browser and tell them to request permissions from a user on behalf of a website. If the user says yes, we get a special device specific token. Later we then can send this special token to Google or Apple's servers which then will relay our information to the browser that owns that special token. There is quite a bit more behind the scenes, (ie Google - w/ service workers, Safari - w/ push packages), but that's the high level of it. While we don't have an export "token" feature as of now, you could essentially export them and use them with another vendor (sort of like an email address). We definitely have no intention of creating any sort of vendor lock-in and would be elated if you wanted to give it a go. If you want to chat more or get even a deeper tech understanding feel free to shoot over an email directly to me (dj[at]aimtell.com) and we can talk :)