# Ticket Commerce Records

### Overview <a href="#overview" id="overview"></a>

Ticket Commerce Records report lets you review ticket searches, reservations, and purchases per use of the Ticket Commerce flow.

<figure><img src="/files/6wFEZ9BjUSwAh81Y6pTQ" alt="" width="375"><figcaption></figcaption></figure>

## Report Components <a href="#report-components" id="report-components"></a>

<figure><img src="/files/n706fQB6bHAyBhFIzyzO" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="247">Component</th><th>Definition</th></tr></thead><tbody><tr><td><strong>End User Action</strong></td><td><p>If the user started a search, but never finished the flow then the EndUserAction is <strong>Search tickets.</strong> </p><p></p><p>If the user completed all questions in a search and was shown a ticket reservation, but did not proceed to purchase, then the EndUserAction is <strong>Reserve Tickets.</strong></p><p></p><p>If the user completes a purchase, then the EndUserAction is <strong>Purchase Tickets.</strong></p></td></tr><tr><td><strong>Action Status</strong></td><td>Fail means that for one reason or another, the call to the ticketing provider failed, and whatever action the user was trying to take did not work. Failure can happen at the search, reserve, and/or purchase steps, and is not related to whether or not the user ever bought tickets. Success means the ticket was purchased</td></tr><tr><td><strong>Event Name</strong></td><td>Name of the event</td></tr><tr><td><strong>Venue Name</strong></td><td>Name of the location</td></tr><tr><td><strong>Event Date</strong></td><td>Event date</td></tr><tr><td><strong>Event Time</strong></td><td>Event time</td></tr><tr><td><strong>Sale Type</strong></td><td>''Resale'' are secondary market tickets, meaning a person is selling tickets they originally purchased for themselves. ''Standard'' are tickets the user is buying directly from the client.</td></tr><tr><td><strong>Price Code</strong></td><td>An attribute per ticket that the ticketing provider uses to find the tickets that best match what the user asked for (e.g. premium tickets vs best available vs lowest price, etc)</td></tr><tr><td><strong>Ticket Vendor</strong></td><td>Name of the ticket vendor</td></tr><tr><td><strong>Location</strong></td><td>Location of a seat requested</td></tr></tbody></table>

## Tips <a href="#tips" id="tips"></a>

1. Understand which pages and channels users are accessing to interact with the Ticket Commerce flow. Identify popular entry points and optimize user journeys for seamless ticket searches and purchases.
2. Use the "End User Action" component to track the customer journey through the ticket purchase flow.
3. Examine the "Action Status" component to understand the success rate of different actions (search, reserve, purchase). Analyze the reasons for failed actions and implement strategies to improve overall conversion rates.
4. Utilize the "Event Name," "Venue Name," "Event Date," and "Event Time" components to monitor the performance of specific events or venues. Identify popular events and peak booking times to adjust inventory levels and pricing strategies accordingly.
5. Monitor transaction amounts and currencies to assess revenue generated through ticket sales. Identify high-value transactions and analyze pricing strategies to maximize revenue and profitability.
6. Leverage the "Sale Type" and "Price Code" components to understand the demand and pricing of different ticket types (e.g., resale vs. standard, premium vs. best available).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.satisfilabs.com/resource-center/ai-agent-engine/reporting-and-analytics/data-reports/ticket-commerce-records.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.