Checklist

Before you publish the mobile app or website and run ad campaigns, go over these settings and verify Integration status.

For mobile app

• Check MyTracker configuration

  Default settings are not always optimal for every app. For example, bufferingPeriod; it's the time during which events are accumulated locally on the device before being sent to the MyTracker server. The default value is 15 minutes, meaning all custom events marked in the app are sent to the server once every 15 minutes.

  If an average user session in your app is less than 15 minutes, the app is not opened frequently, or there are important events you need to get as fast as possible, change the buffering period or use the flush method after each critical event. Learn more for iOS, Android, Unity, Flutter, and React Native.

• If you publish an app on the App Store or Google Play, check the accuracy of the privacy and security information

  Before you publish the app with MyTracker SDK, make sure to read the Privacy & Security section. This information is necessary for the correct filling of the required sections in the App Store and Google Play.

• Together with your product and marketing teams, make sure all necessary custom events are sent to MyTracker

  Users’ in-app actions, like adding to cart, signing up for a test drive, are marked using custom events. Before you update the app in the store, check that events are marked correctly for both product and marketing teams, and that there are enough of them to assess user behavior and optimize ad campaigns. Learn more for iOS, Android, Unity Flutter, and React Native.

• Decide if you need deep links in your ad campaigns

  Deep link are a great tool for working with both new and existing users. With smart links, you can set up an ad campaign for the entire audience and direct users who installed your app straight to a specific location within it, bypassing the app store. This requires configuration on the development side.

  Also, decide on the deep link scheme that is supported by the app

• Upload keys to verify payments

  By default, all MyTracker financial metrics and prediction tools work only for verified payments. Besides, some data (for example, subscription tracking) cannot be obtained without verification. Upload the keys for payment verification into the MyTracker interface.

• Before you run an ad campaign, make sure the latest app version published in the store supports MyTracker

  In the App Store, Google Play, and other stores, app updates do not happen immediately. Before you launch a user acquisition campaign, make sure MyTracker SDK is embedded in the latest version of the app in the store.

  In addition, MyTracker registers an Install on the first launch of an app with the embedded SDK, so, it takes some time for your current audience to appear the tracking system. The exact length of time depends on the app update speed in different stores, as well as the app usage frequency. On average, it takes anywhere from one to three months, or longer for certain app types.

For website

• Make sure that the web counter code is added on all pages on your site

  You need to place the code inside the HEAD or BODY block as close to the top of the page as possible.

• Check that the web counter is called by the site correctly

  There are many reasons why the counter may not be called. For example:

  • The site uses ad blockers.
  • The loading of the counter is initialized by some action on the site.
  • The web counter was not installed or was removed from the page.
  • The site uses redirection that does not pass URL parameters.

• Together with your product and marketing teams, make sure all necessary custom events are sent to MyTracker

  User actions on website, like adding to cart, making an appointment, are marked using custom events. Before you update the website, check that events are marked correctly for both product and marketing teams, and that there are enough of them to assess user behavior and optimize ad campaigns.

• Check method calls for user tracking

  If the site provides user registration and authorization (user tracking), make sure that the setUserID method is called by your site before loading the main MyTracker web counter.

  Also, check that when users register and authorize, you call methods goal: 'mt_registration' and goal: 'mt_login’ to pass it on to MyTracker.

• If necessary, turn on automatic event tracking

  If you need to track automatic events, such as catalog views or site searches, make sure that the Automatic events option is enabled on the web application page in the MyTracker interface.

• Learn the documentation before running paid traffic

  If you plan to run paid traffic to your site, learn about traffic attribution/reattribution and types of advertising links.

If you have any questions, please contact our support team.