Part of the ADI ecosystem

500 banners in one link. Every one with its proof.

ADI LINK generates the client preview for a campaign. On every file, an extra layer shows whether it meets the publisher's spec, the brand rules and the copy the client supplied, signed by the person who checked it. The client comments on the file. When the campaign was built in A.D.I.'s templates and file structure, those comments can be applied to the source files automatically.

adilink.online/[client]/q4-launch/v3 V3
300×250approved
728×901 comment
Video 16:9approved
No agency branding. The client sees the campaign, not the tool. Open on a phone
Checks in the file

Not a link with 500 banners. A link where each of the 500 shows whether it passed.

Three things are compared for every file: the publisher's spec, the brand rules, and the finished text against the materials the client supplied. The results are written into the file's metadata and shown in the client link as an overlay on that banner, signed by the person who checked. The client does not have to trust that the delivery was checked. They can see it, file by file. Nothing else on the market does this.

Client view · overlay on[CAMPAIGN]_300x250_DE.zip · v3
Publisher spec · clickTag OK · 142 KB · stops at 24 s Brand · 12 of 12 rules pass Copy · 5 of 5 lines match the client's deck
checked by [NAME] · 21.08
The overlay is a switch in the client view. Off, it is a clean preview. On, every claim is visible on the banner it is about.

Written into the file

Results travel inside the file's metadata, not in a separate PDF someone has to find. Download the ZIP from ADI LINK and the proof comes with it. Re-upload and the results are rerun against the new version.

Run from where you work

From A.D.I. during production, from ADIMATE on export, or on the uploaded files in ADI LINK itself. Same engine as Vadilator, same report shape.

Signed, per version

The name of the person who checked, the deck version, the brandbook version and the date. "Approved v3" and "checked v3" are the same v3.

Junior

The client writes a comment on the file. Junior makes the change in the source.

ADI LINK is Junior's way into the campaign. Junior is the assistant that works inside A.D.I. When the campaign was set up in A.D.I.'s templates and file structure from the start, the client's comments and corrections become tasks it can carry out on the source files: texts, scripts, assets generated with AI, and elements on layers built from templates. Where the source lives in another program, Junior works through our plugins for After Effects, Photoshop and Figma.

1 · Client, in the link
Comment on 728×90 · DE
Please change the date to 30.06. in all German formats and use the new packshot.
2 · Junior, in A.D.I.
1Deck, DE column: "30.6." → "30.06." (5 rows)
2Packshot → packshot_v3.png in 12 ADIMATE artboards
32 After Effects comps updated through the plugin, re-rendered
Approve and run Show changes
3 · Back in the link
19 filesv4 uploaded
Copy Checkrerun, all match
Commentmarked resolved
A person approves before anything runs. Junior proposes, shows the diff, then works.

Texts

Edits land in the copy deck and flow to every format and language that uses the line.

Scripts

A one-off change across many files is written as a script, shown, and run on the selection.

AI assets

A new background or a replaced detail generated straight into the library and placed on the layer.

Layers, anywhere

Template layers in ADIMATE natively. After Effects, Photoshop and Figma through our plugins, which run the changes inside those programs.

How it works

Client, campaign, files, link. The structure you already use.

01

Create a client and a campaign

Under your own account. Clients, folders, campaigns, the way a preview tool is supposed to work. Nothing to learn.

02

Upload, or send from the tool

Drop in HTML5 ZIPs, statics and videos, or send them straight from ADIMATE's artboards. Each upload is a new version, the old one stays.

03

Send one link

A campaign link for the client, or a quick link for a single file that lives for two weeks. White-label, no sign-in needed to view.

04

Collect the answer

Approved, comments or rejected, per file and per version. "The client approved v3" finally means something.

Comments and statuses

Your statuses, your words. Read by every tool.

The status set is the agency's to define, for campaigns and for files. ADI LINK, A.D.I. and ADIMATE all use the same one, so a rejection with a comment in the client view is a rejection with that comment in the producer's editor, instantly. Nobody copies feedback from one window into another.

to makereadyin reviewin editsapprovedrejected+ your own
ADI LINK · client view
[CAMPAIGN]_728x90_DE
REJECTED
Client · 14:02
Date is wrong, should be 30.06.
ADIMATE · Artboards panel
728x90_DE
REJECTED
Client · 14:02 · same second
Date is wrong, should be 30.06.
Preview

Seen the way it will run.

HTML5 banners play, not screenshot. Videos play with sound. Statics at real size. Scan the file's QR code and the banner opens full screen on a real phone, so "it looks different on mobile" stops being a guess.

·clickTag check on every HTML5 file, before the client clicks it.
·Weight shown next to the format, with the publisher's limit.
·Version history per file: who uploaded what, when, and what the client said about it.
[CAMPAIGN]_300x250_EN.zip142 KB of 150
clickTag OK v3 approved 21.08
On the phone

Scan a code. See the banner full screen, on a real phone.

Every file in ADI LINK has a QR code. Scan it and the 320×50 or the 300×250 opens full screen on your phone, the way the audience will meet it. Not scaled down in a desktop browser, not a screenshot in a deck.

[CAMPAIGN]_320x50_EN.zipv3
Open on a phone
Scan with the camera. No app, no sign-in. The banner plays full width on the screen.
320×50300×250any format
Two things you only see on the phone
·Is the legal line readable at this size, or is it a grey smear?
·Did the agency use the fact that 320×50 scales on mobile and fits a real message, or did they ship a stuffed static 320×50 instead of a responsive mobile format?
Campaign code · for the meeting[CLIENT] · Q4 launch
One code for the whole campaign
Download it from ADI LINK, drop it on a slide. When the client scans it in the meeting, the whole campaign is on their phone, every banner, static and video, before you have finished the sentence.
Download PNGDownload SVG
The code points at the campaign link, so it keeps working after the meeting and always opens the current version. Set it to expire if you want it to stop.
[CLIENT] · Q4 launch62 of 97
SIZE
TYPE
LANGUAGES
STATUS
300×250
HTML5
EN DE IT PL ES
approved
728×90
HTML5
EN DE IT PL ES
in edits
160×600
HTML5
EN DE IT PL ES
ready
1080×1080
Static
EN DE IT PL ES
to make
1080×1920
MP4
EN DE
to make
to make ready in edits approved rejected
Plan and status

Drop in the media plan. The campaign knows what is missing.

Paste the agency's plan and it becomes a list of assets that have to exist: formats, languages, deadlines. Uploads fill the rows. ADIMATE reads the same list, so the producer sees what is left to make and the PM sees what is left to approve, in the same place.

A campaign without a plan just shows its files. Both work.

Who it is for

Media houses, agencies, freelancers on ADIMATE, and teams on A.D.I.

Media houses

Add the materials, generate the client preview, done. White-label, so the client never learns which tool, or which agency, sits behind the link.

Agencies on Adpiler

Keep it. ADIMATE and A.D.I. talk to Adpiler too. ADI LINK is there when you want the version history and the checks in one place, not a reason to migrate.

Freelancers on ADIMATE

Every ADIMATE user has an ADI LINK account. Clients, campaigns, media plans, texts and assets kept here, resizes made in ADIMATE, previews sent back as a link. The whole banner kit, without the full A.D.I.

Teams on A.D.I.

Right-click a campaign in A.D.I., "Sync with ADI LINK", and the preview side is up to date. One account opens all three products.

Preview files served from a global CDN, account data in Switzerland. Enterprise options available.