The init code in the wizard already contains the site key and the collect address. The app id is part of the upload URL and must match the registered value exactly, or events are not accepted.

Prerequisites

The plan includes the app platform. You can change startup code. The application id, bundle id, or HarmonyOS bundle name must match the value passed at init.

Steps

1. Register the app id

   Open ConsoleApp analyticsConfigurationSDK code and add the id that matches the binary. Unregistered apps are rejected.

2. Install the SDK

   Use the install command, init order and version on that page. Details are in Android, iOS, and HarmonyOS. The matrix is SDK overview.

3. preInit first, init after consent

   In the domestic mode, do not send network traffic before the user accepts the privacy policy. After consent, finish init. The SDK sends $app_start on launch.

4. Run the app once

   Cold-start it on a device or simulator.

Verify

Open ConsoleApp analyticsRealtime and look for $app_start. If it is missing, compare the app id and the endpoint.

Common failures

The id does not match the binary, the plan does not include apps, or init ran before consent. If remote config disables sending, the SDK stops. See Collection controls.

Next steps

Exclude test devices and beta builds on ConsoleApp analyticsConfigurationApp settings; until you save rules there, the web exclusion rules apply. Then add custom events with Custom events.