Transaction dump fields: store_item_id, LTO mapping, and net revenue vs order_total_usd

When reviewing or requesting a transaction data dump, there are a few important limitations and field definitions to keep in mind.

LTO ID availability

We do not currently have the internal LTO ID available as a field in the transaction report.

The only additional identifier currently available to add to the report is store_item_id (for example, stm_eIdWgYimQGA).

If you need to connect transaction data to internal LTO naming or performance reporting, the current workaround is to create a mapping table between your internal LTO IDs and product names or available item identifiers in the export.

Why order_total_usd can be higher than the listed purchase price

order_total_usd can be higher than the base purchase price for two reasons:

• It includes any taxes collected as part of the transaction.
• It reflects the total amount actually charged in the player’s local currency, converted to USD using the applicable exchange rate.

This does not mean the game earns that full amount as revenue.

Revenue interpretation

Taxes collected as part of the transaction are not earnings for the game. If you need a cleaner performance view, use net revenue rather than order_total_usd.

If requested, transaction data can be repulled to report net revenue instead of the gross USD total.