Blog · How-to

How to add UTM tags and QR codes to Stripe Payment Links

Short answer: start with a clean Stripe Payment Link, add a consistent set of UTM parameters, then generate a QR code from the final tracked URL. That gives every email, landing page, flyer, and event handout a link your analytics can recognize.

Stripe Payment Links are easy to share, but the default link does not explain where a sale came from. UTM parameters solve that by adding campaign context such as source, medium, campaign, term, and content. A QR code solves the offline side of the same problem: the exact tracked link can be scanned from a poster, invoice insert, booth sign, or printed receipt. Payment Link UTM Builder keeps those two tasks together so teams can create a tagged Stripe Payment Link and a matching QR preview without passing URLs through a spreadsheet.

What is a Stripe Payment Link UTM?

A UTM is a query parameter added to the end of a URL. For Stripe Payment Links, that means the original checkout URL stays the same, but campaign fields are appended after a question mark. Analytics tools can then group sessions and purchases by the fields you used.

Common UTM fields for Payment Links:

• utm_source: the place the click came from, such as newsletter or linkedin
• utm_medium: the channel type, such as email, social, qr, or partner
• utm_campaign: the campaign name, such as spring_launch
• utm_content: the creative or placement, such as hero_cta or booth_sign
• utm_term: an optional keyword, audience, or targeting label

Step 1: Choose the Payment Link

Start with the Stripe Payment Link that already points to the right product, price, and checkout settings. Do not create a new link for every channel unless the checkout itself needs to be different. For most campaigns, one Stripe Payment Link can support many tracked campaign URLs.

Step 2: Add consistent UTM tags

Consistency matters more than clever naming. Pick lowercase values, avoid spaces, and use the same source and medium names across campaigns. A tidy naming pattern makes it easier to compare email, partner, paid social, QR, and event traffic later.

Step 3: Generate a QR code from the final URL

Generate the QR code only after the UTMs are final. If the QR code points to an untagged Stripe Payment Link, offline traffic blends into direct or unknown traffic. If it points to the tagged URL, each scan carries the same campaign context as an online click.

For offline campaigns, use a dedicated medium like qr and a clear content value such as invoice_insert, poster, or event_badge. That keeps scans from different printed assets separate in reporting.

Step 4: Copy, test, and share

Before a campaign goes live, open the tracked Payment Link in a private browser window and confirm that checkout loads correctly. Then scan the QR code from a phone, not just from a desktop preview. This catches printing, contrast, and sizing issues before the link appears in public.

Common mistakes to avoid

• Using different names for the same channel, such as email and newsletter
• Adding spaces or mixed capitalization that split reports into duplicate rows
• Creating a QR code before the final UTM values are approved
• Reusing one QR code across campaigns that should be measured separately
• Shortening links in a way that strips or rewrites campaign parameters

Use one workflow for links and QR codes

A spreadsheet can work for a few URLs, but it is easy to lose track of which link produced which QR code. The safer workflow is to choose the Stripe Payment Link, enter the campaign fields, copy the tracked URL, and generate the QR preview in the same place.

Manual workflow: tracking Stripe Payment Links without a plugin

The manual version is workable for a tiny campaign: copy the Stripe Payment Link, paste it into a URL builder, decide the UTM values, test the final link, then paste that exact URL into a QR generator. The problem is not one link. The problem is keeping the naming system consistent when every channel, partner, and printed asset needs a slightly different URL.

Teams usually start losing signal when someone changes utm_medium from email to newsletter, or when a QR code is generated before the final campaign name is approved. A focused Stripe workflow should make the tracked URL and QR preview part of the same review step.

Where teams get stuck

• Campaign names drift between teams and make analytics reports harder to group.
• Offline scans are mixed with direct traffic because QR codes use untagged links.
• Old links stay in docs, emails, and slide decks after a campaign changes.
• Marketing has to ask a finance or ops teammate to confirm which Payment Link is safe to use.

Payment Link tracking checklist

• Use one naming convention for source, medium, campaign, term, and content.
• Generate the QR code only from the final tracked URL.
• Scan the QR code from a phone before printing or sending it.
• Keep related growth workflows close: promo code batches and localized prices.