Fortress GB

Partner Description

Fortress GB offers a dedicated platform aimed at significantly enhancing fan engagement for sports teams. It achieves this by providing comprehensive loyalty programs and delivering personalized promotions directly to fans. Additionally, the platform integrates seamless, loyalty-linked payment solutions, streamlining transactions while reinforcing fan loyalty.

Key Features Supported

1. vivenu Tickets will fetch Fortress barcode

2. Ticket number creation/card number for season and single events

3. Ticket & Card numbers <> meta information meta.ticketNumber and meta.cardNumber

Example Use Cases

1. Get to know your fans better and unlock Fan Data from ticket purchases to build a foundation for your marketing campaigns and activations.

2. Secure and Seamless access control at Events through branded experiences and unique fan IDs

3. Build Fan Loyalty with ID-based Engagement even during off-seasons.

Fortress GB Setup

Click here for general Support.

Pre-Installation Setup

Entry Permissions

1. Go to Settings → Tickets → Access Control.

2. Set up Entry Permissions using the codes Fortress provides for your entry gates.

3. Ensure the "Label" for each entry permission matches its corresponding Fortress code exactly.

Collect Phone Numbers

1. Navigate to Settings → Data Fields.

2. Enable the option to "Collect phone numbers."

Wallet Ticket Configuration

1. Only Wallet Tickets with barcodes are supported.

2. Deactivate NFC Wallet Tickets under Settings → Tickets → Wallet → NFC.

Season Tickets

1. Enforce authentication for Season Tickets.

2. Restrict the maximum number of tickets and transactions to 1 for these tickets.

Note: Only seated, non-recurring events are currently supported.

App Installation & Setup

1. Install the Fortress App from your vivenu Dashboard.

2. Once turned on, the app will request information:

   1. Find your API credentials in your Fortress Account's Developer Section. Fortress will provide these.

   2. Vivenu Production System: Fortress will provide the correct UniqId.

   3. Choose a vendor prefix: This is a short code for your seller's name (e.g., VIV for vivenu) and will prefix resources created on the Fortress server.

Event Setup

1. After adding your Fortress account, add the events you want to pull into Fortress.

2. Initially, the event will show as "incomplete." To finalize the setup:

   1. Re-open the event setup.

   2. Export the ticket types and the seat map by scrolling down and clicking the export buttons. This creates necessary resources in Fortress.

   3. Refresh the page to confirm the event setup is complete.

3. Check-in information is mandatory and applies to all tickets for that event.

Seating Setup

1. Your event must have seating enabled and a seat map assigned. A vivenu seat map links directly to a Fortress stadium.

2. vivenu Structure: Seat Map → Sections → Blocks.

3. Fortress Structure: Stadium → Stands → Areas.

4. Configuration for Compatibility: Due to differing structures, specific setup in vivenu ensures correct data export to Fortress.

5. Assign a Section Name and Block Name to every Block in vivenu.

6. vivenu Section Names become Fortress Stands. Blocks sharing the same vivenu Section Name will combine into a single Fortress Stand.

7. vivenu Block Names become Fortress Areas. Each unique vivenu Block Name translates to a distinct Fortress Area. Blocks within the same section with identical Block Names will merge into one Fortress Area.

Note: Every block on the seat map must have both a section name and a block name for successful seat map export. If either is missing, the export will fail

Ticket Type Configuration

1. Every ticket type requires 1 entry permission. If multiple are set, only the first will be used. These permissions link to Fortress turnstiles.

2. If a ticket type has a price category attached, it will be used as a Fortress price band.

Successful Installation Check

To verify the successful integration and operation of the Fortress system, observe the following:

1. Confirm Barcode Format: A successfully generated Fortress barcode on a vivenu ticket will display a numerical format (e.g., 642648706607207010221105), differing from the standard vivenu alphanumeric format (e.g., 4kbm54zqd3).

2. Identify Error Barcodes: If the app is active and an event has been added, every sold ticket will attempt to generate a Fortress barcode. Should the event setup be incomplete or incorrect, all sold tickets will receive error barcodes.

3. Common Causes for Error Barcodes: This includes newly created ticket types not yet synchronized with Fortress, or un-exported changes to the seat map after the initial event setup.

4. Verify Setup Completion: To confirm the status of your event setup and the timestamp of the last ticket type and seat map export, check within the Fortress app.

Fortress GB