This page contains the setup guide and reference information for the Tito integrations.
This integration is part of Free, Starter, Professional, Enterprise subscription. Contact your Account Manager for more information.
Prerequisites
An active Tito account with a list of events (ensure you have access, especially if you are not the owner)
Setup guide
Step 1: Set up Tito
Log in to Tito ID service.
On the page, choose Generate New Token.
Copy the API Key.
Now, log in to the Tito Dashboard.
Click on Tito Dashboard.
Locate your Account slug from the URL (e.g., https://dashboard.tito.io/swapcard/test).
The Account slug is the part of the name preceding dashboard.tito.io; in this case, it is swapcard.
Step 2: Set up the Tito integration in Swapcard
Sign in to your Swapcard account.
Navigate to your Event page within the Communities section.
In the left navigation bar, go to Event Builder, then select Integrations.
On the integration selection page, choose Tito from the list of integrations.
Copy the values displayed in Step 1.3 - Set up Tito and Step 1.7 - Set up Tito, using the corresponding API Key and Account slug fields.
Click on Submit.
Select your event for integration - The integration displays all events your account has access to, including upcoming and past events.
Your Tito event has been successfully linked with your Swapcard event.
You have the flexibility to adjust your integration settings according to the specific data requirements. It's crucial to highlight that the synchronization will only begin when you manually start the integration process and finish the necessary mapping.
Supported sync modes
The Tito integration supports the following sync modes :
Feature | Supported? |
Yes | |
Yes | |
Webhook - Overwrite | Partial |
Supported streams
This integration is supporting the following Tito streams in v3.0. Tito integration does NOT yet supporting the beta version v3.1.
Capturing deleted records
When a record is deleted on Tito, it needs to be MANUALY deleted on Swapcard accordingly.
Object Mappings
The Tito integration provides a list of available objects for mapping, which is generated from Releases.
For the Swapcard integration, one object is created to be mapped per Releases. The object name corresponds to title on Releases.
Questions & Object/Custom Fields Mapping
The object fields to be mapped consist of a combination of static fields provided by the Tito API (refer to Streams supporting fields) and dynamic fields provided by the Questions stream.
The Tito integration utilizes the Questions stream to create a list of available questions that can be mapped with Swapcard custom fields.
The supported question types include:
Select
Checkboxes
Text
File
Note that other question types are NOT officially supported by the integration. If you encounter any issues with these specific question types, please report them to our support for case-by-case testing.
Opt Ins
Opt-Ins mapping can be chosen within the object mapping view, included as part of the Questions mappings. This feature allows the import of Tickets only for users who have given consent for their data to be transferred to the Swapcard systems.
Streams supporting fields
Tickets
The integration exclusively imports ticket with a state configured as Complete.
Ticket Field | Mapping Label | Type |
| "Email" |
|
| "First name" |
|
| "Last name" |
|
| "Organisation" |
|
| "Phone number" |
|
| "Barcode URL" |
|
Limitations & Troubleshooting
Connector limitations
Ticket status
The integration exclusively imports ticket with a state configured as Complete.
Barcode
The integration is substituting barcodes, implying that any modifications related to badges on Swapcard Studio will be overridden by the integration.
Group Tickets
To ensure the proper functioning of the Swapcard product, it is essential that each ticket contains unique and required information, including:
First name
Last name
Email
Keep in mind that in the case of group registrations, the integration will exclusively consider uniquely mapped email addresses. Please ensure you map distinct email addresses along with their corresponding first and last names to ensure accurate ticket importation.
Rate limiting
The Tito integration is designed to operate smoothly within typical usage scenarios and should generally not encounter limitations imposed by the Tito API. However, its functionality is dependent on the capabilities of the Tito API. For information on rate limits, please consult the Rate limits for the REST API section in the Tito documentation. If you encounter rate limits, kindly contact the Tito support team for assistance.
Changelog
Version | Date | Subject |
2.7.13 | 2023-09-14 | Maintenance |
Enhancement
Please be aware that any enhancements to this integration, which encompass any requirements not covered by the existing integration state, will be subject to custom development processes and associated costs.