---
title: Retrieve your tracker ID
slug: optimizely-connect-platform/docs/retrieve-your-tracker-id
docTags: 
createdAt: 2026-07-23T12:37:04.808Z
---

Before you can publish and install your app, you need to know the tracker ID of the OCP account where you want to install the app.

## List the accounts you can reach

Run the `ocp accounts whoami` command to list every account you can reach, grouped by organization. The **OCP/ODP accounts** table gives the tracker ID, name, availability zone, and type of each account.

```shell
$ ocp accounts whoami
  Profile

    id                  c19a5189-5a0d-4b7f-8272-f26b5d954320
    email               john.smith@acme.com
    role                deployer
    vendor              acme
    username            jsmith
    github username     johnsmith
    created             2025-01-01 15:00

  Legacy account access

    tracker Id  availability zone
    euYdNiVdeR  us

  OptiID account access

    Organization        Acme Corporation

      OCP/ODP accounts

        tracker Id      name          availability zone  type
        euYdNiVdeR      Acme Test     us                 OCP
        KcTMuByrxc-eu1  Acme Test EU  eu                 OCP

      CMS instances

        acme01saas
          65bbc9e664f748f4b104b933a68fe765  Acme-PROD
          19f5af76864d43c7ba0cb39980d111d0  Acme-TEST

    ────────────────────────────────────────────────────────────────────────

    Organization        Acme Subsidiary

      OCP/ODP accounts

        tracker Id     name                availability zone  type
        KDMqBYgRRd-au  Acme Subsidiary AU  au                 ODP

  Personal apps (1)

    john_personal_app

  Vendor apps (2)

    acme_app       acme_sync_app
```

Copy the tracker ID of the account where you want to install your app. Note the availability zone as well. Commands that target an account outside the default `us` zone require the `-a=<zone>` parameter.

:::hint{type="warning"}
**Important**

Your account does not display if you lack access to the OCP instance where you want to install your apps. Ask an administrator of the organization that owns the instance to grant you a role using the **Admin Center**. Any role is sufficient. You do not need the **Developer** role. See [Developer accounts and organizations](https://docs.developers.optimizely.com/optimizely-connect-platform/docs/get-started-with-the-ocp2-developer-platform#developer-accounts-and-organizations) for information on access levels.
:::

### Understand the output

The `whoami` command reports the following sections, and omits any that do not apply to you:

- **Profile** – Your developer record. The `vendor` field is the developer organization bound to the configured API key. The `role` field is your role in that organization. The CLI omits fields with no value.
- **Legacy account access** – Accounts assigned to you individually before Optimizely introduced Opti ID. Most developers have no accounts assigned this way, in which case the section does not display.
- **OptiID account access** – The OCP accounts, ODP accounts, and Optimizely CMS (SaaS) instances your Opti ID user can reach, grouped by organization. This list comes from your Opti ID user rather than from the API key. It is the same for every key you configure.
  - **OCP/ODP accounts** – The tracker ID, name, availability zone, and type (`OCP` or `ODP`) of each account. An organization with no OCP or ODP accounts displays `None`.
  - **CMS instances** – The CMS (SaaS) instances in the organization, grouped by project. This subsection displays only if the organization has CMS instances. The 32-character value is the instance ID.
- **Personal apps** – Apps registered to you, with the total in the heading.
- **Vendor apps** – Apps registered to your vendor, with the total in the heading.

:::hint{type="info"}
**Note**

A warning in place of the **OptiID account access** section means the CLI could not reach the account-access service. The command still reports your profile and any legacy account access.
:::

### Get machine-readable output

Append `--json` to return the raw profile and account access as JSON, for example, in a CI/CD pipeline:

```shell
ocp accounts whoami --json
```

The CLI writes warnings to `stderr` so that `stdout` contains only JSON. Append `--noProgress` or `--no-progress` to suppress progress indicators without changing the format.