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.

• 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
  organization_name organization_status organization_edition organization_type	organization_country_code organization_language_locale organization_time_zone organization_instance cloned_from_organization_id

• 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.