Once you've integrated Taplytics Push Notifications code by following the instructions laid out in our Mobile SDK Docs for the relevant platform(s), you will need to upload your Apple and/or Google Push Certificates before you can use Taplytics Push Notifications.
Upload your Apple Push certificates so you can send push notifications to iOS devices using Taplytics. If you don’t already have your certificates created, follow our steps below to generate a P8 Key or P12 Push Certificate. Note that you are able to upload and use P8 or P12 certificates interchangeably but P12 certificates come with an expiry date.
- Go to the Apple Developer Member Center website and select "Certificates, Identifiers & Profiles".
- On the left-hand side navigation bar, click on "Keys" and create a new P8 Key by hitting the "+" button.
- Give your P8 Key a name and select Apple Push Notifications service (APNs). Then hit Continue.
Confirm that you've selected the correct services and hit Register.
Download the P8 Certificate when you're ready. Make sure to keep the file safe as you're only able to download it once off of Apple Developer Center. Keep this page handy or copy the Key ID and your Apple Developer Team's ID as you'll need it for the next step.
- Head over to your Taplytics project now and go to the Push Notifications Settings page. You can find that by going to "Settings" on the left navigation menu and selecting the "Push Notification Settings" tab.
- Select "p8" as the Certificate type and upload your certificate to the environments you need. You'll also need to provide these fields:
- Key ID: The P8 Certificate's Key ID (The one we copied earlier)
- Team ID: The Apple Developer Account's Team ID. You can find that on the Membership page at https://developer.apple.com/account
- Bundle ID: The bundle ID / App ID that the App is created with
That's it! If you've already implemented push on your App, you should now be able to send push notifications to iOS devices through Taplytics!
To begin, create a certificate signing request file. This is used to authenticate the creation of the certificate. On your Mac, launch the Keychain Access application. In Keychain Access, click the "Certificate Assistant", and select "Request a Certificate From a Certificate Authority".
Enter your Name and User Email and make sure to click "Saved to disk". Next, press "Continue". Your ".certSigningRequest" file will save to your Mac.
Go to the Apple Developer Member Center website and select "Certificates, Identifiers & Profiles".
On the left-hand side navigation bar, click the "Identifiers" and look for your project. If your app is not on the list, you can click the "+" button to create a new app ID. If you need some help check out the Apple doc for further information.
Click on your app to open and scroll down to find the "Push Notifications" name.
Click the configure button
We will now create certificates for both development and production.
Let's start with development! Click "Create Certificate" under Development SSL Certificate to begin generating your cert.
Click Create and you will be sent to the page where you can upload your .csr file
Now, you need to upload the CSR file you created earlier. Press "Choose File" and find the ".certSigningRequest" file saved to your Mac.
Click "Download" after successfully creating a certificate.
Once the download is completed, open the file to save your development certificate to your keychain.
Now that you have your development certificate generated, you to need to create one for production. Repeat the above steps to create a production SSL certificate.
Once you've generated both the development and production certificates, venture back to your Keychain so you can export your certs and upload them to Taplytics.
When you are in Keychain, go to "My Certificates". Find your newly created development certificate, right click, and hit "Export".
Save the ".p12" file to your computer. The modal that appears will ask you to create a password to protect your exported items. In order to upload to Taplytics properly, leave the password field empty. Instead, just press "OK".
Enter your Keychain password in order to export your files.
Locate your production certificate in the same list. Once you locate it, export it the same way as the one for development. Remember to change the name of your export file so you don't replace the one you just created for development.
If Keychain Access is giving you grief and your production certificate is not in your list, try searching for "Apple Push Services" in the search window. Once you find it, drag your file to "login" and you should now be able to export your production certificate from Login—My Certificates.
Login to your project in Taplytics and navigate to "Settings" > "Push Notifications Settings". Click the upload button and select your development and production certificates to upload. Once the upload completes, your screen will display both of your certificates.
Great Job! You can now send push notifications to iOS devices using Taplytics!
Taplytics lets you keep a copy of both your P8 and P12 Certificates on the dashboard at once. To switch between using P8 or P12, simply select the Certificate Type and hit "Save Credentials". Your certificate will be updated on Taplytics for use within a couple of minutes!
Before you can get started using Taplytics push notifications for Android devices, you need to upload your Firebase Cloud Messaging (GCM) credentials.
First, head over to the Firebase Console. If your project is already in Firebase, simply enter that project. Otherwise, click "Add project".
Navigate to your project's settings.
From here, switch to the "Cloud Messaging" tab where you will find your project "Server Key" and "Sender ID"
Login to your project in Taplytics and navigate to "Settings" > "Push Notifications Settings". Then go down to the 'Firebase Cloud Messaging' section and copy/paste your "Server Key" in the "FCM API Key" field and your "Sender ID" in the "Sender ID" field. Finally, click 'Save Credentials' and you're on your way to sending Push Notifications to Android devices!
Updated about 1 year ago