MARKETING

Reconcile UTM exports against the registry and log gaps to Postgres

Scans newly uploaded campaign-export files in Google Drive, cross-checks every UTM against the approved registry in Postgres, logs unregistered links as gaps.

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerevent
Steps5
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNew UTM export uploaded to Google DriveGoogle DriveGoogle Drive
  • LogicRead file and extract distinct UTM combinations
  • ActionLook up each combination in the Postgres registryPostgreSQLPostgres
  • LogicIsolate unregistered orphan campaigns
  • OutputLog gaps to Postgres and alert team in SlackSlack

What it does

When a campaign UTM export lands in a Google Drive folder, this workflow reads the file, compares each UTM combination against the approved-campaigns registry stored in Postgres, and identifies links that are live in the wild but were never registered. Those orphans get logged as taxonomy gaps in Postgres and the team gets a heads-up so untracked campaigns are reconciled.

When to use it

Use it when campaigns get launched faster than they get registered and you need to catch shadow UTMs — links real users are clicking that have no entry in your source of truth.

How it works

  1. 1A Google Drive trigger fires when a new export file appears in the folder.
  2. 2A logic step reads the file and extracts every distinct UTM combination.
  3. 3A Postgres action looks up each combination in the approved registry.
  4. 4A logic step isolates the unregistered orphans.
  5. 5A Postgres action logs the gaps, and a Slack message alerts the team to reconcile.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  2. 2
    Connect PostgresAny Postgres URL — query, write, migrate.
  3. 3
    Connect SlackChannels, DMs, threads, mentions.
  4. 4
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  5. 5
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  6. 6
    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.