MARKETING

Live UTM Crawl with Redirect Loss Detection

Crawls the actual published landing pages from a campaign list, follows redirects, and detects when UTM parameters are stripped or rewritten in transit.

CategoryMarketing
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerScheduled crawl cadence
  • ActionPull live campaign URLs from AirtableAirtableAirtable
  • ActionFetch each URL and resolve redirectsFirecrawl
  • LogicCompare sent vs surviving UTM params, flag loss
  • ActionLog lossy links with before/after to AirtableAirtableAirtable
  • OutputAlert Slack channel when tracking is droppedSlack

What it does

This workflow goes beyond static text checking: it hits each campaign URL live, follows the redirect chain, and compares the UTM parameters on the final landing URL against what was sent. It surfaces links where tracking silently disappears because of a redirect, a CDN rule, or a shortener.

When to use it

Use it when links look correct on paper but analytics shows missing attribution. Redirects and link shorteners often drop query strings, and this catches that real-world loss that a parse-only audit cannot.

How it works

  1. 1Schedule trigger kicks off the crawl on a regular cadence.
  2. 2An Airtable action pulls the list of live campaign URLs to check.
  3. 3A Firecrawl action requests each URL and captures the final resolved landing URL after redirects.
  4. 4A logic step compares the original UTM params to those that survived and flags any dropped or altered keys.
  5. 5An Airtable action logs each lossy link with the before/after params, and a Slack output alerts the channel when loss is detected.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect AirtableBases, tables, views, automations.
  2. 2
    Connect FirecrawlCrawl, scrape, structured extract.
  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.