Marketplace system tables reference
Preview
This system table is in Public Preview. To access the table, the schema must be enabled in your system
catalog. For more information, see Enable system table schemas.
This article provides an overview of how to use system tables to help operationalize your Databricks Marketplace selling process.
Marketplace system tables live in the system.marketplace
schema. The following tables are available:
Listing access: Records the consumer info for completed request data or get data events on your listings.
Funnel events: Records impressions and actions taken on your listings.
Note
You can use the Provider Analytics Dashboard to monitor recipient usage metrics. The dashboard pulls data from the Marketplace system tables. See Monitor listing usage metrics using dashboards.
Listing access events table
The listing_access_events
table retrieves the consumer info for completed request data or get data events on your listings.
system.marketplace.listing_access_events
has the following schema:
Column name |
Data type |
Description |
---|---|---|
|
string |
The account ID that hosts the listing. |
|
string |
The metatore ID that hosts the listing. |
|
string |
The cloud provider of the metastore that hosts the listing. |
|
string |
The region of the metastore that hosts the listing. |
|
string |
The provider profile ID. |
|
string |
The provider profile name. |
|
string |
The listing ID. |
|
string |
The listing name. |
|
string |
The underlying Delta Sharing recipient name for the consumer. The value is |
|
string |
Whether the consumer is on a Databricks account or not. Values will be either |
|
string |
The consumer’s cloud. Nullable if |
|
string |
The consumer’s region. Nullable if |
|
string |
The consumer’s metastore ID. Nullable if |
|
string |
The consumer’s email address. PII. |
|
string |
The consumer’s name. PII. |
|
string |
The consumer’s company. |
|
string |
The consumer’s intended use of the listing. |
|
string |
Any additional comment the consumer left. |
|
string |
The type of access. The value can be either |
|
date |
The UTC date the event happened. |
|
timestamp |
The exact UTC timestamp when the event happened. Timezone information is recorded at the end of the value with |
Listing funnel events table
The listing_funnel_events
table analyzes impressions and actions taken on your listings. The event_type
tells you what action the consumer took on your listing.
system.marketplace.listing_funnel_events
has the following schema:
Column name |
Data type |
Description |
---|---|---|
|
string |
The account ID that hosts the listing. |
|
string |
The metatore ID that hosts the listing. |
|
string |
The cloud provider of the metastore that hosts the listing. |
|
string |
The region of the metastore that hosts the listing. |
|
string |
The provider profile ID. |
|
string |
The provider profile name. |
|
string |
The listing ID. |
|
string |
The listing name. |
|
string |
The type of consumer action. See Event types. |
|
timestamp |
The exact UTC timestamp when the event happened. Timezone information is recorded at the end of the value with |
|
date |
The UTC date the event happened. |
|
string |
The consumer’s cloud. Nullable if |
|
string |
The consumer’s region. Nullable if |
Known limitations
As of March 12, 2024, Marketplace system tables include activity from consumers using Databricks on Google Cloud. Tables do not include Google Cloud consumer activity prior to this date.
In the
listing_funnel_events
table, the event types ofABANDON_FAIL_DATA
andFAIL_GET_DATA
were not recorded prior to November 30, 2023.
Example queries
This section includes the following sample queries you can use to gain insight into consumer activity on your listings.
Consumer requests from the last 10 days
SELECT event_date, provider_name, listing_name, listing_id, consumer_delta_sharing_recipient_name, consumer_cloud, consumer_region, consumer_name, consumer_email, consumer_company
FROM system.marketplace.listing_access_events
WHERE event_type = 'REQUEST_DATA'
AND event_date >= date_add(current_date(), -10)
Top listings by number of requests
SELECT listing_name, consumer_cloud, count(*) as requestCount
FROM system.marketplace.listing_access_events
GROUP BY listing_name, consumer_cloud
ORDER BY requestCount DESC