Naming conventions and tracking alerts: catch the mess before the client report

Written by Uptimal, the team that builds and operates Upbuild and runs marketing analytics for multinational clients across the globe. Everything below reflects how the product actually works, including the parts that are deliberately boring.

The month-end report for Acme splits spend by market, brand and objective. On the 30th, three rows refuse to add up. One campaign is called test_v2_final, launched on the Meta side by someone who joined in August. Two more were set up by the client's own team in Google Ads and named after the person who briefed them. And purchases on the UK site stopped arriving in analytics on the Tuesday a tag manager version went live, so the report shows a collapse in sales that never happened.

None of this is unusual. It is what accounts look like when many hands touch them. The only question is whether the head of reporting finds out on the 30th, in the report, or on the day it happens, in a message.

Two rules, one sentence each

In Upbuild, with AI Alerts, both problems become standing rules that the head of reporting writes once, in plain words.

The naming rule: "Every new campaign must follow Market_Brand_Objective_Date. Post the ones that don't in the naming channel on Slack."

The tracking rule: "Tell me straight away if purchases stop being tracked on any client site, and check every new tag manager version."

Upbuild AI sets each one up, schedules it and runs it across every account the rule covers. There is nothing else to install. The rules check the same numbers the dashboards show, in the same place the team changes a dashboard or a schedule.

The naming rule, every morning

Reports that split spend by market, brand and objective only add up when every campaign name follows the same pattern. A name is not decoration. It is the row key for the client report, so one wrong name is one wrong row, and a wrong row in a client's report is a conversation nobody enjoys.

Every morning, before the team starts, Upbuild checks every new and renamed campaign in every account the rule covers against the convention. It does not matter which platform the campaign was launched in, such as Google Ads, Meta or DV360, or who launched it: the agency's own team, the client's in-house team or a media partner with access to the account.

The message in the naming channel lists each campaign that breaks the rule and the name it should have. uk_search_brand_sept becomes UK_Acme_Brand_2026-09. Upbuild never renames a campaign itself. The person who launched it makes the change in the platform, and the next morning's check confirms it.

That last point matters for an agency. A tool that renamed campaigns on its own would be rewriting the client's account without asking. A message that says exactly what to change keeps the account where it belongs.

The tracking rule: what it compares

A broken purchase tag is the expensive kind of quiet. One change in Google Tag Manager or Adobe Tags, a renamed variable or a trigger tightened during a test, and purchases stop reaching analytics. The report shows a drop in sales that did not happen, and the ad platforms lose the conversion data their bidding depends on, so budget drifts to the wrong campaigns while everyone argues about the chart.

The tracking rule watches every Google Tag Manager and Adobe Tags container the organisation has shared with her. It checks each new version when it goes live, and every hour it compares the purchases recorded in analytics and in the media platforms with their usual pattern. When purchases fall below the level they usually hold at that hour, the right people get an email straight away with the likely cause: the version that was published, the tag that changed and the time purchases dropped.

The email for the UK site reads: purchases stopped recording on Acme UK; version 58 published at 14:02; no purchases recorded since 14:02, usually about 60 an hour; Google Ads and Meta are bidding without conversion data; likely cause, the purchase tag's trigger changed in version 58. The finding took an hour. Without the rule it takes three weeks and a client escalation, which is the story told in the tag that stopped firing.

Upbuild only reads the tag manager and the analytics setup. It never publishes, pauses or edits a tag, so watching your tracking can never break it.

Who gets told, and what they do

The naming rule tells a channel. The naming channel on Slack is read by the whole media team, so the person who launched the campaign sees their own name on the list and fixes it before the client does. The account lead sees it too, which is how a convention survives a new hire, a new client and a busy quarter.

The tracking rule tells people, by email, straight away. On the Acme UK afternoon the email reaches the analytics lead and the account lead within the hour. The analytics lead opens version 58, finds the trigger change, and either rolls the container back or fixes the trigger and publishes again. The account lead tells the client what happened and what it did not cost, because the platforms were bidding blind for one hour rather than three weeks. Nobody at Upbuild touches the container. The fix is theirs, made in their own tag manager.

Both messages carry what the reader needs in order to act, not just the fact that something moved: the names and their corrections, or the version and the tag. The first click is the fix, not the lookup.

Why this matters more when many hands are on the accounts

A single in-house team with one ad account can hold a convention in its head. An agency cannot. Its accounts are touched by its own team, the client's team, freelancers, a media partner in another market and whoever joined last month. Every one of them has a good reason for the name they chose and a different idea of where the purchase tag lives.

Upbuild is built for that shape. Everyone signs in as themselves with Google or Microsoft. An admin decides who joins the organisation and shares accounts one person and one account at a time, so a rule written by the head of reporting covers exactly the clients the organisation has shared with her, and a new client is covered from the day it is shared. When someone leaves, the admin removes them and their access ends. The rules they wrote belong to the organisation and keep running for whoever takes over.

And nothing Upbuild does can change a budget, a campaign, a tag or an audience. The only writes are the exports you schedule yourself with AI Data Exports. For an agency handling other people's accounts, that is the sentence to put in the proposal.

The naming rule and the tracking rule are the two cheapest habits an agency can adopt before the month-end report. Neither replaces the person who reads the report. They make sure that when she opens it on the 30th, the three rows already add up, and that the client's dashboard has been telling the truth all month.

Frequently asked questions