Detect Tracking Parameters

seo.detect_tracking_parameters

ProductionBounded custom (Class B)Deterministicstrictinstantv1.0.0

No network

Overview

List known tracking query names on one URL and return a clean candidate that keeps everything else We never open a connection, resolve DNS, or follow a redirect. The answer is a structured fact or policy result you can store. A successful call costs 1 execution credit.

Agents kept deleting unknown query keys; this only classifies known tracking names and leaves the rest.

Reliability

seo.detect_tracking_parameters is stable for identical input. Identical input always produces identical JSON. SEO_INPUT_REQUIRED means a required field is missing or has the wrong shape, so send the published object rather than a guessed map; retrying unchanged will not help. SEO_INPUT_TOO_LARGE means a value exceeds its ceiling, so trim it. SEO_HTML_MALFORMED means the HTML could not be parsed under the offline HTML contract, so fix the markup. SEO_XML_MALFORMED means the XML is not well-formed, so correct it. SEO_XML_DOCTYPE_NOT_ALLOWED means the XML includes a DOCTYPE declaration, so strip the DOCTYPE and resend; we refuse DTDs rather than expanding entities. SEO_JSONLD_MALFORMED means a JSON-LD block is not usable JSON, so correct it. SEO_PROFILE_UNKNOWN means the named profile is not bundled, so send one of the published profile ids. SEO_TOO_MANY_RECORDS means a list exceeded its ceiling, so split the batch. SEO_GRAPH_LIMIT_EXCEEDED means the graph exceeded its node or edge ceiling, so shrink it. SEO_INVALID_URL means a URL string is not a usable RFC 3986 URI, so send an absolute URI. SEO_OBSERVATION_INCOMPLETE means required observation coverage is missing, so add the missing evidence. SEO_INPUT_CONFLICT means two fields that cannot be used together were both supplied, so drop one. Retrying an unchanged request will not help.

Context footprint

Returns a compact structured record. A successful call costs 1 execution credit.

When to use it

When you hold a URL and need utm and click-id pairs separated from content identifiers, plus a clean candidate.

When you want a full identity rewrite — use seo.normalize_url — or you still need to fetch the page.

Scope

Note

List known tracking query names on one URL and return a clean candidate that keeps everything else.

Non-goals

Does not fetch a URL, resolve DNS, or run a browser
Does not predict ranking, choose a winner, or claim live index status
Does not fetch, and does not drop unknown parameters

Properties

IdempotentRetry safeStreaming supportedFile input supportedRequires external service

Capabilities

analysisparsing

Cost & billing

Flat rate per invocation

MetercallsBillable onsuccessCost per call1 credit

File handling

Accepts file_refProduces file_refMax input8 KB

How we handle your data

Sensitive output possible

What this means

This skill may receive sensitive content and may return submitted, transformed, extracted, or reformatted content.

Squillify guarantees

Runs inside Squillify
This skill runs inside Squillify.
Payloads are not sent to an external service by this skill.
Squillify does not permanently store submitted payloads.
Telemetry records metadata only, not submitted content.
Submitted payloads are not used for training.
Submitted payloads are not reviewed by humans.
This skill does not target sensitive data.
The response may contain submitted or transformed content.

Your responsibility

Squillify does not determine whether submitted content is sensitive. Your application is responsible for deciding what data it is allowed to submit. Your application is responsible for securing the response.

Read the Microskill Data Handling Policy

Input schema

Field	Type	Required	Description
url	string	Yes	Required. The URL whose query is classified, up to 8192 UTF-8 bytes.
profile	string	No	Must be seo.tracking.parameters@1 when sent. Omit it and we use that bundled profile.
additionalNames	array	No	Extra query names treated as tracking, matched case-insensitively. Omit it and only the bundled names plus the utm_ prefix are tracking.

Output schema

Field	Type	Required	Description
original	string	Yes	The url string you sent, unchanged.
profile	string	Yes	Effective tracking profile, always seo.tracking.parameters@1 today.
trackingParameters	array	Yes	Query pairs classified as tracking, in original order, each with name, value, and valuePresent.
nonTrackingParameters	array	Yes	Remaining query pairs in original order, same object shape as trackingParameters.
cleanCandidate	string	Yes	A copy of the submitted URL with only tracking pairs removed. Host case, path, fragment, and unknown parameters stay.
changed	boolean	Yes	True when cleanCandidate differs from original.

API contract

POST /v1/execute

curl

curl -sS -X POST "$BASE/v1/execute" -H "Authorization: Bearer $KEY" -H 'Content-Type: application/json' -d '{"skillKey":"seo.detect_tracking_parameters","input":{"url":"https://www.example.com/blog/My-Article?utm_source=newsletter&id=7#top"}}'

Integrations

TypeScript SDK

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

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

const { output } = await sq.execute("seo.detect_tracking_parameters", {"url":"https://www.example.com/blog/My-Article?utm_source=newsletter&id=7#top"});

Errors

Code	HTTP	Retryable	Description
VALIDATION_ERROR	400	No	The request payload failed schema validation.
UNAUTHORIZED	401	No	Missing or invalid API key.
SKILL_NOT_ACCESSIBLE	403	No	The API key is not granted access to this skill.
SKILL_NOT_AVAILABLE_FOR_PLAN	403	No	This skill is not included in your current plan.
PLAN_ELIGIBILITY_UNAVAILABLE	503	Yes	Plan eligibility could not be decided. Retry after backoff.
SKILL_NOT_FOUND	404	No	The requested skill or version does not exist.
TENANT_RATE_LIMITED	429	Yes	Request rate limit exceeded. Retry after backoff.
QUOTA_EXCEEDED	429	Yes	Plan quota exhausted. Retryable once the quota period resets.
EXECUTION_TIMEOUT	504	Yes	Execution exceeded the allowed time budget.
SEO_INVALID_URL	400	No	The request payload failed this skill's input validation.
SEO_INPUT_TOO_LARGE	429	No	A size, quota, rate, or time limit was exceeded.

Other limits

Limit	Value
Recommended inline bytes	32 KiB

Limitations

Does not fetch a URL, resolve DNS, or run a browser
Does not predict ranking, choose a winner, or claim live index status
Does not fetch, and does not drop unknown parameters
Following the URL to confirm the campaign
Dropping every query parameter you do not recognise

How to call

POST /v1/execute (requires authentication)

Request bodyjson

{
  "skillKey": "seo.detect_tracking_parameters",
  "input": {
    "url": "https://www.example.com/blog/My-Article?utm_source=newsletter&id=7#top"
  }
}

Examples

Primary business path

Inputjson

{
  "url": "https://www.example.com/blog/My-Article?utm_source=newsletter&id=7#top"
}

Expected outputjson

{
  "profile": "seo.tracking.parameters@1",
  "nonTrackingParameters": [
    {
      "name": "id",
      "value": "7",
      "valuePresent": true
    }
  ],
  "changed": true,
  "original": "https://www.example.com/blog/My-Article?utm_source=newsletter&id=7#top",
  "cleanCandidate": "https://www.example.com/blog/My-Article?id=7#top",
  "trackingParameters": [
    {
      "name": "utm_source",
      "value": "newsletter",
      "valuePresent": true
    }
  ]
}

Tip

First realistic scenario for this skill.

Boundary or option path