How to customize Perfecty Push?
These are the different areas you can configure:
They affect the controls shown in the front page (the Subscription prompt/the Bell icon).
Each of the values is described below:
|Enabled||Show the widget in your website public frontend.|
|Display after this number of visits||Required number of visits to the website before displaying the subscription prompt.|
|Do not use widgets (ask permissions directly)||Ask permissions right after the use visits the website. Will not show the dialog/bell controls.|
|Hide bell after subscribing||Hides the bell after the user has subscribed to your website. Note that the users will not have a way to unsubscribe and will be forced to revoke you the Browser permissions.|
|Subscribe text||This is the text of the question asked to the user for subscribing to Push Notifications. (Default: |
|Continue text||Text of the Button to continue (Default: |
|Cancel text||Text of the Button to cancel (Default: |
|Bell title||Title of the Settings dialog when the Bell icon is clicked (Default: |
|Opt-in text||Text of the Opt-in checkbox (Default |
|Message on update error||Text shown when there's an error updating the preferences (Default: |
They define how the SDK performs the registration and the Push Notifications.
|Service Worker Scope||This is the scope of the service worker. By default we use a value different than root |
|Remove conflicting workers (Don't use it with PWA/AMP)||Removes all the workers from all the scopes (useful when migrating from another provider). Don't use this in a PWA/AMP website.|
|Custom conflict detection||Specify a custom JS regex expression to remove specific conflicting Service Workers. More information|
Change the notifications that the users receive in their Browsers/Mobiles.
|Fixed notifications (do not auto hide)||If checked the notifications will not disappear. Otherwise, they will fade out automatically after a couple of seconds.|
|Default Icon||The default icon to be sent in all the notifications.|
This is for the user segmentation capabilities (still under development).
For the moment it supports the following values:
|Enable and collect data from users||If enabled it will collect and store the IP address from the subscribers.|
|UTM analytics||Paste the UTM Tracking for Google Analytics, for example: |
How to send notifications automatically after publishing a Post.
|Always send a notification||It will always send a Push Notification when a Post is published. You can define it per post in the Post's metabox.|
Define the options for your self-hosted Push Server.
You can define the following values:
|Vapid Private Key||Auto generated||Private VAPID Key|
|Vapid Public Key||Auto generated||Public VAPID Key (Used in the JS SDK)|
|Batch Size||Number of notifications to fetch from the Database in each sending loop. The higher the number requires higher memory, approx. |
|Parallel Flushing Size||Number of concurrent notifications to send. A high value can cause Out Of Memory errors, so please adjust with caution according to your server specs. See: Performance improvements|
|Enable Server Logs||Enables the logs in the Push Server.|