← All articles

Audience growth

How to measure social posts by newsletter signups, not just clicks

Tag the links you share, define a confirmed signup as the outcome, and report each social post from visit to confirmed subscriber, with a worked example and the attribution choices that change the answer.

By Ferryman··6 min read

A click, a submission, and a subscriber are three different events

Most newsletter tools and analytics setups can record several moments in a signup, and they are easy to confuse. A button click means someone pressed Subscribe or opened a form. A form submission means an address was sent. A confirmed subscription means the address is real and the person said yes, for example by clicking a double opt-in email.

Each step loses people, and some steps add noise: typos, throwaway addresses, bots, people who never open the confirmation email. If a post is judged on clicks or submissions, a post that attracts curious tappers can look better than one that brings fewer, real readers. Pick the confirmed subscription as the outcome, and keep the earlier steps as diagnostics.

EventWhat it provesWhat it does not prove
Link click on the social postSomeone left the app toward your pageThat the page loaded or that they read it
Landing page visit (tagged)A session arrived with your campaign tagsInterest in subscribing
Subscribe click or form viewThe visitor reached the formThat an address was sent
Form submittedAn address was sentThat it is real, or that the person confirmed
Subscription confirmedA reachable reader opted inThat they will open the next issue

Record the confirmed signup as your outcome event

Fire the outcome where confirmation actually happens. With double opt-in, that is the confirmation page the email link opens, or a webhook from your newsletter tool, not the thank-you page after the form. In Google Analytics, send it as an event and mark it as a key event so it appears next to sessions in acquisition reports. Give it a plain name, such as newsletter_confirmed, and keep the form submission as its own event so you can see the gap between the two.

Test the journey before trusting the report. Use a tagged link, subscribe with an address you control, confirm it, and check that each event appears once with the campaign values attached. Repeat it on a phone from inside the social app, since in-app browsers and confirmation emails opened on another device are where the chain most often breaks.

Illustrative example: two posts, two different winners

These numbers are invented to show the method; they are not customer data or a benchmark. One creator shares the same newsletter offer in two posts in the same week, each with its own utm_content value, and reads the funnel 7 days after each post.

Step (illustrative)Short video, broad hookText post, specific tip
Tagged visits400120
Form submitted2818
Confirmed1215
Confirmed per 100 visits312.5

What the example shows

Judged by clicks, the video wins by more than three to one. Judged by submissions, it still wins. Judged by confirmed subscribers, the text post brought more readers from fewer than a third of the visits. Both readings are correct; only one answers the question 'which post grew the newsletter?'

The gap between submitted and confirmed is a signal in itself. When it is wide for one source, look at that path: is the confirmation email arriving, are people subscribing from inside an in-app browser and then never seeing their inbox, are bots submitting the form? Fix the leak before deciding the post was weak.

With two posts and a few dozen signups, treat the result as a hint, not a finding. Repeat the comparison over several weeks with the same rules before changing what you publish.

Choose first touch or last click before comparing

People rarely subscribe on the first visit. Someone may tap a video on Monday and come back through a text post on Thursday. Analytics tools assign the credit under a model, and different reports can answer differently: a first-user view credits the visit that brought the person in, while session-scoped reports credit the session in which the event happened. Neither proves that the post caused the signup.

We see this in Ferryman's own signup records, which keep the first tagged visit by design: a person who first arrived from one campaign and signed up days later from another is stored under the first one. Both views are useful, but they produce different rankings. Write down which one a report uses, and do not mix them in the same comparison.

Write down what you cannot see

Every setup has gaps, and naming them keeps the numbers honest. Visitors who decline analytics consent may not appear at all. A signup form hosted on your newsletter provider's domain needs cross-domain measurement, or the campaign tags stop at your site. Some apps strip or hide referrers, so untagged links show up as direct traffic. Someone who reads the post, then types your site's address later, carries no tags.

Note these limits next to the report, with the date you last tested the journey. A smaller number you can explain is more useful than a larger one you cannot.

Where Ferryman fits

Ferryman publishes the same post, with your tagged links, to the platforms you choose, and its analytics view shows supported views, likes, replies and reposts for posts published through Ferryman, on paid plans. That covers the exposure side of the funnel.

Ferryman does not see your website visits, form submissions or newsletter confirmations. Those come from your analytics and your newsletter tool, joined by the campaign tags you set.

Sources & further reading

Written by Ferryman. Sources checked Nov 19, 2026. Platform rules can change; consult the linked documentation for current requirements.