Skip to main content

Introduction

Adtrace is a mobile attribution and analytics platform designed to help app developers and marketers track, analyze, and optimize their app performance. By providing insights into user acquisition, in-app behavior, and campaign performance, Adtrace empowers businesses to make data-driven decisions. It integrates seamlessly with advertising platforms, enabling the tracking of user interactions from ad clicks to app installations and beyond. Adtrace also supports fraud detection, helping businesses maintain data accuracy and minimize ad spend wastage. Its customizable panel and detailed reports provide actionable insights for maximizing user engagement and retention.

One of the standout features of Adtrace is its real-time attribution technology, which allows businesses to measure the effectiveness of their marketing campaigns instantly. With support for deep linking and re-engagement tracking, Adtrace ensures a smooth user journey, from initial interaction to conversion. It also offers tools for cohort analysis, event tracking, and audience segmentation, enabling businesses to refine their strategies. Adtrace is known for its commitment to user privacy, adhering to global data protection regulations like GDPR and CCPA. This makes it a reliable choice for companies aiming to grow their apps while maintaining compliance with industry standards.

Adtrace concepts​

Install​

On device​

"install" concept has different meaning in attribution vocabulary than just installing apk on device. main differences are:

  • app must be opened
  • sdk integration must be checked and done correctly (data from panel)
  • lifecycle of the application must be obtains and sdk must be attached to it's callbacks.
  • sdk_click package from sdk must be send. the response for that will be attribution changing. sdk has a callback when attribution changes and it will pass an Attribution object. this attribution object contains adid from server. this id will only be generated when a device is created by the server. so in other words when sdk received adid that means server successfully created a device.

On web​

in web environment there is no such thing as "install" defined in native android or ios. to simply this concept the install for web apps will be defined as:

  • web app opened on the users "browser"
  • sdk is correctly implemented and initialized with correct config data (from panel)
  • on PWA "install on device" which makes a shortcut will not do anything. this DOES NOT mean install. it is only for creating a shortcut on the deivce screen.
  • due to limitation of web to access device id, a generated uuid will be assumed as device id. this means if app does not have access to it's local storage for persistance, it will not be able to detect the device. so inconoto mode, changing browser will make another sdk_click call and new install even on same device.

Which SDK to use?​

What is a "Tracker" and how it works?​

Event Tracking​

How to debug?​