Subscriber Snapshots

Subscriber snapshots give you a point-in-time summary of subscriber activity. Use subscriber snapshots to see usage trends by org and package.

AppExchange App Analytics is subject to certain usage restrictions, as described in the AppExchange Program Policies.

Note

AppExchange App Analytics takes a daily snapshot of org, package, and custom entity data. Snapshots are captured daily at 00:00 UTC and become available for download immediately. You request a date and time, or range of dates and times, and you receive one snapshot per valid date and time requested. For example, if on April 7, 2023 you request a date and time range of StartTime=2023-04-04T00:00:00Z EndTime=2020-04-07T00:00:00Z, you receive three snapshots, one for each completed day.

Field	Description
attribute_name	Represents a characteristic of a custom entity, managed package, package version, or org. Example: `UsersWithMFA`
attribute_value	A string that represents a characteristic or measure of an `attribute_name`. Examples: `0.570` `1.000` `Acme, Inc.` `Active` `Deprecated`
count	Total records for the custom entity in that org on the specified snapshot date.
custom_entity	The developer name of the component or custom object. Examples: `Amount` `Travel_Expense`
date	The subscriber snapshot date requested, in `YYYY-MM-DDT00:00:00Z` format. Each point-in-time snapshot is captured at `00:00 UTC` on the date specified. Example: `2023-04-04T00:00:00Z`
managed_package_namespace	Namespace of the package. Example: `sfdx_isv_pkg001`
organization_edition	The name of the Salesforce edition the subscriber org is using. Examples: `Developer Edition` `Enterprise Edition` `Unlimited Edition`
organization_id	The 15-character ID of the subscriber org. Example: `00D4m000000Td8Y`.
organization_name	The name of the subscriber org. Example: `My_Org`.
organization_status	The paid status of the subscriber org. Examples: `ACTIVE` `DEMO` `FREE` `TRIAL`
package_id	The ID of the managed package. Example: `033xx00000000CI`.
package_version_id	The ID of the managed package version. Example: `04t6A0000004eytQAA`.

The attribute_name and attribute_value fields are a key-value pair. Each pair has a specific scope. Some pairs provide org-level metadata, and others provide custom entity, managed package, or package version metadata,

Interpret these two fields in tandem using the information in this table.

As of Spring ’25, trial orgs aren’t included in subscriber snapshot MFA data.

Note

attribute_name	Description	attribute_value	Scope
`UsersWithMFA`	Represents the percentage of your unique, standard users who enabled multi-factor authentication (MFA) using one of these methods. User permission sets Profile permission sets High-assurance session security level The corresponding `attribute_value` is always between 0 and 1, where 0 represents 0% and 1 represents 100%.	Percent Examples: 0.060 0.940	Org-level. For all packages installed into an active or demo org, the same org-level `UsersWithMFA` percent repeats on every package version row.

attribute_name

Description

attribute_value

Scope

UsersWithMFA

Represents the percentage of your unique, standard users who enabled multi-factor authentication (MFA) using one of these methods.

User permission sets
Profile permission sets
High-assurance session security level

The corresponding attribute_value is always between 0 and 1, where 0 represents 0% and 1 represents 100%.

Percent

Examples:

0.060
0.940

Org-level.

For all packages installed into an active or demo org, the same org-level UsersWithMFA percent repeats on every package version row.

Second-Generation Managed Packaging Developer Guide

Subscriber Snapshots