Frequently asked questions

IntegrationA message about an incorrect integration appearsSubscribing for notificationsCan I change the content of the sign-up form?I can’t subscribe for notifications Sign-up form appears after already beign completed (Google Chrome)How to unsubscribe from notifications?Can I only collect subscribers who have entered my site from mobile devices? Or can I completely exclude them?Can I determine which visitors will be shown the ringtone widget and who isn’t?Why can’t I see the subscription form on my site for iOS devices?SubscribersHow are subscribers identified?What data does PushPushGo collect?Are you collecting IP addresses of the customers?Why did my last campaign cause so many unsubscribes?Why do I always see 0% when exporting data?NotificationsFor how long are notifications displayed?A large graphic limits text in notificationWhich elements of the large picture notification (rich push) link to the landing page?Why do I not see action buttons in a test notification when testing rich push?What causes the default notification to appear?Why do my campaigns have weaker CTRs on Firefox?Why, after the automation scenario has already been turned off, did I receive the notification set in it?Can I delete notifications from my inbox?Can I use a .gif file in web push notifications?Is it possible to change the appearance of the notification (in addition to the photo and content)?PaymentsHow do I activate automatic recurring payments?I made a payment but my account is still blockedApplication

Web push technology is based on the use of service workers in the browser, meaning the recipients are identified by the browser they use. Our platform does not use personal data or cookies. Each person who subscribes to notifications receives an individual string of characters, the so-called SubscriberID.

Specification for subscribing to WebPush are as follows:

1. Loading the PushPushGo script

The user enters a website where the PushPushGo plugin is implemented
[HTTPS - Downloading the JavaScript script to the user page]

2. The appearance of the initial subscription form

A message appears prompting you to subscribe to [Pre-Paste JavaScript]. At this point it is possible to accept or reject the message. Rejection causes the data to be saved in the IndexedDB browser memory.

3. The second registration form

Upon acceptance, a second registration form appears

4. Service Worker registration

The HTTPS inquires after the Intermediary (google, mozilla) with a request to generate the subscriber's HASH along with the keys for the authorization of the campaign.

5. Transfer of data to PushPushGo

After giving consent, the subscription proceeds, meaning that the above-mentioned information is transferred to the PushPushGo database through an HTTPS connection and in reply PushPushGo returns the subscriber's ID. This data is stored in IndexedDB (available only to this user from the level of our script). A notation that it is already saved to the database and further permission is not needed. 

6. Communication with subscribers

Using the PushPushGo servers, the owner of an integrated site using the application can now directly communicate with that person (without having an e-mail address, telephone number, or any personal data) 


Test web push on your website

Get started for free

The trial version includes all features

European Funds banner
Our website is using cookies.
Close Read more