You are here:
Digital Wallet Data Lake Objects (DLOs)
During the Digital Wallet setup process, Digital Wallet creates data streams and data lake objects (DLOs) in your org. These DLOs capture your raw consumption data and track your entitlement usage on both an hourly and daily basis. They apply contractual multipliers to convert raw usage into consumption credits, all while keeping a record of the specific entitlements your company has purchased. Our enriched DLO provides critical metadata that fuels ready-to-use reports and dashboards. It also enables you to create powerful custom reports, letting you easily slice and dice your data to find advanced insights.
When Do I Add These DLOs to a Data Space?
A data space isn’t required to view consumption data in Digital Wallet. To use some Data 360 features to view consumption data, a data space is required. In these specific cases, be sure to add the appropriate DLOs to a data space:
- To view our Data 360 pre-built reports or build custom reports, add the TenantEnrichedUsageEvent and TenantUsageAttrDetail DLOs to a data space.
- To view the data in a Digital Wallet DLO using standard Data 360 features, such as Data Explorer or Query Editor, add it to a data space.
See Salesforce Help: Add Data to a Data Space Using Data Lake Objects.
Do I Incur Costs with Digital Wallet DLOs?
Many features involving Digital Wallet DLOs are provided at no additional cost. These actions don’t incur costs:
- Storing DLO data.
- Ingesting data for the DLOs via data streams.
- Using Data Explorer and Query Editor to view and run queries.
- Viewing or creating custom reports built upon the TenantEnrichedUsageEvent DLO.
These actions can incur costs. This list contains several key scenarios but isn’t exhaustive.
- Querying the Digital Wallet DLOs using a Java Database Connectivity (JDBC) connector.
- Running a query that joins Digital Wallet data with a standard, non-cost-excluded entity.
- Using the DLOs as inputs in a data transform.
- Joining a Digital Wallet DLO with a non-cost-excluded DLO.
- Querying a custom data model object (DMO) based on a Digital Wallet DLO.
Can I Modify the DLOs?
All Digital Wallet metadata, connectors, and objects are read-only. You can’t alter the usage data, or edit or delete any of the metadata, including Data Lake Objects and connectors. Data Explorer stores data in the UTC time zone, not the associated org time zone in Digital Wallet.
Digital Wallet DLOs at a Glance
| Digital Wallet DLOs | Description | Learn More |
|---|---|---|
| TenantBillingUsageEvent | This DLO tracks events that trigger consumption from a certain service to Digital Wallet. | TenantBillingUsageEvent Data Lake Object |
| TenantDailyEntitlementConsumption | This DLO stores the daily consumption calculations. | TenantDailyEntitlementConsumption Data Lake Object |
| TenantEnrichedUsageEvent | This DLO is an enriched version of the TenantBillingUsageEvent DLO used for reporting purposes. It contains tagging information about a billing usage event (called consumption tags) alongside standard billing data. Consumption tags enable further slicing and dicing of usage data to provide more advanced insights. | TenantEnrichedUsageEvent Data Lake Object |
| TenantEntitlementTransaction | This DLO tells our backend service the entitlements available for an org. Entitlements have a start and end date, and supported usage types. | TenantEntitlementTransaction Data Lake Object |
| TenantHourlyEntitlementConsumption | This DLO provides an hourly aggregation of the TenantBillingUsageEvent usage events. | TenantHourlyEntitlementConsumption Data Lake Object |
| TenantUsageAttrDetail | This DLO provides the ability for you to create reports for additional Data 360 attributes, for example, by data space. | TenantUsageAttrDetail Data Lake Object |
| TenantUsageTypeMultiplier | This DLO provides the multipliers to apply to a given usage type, and dictates how to convert raw usage into credits to draw down against your entitlements. | TenantUsageTypeMultiplier Data Lake Object |
- TenantBillingUsageEvent Data Lake Object
The TenantBillingUsageEvent data lake object (DLO) captures the raw consumption data sent from a service to Digital Wallet. - TenantDailyEntitlementConsumption Data Lake Object
The TenantDailyEntitlementConsumption data lake object (DLO) stores daily consumption calculations. - TenantEnrichedUsageEvent Data Lake Object
The TenantEnrichedUsageEvent Data Lake Object (DLO) is an enriched version of the TenantBillingUsageEvent DLO, specifically created and optimzed for consumption reporting. In addition to capturing raw usage data, it contains standard consumption tags that provide metadata alongside billing usage to enable further slicing and dicing for more advanced insights. This DLO fuels the data provided in the Digital Wallet out-the-box-reports and dashboards, and enables you to build your own custom reports. And best of all, you can create reports directly from it, and you don’t incur any costs when building a report based on it. - TenantEntitlementTransaction Data Lake Object
The TenantEntitlementTransaction data lake object (DLO) represents the entitlements available for an org. Entitlements have a start and end date, and supported usage types. This object tracks what you purchased, your contract IDs, and their associated entitlements. - TenantHourlyEntitlementConsumption Data Lake Object
The TenantHourlyEntitlementConsumption data lake object (DLO) stores the hourly consumption calculations. - TenantUsageAttrDetail Data Lake Object
The TenantUsageAttrDetail data lake object provides the ability for you to create reports for additional Data 360 attributes, for example, by data space. We plan to add additional attributes over time. - TenantUsageTypeMultiplier Data Lake Object
The TenantUsageTypeMultiplier data lake object (DLO) captures the information used when calculating the TenantHourlyEntitlementConsumption. The multiplier determines the rate at which consumption is calculated according to your contract. This information determines how Digital Wallet converts raw usage to consumption credits for the specified usage type and usage subtype.
