Skip to main content

Test the integration

The most important concept is "Install". "first open" . after installation on device is considered as "install". in order for you to track information of user interacting with your app, a valid "install" must be recorded first. sessions and events are received and stored when sent to Adtrace but shown only after sending "install". In order to make sure that your implementation is done properly you can use the following options.

Using logs
  1. set logLevel to verbose and environment to sandbox.
  2. make sure to connect your device so that it prints the logs ('Adtrace' tag for filtering).
  3. uninstall and reinstall the application and wait for the logs after "first open".
  4. after a few seconds, search for "adid" in server responses. it is a hash token id which is assigned to the application on a device by the server after install. receiving this id means your install recorded correctly. if no adid found, it's likely that there is a problem with integration. review the previous steps and see the example apps and try again.
"adid" : "mhxd6or7d3u57fnbdy2r4urdrdxr7tlr"
Using panel
  1. for android devices find your device google advertising id (a.k.a gps_adid,GAID) usually in this path on the device: Settings > Google > Ads. for iOS devices you need to retrieve device's IDFA programmatically. (in both cases SDK log prints device IDs in Verbose mode )
  2. go to Adtrace panel (login to your account and your app), go to the path: Settings > Testing console.
  3. enter your device id and choose the type of it. if no "install" found for your ID, it's likely that there is a problem with integration. review the previous steps and see the example apps and try again.
gps_adid: 7c67ef26-830e-49b7-8948-b868b19bf4b3
// or
idfa: 7c67ef26-830e-49b7-8948-b868b19bf4b3
Details

Using callbacks Adtrace SDK enables callbacks for different requests. one of the most important ones is config.attributionCallback. this function gets called when attribution is changed (e.g. when install occurred).

you receive different values from the Attribution object one of which is adid. this is a hash token id which assigned to the application on a device by the server after install.

if this method gets called and you receive the adid "install" is recorded properly. if it does not get called in a few seconds after "first open" (in the worst cases), it's likely that there is a problem with integration. review the previous steps and see the example apps and try again.