Changelog

October 22, 2026. Two launches, available to every account.

• Open Video Studio in the dashboard (/dashboard/studio), or ask your connected assistant.
• Draft a short video ad from your landing page, preview frames, generate scene images, record voiceover lines, check the result, and render an MP4 with a poster image.
• Renders run in your browser when it can, otherwise in the cloud. Every file is checked for loudness and timing before you get the download link.
• Drafts, images, and voice lines are metered from your prepaid balance; images and voice lines cost a cent or two each. Checks and renders are free.
• Rendered videos are downloads for now. Adprime Zero does not place video ads anywhere yet.

• A brand kit holds your colors, fonts, logo, product and style photos, voice, tagline, tone, image style, and guidelines. One kit is your default.
• Make one from your website in one step (it reads your site's colors, fonts, and icon and proposes the rest, for about a cent or two), or start blank. A kit made from a site starts with the site icon as its logo, so upload your real logo file.
• New video projects use your default kit, drafts follow its tone, and generated images can follow its product and style photos. Banner variants do not use kits yet.
• Find it on the Brand kits tab in Video Studio.

Connector tools: 12 for video (start with video_ad_guide, then create_video_project, draft_video_spec, and render_video) and 7 for brand kits (such as list_brand_kits and derive_brand_kit_from_site). The REST routes are /video/* and /brand-kits.

October 21, 2026. Connecting an assistant to Adprime Zero now takes one URL: https://mcp.adprimezero.com/mcp.

• Works where you already chat. Claude (claude.ai and Claude Desktop), ChatGPT, Claude Code, Cursor, and VS Code all take the URL. Cursor and VS Code get one-click install buttons on Connect your assistant.
• Sign in instead of pasting a key. The app opens a browser page. You enter the six-digit code from your email and click Allow. A new email gets an account on the spot.
• Each app gets its own key. It shows on the dashboard API keys page as MCP connector: <app name>. Revoke it there to disconnect that app.
• Run a campaign end to end. New tools read your balance (get_account), list and read campaigns, ads, and audiences, and launch, pause, or resume a campaign. Launching still waits until the ad, the landing page, and the balance are ready.
• Nothing to install. The setup no longer asks you to run npx -y ztdsp; the connector replaced it.

Scripts that cannot open a browser can still send an API key from the dashboard to the same URL. Connect your AI assistant and launch walks through the first campaign.

October 12, 2026. Image models make large square or wide pictures. Display ads need exact sizes, such as 300x250 or 728x90, at 220 KB or less. Adprime Zero now bridges the two.

• Make a banner from any image in your media library. Pick the size. The product crops the image (or fits all of it, if you ask), compresses it under the size limit, and saves the banner next to the original. Making a banner is free and never submits anything.
• Read the warnings. A wide 728x90 or 320x50 crop keeps only a thin band of a square picture. The result says how much was kept and what was cut, so you or your assistant can regenerate the image at the banner's shape or fit the whole picture instead.
• Submit by media id. Pre-check and submit take the banner's media id, so the image never has to pass through the chat.
• Look before you submit. Each banner comes with a private preview link, valid for 72 hours, that opens in a browser tab.

Where: the connector tools upload_media, list_media_library, get_media_item, and derive_banner_from_image, plus account_media_id on pre_check_creative and submit_creative; the REST route POST /media-library/:id/derive-banner; and Variant Studio in the dashboard, which now builds banners from the source image you attach.

PNG and JPEG images work. Convert WebP or GIF images first.

October 2, 2026. An Adprime Zero account is now a workspace that several people can share.

• Invite people by email from the Team page in the dashboard (/dashboard/team). The link alone never signs anyone in: the invited person confirms with a six-digit code sent to their own address. Invites expire after seven days.
• Three roles. The owner and admins see and manage everything. Members see only the campaigns of the teams they sit on.
• Teams group campaigns. Give each member read access (campaigns and reports) or edit access (create, launch, pause, and change ads) on a team. Moving a campaign between teams never touches its delivery.
• One wallet. The prepaid balance, billing, the ad and audience libraries, and conversion events stay shared across the workspace.
• Every key belongs to a person. API keys and connected assistants act with their owner's permissions. Removing someone revokes their keys at once.
• Switch workspaces from the header if you belong to more than one.

Assistants can do the same through the connector: invite_teammate, create_team, list_teams, list_workspace_members, move_campaign_to_team, and get_my_workspace_access, which tells an agent what its key is allowed to see.

Small-team ad launch shows one way to split the work.

2026-09-10. A second wave of Lab, Notes, Guides, Playbooks, Compare, and Glossary pages is live.

New buyer and agent jobs:

• Apply a Supply Audit finding
• Supply Audit tools for your agent
• Subscribe to webhooks
• Agent funding handoff
• Pause and resume a campaign

New Lab and Notes:

• Why audited spend uses Math.max
• Split the key before you exclude
• Incomplete coverage is not clean
• IVT shows in Beeswax first
• Require AUTH_DIRECT and AUTH_RESELLER (plan)
• Plan for more than one creative
• Applied finding came back open
• The reporting user is not the other login
• Build the web Worker before you deploy

Playbooks and glossary for detectors, destination drift, funding intents, coverage verdicts, webhooks, click tokens, and creative add-ons.

The first-wave index is Publication places launched.

September 3, 2026. A lifetime budget is optional. When you leave it out, a campaign should spend until you pause it or the prepaid balance is gone. Because of a bug, it stopped after one day instead.

• What went wrong. Every place that created a campaign on the exchange filled a missing lifetime budget with the daily budget. Day one used it up, the campaign never served again, and our dashboard still said running. It happened three times: the June 18, 2026 learning campaigns, the June 2026 relaunch, and a September 3, 2026 portfolio.
• What it does now. One rule decides the exchange's lifetime figure. An explicit lifetime budget is honoured exactly, so a $20 test stays $20. A missing one becomes a 30-day envelope (30 times the daily budget), so a $20 a day campaign is not turned into a $20 lifetime campaign.

If you left out a lifetime budget and your campaign died after one day, this was the cause. Story: a lifetime cap that silently became one day.

September 4, 2026. The exchange can now pace a campaign's daily budget evenly through the day, on its own clock.

• What changed. We had read one error message ("Bidding strategy CPM is not enabled for pacing. Please reach out to your account team.") as a missing feature. It only meant that plain CPM bidding is the unpaced kind. The paced variant, CPM_PACED, accepts daily pacing with even spend.
• Daily, not lifetime. Pacing across a whole flight needs an end date, and an Adprime Zero campaign may have no lifetime budget. So campaigns pace by the day.
• One pacer at a time. Exchange pacing and our own budget-slice pacer must never both act on one campaign: together they can stop delivery. A campaign is paced by one or the other.

The longer story: daily pacing, not lifetime pacing.

September 2, 2026. The nightly traffic audit (Supply Audit) can now act on its most common findings: individual ad slots (placements) and sites.

• What changed. We used to refuse placement and site findings with a message saying they needed a special list object we could not create. The exchange's own list of targeting options says otherwise: placements and sites are direct settings. Domains and app bundles still need a list, so those findings stay blocked for now.
• Why it mattered. That one wrong sentence had been blocking most of the waste the first audit could see.
• What apply does. It creates a new targeting set without the flagged supply. It never pauses a campaign, never changes a budget, and never touches live delivery on its own. Point the next campaign at the new set (for example by copying the campaign) and the flagged supply stops serving.

Under the hood, a finding's stored key combines the exchange and the slot; only the part after the separator goes to the exchange, because the full key matches nothing. Details: placement vs site vs domain.

2026-09-09. The public site now has publishing places next to product docs.

• Lab (/lab) for supply, buying, ideas, and measurement tests.
• Notes (/notes) for corrections and hard-won sentences.
• Guides (/guides) for buyer jobs.
• Playbooks (/playbooks) for prompts and checklists.
• Compare (/compare) for honest scope against agencies, DSPs, Google Ads, and Meta.
• Glossary (/glossary) for one-term pages.
• Benchmarks (/benchmarks) for dated scorecards from our flights.
• Changelog (/changelog) for what shipped.

Product docs stay at /docs. Paid funnels stay at /lp. Supply-bench probes stay at /sb. Lab is not a signup funnel and /sb is not editorial.

Start from how to judge display traffic or run ads from Cursor.

June 26, 2026. Delivery clicks come from the exchange's clicks field (plural). Our reporting asked for click, the request still succeeded, and every campaign read zero clicks. That zero looked exactly like a dead campaign, and it is why the June 2026 learning-flight readout was confusing. This entry keeps the date attached to the field name.

Related traps that still apply when a report shows zero clicks:

• Report rows arrive with label-cased keys (Clicks, Campaign ID). Code that looks for snake_case names reads every metric as zero.
• Fast spend snapshots store clicks as zero on purpose. They are not proof that nobody clicked.
• generated_at is when Adprime Zero answered, not when delivery was last reported.
• Click tokens are redirect plumbing, not the exchange's click count.

If spend or impressions exist and clicks are zero, check freshness and reporting status before you change targeting. Writeup: why a dashboard can show zero clicks.