FAQ
Frequently Asked Questions about Website Integration.
Last updated
Frequently Asked Questions about Website Integration.
Last updated
Yes, but since there is only one service worker allowed per domain, you need either:
join both service workers together using importScript:
importScripts('
https://cdn.pushpushgo.com/63c574dd030eb6beb6d2c097/worker.js
')or put them separately and point where the service worker from PushPushGo app is located (on your site) by providing its path and typing ‘/ppg_scope’ in service worker scope in project settings:
Yes, but since PWA will always have its own service worker and there is only one service worker allowed, you need to use one of the solutions from question above "I already have another service worker. Can I integrate with PushPushGo?".
Yes, you can integrate your website via GTM, but only basic integration will be possible, since you do not have access to the server root path.
Go to your Google Tag Manager and then:
Create a new tag. Select the “Custom html” type and paste the code from the Integration > Installation tab.
Open “Advanced settings” and enter “1” in “Tag firing priority”.
Set the trigger to “DOM Ready”.
Remember to publish changes.
If you want to change the service worker name, for example from ‘sw.js’ to ‘service-worker.js’:
save the service worker path in project settings as ‘/service-worker.js’.
If you want to change the directory where the sw.js file is located (for example, to ‘static/sw.js’):
save service worker path in project settings as ‘/static/sw.js’ and service worker scope as ‘/static/’.
Remember - after setting scope different than ‘/’ (global), eg. ‘/static’, our application will work only on subpages in that scope or below, so:
https://example.com/static - code will work here
https://example.com/static/page1 - code will work here
https://example.com/ - code won't work here
https://example.com/cart - code won't work here
If you still want our code to work globally in that case, you have to set scope as default - ‘/’ and add the following response header: "Service-Worker-Allowed": "/" to subpage containing service worker.
You need to integrate each project by placing the integration script in the corresponding website subdirectory source code and service worker in the subdirectory folder of the server.
Then, change the service worker path & scope of every project in project settings accordingly. For example, for ‘your-site.com/en’ change service worker path to ‘/en/sw.js’ and service worker scope to ‘/en/’, and for ‘your-site.com/de’, change service worker path to ‘/de/sw.js’ and service worker scope to ‘/de/’.
Sometimes when there is no possibility to add more than one worker, you can try importing subdomains’ service workers into main service worker and write logic to use them conditionally.
Every sign-up for notifications appears in the browser settings. Instructions for disabling notifications vary among different browsers.
Google Chrome
Go to Browser settings > Privacy and security > Site settings > Notifications. You can also paste chrome://settings/content/notifications in your address bar. On the list, you can find all the pages on which you have agreed to receive notifications. If you want to unsubscribe from any of them, just choose Remove from the menu.
Firefox
After entering Options> Privacy and Security, search for Permissions>Notifications.
On the list, search for the page from which you want to unsubscribe, and choose the Remove Webiste option.
If you have properly integrated PushPushGo with your site but still don’t see the sign-up form, or if your data isn't visible in the panel as the new recipient even after allowing notifications, check whether any of these apply:
You are using an incognito window
You are already signed up for notifications
You have blocked notifications in the browser settings
You have blocked notifications in the operating system settings
Sometimes, testing the sign-up form requires performing steps that are not typical for an avarage user. It’s a good idea to clear any settings that might affect the notifications before testing the sigh-up process.
