MARKETING

AI reviewer that judges campaign UTMs against your living style guide

An agent reads your UTM convention from a Notion doc, evaluates each newly submitted link for both rule compliance and naming-quality issues the rules don't fully cover.

CategoryMarketing
Enginepaperclip
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew link entry created in NotionNotionNotion
  • ActionFetch current UTM convention guide from NotionNotionNotion
  • LogicAgent reasons about compliance + naming quality
  • ActionGenerate verdict and suggested corrected link
  • OutputWrite annotated review back to the Notion entryNotionNotion

What it does

This is an agent-driven reviewer for cases where strict regex isn't enough. It loads your team's UTM convention from a Notion page (the single source of truth), then evaluates each submitted campaign link not just for hard rule breaks but for fuzzy quality problems — inconsistent abbreviations, a campaign name that won't sort well next to siblings, or a source that technically passes but doesn't match the channel context. It writes a reasoned verdict and suggested rename back to Notion.

When to use it

Use it when your convention has nuance that simple validators miss and you want judgment, not just a boolean. Good for teams whose naming guide evolves and lives in Notion.

How it works

  1. 1A new link entry in Notion triggers the review.
  2. 2The agent fetches the current convention guide from its Notion source page.
  3. 3It parses the link's UTMs and reasons about compliance plus naming quality against the guide.
  4. 4It produces a verdict, a confidence note, and a suggested corrected link where warranted.
  5. 5The annotated review is written back to the link's Notion entry for the owner.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect NotionPages, databases, comments.
  2. 2
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  3. 3
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  4. 4
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.