Your rules live in the platform instead of a spreadsheet. Every campaign, insertion order, line item and creative is checked against them, wrong names are flagged before they reach a report, and the fix is written back to the DSP.
When a campaign is built or edited
KESTREL_Q4 · 12 line items
Campaign · IO · Line item · Creative
Budgets, flights, targeting, URLs
Re-run on every edit and duplicate
kestrel_q4_prosp → KESTREL_Q4_Prospecting_US
Cuts by market and product total correctly
Nothing enforces it when a trader builds, duplicates or edits a campaign. Conventions drift with every new trader and every new client.
DV360 has four levels, Meta has three. One convention has to hold across all of them, and no DSP will do that for you.
A misplaced field means the line item can’t be split by client, market or funnel stage. Its spend lands in “Other”, and the cut never totals correctly.
Every correction is a manual rename inside each platform’s own interface, one line item at a time, long after the spend has gone out.
100%
Naming compliance across live campaigns
Assembly Global
4
Levels checked on every DV360 campaign
Campaign · IO · Line item · Creative
7
Platforms held to one convention
DV360 · Meta · The Trade Desk · Google Ads · Amazon Ads · TikTok Ads · Snapchat
Each one works on campaigns you already run, including the ones atomicAds didn’t build. Use one, or run the whole chain.
Holds your convention and your allowed values per client, checks every name against it at every level, and writes the correction back to the DSP.
Checks the rest of the setup in the same pass: budgets, flights, targeting, frequency caps and landing pages, so a compliant name isn’t hiding a broken campaign.
Reports sit on the names Taxonomy has already cleaned, which is the point of enforcing them — a cut by market, product or audience finally adds up.
Direct sign-in to each platform with our own pipeline on top, so the check runs on source data and the fix goes back the same way.
Same agents either way. The only difference is who presses approve.
Build the taxonomy from your own fields and allowed values, per client, and your team works from one queue of names that break it.
Our ad ops specialists set the convention up, run the audit across your live accounts and keep it clean as campaigns change.
“Always-on built-in QA, alerts, monitoring, and optimizations… have streamlined our entire workflow, reduced errors and waste, improved campaign performance, and freed our team to focus on strategy.”
Wayne BlodwellGlobal SVP, Assembly Global100%
Naming compliance across live campaigns
“Before AtomicAds, our campaign lifecycle was highly manual and inefficient… The consistency and speed have been a game changer for our client servicing and delivering incredible results on campaigns.”
Tim PearceCEO and co-founder, SeeViews15 hrs
Per trader, per week, returned to trading
DV360
Line items, insertion orders and pacing checked across every DV360 advertiser.
Meta
Ad sets, budgets and naming checked on Meta campaigns before and after launch.
Google Ads
Search and Performance Max budgets, pacing and naming checked daily.
The Trade Desk
Campaigns, ad groups and bid factors QA’d across your Trade Desk seats.
StackAdapt
Line items, frequency caps and pacing checked across StackAdapt campaigns.
Amazon Ads
Sponsored Ads and DSP orders monitored for budget, pacing and naming.
Campaign groups, targeting and spend monitored across LinkedIn ad accounts.
Ad groups, budgets and naming checked across Pinterest campaigns.
Snapchat
Ad squads, budgets and pacing monitored across Snapchat campaigns.
TikTok
Ad groups, budgets and pacing monitored across TikTok campaigns.
Anything else, ask us on the demo. We’ll show it on your own accounts.
Request a DemoYes. The agent audits every live campaign in the account however it was built, including ones created by hand in the DSP, so you see the current state from day one.
Yes. Every client gets its own taxonomy and allowed values, and one client’s rules never touch another client’s accounts.
The rules are set per level, and the agent maps them to each platform’s own structure — four levels on DV360, three on Meta — so the same convention holds across all of them.
Only if you allow it. Write-backs can go through an approval step, and every change is logged with who approved it.
Cuts by market, product or audience start totalling correctly, because the dimensions come from names that follow the rule. That is usually the reason teams want this in the first place.
Most teams connect their platforms and see the first audit of live campaigns. The free audit runs before you commit to anything. We’ll give you a timeline for your own setup on the demo.
A free audit across your live DV360 or Trade Desk campaigns: which names fail at which level, on which platform, and what the corrected names would be.
100%
Naming compliance reached at Assembly Global
