Second-Generation Managed Packaging Developer Guide
Workflow for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
App Analytics Use Cases
Enable App Analytics on Your Second-Generation Managed Package
Download Package Usage Logs, Package Usage Summaries, and Subscriber Snapshots
Considerations for Custom Interactions
Package Usage Logs Schema
Subscriber Snapshots
Test Custom Integrations
Gaps Between First-Generation and Second-Generation Managed Packaging
Package Usage Logs
Analyze adoption and user behavior, then make informed feature development decisions
based on data from package usage logs. AppExchange App Analytics tracks UI, API-based,
Lightning-based, and Apex operations, and it logs each CRUD operation on components and custom
objects in packages. Events from sandbox and trial orgs are tracked in package usage logs. Events
from scratch orgs aren’t tracked.
AppExchange App Analytics is subject to certain usage restrictions as described in the AppExchange Program Policies.
Note
-
How to Read App Analytics Package Usage Log Data
App Analytics package usage logs contain data about how subscribers interact with your managed package. Your managed package contains packaged components, and each package usage log line describes an interaction that a user has with one of your packaged components. To understand that interaction, analyze each log line—or record—and focus on: what packaged component was accessed, who interacted with that packaged component, and how that packaged component interaction occurred. Finally, analyze the specific interaction data. -
Package Usage Logs Schema
Make informed development decisions based on package usage log data. Analyze adoption, user behavior, company information, and Lightning app and page usage data. Package usage logs list activity during a 24-hour period, between 12:00 AM and 11:59 PM UTC.