---
schema_version: "1"
id: 89837d59d325983a4a89217c08b69bcc7b93a73b498eb8f0604c0044b095e91a
title: Identify Who Interacted with Your Packaged Component
collection: developer
version: current
locale: en-us
portal_url: https://docs.salesforce.com/developer/current/en-us/platform-pkg-exchange/managed_packaging/guides/second-generation/appexchange/app-analytics/app-analytics-read-logs/app-analytics-read-logs-who-interacted.md
canonical_url: https://developer.salesforce.com/docs/platform/pkg2-dev/guide/app-analytics-read-logs-who-interacted.html
source_site: developer.salesforce.com
content_type: documentation
content_hash: d015ba899f65baf7fe493a295722ccea0e95f289ea3d2e5bbe00191747527bbc
products:
  - Second-Generation Managed Packaging Developer Guide
  - merged-docs
---

# Identify Who Interacted with Your Packaged Component

After you identify your packaged component, identify both the subscriber org and the user who triggered the interaction.

## Before You Begin

| Required Editions                                                                        |
| ---------------------------------------------------------------------------------------- |
| Available in: both Salesforce Classic and Lightning Experience                           |
| Available in: **Enterprise**, **Performance**, **Unlimited**, and **Developer** Editions |

- Identify the subscriber org with the `organization_id`. Some standard fields are always populated and provide you with info about the subscriber org. Some supplemental fields, when populated, add detail about that org.

  This table describes the subscriber org fields.

  | Standard Fields                                                                                                                | Supplemental Fields                                                                                                                                                                         |
  | ------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
  | <ul><li>`organization_name`</li><li>`organization_status`</li><li>`organization_edition`</li><li>`organization_type`</li></ul> | <ul><li>`organization_country_code`</li><li>`organization_language_locale`</li><li>`organization_time_zone`</li><li>`organization_instance`</li><li>`cloned_from_organization_id`</li></ul> |

- Use the `user_id_token` to identify and describe the user associated with the interaction. This hashed token represents the ID of the user who accessed the package. The ID persists, even if a user’s details change, across any packages that the user interacts with.

  These supplemental fields, when populated, can provide you with more data about the user.

  - `user_type`
  - `user_agent`
  - `user_country_code`
  - `user_time_zone`
  - `session_key`
  - `login_key`
    Because `user_id_token` can represent many different usage situations, we don’t recommend using App Analytics for auditing customer license usage.