Testing Push Notifications

Best Practices

The following are the best steps and practices for setting up a test for push notifications.

For iOS

When setting up your first In-App test push, TUNE recommends setting up two separate mobile apps in the platform; one for Production and one for Development. Please pay special attention to the recommendation to create separate Development and Production apps within your TMC account so that you can test everything completely without impacting your production data. Debug macros can be set to automate this process.

  • Development app: When the application is a development app, it is past most testing and is ready for production. Typically, developers use development mode as a local version of the application that multiple developers can maintain, and sync under a controlled version.
  • Production app: When the application is in production stage and is used on release. TUNE recommend doing most changes in the development app, verify that everything is working as planned, and then implementing the changes to the production app.

The main distinction for both the production app and the development app is the push certificate. The push certificate can be setup as either a development certificate or a production certificate. Initially, TUNE recommends working with the development certificate first. In order for your push test to work, verify that the app build and the certificate type match (Dev Build-Development Certificate OR Prod Build-Production Certificate).

Important Note: If you are building and testing your application through Xcode, your application resides in the development build. If your application is in production and in the app store, your application resides in the production build. These distinctions are key to a successful push test!

For Android

The testing process for Android is simplified because it does not have distinguishing certificates. If you are using Firebase to generate your device tokens you will rely on the registration_id variable with our Tune.setPushRegistrationId(String registration_id) method.

The following section outlines how to retrieve the Firebase registration_id: https://firebase.google.com/docs/cloud-messaging/android/client.

Once you have the registration_id value, you can insert that value in our Tune method: Tune.setPushRegistrationId(registration_id) and retrieve the device token. If this is your first time setting up push and are only using In-App Marketing as your push provider, use the Tune.setPushNotificationSenderId(String senderId).

Important Note: When setting up Android, be sure that you are using the correct setPush method (setPushRegistrationId vs setPushNotificationSenderId). These distinctions are key to a successful push test!

Get Started!

Once you’ve received your first successful push test, you can get started with your campaign testing. When starting your very first push test, there are a few steps TUNE recommends or the best test experience. Before we get started, we will need to register your device as a test device. Please go to the Attribution Analytics page and on the left hand menu and select Test profile. From there, add your device's information in the Test Profile. For more information on this topic, please see our Creating a Test Profile article in TUNE Help.

Now that you have a test device set up, you can move onto the In-App Marketing platform page. Once you are in the IAM platform page and have set up your application, you can begin testing your campaigns on your test device.

Test your campaign on your device:

  1. Open In-App Marketing.
  2. Go to the Messaging tab on the right.
  3. Create a campaign. Once you've composed a campaign and are just ready to send out your notifications, you can test your campaign on your test device.
  4. Under the compose tab, you will see a test device on the right. From there you can see how your message appear on a device. For real time testing, select from the device you want to test from the drop down.
  5. Select your test device and send yourself a test message!

For more information on creating and testing your campaigns, please see Sending a Test Message section in our Creating a Push Campaign article.

Note: If you are including an image in your push campaign, TUNE's recommended image specifications are 600x300. TUNE recommends 600x300 image specifications to ensure that the image is rendered on low end and mid range devices. While a large size image with 2:1 aspect ratio may render on high end devices, it my not on low end to mid range devices. We recommend testing the image on devices in addition to using preview mode.

TestFlight

For information on testing In-App Marketing using TestFlight, see our Testing Push Notifications with TestFlight article.

No Comments

Leave a reply