Track every campaign
See which sources, mediums, and content blocks deserve attention.
stripe
Built for Stripe
Payment Link UTM Builder
Add UTMs and QR codes to Stripe Payment Links.
Install plugin- ✓Track which campaigns and channels drive payments.
- ✓Generate a QR code preview for invoices, posters, and emails.
- ✓Keep every Stripe Payment Link clean, tagged, and copy-ready.
Create tagged Payment Link
Select Payment LinkStarter Plan - $29/month
UTM Parameters
utm_source
newsletter
utm_term
pricing_page
utm_medium
email
utm_content
cta_button
utm_campaign
spring_launch
https://buy.stripe.com/14k3cN7rD4gY3a8cMN?utm_source=newsletter&utm_campaign=spring_launch
QR Code
9:415G
Preview
Starter Plan
$29.00
per month
Pay now
Secure checkout by Stripe
QR codes in one click
Add QR code previews for receipts, flyers, emails, and events.
Copy-ready links
Keep Payment Links short to manage and ready for campaign handoff.
Built for Stripe
Works around Stripe Payment Links so campaign work stays focused.
How it works
Create. Tag. Track.
Select the product or plan your team is already selling through Stripe.
Set source, medium, campaign, term, and content fields in one tidy view.
Copy the tracked URL or use the QR preview when the campaign goes offline.
How do UTM tags work with Stripe Payment Links?
A tagged Stripe Payment Link is the original checkout URL plus supported UTM query parameters that describe the campaign source, medium, name, term, or content. The builder assembles that URL and a matching QR preview; it does not change the Payment Link's product, price, or checkout settings.
Build and verify the campaign URL
Choose the intended Payment Link, enter only the campaign fields your reporting plan uses, then inspect the complete generated URL. Copy that URL for digital channels or encode the same destination in a QR code. Before launch, open the result in a test browser, complete a test-mode payment where appropriate, and verify the redirect and analytics destination.
Stripe supports utm_source, utm_medium, utm_campaign, utm_term, and utm_content. Its official
Payment Link URL-parameter guide
explains when those values are returned after checkout.
Permissions, privacy, and link security
Access is currently request-based. If a released build lists existing Payment Links, its Stripe installation screen must show the required read permission; that screen is the final authority for scope. Generating a tagged URL and QR code should not require changing the underlying Payment Link.
Query strings are visible to recipients, browsers, analytics tools, screenshots, and server logs. Never place names, emails, internal customer IDs, API keys, tokens, or other secrets in UTM fields. Share each link only with its intended audience and review the Workestic Privacy Policy before requesting access.
Role-based campaign uses
- Growth teams can standardize source, medium, campaign, term, and creative naming.
- Partnership and event teams can create QR destinations tied to a specific placement.
- Revenue operations can review naming conventions and reconcile tags with downstream reports.
- Support teams can verify which public link was shared without receiving edit access to checkout configuration.
The Stripe Payment Link campaign guide covers handoff and measurement in more detail.
Limits and edge cases
Stripe limits UTM values to 150 characters and accepts alphanumeric characters, dashes, and underscores; invalid values can be discarded without breaking checkout. To receive UTM values in the post-payment redirect URL, the Payment Link must use redirect confirmation behavior. A QR scan or page visit is not proof of payment.
Existing query parameters, URL encoding, redirects, link shorteners, analytics consent, and offline camera behavior can affect measurement. Keep an untagged source link, test every final destination, and use Stripe payment or Checkout Session records—not UTM tags alone—as the source of truth for completed payments.