Usage Data will be present in the License Utilization App in the following scenarios (assuming the sync is working as intended in each scenario):
Question: Billable Users is great, but when will I be able to see SMAU and other activity metrics?
Answer: The Product and Data teams are working to get these metrics at the subscription level, and when they do we will add to this dash! Follow the progress here (GitLab internal only).
Question: I viewed one of my Accounts, and some of the Subscription Data says "Not Available", what went wrong?
Answer: Billable User data is not yet available for some subscriptions based on the customer needing to send data (opted into Service Ping or is sending data via Cloud License) and be on version 14.1+. Some subscriptions will never receive their Billable User count because of air gapped hosting. In either scenario please post on the Feedback issue if you think the customer's subscription data should be available.
Question: I expected there to be more (or less) Subscriptions related to the Account then was is appearing, why is this?
Answer: Please confirm in the #Sales-Support slack room if you think viewing the app uncovered and issue with the customer's Subscriptions.
Data Point | Description | Source |
---|---|---|
Plan Name | Subscription GitLab Tier | Zuora 360 |
Hosting Type | GitLab.com vs Self Managed | Data Team Dashboard |
Licensed Users | Quantity of licenses sold | Zuora 360 |
Billable Users | Quantity of users who count toward being billed | Service Ping |
Seat Price | MAX of Seat Price | Zuora 360 |
Overage Value | If Over: (Billable - Licensed) x Seat Price | Calculated |
Subscription Start Date | Subscription Term Start | Zuora 360 |
Subscription End Date | Subscription Term End | Zuora 360 |
Reported Date | Date we last received billable user data | Service Ping |
First, product usage data is uploaded into Salesforce as a .csv file attachment to a License Utilization Run record. When triggered, the Run calls classes which read the .csv and inserts License Utilization records. Each of these License Utilization records know which Zuora Subscription it relates to and through this, which Customer Subscription as well. Then, we run a process which collects information from Licese Usage and Zuora Subscription Product Charge records and stamps the related Customer Subscription. On each Account record page, a button has been added which brings you to another page. This page displays all Active Customer Subscriptions related to that Account that entitle the customer to licenses.
LicenseUsageRun.trigger
. Used to break up the insertion of License Utilization records into batches.LicenseUsage.cls
.LicenseUsage.page
. Collects only the Customer Subscriptions related to the Account. Ensures the data will properly display the Seat Usage graph.