This page contains guidance to help you better understand how our customers are using GitLab so that you can be more prepared and informed in customer conversations.
Using GitLab Version Check, GitLab usage data is pushed into Salesforce for both CE, EE and EE trial users. Once in Salesforce application, you will see a tab called "Usage Statistics". Using the drop down view, you can select CE, EE trails or EE to see all usage data sent to Gitlab. Since version check is pulling the host name, the lead will be recorded as the host name. Once you have identified the correct company name, please update the company name. Example: change gitlab.boeing.com to Boeing as the company name.
To view the usage, click the hyperlink under the column called "Usage Statistics". The link will consist of several numbers and letters like, a3p61012001a002. You can also access usage statistics on the account object level within Salesforce. Within the account object, there is a section called "Usage Ping Data", which will contain the same hyperlink as well as a summary of version they are using, active users, historical users, license user count, license utilization % and date data was sent to us.
A few example of how to use Usage Statistics to pull insight and drive action?
Take a look at a Training Video to explain in greater detail by searching for the "Sales Training" folder on the Google Drive.
In an effort to make the Usage/Version ping data simpler to use in SFDC, there are 2 fields directly on the account layout - "CE Instances" and "Active CE Users" under the "GitLab/Tech Stack Information" section on the Salesforce account record.
The source of these fields is to use the latest version ping record for and usage record for each host seen in the last 60 days and combine them into a single record. The hosts are separated into domain-based hosts and IP-based hosts. For IP based hosts, we run the IP through a reverse-DNS lookup to attempt to translate to a domain-based host. If no reverse-DNS lookup (PTR record) is found, we run the IP through a whois lookup and try to extract a company name, for instance, if the IP is part of a company's delegated IP space. We discard all hosts that we are unable to identify because they have a reserved IP address (internal IP space) or are hosted in a cloud platform like GCP, Alibaba Cloud, or AWS as there is no way to identify those organizations through this data. For domain-based hosts, we use the Datafox &/or DiscoverOrg domain lookup API to identify the company and firmographic data associated with the organization and finally the Google Geocoding API to parse, clean, and standardize the address data as much as possible.
These stats will be aggregated up and only appear on the Ultimate Parent account in SFDC when there are children (since we don't really know which host goes to which child).
To see a list of accounts by # of CE users or instances, you can use the CE Users list view in SFDC. To filter for just your accounts, hit the "edit" button and Filter for "My Accounts". Make sure to save it under a different name so you don't wipe out the original. These fields are also available in SFDC reporting.
A few caveats about this data:
For the process of working these accounts, appending contacts from third-party tools, and reaching out, please refer to the business operations section of the handbook.
The goal of this process is to capture information about the technology an account in SalesForce uses in each stage of their DevOps Tools landscape (based on competitors as of 2020-04-10). This will allow us to market & sell to specific stages in their CI/CD process more accurately.
Please enter the following data in the "Stage Technology" section of the Account object in SFDC:
st_(Stage) Tech: Current technology used by prospect/customer (Including GitLab)
st_(Stage) Appetite for Replacement: Red (Don't want to change), Yellow (Might change) /Green (Willing to change)
st_(Stage) Contract End Date: As exact as possible date their current technology contract end
This is to support the FY21Q1 OKR for identifying third-party tools. Please add feedback, requests, and other commentary about this to the linked OKR issue.
See the License Usage Handbook for more information.