Implementing event tracking

Enable 3rd party event tracking

To enable 3rd party event tracking, you need to set in the noctuagg.json file. There are 3 services that you can enable:

"adjust": {
    "environment": "production",
    "android": {
      "appToken": "u12y3gu21",
      "eventMap": {
        "purchase": "qye2vk",
        "login": "xoizir"
      }
    },
    "ios": {
      "environment": "production",
      "appToken": "3kh12b",
      "eventMap": {
        "purchase": "qye2vk",
        "login": "xoizir"
      }
    }
  },
  "facebook": {
    "android": {
      "appId": "3123213123",
      "clientToken": "31232l13hnklj12",
      "displayName": "SDK Test Noctua",
      "enableDebug": true
    },
    "ios": {
      "appId": "123213123123",
      "clientToken": "k12bh3kj123kj",
      "displayName": "SDK Test Noctua",
      "enableDebug": true
    }
  },
  "firebase": {
    "android": {
      "customEventDisabled": false
    },
    "ios": {
      "customEventDisabled": false
    }
  }

Note

You don't need to provide all the services yourself. The configuration from Noctua Team is the default one.

Event map

The event map is a dictionary that maps the event name to the event name in the 3rd party service. This is useful if you want to use the same event name in the SDK as the one in the 3rd party service that use backend-generated events like Adjust.

{
  ...
  "eventMap": {
    "purchase": "qye2vk"
  }
  ...
}

Implementing event tracking

To implement event tracking, you need to use the Noctua.Event class. We have 2 types of events that you can use:

Custom Event

Implement custom event tracking to gather valuable user data.

Revenue Event

Track revenue to gather valuable user data related to revenue.

Note

You don’t need to implement any tracking related to purchases. It’s already being handled within our In-App Purchase feature.