OneSignal is a high volume and reliable push notification service for websites and mobile applications. It support all major native and mobile platforms by providing dedicated SDKs for each platform, a RESTful server API, and an online dashboard for marketers to design and send push notifications. OneSignal features include segmentation, automatic/triggered notifications, variable substitution, a notification delivery API, and detailed reporting tools.
Push notifications are a new marketing channel to engage your site visitors without knowing their email or other contact details, a channel built into every mobile device sold today. They allow apps to reach out to users with short messages that users may respond to. Web push notifications are messages that come from a website. You get them on your desktop or device even when the website is not open in your browser. Web Push Notifications generally work only on SSL sites (HTTPS), but OneSignal provides this feature for also for HTTP sites by assigning you a free HTTPS subdomain.
The following image illustrates the flow when integrating Gigya and OneSignal:
- User registers / logs in via Gigya
- Gigya checks for this user in OneSignal
- If the user is registered in OneSignal, Gigya sends tags to OneSignal, based on their profile data
- In OneSignal, the user is assigned to one or more segments, according to the tags passed
- Based on the segmentation, personalized notifications can be sent
- You have registered to OneSignal.
- You have set up a OneSignal app.
- You have created the relevant segments in OneSignal (in this example, gender).
1. Integrate SDKs into your App
- Download Gigya's mobile SDK and follow the relevant documentation to integrate the SDK into your mobile application.
- Integrate OneSignal's mobile SDK and follow the documentation to integrate the SDK into your mobile application.
2. Add Code
Place the following code in the <head> tag of your site's index.html file:
You can find your App ID in OneSignal App Settings:
Add the following code to Gigya's onLogin event:
See detailed explanation in the image below:
As a result, attributes associated to the user's profile in Gigya, are pushed as tags to OneSignal: