Onboard a digital signage device (step-by-step)

How to onboard digital signage should not mean weeks of IT tickets. If you have a screen, a player, and a network connection, you can go from download to live content in minutes. This guide covers digital signage device setup with AdSign — install the player, name your device, assign content, and confirm playback.

This is device onboarding (pairing a physical player to your account). If you are an agency rolling out clients under your brand, see onboarding your first signage clients for discovery, pilots, and handoff — a different workflow, same platform.

What does device onboarding mean?

Device onboarding is the process of connecting a playback device — Android TV, Android box, Windows PC, or Raspberry Pi — to your AdSign account so the cloud dashboard can push playlists, schedules, and wall layouts to that screen.

A successful AdSign player setup ends with:

The device online in your dashboard
A clear device name you recognize (Front-Menu-01, Lobby-Wall-Left)
Content playing on the screen without manual USB updates

Simplified onboarding is built for operators who need speed: retail managers, franchisees, and small teams without dedicated AV staff.

Prerequisites before you start

Gather these before you open the player app:

AdSign account — Start a free trial if you do not have one yet.
Supported hardware — Android TV, Android Box, Windows, or Raspberry Pi (full device list).
Network — Wi‑Fi or Ethernet; guest networks with captive portals often block players until allowlisted.
Display — TV or monitor connected via HDMI; note portrait vs landscape.
Content ready — At least one playlist or channel to assign after pairing (templates help if you are starting from scratch).

For video walls, you will repeat onboarding per panel — see the digital signage video wall guide.

Step-by-step: onboard your first device

Step 1: Download the AdSign player

Visit /download/ and install the correct build for your platform. On Android TV, use the store or sideload flow your deployment standard allows. On Windows or Pi, follow the installer for your OS.

Step 2: Install and launch the app

Open AdSign on the device. Confirm the display resolution and orientation look correct in the TV settings before you pair — fixing rotation later is easy in software, but physical mount orientation is cheaper to get right once.

Follow the on-screen prompts to connect the player to your AdSign organization. Use the same login your team uses in the web dashboard, or the pairing code flow shown in the app if your rollout uses codes.

Step 4: Name your device

Choose a consistent naming scheme:

Location + role — Chicago-Menu-01
Wall position — Lobby-Wall-TR
Client prefix for resellers — ClientA-Downtown-01

Good names save hours when you have dozens of screens and when support asks “which player is offline?”

Step 5: Assign a playlist or channel

In the dashboard (or during guided setup), assign the device to a playlist or channel. Channels are useful when multiple screens must stay in sync — see channel playback sync.

Step 6: Confirm playback on the physical screen

Stand in front of the display. Verify:

Content loops as expected
No black bars from wrong aspect ratio
Network drop recovery (briefly disconnect Wi‑Fi if you need a hard test)

Your digital signage device setup is complete when the screen matches what you published in the cloud.

Watch the onboarding walkthrough

Follow along in this short video:

You can also use the homepage onboarding section for the same walkthrough embedded on the main site.

Who should own device onboarding?

In a small business, the owner or marketing lead often completes the first AdSign player setup. In larger chains, a regional manager or IT liaison pairs devices while headquarters owns templates and playlists. Resellers may onboard players during installation, then hand the dashboard login to the client for day-to-day updates.

Clarify roles early: who downloads the app, who names devices, who publishes content, and who gets alerted when a screen goes offline. That split prevents duplicate accounts and orphaned players sitting in “test” mode on a live TV.

Tips for retail and hospitality rollouts

Pilot one location first — Onboard two screens, run for a week, then clone playlists and naming rules to other stores.

Standardize names and tags — Document a one-page rule every franchisee follows.

Use a test playlist — A simple branded slide proves the pipe works before you upload campaign video.

Document network requirements — MAC allowlists, VLANs, and DNS filters are the top cause of “works in HQ, fails in store.”

Train one “screen owner” per site — They do not need IT depth; they need to know how to reboot the player and who to call.

Batch onboarding days — For ten or more screens, bring a printed grid of device names and positions. Pair one screen at a time in the same order you mounted them to avoid swapping labels.

Reuse templates — After the first screen plays, duplicate playlists and schedules rather than rebuilding creative per device. AdSign’s template library speeds first publish.

After onboarding: what to configure next

Once playback is live, most teams configure in this order:

Scheduling — Daypart menus, weekend promos, and holiday overrides.
Zones or overlays — Tickers, logos, or emergency banners if the layout uses them.
Groups — Organize devices by region or brand for bulk updates.
Channels — If multiple screens must stay in sync, assign a channel rather than only a standalone playlist.
Video walls — If this site includes a hero wall, complete per-panel onboarding then follow the video wall guide.

Skipping straight to advanced features before the first playlist loops cleanly is a common source of support tickets — prove the base path first.

Troubleshooting device onboarding

Device shows offline — Check power, Ethernet/Wi‑Fi, firewall rules, and that the player app is running. Reboot the player before opening a ticket.

Wrong orientation — Adjust display rotation in device settings and republish; confirm creative matches portrait vs landscape.

Content not updating — Confirm you published to the correct device or group; allow a minute for sync on slower networks.

Black screen after pairing — Verify a playlist is assigned and not empty; check HDMI input on the TV.

Onboarding succeeded but playback stutters — Prefer wired network for 4K loops; reduce bitrate or use hardware-appropriate templates.

FAQ

How long does AdSign device onboarding take?

Most teams finish the first screen in under 10 minutes once the player is installed and network is open. Bulk rollouts scale with naming discipline and prepared playlists.

Do I need IT to onboard digital signage?

Not for a typical single-site setup. Enterprise networks with strict firewalls may need IT to allow traffic once; document requirements early.

Android TV vs Windows — which is better for onboarding?

Both are supported. Android TV is common for TVs with built-in OS; Windows suits kiosk PCs and some video walls. Pick what you can service locally.

What is the difference between device onboarding and client onboarding?

Device onboarding pairs one player to your account. Client onboarding (for resellers) is the business process of selling, surveying, and handing off signage to an end customer — covered in our agency onboarding guide.

Can I onboard devices remotely?

You still need someone on site for HDMI and power. Pairing and content assignment happen in the cloud once the player is online.

How does onboarding relate to channel playback sync?

After devices are onboarded, assign them to the same channel if you want channel-level playback sync across a zone or store.

Start your free trial and onboard your first screen today.