inPIPE by Seresa

= Can I use this plugin just to generate UTM parameter query strings? =\ Yes! The plugin allows you to easily generate UTM parameter query strings for your marketing campaigns. You can create both plain and coded UTM query strings with simple click options. If you only need to generate and use UTM parameters without decoding, you can do so without enabling the decoding feature. = Can I use plain UTM parameters instead of coded ones? =\ Yes! The plugin supports both plain and coded UTM parameters. If you don’t enable decoding, your standard UTM parameters will work as usual. If you want extra protection against ad blockers, you can enable decoding in the plugin settings. = How do I enable coded UTM decoding? =\ Go to Settings > WP inPIPE and turn on the option for Coded UTM Processing. When enabled, the plugin will detect and decode coded UTM query strings, replacing them with the full UTM parameters in the URL bar and pushing them to the dataLayer. By pushing decoded UTM parameters directly into the dataLayer, Web GTM can receive the data without requiring extra configurations to extract and manage UTM values. This simplifies tracking setup and ensures cleaner data in your analytics.

UTM API Access is a secure, key-protected REST API that lets external tools, scripts, and AI automations create, list, update, and delete your UTM links without using the dashboard. It exposes four server-to-server endpoints under /wp-json/inpipe/v1/ext/ — utm-generate, utm-list, utm-delete, and status. Full details, authentication, and code examples are in the inPIPE UTM API Documentation.

First make sure UTM Processing is enabled, then open the UTM API Access panel in the inPIPE settings. Turn on the master toggle to provision your two scoped keys — a read-only key (for utm-list and status) and a read-write key (also required for utm-generate and utm-delete). You can copy or regenerate the keys at any time from the panel.

Yes. Every request is served over HTTPS only and must carry a valid API key. The two keys are scoped (read-only vs. read-write) and stored encrypted at rest using libsodium, with the encryption key derived from your wp-config salts and never written to the database. The layer also applies per-operation rate limiting, per-site IP throttling, a same-site domain guard, and a storage cap. The endpoints are server-to-server only (browser CORS is suppressed).

Complete documentation — endpoint reference, request/response formats, authentication, rate limits, and examples — is available here: inPIPE UTM API Documentation