Vengo OnSign Integration

Requirements:

• An active OnSign Account
• An active Vengo Account 
  • Vengo Credentials:
    • Vengo Organization ID
    • Vengo Ad Unit ID usually unique for each screen
• OnSign Player requirements:
  • Windows, Android, or Linux player - Running OnSign App version 10.6.0 or higher
  • Samsung Tizen - Running OnSign App 10.6.3 or above and Firmware 2430.3 or above
  • LG webOS 4 or 6 - Running OnSign App 10.6.3 or above and Firmware 03.68.33/1.6.8 or above 

Although its not a strict requirement, we highly recommend using Programmatic Apps with OnSign Pro plan or above, as this will enable the use of Player Custom Attributes as input variables to the programmatic Apps

Step 1 - Configuring Custom Player Attributes

Custom Player Attributes act as local variables that Apps can access during playback.

Each Player can have its own unique attribute values, defined and stored once the attribute is created.

This makes Custom Attributes especially useful for storing programmatic credentials. Instead of setting up multiple Apps, only one App is needed. When it runs, the App automatically retrieves the credentials stored on the Player and uses them to make the programmatic ad request.

While Custom Attributes can be created at the Account Settings, the Vengo programmatic App provides an internal shortcut that allows to creating the required Custom Attributes directly directly from the App.

1. Click on the “Content” menu
2. Create, or navigate to the folder where the Vengo App Should be Stored
3. Click the “New” button > App > Then type "Vengo" into the search box and select the Vengo App.
4. Enter a valid Name so the App can be saved later.
5. Expand the App Attributes (this is where the credentials should be entered)
   1. In most cases, the “Vengo Organization ID” will be the same for all players, so this can be entered directly in the App, meaning its not required to create a Custom Attribute for it.
   2. The “Vengo Ad Unit ID” is usually unique for every screen, so either connect it to an existing Custom Player Attribute in case you already have it, or click the drop-down, go all the way to the bottom and click “Create New Player Attribute”. Just follow the steps for setting up a specific Player Attribute.
6.  Select the environment that the App should be connected Production or Staging.
7. Select a fallback media. The fallback media is an image or video that will be shown when there is no ad to be shown.
8. Configure the Fallback Duration. This is optional and only applies to images media fallback.
9. Check the “Skip Playback When No Ad Is Scheduled” in its the desired behavior is not to sky the app playback when there is no ad to be shown.
10. Now that all is set, just save the app!

Now that the Custom Player Attributes are created, the Vengo Organization ID and Vengo Ad Unit ID should  be configured on all players that will use the 

Step 3 - Setting the Vengo Ad Unit ID for each player

While the app is all set and ready to be published, it is still required to set the Vengo Ad Unit ID for each player through the Custom Player Attribute previously configured. 

This process needs to be performed for each player that will playback the Vengo App.

1. Click on the player Menu
2. Select the player to be configured
3. Click on the player settings
4. Locate the Vengo Ad Unit (Custom Player Attribute)
5. Enter the Vengo Ad Unit 
6. Save the settings

Step 4 - Publishing the Vengo App

Now that everything is set, the only remaining step is publishing the app!

Programmatic apps are considered “Variable Content Length”, meaning their duration can vary depending on the ad received. While this provides flexibility, it also requires extra care when deciding how these apps are placed or published.

Key rule: Variable Content Length apps may be skipped entirely or end before the defined duration, but they can never exceed the time allocated to the item.

Example: Suppose a Programmatic App is placed inside a playlist item with a duration of 10 seconds. In practice, this means:

• If no ad is available and the app is configured to skip, the item may be skipped.
• If an ad shorter than 10 seconds is received (e.g., 7 seconds), the ad will play and end at 7 seconds, then gracefully transition to the next item in the playlist.
• If an ad longer than 10 seconds is received, the app will play but cut it short at 10 seconds. Since the ad was not shown in full, the confirmation will not be sent to the programmatic platform — meaning this ad will likely not be paid.

Step 5 - Testing your Credentials

Vengo requires two credentials to correctly retrieve ads:

• Vengo Organization ID  - Unique number to identify the advertising network
• Vengo Ad Unit ID - Unique ID to identify the specific Ad space (screen).

To test and ensure your credentials are correct, just copy this URL into your browser, replacing the respective items with your credentials.

Testing credentials on Vengo Staging environment:

https://staging-pubads.vengolabs.com/trafficking/vast/ad_request?organization_id=[VengoOrganizationID]&ad_unit_id=[VengoAdUnit ID]

Testing credentials on Vengo Production environment:

https://pubads.vengolabs.com/trafficking/vast/ad_request?organization_id=[VengoOrganizationID]&ad_unit_id=[VengoAdUnit ID]