Push Integration
If your eCommerce website already collects permission data from one of the Push Services and you decide to change Push Service - to Segmentify, Segmentify can do it if the Push Notification Platform is worked under the GCM, FCM, or uses VAPID. All permitted users can be migrated to the Segmentify service.
Which steps must be required to integrate Segmentify Service seamlessly?
- Segmentify needs a token list and credential data from the old Push Service.
- Segmentify Service Worker file and Manifest JSON file path must be placed the same as the old Push Service. The URL must be the same as the old one.
- Old service worker file names must not be changed.
- All steps must be evaluated with the Customer Success Team. Please always keep going with Customer Success approval.
Migration from FCM
All required credentials are stored from the Firebase side.
Needs | Required |
| subscriptionId | Yes |
auth | Yes |
p256dh | Yes |
Token ID List | Yes |
Server Key & Sender ID | Yes |
Project Ownership | Yes |
Device (Mobile. PC, Tablet) | No |
Browser (Chrome, Firefox, Yandex, Opera) | No |
Device & Browser information is not a must for the migration process but without this information Segmentify can not send push according to the device selection and can not show the permission browser dimensions in the report.
How can I change the project ownership from Firebase or do I have another option?
For Push Migration, Segmentify has two options to migrate Push Permissions.
- Option 1 | Enter to your Firebase Project and click on the "Service Accounts" from Menu. Admin SDK configuration snippet should be selected as "Java". Then click on the "Generate New Private Key" button.
- Option 2 | Enter to your Firebase Project and click on the "Users and permissions" tab from Menu. Click on the "Add member" button and give a role as owner or editor to the "push@segmentify.com" account.
Migration from VAPID
| Needs | Required |
subscriptionId | Yes |
auth | Yes |
p256dh | Yes |
Token ID List | Yes |
Public Key & Private Key | Yes |
Device (MOBILE, PC, TABLET) | No |
| Browser (Chrome, Firefox, Yandex, Opera) | No |
Device & Browser information is not a must for the migration process but without this information, Segmentify can not send pushes according to the device selection and can not show the permission browser dimensions in the report.
Related Articles
Introduction to Personalised Push
Push is a great channel for eCommerce and digital marketing because it can reach customers quickly and increase their traffic and revenues in a very basic way rather than Email and SMS. Push is a type of campaign that is usually sent instantly and ...Activation of Segmentify Push Service
Integrating Segmentify's Push into eCommerce websites' steps are explained below. Step 1. Login to the Segmentify panel. https://v3.segmentify.com/login Step 2. Go to Account Settings and select the Push module from the sidebar. The screen that opens ...How to Create Bulk / Segmented Push Campaign
With Bulk / Segmented Push Campaigns, which offer the opportunity to send push notifications to all customers or segment users, customers receive pushes from their favourite categories. Below are some steps to create a Bulk/Segmented Push campaign. ...Experience the Push Dashboard
Data of Personalised Push Notification campaigns are kept in the Dashboard. It is up to you to choose which time this data belongs to. Whether today's or the previous month's data can be viewed on this screen with a few clicks. The time metrics ...Introduction to Segmentify Push Scenarios
Push Notifications are indispensable for eCommerce today. Push campaigns that serve different purposes can increase the conversion rate considerably since they are campaigns that directly reach the customer. At this point, Segmentify offers a wide ...