AdConnect for LDSK

Dise AdConnect enables the integration of 3rd party advertising platforms into Dise.

LDSK is a media planning and audience targeting platform for DOOH and In-Store Retail Media.

To use the AdConnect for LDSK app, you will need an account and an API key from LDSK, please refer to ldsk.io for more information.

You will also need to register your inventory of displays with LDSK. When registering the inventory, use the Display ID from Dise to identify each screen.

If the Dise display ID is not registered in the inventory in LDSK, a pairing code will be displayed on-screen, allowing the display to be identified and registered in the LDSK inventory.

Note that AdConnect for LDSK consists of two separate apps which work together to make the integration work:

LDSK Worker - this app needs to continuously run in the background, as it handles all communication with LDSK, including fetching ad schedules and media assets, and reporting heartbeats, status, and proof of play
LDSK Playout - this app does the actual playout of an ad, and is placed in a channel and playlist. Typically, there will be other content playing in the channel as well

Installing and using the app

Make sure you are all set up in LDSK, with an API Key and all Display IDs registered in the inventory
Download the worker app here:
LDSK Worker
56.97 KB
You need to set your API key in the config.json file of the worker app. Read Customizing the app below for details.
Upload the zip (including the config.json file with your API key) as a template in the CMS
Create an invisible / background layer with a channel and playlist.
Create a message and publish to the playlist. The AdFeed Channels field can be left blank (read below on using multiple AdFeed channels)
Download the AdConnect playout app here (Portrait and Landscape versions provided for convenience):
LDSK (P)
58.27 KB
LDSK (L)
58.27 KB
Upload the zip (including any changes to the json files) as a template in the CMS
Create a message from the template, and publish to playlist.
The AdFeed Channel field can be left blank. It is recommended to upload your own fallback media, which is displayed when no ad is available from LDSK. Otherwise, the default fallback will be shown:

Tip: AdConnect works well in combination with the Share of Voice feature in Dise

Customizing the worker app

To customize the worker app, unpack the zip file, edit the config.json file as described below, then create a new zip with all files.

Setting the LDSK API key (mandatory!):
```
"apiKey": "",
```
Impersonating a different Display ID:
```
  "playbackDeviceId": "",
```
Normally, the AdConnect app will read the actual Display ID from the player, but for test purposes, you can override this and hardcode a different ID in the config.json file
Changing the interval for reporting status heartbeats and proof of play:
```
    "heartbeatInterval": 5,
    "proofOfPlayInterval": 15
```
The LDSK worker app defaults to reporting status heartbeats every 5 minutes and proof of play every 15 minutes, but you can change these values
Auto-pairing with LDSK:
```
  "externalIdFormat": "{{SiteId}}_{{ZoneName}}_{{Channel}}",
```
NOTE: this configuration should be confirmed with LDSK before use.
Auto-pairing can be enabled by supplying a specially formatted externalId to LDSK via the Worker template. The format is defined with template values surrounded by double curly brackets (e.g. {{SiteId}}).
- Supported values are listed in the Global CX Attributes. Only attributes beginning with static.dise. are supported.
- The attribute {{Channel}} is also available, corresponding to the channel specified in the template (or the default channel if none is provided).
If the ID of the display has not been registered as a device in LDSK, the playout app will show a LDSK pairing code. To avoid this, and show the fallback content instead:
```
    "hidePairingCode": true,
```
The pairing code will still be written to the player log file if the log level has been set to “debug”

Customizing the playout app

To customize the playout app, unpack the zip file, edit the template.json file as described below, then create a new zip with all files.

Changing the template name in template.json:
```
"name": "LDSK (L)",
```
This is particularly useful if you need several copies of the app covering different resolutions than the standard portrait and landscape versions provided here.
Changing the resolution in template.json, if you need other resolutions than standard portrait or landscape:
```
"targetWidth": 1920,
"targetHeight": 1080,
```

Using multiple AdFeed channels

In some advanced use cases, where the LDSK app is used in multiple triggered scenarios in Dise, there may be a need to differntiate between the different scenarios from the LDSK perspective. To allow LDSK to serve different ads depending on which scenario it is invoked from, you can define AdFeed channels for each scenario where LDSK ads are shown:

Decide on a unique name for each AdFeed channel
In the LDSK Worker app message, enter all the names (separated by commas) in the AdFeed Channels field
Create separate messages from the LDSK playout app for each AdFeed channel, enter the respective name in each instance, and publish to the appropriate scenarios.