Second-Generation Managed Packaging Developer Guide

Second-Generation Managed Packages
What’s a Second-Generation Managed Package?
Before You Create Second-Generation Managed Packages
Workflow for Second-Generation Managed Packages
Components Available in Managed Packages
Behavior of Specific Metadata in Second-Generation Managed Packages
Develop Second-Generation Managed Packages
Install and Uninstall Second-Generation Managed Packages
Prepare to Distribute Your Second-Generation Managed Package
Push a Package Upgrade for Second-Generation Managed Packages
Advanced Features for Second-Generation Managed Packages
Best Practices for Second-Generation Managed Packages
Manage Licenses for Managed Packages
Manage Features in Second-Generation Managed Packages
Get Started with AppExchange App Analytics
App Analytics Use Cases
Enable App Analytics on Your Second-Generation Managed Package
Download Package Usage Logs, Package Usage Summaries, and Subscriber Snapshots
AppExchange App Analytics Best Practices
How Does AppExchange App Analytics Data Flow?
How Should I Plan My App Analytics Query Strategy?
Recommendations
Small-Sized Partners
Medium-Sized Partners
Large-Sized Partners
Where Do I Go for More Information About AppExchange App Analytics Queries?
Package Usage Summaries
Package Usage Logs
Subscriber Snapshots
Test Custom Integrations
AppExchange App Analytics Developer Cookbook
Gaps Between First-Generation and Second-Generation Managed Packaging
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Medium-Sized Partners

Medium-sized partners have bigger subscriber bases and about six managed packages. A medium-sized partner’s total daily usage data across all managed packages is at or just over 20 GB. Also, this partner’s queries approach or hit the 15-minute processing time limit.
Available in: both Salesforce Classic and Lightning Experience
Available in: Enterprise, Performance, Unlimited, and Developer Editions

We recommend that after you run your regular queries one time, use catch-up queries as your main queries for subscriber snapshots and package usage summaries. Use a combination of daily queries and catch-up queries for package usage logs.

Data Type How to Get Started How to Schedule Catch-Up Queries
Subscriber Snapshots An initial query to retrieve data from when App Analytics was enabled for your managed packages.
  • One daily query.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to 30 days ago.
  • Omit EndTime.
  • Each day advance StartTime and AvailableSince by 1 day.
Package Usage Summaries An initial query to retrieve data from when App Analytics was enabled for your managed packages.
  • One daily catch-up query.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to the first of the previous month.
  • Omit EndTime.
  • Each day advance AvailableSince by 1 day.
  • Each month advance StartTime to the first of the previous month.
Package Usage Logs One regular daily query per package.
  • One daily catch-up query per package.
  • Set AvailableSince to the day and time your last regular query ran.
  • Set StartTime to 30 days ago.
  • Set EndTime equal to the StartTime of your regular query.
  • Each day advance StartTime, EndTime, and AvailableSince by 1 day.

Example

Half of your customers use your package on an NA or EU instance, so you run your regular queries at 18:00 UTC. The other half of your customers are on an AP instance, so you create catch-up queries to ensure that you capture data from around the world.

  1. On March 31 at 18:00 UTC, run your regular package usage log queries for each of your packages.

    Package 1

    Package 2

  2. On April 1 at 18:00 UTC onwards, run regular and catch-up package usage log queries.

    Package log file regular and catch-up queries timelline on April 1.

    A. Regular Queries

    Package 1

    Package 2

    B. Catch-Up Queries

    Package 1

    Package 2

  3. On April 2, repeat the same queries that you ran on April 1, but advance the queries by a day. Package log file regular and catch-up queries timeline on April 2.

    A. Regular Queries

    Package 1

    Package 2

    B. Catch-Up Queries

    Package 1

    Package 2