Campaign URL Reader

Overview

You send a link and we tell you which campaign parameters it carries, what their values decode to, how often each one repeats and which vocabulary each belongs to — the five core parameters, Google's four additions, or one of fourteen vendor click identifiers. The cleaned link comes back beside them, with exactly those parameters removed and nothing else touched: host case, port, dot segments, the order and bytes of every surviving parameter, and the fragment all survive. Repeated parameters are reported rather than resolved, because which one an analytics product honours is its decision and not ours. We fetch nothing and canonicalise nothing.

Link normalisers drop tracking parameters and tell you only the names they dropped, which is the wrong half: you wanted to know that the visitor came from the spring newsletter, not that a parameter called utm_campaign used to be there. You get the values, the repetition and the cleaned link in one answer.

When to use it

Scope

Non-goals

• Does not canonicalise the link — the cleaned link is not a comparison key, and web.normalize_url is what produces one
• Does not fetch, resolve, expand or check the link
• Does not decide which repeated occurrence wins; every one is reported
• Does not report a name it cannot classify, so there is no utm_ prefix rule
• Does not report routing or cookie-linker parameters such as ref, _ga and _gl

Properties

Capabilities

Cost & billing

Flat rate per invocation

File handling

How we handle your data

Input schema

Output schema

API contract

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"marketing.utm_parse","input":{"url":"https://acme.example.com/pricing?utm_source=newsletter&utm_medium=email"}}'

import { Squillify } from "@squillify/sdk";

const sq = new Squillify({ apiKey: process.env.SQUILLIFY_API_KEY });

const { output } = await sq.execute("marketing.utm_parse", {"url":"https://Example.com/pricing?plan=team&utm_source=news+letter#faq"});

Errors

Other limits

Limitations

• Does not canonicalise the link — the cleaned link is not a comparison key, and web.normalize_url is what produces one
• Does not fetch, resolve, expand or check the link
• Does not decide which repeated occurrence wins; every one is reported
• Does not report a name it cannot classify, so there is no utm_ prefix rule
• Does not report routing or cookie-linker parameters such as ref, _ga and _gl
• Producing a canonical link to compare or deduplicate against
• Reading parameters that are not campaign parameters
• Checking whether the link resolves or what it returns

How to call

POST /v1/execute (requires authentication)

{
  "skillKey": "marketing.utm_parse",
  "input": {
    "url": "https://Example.com/pricing?plan=team&utm_source=news+letter#faq"
  }
}

Examples

{
  "url": "https://Example.com/pricing?plan=team&utm_source=news+letter#faq"
}

{
  "params": [
    {
      "name": "utm_source",
      "class": "utm_core",
      "occurrence": 0,
      "valuePresent": true,
      "value": "news letter",
      "rawValue": "news+letter"
    }
  ],
  "cleanUrl": "https://Example.com/pricing?plan=team#faq",
  "summary": {
    "matchedCount": 1,
    "removedOccurrenceCount": 1,
    "repeatedNames": [],
    "otherQueryParamCount": 1,
    "malformedEscapeCount": 0,
    "spaceDecoding": "plus_as_space",
    "unicodeForm": "none",
    "classes": [
      "utm_core",
      "utm_extended",
      "click_ids"
    ],
    "truncated": false
  },
  "byName": {
    "utm_source": [
      "news letter"
    ]
  }
}

{
  "url": "https://acme.example.com/offer?utm_source=newsletter&gclid=EAIaIQobChMI",
  "include": [
    "CLICK_IDS"
  ]
}

{
  "params": [
    {
      "name": "gclid",
      "class": "click_ids",
      "occurrence": 0,
      "valuePresent": true,
      "value": "EAIaIQobChMI",
      "rawValue": "EAIaIQobChMI"
    }
  ],
  "cleanUrl": "https://acme.example.com/offer?utm_source=newsletter",
  "summary": {
    "matchedCount": 1,
    "removedOccurrenceCount": 1,
    "repeatedNames": [],
    "otherQueryParamCount": 1,
    "malformedEscapeCount": 0,
    "spaceDecoding": "plus_as_space",
    "unicodeForm": "none",
    "classes": [
      "click_ids"
    ],
    "truncated": false
  },
  "byName": {
    "gclid": [
      "EAIaIQobChMI"
    ]
  }
}

Recommended use cases

• Recover which campaign brought a visitor, by value and not just by name
• Strip campaign parameters before storing a link as content, keeping the rest of the query byte for byte
• Reconcile a click identifier against a vendor report, using the raw and decoded forms side by side

Avoid for

• Producing a canonical link to compare or deduplicate against
• Reading parameters that are not campaign parameters
• Checking whether the link resolves or what it returns

Related skills

Composable with

Safety & privacy

• Runs without calling any external service.
• Your payloads are never stored permanently.
• Telemetry captures metadata only — never your payload contents.
• We never train models on your payloads.
• No human reviews your payloads.

Tags