Connect an AI Assistant to Your UTM Links (inPIPE UTM API Skill) #

Audience: site owners using inPIPE by Seresa who want an AI assistant (e.g. Claude) or an automation to create and manage UTM tracking links for them.Requires: UTM Processing enabled · UTM API Access turned on · an API key.

Tired of hand-building UTM links one by one? Let your AI assistant do it. inPIPE wraps your UTM Generator in a secure, key-protected API — and the skill file below teaches your assistant how to use it. Download it, paste in your key, and just ask: “Build me a UTM link for the summer sale.” It creates, looks up, edits, and removes your links for you — safely, within your rate and storage limits.

What you’ll set up #

A UTM link is a normal URL with tracking tags on the end (?utm_source=google&utm_medium=cpc&…) that tell your analytics exactly where each visitor came from — so campaign traffic stops landing in the “Direct / unknown” pile. inPIPE’s UTM Generator builds and saves these links for you; this guide connects that Generator to your AI assistant so it can do the work on request:

• ⚡ Build a whole campaign in seconds from a single prompt.
• 🎯 Consistent naming on every link, automatically.
• 🔁 Reuse instead of duplicate — it checks for existing links first.
• 🤖 No WordPress login — create, edit, and remove links from your chat.

Three quick steps: download the skill → paste in your key → start asking. Want the full reference instead? See the UTM API documentation.

1. Download the skill #

Download the file, then add it to your AI assistant. Most assistants (Claude, ChatGPT, Gemini) accept a Markdown file like this — attach it to a chat or project, or add it as a skill / knowledge file.

⬇️ Download the inPIPE UTM API skill (.zip — unzip to get inpipe-utm-api-skill.md)

2. Get your API key #

1. In WordPress, go to inPIPE → Settings → UTM Processing Settings.
2. Make sure UTM Processing is ON, then open the UTM API Access panel.
3. Turn on Enable UTM API Access, then the part you need:
   • Read API — list and status only.
   • Update API — create, edit, and delete links (this key can read too).
4. Click the copy icon next to the key you want and copy it.
   • The Read API key has ro in it; the Update API key has rw.

Tip: Give the assistant the Update API (rw) key only if you want it to create or change links. For look-ups only, use the Read API (ro) key.

Security: Regenerate your keys every few months — and right away if a key may have leaked. Regenerating turns off the old key immediately.

3. Configure the skill #

Open the downloaded file and fill in the single config block near the top — nothing else:

inpipe_utm_api:
  site_url: "https://your-site.com"       # your WordPress site root (with https)
  api_key:  "inpipe_utm_rw_xxxxxxxx..."   # the key you copied above

That’s it. The assistant derives everything else (request URL, auth header, scope) from those two values.

HTTPS is required. The API refuses plain http:// requests. If your site is behind an SSL proxy (e.g. Cloudflare), contact support to enable proxy trust.

4. Use it #

Ask your assistant in plain language, for example:

• “Create a UTM link for https://your-site.com/blog — source google, medium cpc, campaign summer_sale.”
• “List my UTM links for the summer_sale campaign.”
• “Change the source on code u4gf2 to bing.”
• “Delete the link with code u4gf2.”

The assistant checks for duplicates before creating, respects your rate limits, and hands you back the finished link plus its code for future edits.

5. Good to know #

• Two keys, least privilege — share the Read API key when something just needs to look.
• Limits — sensible per-second/minute/hour caps apply automatically (shared-hosting-safe); a 10,000-link storage cap protects your site.
• Delete is permanent — there’s no trash or undo.
• Turn it off anytime — flip the UTM API Access toggle (or UTM Processing) off and every key stops working instantly; turn it back on and your keys/settings return.

Need help? See the full UTM API documentation or contact support with your site URL and the response code you’re seeing — never share your full key.