Last modified November 22, 2014 by Gordon Glauser

Going Live Checklist

Follow this guide to ensure your Swrve integration is sending all the information needed to meet your goals.

Production Environment

❑ Create Production environment
❑ Update API Key in your app
❑ Update credentials on the Integration Settings page
❑ Add currencies on the App Settings page

You have most likely been testing in a Sandbox environment. Sandbox environments are for testing only, and are not built to handle more than 100 DAU. Create a Production dashboard by adding a platform to your app. Choose a platform type of Production. This environment will have a new API Key. Be sure to change the API Key in your app before you release. You will also need to update credentials like your push certificates and IAP validation details on the Integration Settings page. Lastly, if you are using virtual currencies, add these on the App Settings page.

Segments, Funnels and Resources

❑ Populate with segments
❑ Populate with funnels
❑ Populate with resources
❑ Test funnels

You should create these items in your Production environment. Remember that Segments and Funnels are not retroactive; we recommend you create these before you launch. Test funnels before launch by triggering the events in order to ensure they are being captured in your funnel report.

IAP Event

Register a QA device with Swrve
❑ Make a virtual purchase
❑ Verify the product ID in the QA event log
❑ Verify the currency code is an iSO currency code in the QA event log
❑ Verify the quantity is correct in the QA event log
❑ Upload and verify Licensing Key, iTunes Bundle ID or Package Family Name

The IAP event is how you keep track of all real world purchases. Ensure that you are sending this event with the correct information for productID, currency code and quantity. Use the logging feature of your QA device to verify all information is being sent correctly. When you make a purchase in your test environment, double check that the reporting in the dashboard is accurate. Swrve provides revenue figures in your dashboard which are as accurate as possible. However, in order to do this, you must enter your Licensing Public Key for Google, iTunes Bundle ID for Apple, or Package Family Name for Windows. On the Setup menu, click Integration Settings to check this information is entered and correct.

Virtual Currencies

❑ Add all virtual currencies to dashboard
❑ Verify currencyGiven event behaves correctly

You must add all virtual currencies in the dashboard in order for Swrve to process transactions. On the Setup menu, click App Settings to view or add currencies. Make sure you enter the name of the currency exactly as it has been configured in your app (for example, case-sensitive). Ensure that your currencyGiven event is correct by using your QA device. Take yourself to a point in the app where currency is given. Follow the logging for your device to see the details on this event.

Push Notifications

❑ Upload and verify APNS Certificate, Cloud Messaging Server Key or Windows Push Notification Service SID and Client secret key
❑ Register a QA device with Swrve
❑ Send a push notification to the QA device
❑ Verify that an engaged event is recorded in the QA log, for example Swrve.Messages.Push-123.engaged
❑ Test key/value pairs behave as expected

Upload your Apple APNS Certificate to the dashboard. Remember that the Production certificate will be different from the one you used in testing. Google requires a Cloud Messaging Server Key and Windows requires a Push Notification Service SID and Client secret key. On the Setup menu, click Integration Settings to check the correct Certificate or Key has been uploaded.

In-App Messages and Conversations

❑ Register a QA device with Swrve
❑ Set up an in-app message or Conversation, add your QA device to the message and get it to display in your app
❑ Get a list of instrumented deeplinks from engineering team
❑ Test behavior of each deeplink

Check your deeplinks have been instrumented and perform as expected by creating an in-app message or Conversation. For at least one button assign a ‘Deep Link’ as the action. Enter the deeplinks as listed by your engineering team. Choose a trigger event for this QA message which is easy to fire. Click the button and verify that the deeplink works correctly. Repeat for all deeplinks in your integration.

Resource A/B Testing

❑ Register a QA device with Swrve
❑ Setup a test for each resource A/B test that you will run
❑ Put QA device in each treatment of each resource A/B test
❑ Verify the correct experience is seen for each treatment

To experience what your users will when they are in a resource A/B test treatment, on the Campaigns menu, click Resource A/B Testing. Choose a test you have created. At the bottom of the page you will see a list of QA Devices with radio buttons. These buttons allow you to put your QA device into each treatment in the test. You will need to shut your app down completely on the device (that is, hard close) in between moving from one treatment to the next.