MARKETING

Scheduled UTM Sweep Across the Campaign Tracker Sheet in Drive

Runs nightly over a shared Google Drive campaign-tracker spreadsheet, audits every UTM link in the sheet.

CategoryMarketing
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerNightly schedule fires
  • ActionRead campaign-tracker spreadsheet from Drive folderGoogle DriveGoogle Drive
  • LogicValidate UTM params per row and detect cross-campaign duplicates
  • LogicCompile per-row verdicts and pass/fail/warning summary
  • OutputWrite dated compliance report file to Drive folderGoogle DriveGoogle Drive

What it does

This is a batch auditor for teams who keep all their campaign links in one master spreadsheet on Google Drive. On a nightly schedule it reads the entire sheet, validates the UTM string on every link row, scores each as compliant or not with a specific failure reason, and writes a dated compliance report back into the same Drive folder for the morning standup.

When to use it

Use it when many people add rows to a shared campaign tracker throughout the day and nobody validates them in real time. The overnight sweep means every link is checked by morning without anyone running a manual review.

How it works

  1. 1A scheduled trigger fires nightly at a set hour.
  2. 2The workflow locates and reads the campaign-tracker spreadsheet from the configured Google Drive folder.
  3. 3A logic step iterates the rows, parsing and validating UTM parameters and flagging duplicates across campaigns.
  4. 4It compiles per-row verdicts plus a summary count of pass, fail, and warning.
  5. 5The finished compliance report is written as a new dated file back into the Drive folder.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect Google DriveDocs, sheets, slides, files.
  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.