Skip to main content

Creators and newsletters

Know whether the newsletter, YouTube or your blog sold the course.

You sell a course, an ebook or templates through Stripe, Lemon Squeezy or Paddle. Vero ties each sale to the source that brought the buyer, without cookies.

The problem

  • Your checkout tells you who bought, not whether the newsletter, a video or a post sent them.
  • Clicks from email usually arrive with no referrer, so your newsletter looks like Direct traffic.
  • A launch email and a podcast mention land on the same day, and the sales chart cannot tell them apart.

How Vero helps

The sale knows where it came from

The checkout module adds the visit to your Stripe Payment Links and Lemon Squeezy checkout links at the click; with Paddle you pass it in the checkout’s custom data. The provider’s signed webhook brings it back, and refunds come off the source that sold.

One source per channel

Build every link you share with the UTM builder: the newsletter as utm_source, the issue or episode as utm_campaign. Email clicks then arrive under the newsletter’s name instead of Direct, with the revenue they brought, and revenue by campaign shows which issue or episode sold.

Money per channel

Read revenue by source, by campaign, by referrer and by channel to see which channel sold and which only got read. Anomaly alerts email you when visits, or sales on a site that sells most days, fall well below a typical day.

What you use

  • Checkout module for Stripe Payment Links and Lemon Squeezy
  • Revenue by UTM source and campaign, referrer, channel and entry page
  • UTM link builder for every issue and post
  • Refunds subtracted from the source that sold

Worked example from the public demo

What a signup and a sponsorship are worth

The public demo is a fictional SaaS in its launch week, but its goals read like a creator’s: newsletter signups, a post people read, a free download, and one paid newsletter placement.

  1. Signups as a goal

    The newsletter goal counted 934 signups, 5.7% of the week’s 16,491 sessions, on the same screen as trial_started and purchase. The downloads module also counted 142 downloads of integration-guide.pdf, with no extra code.

  2. The post people read, and wait for

    /blog/cookie-free-analytics-2026 drew 2,841 pageviews, but its LCP at p75 is 3,410 ms against 812 ms for the site. The post that brings readers is the slowest page in the demo, so that is where the first fix goes.

  3. A sponsorship that lost money

    The SaaS paid €900 for a slot in someone else’s newsletter. Tagged as spring_launch, it sent 743 visits and €482 in sales: -€418 after the spend. Without the tag, those clicks would have landed in Direct, because an email client sends no referrer.

If you sell sponsorships, this is the screen your sponsor will read. If you buy one, tag the link and enter the spend first, so the placement answers in money, not in opens.

Figures from the public demo: launch week for a fictional SaaS, not Vero’s data or a customer’s. Open this screen in the demo

Frequently asked

Do I need a developer to connect Lemon Squeezy?

No. Add one webhook in Lemon Squeezy pointing to Vero, paste its signing secret into Vero’s settings, then turn on the tracker’s checkout module: a click on a checkout link carries the visit, and the signed webhook brings it back with the sale.

Does Vero track email opens?

No. Vero measures your own site: the visit that arrives from the email and what it buys. Opens and clicks inside the email stay in your email tool. Tag your links so those visits arrive under the newsletter’s name.

What counts as revenue?

What was charged, without tax, less refunds, before your payment provider’s fees. The same definition for Stripe, Lemon Squeezy and Paddle.

More use cases

See which channel sells

By joining you agree to receive launch updates and accept our Privacy Policy.

See the demo