Dotdigital has the capability to send mobile push notifications to your app users using either our Program Builder or our omnichannel messaging API. We support sending push messages with optional deep links, URLs or custom data, this allows you to leverage any built in functionality of your app directly from a user tapping a push message.
Deep linking and custom data with push messages
Your app must be written support deep links or understand custom data payloads sent via a push, we simply deliver the link URL or custom data, the app must interpret them.
It's important before we go over the steps on how to enable the push channel in Dotdigital that some key concepts are understood.
Dotdigital requires all users you want to send push notifications to have an email address, as this is used to create a contact in Dotdigital, and you target your pushes by sending to contacts.
If you have a requirement to send push to users without an email address this is possible using the API only. Contact your Customer Success representative about our CPaaS APIs.
Unlike channels such as email or SMS, it's not possible to import data to make contacts in Dotdigital push contactable. Your push audience is discovered as your users or customers open your app with the App Messaging SDK integrated into it, as it passes to Dotdigital the necessary push tokens and email address to send a push message.
When a contact is push contactable the PUSHOPTIN_xxx data field is populated, otherwise this field is blank.
Do not edit or amend the PUSHOPTIN field
The PUSHOPTIN_xxx data field is automatically managed by the platform and must not be altered or populated manually, as this causes issues with push messaging.
Our App Messaging - Foundation SDK must be embedded in your app to enable us to register users as contacts in Dotdigital, and acquire the necessary push tokens automatically from your app in order for you to push to the user's device.
Your app passes our SDK a security token, which it validates, to register a user. The security token needs to be in the JWT format (JSON Web Token).
The following diagram illustrates the SDKs use:
In order for Dotdigital to send push messages through Apple or Google you must first push enable your app, which is usually done by your mobile development team in the app admin portals for Google and Apple.
Once configured, you need to configure various identifiers, certificates and tokens into Dotdigital in order to enable us to push to your app.
We strongly recommend having your mobile development team assist your with this configuration.
To send push notifications from Dotdigital to your app, you need to do the following to link Dotdigital to your app and users:
These steps ensure that Dotdigital has the necessary information to use Apple and Googles push channels to reach your app, and that the app passes the necessary information to send push to individual app users.
In this step you configure Dotdigital to be able to use Google's FCM and Apples APNS push services to send messages to your apps. This involves configuring tokens and certificates that are issued for Apple and Googles platforms when configuring push for your app, so it is recommended that you have someone with mobile development knowledge available to complete this step.
In addition to the push platform configuration we also need you to configure your security token values so that our SDK can recognise authenticated security tokens (JWTs) passed by your app to the SDK. We explain how we use security tokens in more detail later.
To complete this step, check out the guide Create a push notification profile.
Now that Dotdigital knows how to use push with your app, it’s time to embed our SDK into your app so that it can pass back the necessary information to send messages to a specific user.
The SDK communicates with our platform for you to:
- Register your app users into Dotdigital as contacts.
- Collect the necessary push tokens from the users device to allow pushes to be sent.
We need to ensure that it is your app registering users for push and this is done by your app passing a JWT (JSON Web Token) to the SDK. The passed JWT is verified using the authorisation information for the JWT you configured in your push notification profile in Step 1, and if valid the user is registered. Your app will need to provide a valid JWT to initialise the SDK.
To learn more, check out the guide Create a JWT.
To complete this step, select the links below for the technologies used to build your app:
Supported iOS and Android versions
Our mobile SDKs support the latest versions of Android and iOS, as well as the previous two versions.
Dotdigital requires you to pass the SDK an unique email address per user in order for it to create or update a contact, so that you can target these contacts for push sends. Once the user is registered after passing a valid JWT all your app needs to do is update the SDKs user profile with an email address and a contact is automatically created in Dotdigital to allow you to push to this specific app user.
If you have followed all the steps above you should now see your app users appearing as contacts in Dotdigital, and you can use program builder or the omnichannel API to send them push notifications.
Updated 2 months ago