Different third-party apps receives different types of data depending on what they’re designed to do. As example, a CRM system receives 'Contacts' while an analytics tool receive all types. Below you will find the events that Nettla includes in its transfer.
Event types
Simplified term | Event terminology | Description |
Booking Created | bookingCreated | A booking item is created in the schedule |
User joined booking | bookingUserJoined | Another user joins an existing booking item |
User left booking | bookingUserLeft | A joiner leaves an existing booking item |
Booking cancelled (user) | bookingCancelledByUser | A user cancels a booking item |
Booking cancelled (admin) | bookingCancelledByAdmin | An admin cancels a booking item |
Booking completed | bookingCompleted | The session end time of a booking has passed |
Payment reserved | paymentReserved | Amount is reserved on a cardholders account |
Payment Succeeded | paymentSucceeded | Amount is captured on a cardholders account |
Payment cancelled | paymentCancelled | A payment has been cancelled |
Payment refunded | paymentRefunded | A payment has been refunded |
For all events
Simplified term | Event terminology | Description |
Event type | eventType | Type of event, for example bookingCreated, paymentSuccessful |
Club ID | clubId* | If you are receiving data from more than 1 club |
Company ID | companyId | If you are receiving data from more than 1 company |
Event ID | eventId | Unique ID for the event |
Date & time stamp | timeStamp | Date and time the event took place |
User Data (Contacts)
Simplified term | Event terminology | Description |
Nettla User ID | userId |
|
First name | FirstName |
|
Last name | LastName |
|
Email address |
| |
Phone number | phoneNumber |
|
Gender | gender |
|
Date of birth | birthDate |
|
Padel Level | padelLevel |
|
Street Address | streetAddress |
|
City | City |
|
Region | Region |
|
Postal Code | postalCode |
|
Country | Country Code |
|
Date joined club | dateJoined | The date the player first joined your player list |
Membership type | membershipName | What membership type the player holds |
Membership status | membershipStatus | Success, cancelled, paused |
Collection | cohortTypes | If the player belongs to a collection |
Booking data
Simplified term | Event terminology | Description |
Booking ID | bookingId | Unique ID for the specific booking |
Sport | sport |
|
Court(s) | *courts |
|
Booking type | bookingType | Court Booking, Match, Activity, etc. |
(if activity) Activity type | activityDetails -> name: | Nested sub-event inside activityDetails |
(if activity) Max spots | activityDetails -> maxParticipants | Nested sub-event inside activityDetails |
(if activity) Spots filled | activityDetails -> currentParticipants | Nested sub-event inside activityDetails |
Coach | coachId | Who coached a private coaching session |
Organiser | organiserId | Who organised/coached an activity |
Start date & time | startTime |
|
End date & time | timeStamp |
|
Purchased date & time | purchasedTime |
|
Duration | durationMin | Session duration in minutes |
(player) User IDs | participants -> userId | Nested sub-event inside participants |
(player) Amount | participants -> amount | Nested sub-event inside participants |
(player) Payment Method | participants -> paymentMethod | Nested sub-event inside participants |
(player) Payment status | participants -> paymentStatus | Nested sub-event inside participants |
Total amount | totalAmount |
|
Currency | currency |
|
Booking status | status | Open, Cancelled, autoCancelled, Completed |
Payments data
Simplified term | Event terminology | Description |
Payment ID | paymentId | Unique ID for the purchase |
Reference ID | referenceId | What the payment refers to (booking, match, etc) |
Article type | type | Booking, publicMatch, Activity, etc. |
Article name | name | Activity name, membership name, etc. |
Date & time purchased | purchasedTime |
|
Purchasing player | payerId | The player who made the purchase |
Amount | amount |
|
Currency | currency |
|
Payment method | paymentMethod | Card, ApplePay, Points, etc. |
Payment status | paymentStatus | Success, Unpaid, Refunded, etc. |
Payment source | paymentSource | Mobile app, Widget, or Admin |
Discount code | promoCode | Discount code used |
Additional items | inventoryItems | Name(s) of additional items purchased |
Courts data
Simplified term | Event terminology | Description |
Bookable hours per court per day | courtSummaryCreated | Numbers of hours each court was bookable for the previous day, for occupancy purposes |
*Club ID's are found in Nettla Admin -> Settings -> The Club
*Court ID's are found in Nettla Admin -> Settings -> Courts -> Press on a court -> See Court ID on the pop-up side sheet