This guide explains how to easily assign a customer to a pass when the pass is to a given address (as part of the ticketing system Infomaniak).

Prerequisites

• The customer card must exist with an associated email address
• The pass must have an informed email address so that this feature can offer customers to connect. Therefore, the option must be visible or mandatory in the pass configuration.
  
   

Do the command by telling the email address

When adding passes to the basket, or once in the basket, please enter an email address. Several passes, each with their email address, can appear in the basket.

Once the pass is validated, on the tab Client, an additional field will offer you the choice of customers to link to the order.

This guide explains how to modify how your events are displayed in the Infomaniak ticketing service

Access the options to configure the display

1. Log in to your Infomaniak space (manager.infomaniak.com)
2. Go to the Ticketing service
3. In the left-hand menu, under Boutique / Go live, click on Boutique options

Select a display mode for multi-date events

1. Select the methods which will be available on the online ticketing service to enable your customers to choose between the different display modes that they wish
2. Select which display mode will be used by default
3. Indicate if available places should be indicated or not (event capacities displayed)
   
   
   

The different display modes available

List format

The list format display is practical of the dates are spread out over time with empty periods in between (weekly or month, for example) and/or if the ticketing service should be able to propose several dates or sessions, without these being indicated on a calendar.

Monthly calendar

The monthly calendar makes it possible to indicates events on a monthly calendar. This is an effective display mode, but can be very full if there are several sessions per day.

 

Weekly calendar

Very useful if you want to display event dates from one week to the next, especially if there are several performances per day, or if the event is held over a short period of time and you want to display the days of the week.

Find out more

Quickstart guide: ticketing service

How to modify the options of my online ticketing service (boutique)

 

This guide explains how to set up a validation system for passes or subscriptions (within the framework of the ticketing system).

Introduction

• This option allows you to create passes for which visitors complete a registration that you can validate before they can be used.
• This feature will be useful for any restricted access or when validation of the request must be done by the organizer.
  • This can include accreditation requests, registrations for specialized courses requiring the verification of certain documents, access to certain areas or events, etc.
     

Setting up the pass to validate

To do this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the ticketing related to the event.
3. Click on Scheduling in the left sidebar.
4. Click on Pass in the left sidebar.
5. Click on ‍ Add a pass.
6. During the pass creation process, enable Pass Validity by setting it to Yes.
   • This action will automatically set the necessary options for this feature, namely a free custom pass with a minimum of 0 tickets.

Once the pass is created, you will need to configure the information requested from the visitor by going to the pass and clicking on the Settings tab:

It is thus possible to make each field hidden , visible , or mandatory …

If more information or supporting documents are required, it is possible to add them using the form function:

1. Create a form by price with the information requested from the visitor.
2. Associate the price form with the pass:
   

Procedure for requesting a pass to be validated

The visitor will be able to order the pass like any other order procedure. A few differences should be noted:

• The terms used during the online procedure will refer to validation requests instead of orders.
• The visitor will receive a first email confirming that their request has been received and that they will be notified when their request is validated.
• The visitor will receive the pass in a confirmation email when the pass is validated.

Procedure for validating a request

To validate a pass validation request from a visitor, you will need to go to the list of passes:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the ticketing related to the event.
3. Click on Sales in the left sidebar.
4. Click on Pass in the left sidebar.

‍If needed, use the filter to display only the passes to validate and choose the desired pass category:

Verification before validation

Click on the passes to verify. All the information is on the pass page.

If additional fields have been added via a form, they will be found in the Edit information section:

Example with files that the user has uploaded:

Change the status

Change the status to Validated and Withdrawn or no, so that the pass is valid:

An email will be automatically sent to the visitor with the information to fill out their pass with the tickets to be added.

In case of a refusal, it is possible to send an email to the visitor to invite them to change the information.

It is also possible to do this on the previous page via a multiple selection, for example:

This guide explains how to manage orders and print tickets from the mobile ticket office (as part of the ticketing system Infomaniak).

Preamble

• For an overview of the mobile ticket office, refer to this other guide.

4. Printing orders

To do this:

1. Select the order to print.
   • If you are in the sales process and have just validated an order, it will be selected by default when you reach this step.
2. Click on the desired printer to print the ticket(s):
   
3. In the case of a pass, the mobile ticket office will indicate the available badge printers:
   

Print a receipt with the ticket

You can print a receipt for the order by activating the option on the right of the prints. The receipt will be printed at the end of the tickets:

Search for an order and filter the order list

It is possible to filter the list of orders or perform a specific search. The search field allows you to use all information related to the order, such as the name, email address, order number, etc.

You can also filter orders by event date.

Manage orders

Each order has options allowing you to manage it more precisely:

• Add or modify the order's client:
  
• Send by email the invoice, the tickets or the confirmation email, or print the receipt:
  
• Manage tickets individually, either to print a selection of tickets, or, for reservations, split the reservation:
  
• If the order contains passes, access the pass options:
  
• If the order contains gift certificates, display them and copy the code to the clipboard:
  

Next steps

• Send the cash report (Coming Soon)
• The mobile ticket office settings (Coming Soon)

This guide shows an example of a pass configured as a subscription where all events are included upon purchase (within the framework of the ticketing system Infomaniak).

Preamble

• For an overview of the pass and everything it can do, refer to this other guide.

The ticket pack

The example below allows for a pass that acts as a pack of several tickets. Typical uses for this type of pass would include:

• A pass with entries for 2, 3 or 4 nights of a multi-day festival.
• A pass with different activities, such as a package "museum entry with meal" where the entry and the meal are two individual and distinct events.
• A ticket pack including entry to multiple venues on the same day.

Creating the pass

After filling in the information, such as the name of the pass, the price, or the quantity of passes available, you need to set the pass to Automatic:

The pass is configured as a ticket so that participants can print each ticket individually:

Event Association

The events are associated with the pass, with a limit of one ticket per event and no additional cost:

This pass includes a ticket for event 1 and a ticket for event 2:

Pass design

This pass will never be printed, as only the individual tickets linked to the events will be printed. Therefore, there is no need to configure the pass's visual. The customer who purchases this pass will receive a ticket for event 1 and a ticket for event 2, so you will need to define the visual of these tickets.

Information requested

This pass is not personalized, but to facilitate identification, we give the possibility to enter the first and last name:

This guide explains how to split reservations with multiple tickets (within the framework of the ticketing system Infomaniak).

This allows you to validate part of a reservation, in case the reservation includes multiple tickets, but only part of it needs to be validated at the counter.

Prerequisites

• This operation requires that an order is currently set to pay on site.
  • For more information about this payment method and how to activate it, refer to this other guide.

Splitting from the web ticket office

To do this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the ticketing for the event in question.
3. Click on Guichet in the left sidebar:
   
4. Find the reservation from the search field at the top of the page; you can find the order using the order number or any other element related to the order:
   
5. The reservation appears in the right column; if it is a reservation, you can click on the arrow to the right of the Validate button and Split the reservation:
   
6. The next screen allows you to select the tickets to validate:
   
7. Now, simply proceed with the validation of the selected tickets. You will notice that this action creates a new order, and the original order will only contain the tickets not selected during the split:
   

Splitting from the sales tablet

The procedure for splitting an order on a tablet is similar to the procedure on the web check-in:

1. Log in to your Infomaniak account.
2. Click on the Orders tab and find the order to split.
3. Click on the Tickets tab of the order:
   
4. Select the tickets to validate and click on Split:‍
   ‍
5. ‍Continue the order to validate it:
   ‍
6. The new order appears as validated, and the initial order shows the remaining tickets:
   ‍

This guide provides the list of triggers to use for your trackers of type Google Tags and Meta pixel (Facebook) for your store (as part of the ticketing system Infomaniak).

Examples of Meta pixel and Google Tags

Refer to the external documentation for the pixel Meta:

!function(f,b,e,v,n,t,s){
    if(f.fbq)return;
    n=f.fbq=function(){n.callMethod?
    n.callMethod.apply(n,arguments):n.queue.push(arguments)};
    if(!f._fbq)f._fbq=n;
    n.push=n;n.loaded=!0;
    n.version='2.0';
    n.queue=[];
    t=b.createElement(e);
    t.async=!0;
    t.src=v;
    s=b.getElementsByTagName(e)[0];
    s.parentNode.insertBefore(t,s)
}(window,document,'script','https://connect.facebook.net/en_US/fbevents.js');

document.addEventListener("ike_event_view", function( e ) {
  fbq('init', '14085424191xxxxx');
  fbq('track', "PageView");
  fbq('track', 'InitiateCheckout');
});

document.addEventListener("ike_cart_payment_launched", function( e ) {
  fbq('init', '14085424191xxxxx');
  fbq('track', "PageView");
  fbq('track', 'Purchase', {value: e.detail.topaid, currency: e.detail.currency.name});
});

… and for the Google Tag Manager (GTM) + gtag.js:

window.dataLayer = window.dataLayer || [ ];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'UA-xxxxxxx-x');
document.addEventListener("ike_event_view", function( e ) {
  gtag('event', 'view_item', {
    'event_category' : e.name,
    'event_label' : e.date
  });
});

document.addEventListener("ike_cart_add", function( e ) {
  gtag('event', 'add_to_cart');
});

document.addEventListener("ike_cart_confirm", function( ) {
  gtag('event', 'checkout_progress', {
  'event_category' :'valid cart'
  });
});

document.addEventListener("ike_cart_payment_launched", function( e ) {
  gtag('event', 'add_payment_info', {
     'event_category' : 'paiement',
     'event_label' : e.detail.currency.name,
     'value': e.detail.topaid
  });
});

On Google Tag Manager, make sure the format for the tags is properly respected:

(view_item|add_cart|add_payment_info)

CSP and its impact on conversion tracking

The “Content Security Policy” (CSP) is a web security policy that protects pages against certain attacks such as Cross-Site Scripting (XSS) and the injection of malicious content. However, it can also block certain legitimate scripts, such as Meta tracking pixels or Google Tag Manager, thus preventing the proper functioning of conversion tracking.

Why don't some pixels work?

If your website displays an error related to the Content Security Policy (CSP), particularly in the console or the network tab of the browser's developer tools, this means that certain third-party scripts—such as Google tags or Meta (Facebook) pixels—are blocked. To ensure proper functioning of conversion tracking on your store, it is necessary to add a specific exception in the CSP configuration of your site to allow the resources used by the Infomaniak ticketing system.

Main CSP directives impacting tracking

• script-src‍ : defines the authorized sources for scripts.
• img-src‍ : controls images (including the <img> tags used for tracking pixels).
• connect-src‍ : manages tracking requests sent to the servers of marketing tools.

For example, if you use Google Tag Manager or Facebook Pixel, make sure your CSP policy explicitly allows the loading of scripts and the sending of data to their domains. Here is an example of directives to include in your CSP, to be adapted according to your configuration:

script-src 'self' https://www.googletagmanager.com https://www.google-analytics.com https://connect.facebook.net;
img-src 'self' https://www.google-analytics.com https://www.facebook.com;
connect-src 'self' https://www.google-analytics.com https://www.facebook.com;

Google provides a detailed guide on configuring CSP compatible with its tracking tools.

Also, check that your security management system (application firewall, CDN, CMS) does not block these resources, and apply the necessary adjustments to ensure proper triggering of tracking events.

If your CSP is too restrictive, it can prevent the loading of third-party scripts such as:

• Facebook Pixel (connect.facebook.net)
• Google Tag Manager (GTM) (www.googletagmanager.com)
• Google Analytics (www.google-analytics.com)

Errors visible in the developer console (Browser Developer Tools):

Refused to load the script 'https://connect.facebook.net/en_US/fbevents.js'
because it violates the following Content Security Policy directive: "script-src 'self'"

• Missing data in Google Analytics or Facebook Ads Manager.
• Failure to trigger events defined in GTM.

When the CSP blocks these resources, they cannot collect data on visitors or record conversion events.

Complete list of triggers

Home page:

trigger : ike_home_view
Data : none

document.addEventListener("ike_home_view", function(e) {
  //send to your tracking tool
});

Event page:

A page for an event with multiple dates
trigger: ike_event_view
Data: detail.name

document.addEventListener("ike_home_view", function(e) {
  console.log(e.detail.name);  
  //send to your tracking tool
});

Date page:

Page of a date of an event
trigger : ike_date_view
Datas : detail.name, detail.date

document.addEventListener("ike_home_view", function(e) {
  console.log(e.detail.name, e.detail.date);
  //send to your tracking tool
});

Pass page:

Page of a pass category
trigger: ike_abo_view
Data: detail.name

document.addEventListener("ike_abo_view", function(e) {
  console.log(e.detail.name);
  //send to your tracking tool
});

Pass selection page:

Page for selecting pass dates
trigger: ike_abo_selection
Data: detail (cart details)

document.addEventListener("ike_abo_selection", function(e) {
  console.log(e.detail.name, e.detail.date);
//send to your tracking tool
});

User login:

Triggered on successful login
trigger: ike_user_login
Data: detail (cart details)

document.addEventListener("ike_user_login", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

User logout:

Triggered when a user logs out
Data: detail (cart details)

document.addEventListener("ike_user_logout", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart add:

Triggered when an item is added to the cart

Trigger: ike_cart_add
Data: detail (cart details)

document.addEventListener("ike_cart_add", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart page:

Trigger: ike_cart_view
Data: detail (cart details)

document.addEventListener("ike_cart_view", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart update:

Triggered when a cart element is updated

Trigger: ike_cart_update
Data: detail (cart details)

document.addEventListener("ike_cart_update", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart empty:

Triggered when the empty button is pressed

Trigger: ike_cart_empty
Data: detail (cart details)

document.addEventListener("ike_cart_empty", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart confirm:

Triggered when the confirm button is pressed

Trigger: ike_cart_confirm
Data: detail (cart details)

document.addEventListener("ike_cart_confirm", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart delivery page:

Trigger: ike_cart_delivery_view
Data: detail (cart details)

document.addEventListener("ike_cart_delivery_view", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart form page:

Trigger: ike_cart_form_view
Data: detail (cart details)

document.addEventListener("ike_cart_form_view", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart payment page:

trigger: ike_cart_payment_view
Data: detail (cart details with paymentMethodSelected)

document.addEventListener("ike_cart_payment_view", function(e) {
  console.log(e.detail);
  //send to your tracking tool 
});

Cart payment changed:

Trigger: ike_cart_payment_changed
Data: detail.path

document.addEventListener("ike_cart_payment_changed", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart payment launched:

Trigger: ike_cart_payment_launched
Data: detail (cart details)

document.addEventListener("ike_cart_payment_launched", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart payment success page:

trigger: ike_cart_payment_success
Data: detail (cart details)

document.addEventListener("ike_cart_payment_success", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Cart delete item:

trigger: ike_cart_delete
Data: detail (previousCart and newCart)

document.addEventListener("ike_cart_delete", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

Page Changed:

trigger: ike_page_changed
Data: detail.path

document.addEventListener("ike_page_changed", function(e) {
  console.log(e.detail);
  //send to your tracking tool
});

This guide explains how to create a pass (within the framework of the ticketing system Infomaniak).

Start creating pass

To do this:

1. Click here to access the management of your product on the Infomaniak Manager (need help?).
2. Click directly on the name assigned to the ticketing related to the event.
3. Click on Programming in the left sidebar.
4. Click on Pass in the left sidebar.
5. Click on Add a pass:
   

The pass will be configured in several steps:

1. Define the type during creation (subscription, ticket pack, etc.) as well as the basic information and parameters (below)
2. Associate the events with the pass
3. Set up the visuals and information related to the pass.
4. Set the information for the subscribers who will be linked to the passes

1. Configure the pass

Name and description of the pass

This section allows you to define the name of the pass as well as a description of the pass:

It is recommended to use a sufficiently short name in the Pass Name on Ticket section, which will be printed directly on the pass.

Pass support

Two types of support can be chosen:

1. The PVC card, credit card type, often used for seasonal or annual subscriptions.
2. The Phone/Paper format which prioritizes the use of the phone but also allows printing the ticket on an A4 or A6 sheet.

If the PVC card is chosen:

• Pay attention to the font size used for the Name displayed on the ticket which will be taken up here and which will be limited to 35 characters.
• Choose the pick-up method that will be available to the customer.

If the Phone/Paper format is chosen:

• The visitor will receive their pass in digital format via email.
• He or she will be able to download the pass in PDF format from the link included in the email.

The appearance of the pass can be configured once the pass is created in the pass appearance configuration menu.

Manage the display during scan checks

The two options here allow you to define the parameters used to check the passes:

1. The passes will have random barcodes upon creation, but the organizer will be able to modify them freely from the management of each pass.
2. The icon that will be displayed during pass check:
   

Pass price

Validity period

The validity period will be used if you want to ensure that this pass will only be available during a restricted period. It is notably possible to configure a pack of tickets that will only be usable during the winter season, for example for a seasonal promotion.

It should be noted that if a pass is outside the validity period, it will be possible to purchase it, but it will not be usable or accessible to add more tickets to it.

Pass type

1. Custom: This pass allows the customer to choose the events and dates from the options proposed. Therefore, you must decide on the pass limitations:
   • Single event choice: The customer will only be able to choose one event, but depending on the ticket limit, they can choose one or more for the chosen event. Warning: When a customer buys a card, the system will deduct the number of seats entered in this field from all events related to the pass. These seats will be "reserved" for this pass. When the customer goes through the scanners, the system will release the seats for all other events.
   • Maximum ticket: The number of tickets that can be associated with the pass
   • Minimum ticket: If a minimum of 0 is set, the customer can buy an empty pass and choose their seats later. Any number other than 0 will force the customer to choose tickets when purchasing the pass.
   • One event per day limit: The pass has a limit of one event per day. The customer will not be able to order more than one ticket per day for this pass
   • All seats on the same day: Allows you to choose a date and then choose the events of that date.
   • One performance limit per event: Allows you to define whether the customer can attend an event multiple times (in the case of multi-dates). If activated, the customer will only be able to take one ticket per event of the "same name" (or "same performance") for this pass. Warning: The spelling of the event name must be identical
   • Minimum different events / pass: The customer must take as many tickets for different shows available on the pass. It will be used to prevent the visitor from taking all their tickets for a single show.
2. Automatic: the pass will not be customizable by the client: it will automatically take the tickets that will be defined by the organizer.
3. Fixed numbered seat: in the case where the event takes place in a venue with a seating plan, this type of pass allows the customer to choose the pass with a numbered seat on the seating plan. This seat will remain unchanged for all events associated with the pass taking place in the same venue.

Example configurations

• All-inclusive season subscription
• Multi-day pack (2-day pass, weekend pass)
• Package of several events to choose from

Next steps

After creating the pass, the next step is to associate the corresponding events and configure the various available options:

1. Associate events
2. Set up the visuals and information
3. Collect the information of subscribers

This guide explains how to set up a pass or subscription renewal system on your Infomaniak ticket office. This feature will allow visitors with subscriptions to renew them for the new season. 

It is not mandatory to have seasonal or annual subscriptions to use pass renewal, but it is imperative to have a new period with passes configured.

Prerequisites

So that renewals can be activated on your ticket office, you will need to create passes for the new period.

Create a renewal

1. Log in to your Infomaniak space
2. Go to the Ticket Office 
3. Go to the period over which renewals will be offered
   
   
4. Go to Programming and Pass in the side menu on the left
   
5. Click on Subscription Renewal 
   
   
   
   
6. Click on Create renewal
7. On the pop-up register, in order
   1. The subscription of the previous period
   2. The subscriptions that visitors will be able to take out upon renewal. Several subscriptions may be offered at this stage.
      
      
8. Indicate, if you wish, a validity period for the renewal

Renewal procedure for the visitor

The visitor can renew their subscription by following this procedure from the pass renewal link which will be found by default at the bottom of your ticketing page.

For direct integration, it is possible to use the URL of the desired ticket office, and add /pass-renew at the end. For example : 

https://infomaniak.events/shop/abcABC4242I/pass-renew

Tracking renewals

It is possible to follow each renewal via the renewals tabs:

• To this ticket office : indicates the renewals carried out from a previous season to the one you are in
• From this ticket office : indicates subscriptions renewed from the chosen ticket office to a new period

This guide explains how to print badges via the Infomaniak tablet ticket office.
 

The equipment is already configured to connect to the network and to the tablet automatically. This will automatically be detected when a badge is ready to be printed.

Connect the printer to the network
 

1. Switch the printer on
2. Connect the printer to your Internet network using the RJ45 Ethernet cable
3. Connect the wifi terminal to your network

Print badges via the tablet

1. Switch the printer on.
2. Log in to the ticketing service account via the tablet using the Infomaniak account username and password.
3. The tablet will connect to the ticket office interface automatically
4. Create an order on the tablet or search for an existing order
5. Click on the printer icon
   
   

If the printer does not appear in the list on the right

• Try to refresh the list by clicking on the turning arrows
• Check that the printer is connected on your network with the ethernet cable
• Check that the Wifi terminal is connected and is switched on
• Check that the printer and the tablet are connected to the Infomaniak network
• To check that the printer is correctly connected to the network, click on the button on the left of the printer screen and check that it has an assigned IP address
• If not, restart the printer

Learn more

• Start-up guide: ticketing service
• Configuration of the badge printer
• Print badges via a computer