DOCSEARCHbyAlgolia
Submit Docs

Tito Documentation

website·Indexed 39 days ago

https://help.tito.io/en/

Guides for using Tito to sell event tickets, manage attendees, and handle registrations. Covers event customization, ticket setup, payment integrations with Stripe and PayPal, tax handling, check-in apps, and developer tools like webhooks and the embeddable widget.

Tokens
39.3K
Snippets
79
Records
373
Agent score
68%

What's inside Tito

  1. Overview of Tito Activities

    Activities allow event organizers to dynamically track attendance numbers across different ticket types, add schedules (dates, times, and venues) to event components, and offer selectable options like workshops to attendees.

  3. Overview of Tito Source Tracking

    Source Tracking allows you to create unique links for specific sources to track the origin of orders. Common use cases include generating affiliate links for partners, testing paid advertising campaign performance, or identifying sales originating from specific social media platforms like Twitter.

  4. Overview of Tito RSVP Lists

    RSVPs is a beta feature in Tito that allows organizers to create unique, single-use invitation URLs. These links are sent to specific people via email, ensuring that each link can only be used once to claim a ticket.

  5. Overview of Tito Upgrades

    Upgrades is a beta feature that allows event organizers to offer extras to attendees during the ticket purchase process. Upgrades must be added to tickets at the time of purchase; attendees cannot add them to their order at a later date. To request access to this feature, contact support@tito.io.

  6. Understand Tito's billing and fee structure

    Tito charges a fee as a percentage of the ticket price; there is no cost for free tickets. Fees are charged in EUR, with exchange rates updated daily via openexchangerates.org. Note that payment processors like Stripe and PayPal charge their own separate processing fees in addition to Tito's fees.

  7. Use Test Mode to simulate event registrations

    Tito's Test Mode allows you to preview the registration experience and process test transactions without incurring fees. Test data is kept entirely separate from live data, meaning test transactions do not need to be manually deleted and do not affect your live or draft event statistics.

  8. Understand the Tito Ticket Webhook Payload

    When a ticket-related webhook is fired, Tito sends a detailed JSON payload containing information about the ticket, the event, the attendee, and any custom question responses. Key sections include event (event details), answers (an array of question/response objects), and responses (a key-value map of question slugs to answers).
    {
  "id": 795,
  "event": {
    "id": 64,
    "title": "AwesomeConf ?",
    "url": "https://heroku.tito.io/paulca/awesomeconf",
    "account_slug": "paulca",
    "slug": "awesomeconf",
    "currency": "EUR",
    "start_date": "2020-12-01",
    "end_date": null
  },
  "name": "Peter Winter",
  "first_name": "Peter",
  "last_name": "Winter",
  "email": "winter@example.com",
  "phone_number": null,
  "company_name": "Peter Winter",
  "reference": "1i5nfwf2t",
  "price": "1.00",
  "tax": "0.19",
  "price_less_tax": "0.81",
  "slug": "1i5nfwf2t24",
  "state_name": "incomplete",
  "gender": "male",
  "release_price": "1.00",
  "discount_code_used": "",
  "total_paid": "1.00",
  "total_paid_less_tax": "0.81",
  "updated_at": "2017-08-27T13:07:47.000Z",
  "url": "https://heroku.tito.io/tickets/1i5nfwf2t24",
  "admin_url": "https://heroku.tito.io/paulca/awesomeconf/admin/tickets/1i5nfwf2t24",
  "release_title": "AwesomeConf ticket",
  "release_slug": "31az2uvoh4",
  "release_id": 90,
  "release": {
    "id": 90,
    "title": "AwesomeConf ticket",
    "slug": "31az2uvoh4",
    "metadata": null
  },
  "custom": null,
  "registration_id": "bdtyap3hguq",
  "registration_slug": "bdtyap3hguq",
  "metadata": null,
  "answers": [
    {
      "question": {
        "title": "Phone Number",
        "description": "",
        "id": 200
      },
      "response": "555-555-0199@example.com",
      "humanized_response": "555-555-0199@example.com"
    }
  ],
  "responses": {
    "phone-number": "555-555-0199@example.com"
  },
  "upgrade_ids": [],
  "registration": {
    "url": "https://heroku.tito.io/registrations/bdtyap3hguq",
    "admin_url": "https://heroku.tito.io/paulca/awesomeconf/admin/registrations/bdtyap3hguq",
    "total": "1.00",
    "currency": "EUR",
    "payment_reference": null,
    "source": null,
    "name": "Paul Campbell",
    "email": "funconf@gmail.com",
    "receipt": {
      "total": "1.00",
      "tax": "0.19",
      "payment_provider": "Unknown",
      "paid": true,
      "receipt_lines": [
        {
          "total": "1.00",
          "quantity": 1,
          "tax": "0.19"
        }
      ]
    }
  }
}

  9. Understand Tito's organizational hierarchy

    Tito uses a three-tier structure to manage event ticketing:

    1. User: A personal account tied to an email and password. It is recommended that each team member has their own user account for security and auditability.
    2. Account: The top-level container for all events (typically named after a company). The account name is publicly visible and appears in the Tito URL. One account can host multiple events and multiple users/teams.
    3. Event: A self-contained entity with its own ticket types, attendee lists, and customizations. Events can be duplicated for future use.

  10. Notify customers about refunds

    Tito does not send automatic email notifications for refunds. To notify customers, use the Messages feature. You can manually add ticketholders' email addresses in the Manually add or remove emails > Email addresses you want to add field. It is recommended to include a link to the Lookup Tool so customers can download their refund receipts.

  11. Access and share your Tito public timeline

    The public timeline is a centralized page listing all your discoverable public events. The URL format is https://ti.to/your-account-slug. To find your specific timeline link, navigate to Account settings (or click your account name); the link is displayed at the top of the account settings page.

  12. Understand attendee summary fields

    The Attendee summary provides a detailed overview of a participant, including:

    • Reference: A unique five-character ticket reference code (e.g., #GIA0-1), consisting of a four-digit order reference and a serial number.
    • Order information: Details on who purchased the ticket and when; clicking this reveals the full Order summary.
    • Status: Indicates if the ticket is unassigned, incomplete, or complete.
    • Ticket type: The specific registration category for the attendee.
    • Attendee details: Name, email, and responses to any enabled custom questions.
    • Internal notes: A private area for team members to add notes that are not visible to the attendee.