Trigger train

What is SNCF / SNCF API?

SNCF (Société Nationale des Chemins de fer Français) is the French national railway company, managing domestic and international passenger and freight transport.

The SNCF API gives real-time access to structured data related to train schedules, delays, arrivals and departures across the French railway network.
In this case, Displayce leverages this data to trigger DOOH campaigns based on train activity (arrival/departure) at stations where screens are located.

This collaboration is enabled thanks to MediaTransports, the media owner of screens within train stations.

How can I see the Train trigger in Step 3 (Buying)?

To see the Train trigger in step 3 of your Line Item setup, two conditions must be met:

1. You need to have at least one screen located in a train station in your targeting in step 2

It can be done through several ways:

Using the targeting tools in the side panel (Geolocations/Screens characteristics):
- Google POI - use the search bar to find the train station within the 'Places' filter powered by Google, and then increase the perimeter around the pin point if needed,
- Venue types - use the venue type Transit > Train Stations,
- Locations filter - you can search for the closest city near the train station to select train stations screens (depending on the targeted train station, this will not be the most reliable option), (select station names + adjust perimeter),
Using the map tools:
- Polygon tool - draw an outline around a station using the dedicated 'polygon' tool on your map,
- Radius tool - draw a circle around the station using the 'radius' tool on your map, and then increase or decrease the radius.

2. You need at least one deal hat contains at least one screen located in the train station

Once both conditions are met, the Train trigger panel will become available in step 3, with the Trains to and Trains from options.

⚠️ Important:
The deal must be linked to the SSP VIOOH.
➔ The Train trigger mapping (matching between screen IDs and station data) was built based on VIOOH frame IDs only.
➔ While keeping deals from other SSPs won't block the setup, it could result in less accurate forecasting.

Recommendation: If you use the Train Trigger, prioritize only VIOOH deals for better accuracy.

Trigger Coverage

Geography: Only French train stations are currently covered 🇫🇷
International trains: Supported only if they arrive from or depart to European destinations available in French train stations (e.g. Belgium, Germany, Spain).
Inventory: Trigger is applied only on MediaTransports' inventory
Trajectories: Only direct train journeys are available. No support for connections or multi-leg routes.

List of Stations available in Programmatic DOOH (MediaTransports)

All TGV, TER, and Intercités stations are available.

Targeting Specifications

Train Triggers act as event-based activations (based on the occurrence of train arrivals or departures).

The Train trigger acts as a screen-level filter, similar to the CIRIUM (airport) trigger.
Once added in step 3:

Trains To → Targets screens located in stations with departures to the selected station
Trains From → Targets screens located in stations with arrivals from the selected station

Trigger is not a location selector but an event detector.

Ex: Let's say you want to target travelers arriving in Paris from Bordeaux, Toulouse and Marseille.

Good configuration to achieve the objective:

Step 2 - Geographical targeting:

Select only Paris stations (Gare de Lyon, Gare Montparnasse, Gare du Nord, etc.) via Google POI, Polygone or Radius.

Step 3 - Train Trigger:

Trains From: Bordeaux, Toulouse, Marseille.

Result: The line item will only be activated in Paris stations, when trains arrive from Bordeaux, Toulouse or Marseille.

Triggers ≠ Geolocation! Always remember:

Step 2 = define where I want to activate screens.

Step 3 = define under what conditions (event-driven) I want to trigger an activation.

Granularity over screen activation

Currently, the trigger works at the station level, not at the hall/platform level.
All available screens in the selected station are activated at the same time, regardless of exact location within the station.

Trigger Temporality

The current expected behavior is:

Departures: Screens are activated from 1 hour before departure until 15 minutes after
Arrivals: Screens are activated from 15 minutes before arrival until 30 minutes after

Delays are taken into account → activation time dynamically adjusts to actual arrival/departure time.

Combining Triggers

The Train trigger follows the same logic as other triggers:

Trains from X OR Trains from Y → Activation happens when either condition is met.
Trains from X OR Trains to Y → Activation happens when either condition is met.
Trains from X AND another trigger (e.g. Weather: Rainy) → Activation happens only when both conditions are met.

Examples:

Trains from Bordeaux + Trains from Lyon → OR logic
Trains from Bordeaux + Weather trigger (Sunny) → AND logic

Reporting

Currently, there is no specific reporting element tied directly to the Train trigger.

We know how often a frame is activated per hour
However, we do not track the exact reason (train vs weather vs other trigger)