GTM Ultimate Stack
Schedule a recurring orphan and hygiene report across brands
Save an inventory extract and its filters as a recurring report, so orphaned and off-convention items surface on schedule without anything being changed.
Decide what the report should catch
A scheduled report is a saved extract: the brands you chose, plus the filters you set. Each run repeats it and delivers the result. It works best when it answers one question you would otherwise forget to ask. For example:
- Orphaned triggers, all brands: Usage Orphaned, Entity Triggers.
- Tags breaking the naming rule: Entity Tags, with a Name regex that matches anything not following the convention.
- Anything kept alive only by inactive items: Usage Only inactive users.
- One vendor everywhere: Name contains the vendor's name, to keep an eye on a rollout.
A saved report keeps the brands, the entity, the usage filter and the name filter. The type, status and container filters only apply on screen and are not saved, so build your question from the first four.
A list of four saved-report ideas with the filters each uses.
Save the extract as an automation
Set up the extract in the panel as you normally would: pick the brands and set the filters. Then open the Automation section beside it and save the schedule. It records the current scope and filters, and you can open it later to edit them.
Only the extract can be scheduled. Rename, pause, delete, create, copy and Apply always need you in the panel. A schedule can tell you what has changed; it can't change anything.
A week strip with a Monday morning extract, a read-only extract card and a card listing the actions that can never be scheduled.
Know when a scheduled run happens
Schedules run on your Windows computer, so a few conditions apply:
- up to 10 scheduled runs a day;
- the computer must be awake and connected, with ODDVX running;
- a run missed because those conditions weren't met is skipped, not queued for later.
Pick a time when the machine is reliably on, and check the run history now and then. If a run seems to be missing, first check that the computer was awake and ODDVX was running at that time.
A week of run history with four runs and one skipped day, plus the run conditions.
Deliver it
Each run can send its result by email, with the inventory attached as a CSV: entity, account, container, name, type, status, usage and reference count. Send it to the people who will act on it, and keep the files in your findings register so this month can be compared with last month.
Email and CSV delivery are Premium. Before sending a report outside your team, remove client identifiers and anything personal.
Three delivery steps followed by an email card and a CSV attachment card.
Optional: let Oddie fill in the scope and filters
If you have Oddie, the in-app guide, set up with your own AI provider key, you can describe the report in a sentence, for example orphaned triggers in all the AU brands. Oddie fills in the scope and filters for you to check. It never runs the extract and never changes anything. You press Extract, and you save the schedule.
An Ask Oddie form with a typed request, a note that four brands and two filters were filled, and a note that Oddie never runs or changes anything.
Turn the report into a monthly action list
A report nobody acts on is just noise. Once a month, compare the latest report with the previous one:
- What is new since last month, and which brand is it in?
- What was resolved, and does the count show it?
- Which items need an owner's answer before anything can be decided?
Turn each answer into an owned action with a date, and feed confirmed cleanups into an orphan cleanup batch or a rename batch.
Two panels: the monthly report's counts and changes, and a list of owned actions with dates.
ODDVX for Windows
Build once. Stage it in every brand.
Start free on one GTM account. Premium adds several accounts in one run, exports and scheduled reports.