Kibana Glossary
This glossary explains the main elements used in Kibana, covering visualisation tools, report indexes, and the fields that shape how data is explored. It is intended as a simple reference point for anyone working with Ticketure data so teams can understand what each index represents and how it behaves in reporting.
VISUALIZATION TYPES
| Lens |
Allows for 'drag and drop' building, various visual outputs (bar charts, pie charts, tables, etc). Has a limit for the number of rows it can calculate accurately, we recommend not exceeding more than 7,000 top-level values at max. Aggregation has a higher limit, which is better for larger data outputs. |
| Maps |
This creates a visual representation of activity using layered combinations of indexes. Unlike tables and charts, maps offer a more intuitive way to identify patterns based on location and area. |
REPORT INDEX
| Cart |
The center of any transaction in Ticketure is the Cart. This index allows you to view the cart and determine things like 'unbalanced' carts - or carts that have more/less inventory in them than payments. From this index, we have provided reports like the Aging Reports or Overpaid and Underpaid by Visit Date reports. The cart index (as well as Transaction By indexes) contains the Campaign details that are being tracked for conversions. |
| Discount |
The Discount Index is a very useful index for performing analysis of coupon redemption, usage, original amounts, and amount of discounts given, etc. Grouping discounts by code group and even down to the exact code used allows for detailed data segmentation for discounts. |
|
Identity |
Only the name, email address, membership code, and role of the identity/Customer within Ticketure. In addition to customers, this index also stores basic information about Organizations. This index would only be useful if you are pulling a list of Customers and wanted to include those Customers who had NOT completed a transaction. Otherwise, we would suggest using the Transaction_By indexes as they will provide the additional data requested. |
|
Inventory |
Great for analyzing the overall capacity of your sessions/time slots. You are worried less about the details of who is coming and when did they buy their tickets and more about what is available to be purchased, how many people have scanned in, etc. |
|
Membership-by-expiry |
You will want to know what happened with memberships based on their expiry/expiration date. Ex: give me a list of all members who are expiring in the next 3 months but are not enrolled in Auto-Renew. |
|
Membership-by-purchased |
You want to know what happened with memberships over a given time period. Ex: Show me all the memberships purchased/renewed during Black Friday. |
|
Ticket |
This Index is similar to Transaction by Session in that the date filters are related to the Session date of the event. This index isn't used as often as one would think given the capabilities/similarities to the transaction by Session index but can be useful for looking for a ticket's status or for pulling a list of scan codes (barcodes) for a particular list/run of tickets. |
|
Trail |
The Trail Index is short for the 'audit trail' index. This index tracks most API call within the system allowing our development team to analyze a series of API calls to help determine the cause of an issue, or provide an answer to the age old question of 'Who made this change and when did they make it?'. As with the Identity index, this one isn't typically used by Customers. |
|
Transaction-by-occurrence |
You want to know what happened for a particular time period. Ex: Show me my sales for this week - regardless of when the event/session is. |
|
Transaction-by-session |
You want to know what happened for a particular session. Ex: Show me the sales for events/sessions this week. |
ACTION CODES
|
Purchased |
Ticket action for the purchase of a ticket. |
Transfer_to |
Ticket action the session to which a ticket was transferred into. |
|
Refunded |
Ticket action for the refund of a ticket |
Held |
Ticket action for a ticket being placed into a held cart. |
|
Redeemed |
Ticket action for the redemption of a ticket within its scan window |
Released |
Ticket action for a ticket being released from a held cart. |
|
Force_redeemed |
Ticket action for the redemption fo a ticket outside scan window or duplicate scan. |
Capture |
Payment action for a payment being captured. |
|
Transfer_from |
Ticket action for the session from which a ticket was transferred from. |
Refund |
Payment action for a payment being refunded (note that 'ed' is only variance between ticket and payment action). |
USEFUL METRIC INFO
( Primarily applies to Aggregation reports)
|
Metric Aggregation |
Within 'Metrics' - the mathematical command required, eg 'Sum', 'Average'. How you want the number to be calculated. |
Terms |
Most commonly used - the parameters you want to apply to the data breakdown in that row. |
|
Bucket Aggregation |
Within 'Buckets' - the method by which you want to break down non-mathematical data, eg 'Terms' or 'Date Histogram'. |
Date Histogram |
Breaking down dates/times by certain parameters, eg 'every 1 hour', 'every 1 week' etc. |
CURRENT AVAILABLE FIELDS
| @timestamp | Will show the time data is added to Kibana - typically aligns with a transaction action timestamp | identity_extra.customer_note | Internal or customer-provided note |
| action_code | Will show the action taken against a ticket, eg purchased, refunded, transferred to, transferred from, etc | identity_extra.email_confirm | Email confirmation status |
| admit_first_name | Will show lead booker's first name unless they have gifted the ticket or requested a name change | identity_extra.newsletter | Will show whether the customer has opted in to your mailing list (1=yes, 0=no) |
| admit_last_name | Will show lead booker's last name unless they have gifted the ticket or requested a name change | identity_extra.phone | Phone number associated with identity |
| after_fees_value | Will show the Gross total of a paid ticket (including VAT and any applicable fees) | identity_extra.state | Address detail attached to the transaction |
| before_fees_total | Will show the Net value of a paid ticket (excluding VAT and any applicable fees) | identity_extra.tix:csr:info | Customer service ticket metadata |
| before_fees_total | Total amount before fees | identity_extra.tix:csr:last_version_used | Last CSR system version used |
| before_fees_value | Amount before any fees applied | identity_extra.tix:csr:settings | Customer service configuration settings |
| campaign.source_totem | Will show transactions made via the QR code on the totem for walk up sales | identity_extra.zip_code | Address detail attached to the transaction |
| cart_id | Will show the URL GUID for the cart | identity_first_name | Will show lead booker's first name |
| cart_number | Will show the cart number for an order | identity_last_name | Will show lead booker's last name |
| channel_id | Will show the sales channel the transaction went through - Web, POS or CMS | identity_name | Will show lead booker's full name |
| currency_code | Currency used for the transaction | inside_fee_value | Will show the total value of inside fees on an order |
| day_of_week | Will show the day of the week the booking has been made for | membership_code | Membership identifier code |
| days_to_event | Will show number of days remaining to the session date booked from today's date | membership_role | Role associated with the membership |
| discount_value | Will show the value deducted from the ticket after a discount code has been applied | Net | Net amount after deductions |
| dispute_reason | Reason a payment dispute was filed | net_after_fees_price | Price after fee are applied |
| dispute_status | Current status of the dispute | occurred_on | Will show the date an action occurred on, eg a refund or transfer |
| end_datetime | Event or transaction end date and time | order_number | Will show the order number for a booking |
| event_category | Classification or category of the event | org_address | Organization’s physical address |
| event_day_of_week | Day of week the event occurs | org_name.keyword | Exact organization name for search |
| event_name | Will show the name of the event | outside_fee_value | Will show the total value of outside fees on an order |
| Event_sales_link | URL for event ticket sales | payment_identifier | Payment identifier, such as card brand and last 4 or check ID |
| event_type | Type or format of event (single, repeating, or time-entry) | payment_name | Name or label of the payment |
| face_value | Will show the face value of the ticket before any fees or discounts are applied | payment_value | Will show the total payment made on an order |
| fees.inside_percent | Percentage fee charged internally | portal_name | Platform or portal name |
| fees.outside_fixed | Fixed external processing fee | price_library.library | Pricing library source |
| fees.outside_percent | Percentage external processing fee | price_library.nominal_value | Base listed price value |
| Field | Description | price_library.row | Pricing table row reference |
| gateway_id | This identifies the payment type | price_library.tier | Pricing tier level |
| gateway_token | Tokenized payment method reference | purchased_on | Will show the date of purchase |
| gateway.card_brand | Card brand used for payment | purchased_qty | Will show the total tickets purchased |
| gateway.card_country | Issuing country of payment card | redeemed_qty | Will show the total tickets redeemed (scanned) |
| gateway.card_funding | Card funding type, credit or debit | refund_fee_value | Fee amount refunded |
| gateway.card_last4 | Last four digits of card number | revenue_value | Revenue amount generated |
| gateway.wallet_type | Digital wallet used, if any | seller_name | Will show the name of the seller account |
| giver_email | Email address of the payer | staff_email | Staff member email address |
| giver_name | Name of the payer | staff_flag | Will show transactions where a staff flag is attached, so what your team have been doing |
| giver_type | Classification of payer type | staff_name | Will show the name of the staff member who processed the transaction |
| gl_code | General ledger accounting code | start_datetime | Will show the session date and start time that the tickets have been booked for |
| held_qty | Will show the total tickets held (ie unpaid reservations) in an order | ticket_group_name.keyword | Breakdown of tickets by ticket group name |
| held_value | Will show the total value of those unpaid reservations | ticket_group_type | Category of ticket group (Codes, membership, passes, seated, tickets, etc) |
| id | Unique system record identifier | ticket_type_name.keyword | Breakdown of tickets by ticket type name |
| identity_email | Will show the email address attached to the transaction | timezone_name | Timezone associated with date fields |
| identity_extra.address | Address detail attached to the transaction | transaction_id | Unique transaction identifier |
| identity_extra.address_more | Additional address information in line 2 | type | Recored ticket or payment type |
| identity_extra.city | Address detail attached to the transaction | valid_from | Will show the start date of validity for an open ended ticket or membership |
| identity_extra.country | Address detail attached to the transaction | valid_to | Will show the expiry date of validity for an open ended ticket or membership |