Sign Up to Our Newsletter: Better CTAs and a Simpler Form

Key takeaways

• The sentence above the button does most of the work. Readers skip a signup box when it doesn't say what arrives, how often, and why it's worth an inbox slot.
• The button should finish that sentence in the reader's voice. Send me the Friday brief beats Subscribe because it repeats the promise at the moment of the click.
• One field is the default. Every extra field needs a job you'll use in the next three emails, or it goes.
• Consent is part of the copy, not the legal footer. A plain unticked checkbox line and a record of when someone agreed protect you in the EU and cost nothing elsewhere.
• What happens after submit decides whether the signup sticks. A confirmation page that sets expectations turns a form entry into an opened first email.

Most advice about the phrase sign up to our newsletter focuses on the button, swapping Subscribe for Count me in or Join the club. That's the least important word on the form. People don't ignore a signup box because the button is dull; they ignore it because nothing on it tells them what they'd be agreeing to receive.

So this guide works from the top of the box down: the promise, then the button, then the fields, consent and the page that follows. At the end there's a table of 15 promise-and-button pairs you can adapt, sorted by the kind of newsletter you send.

Why "sign up to our newsletter" gets ignored

The phrase asks for something (your email) and offers a category (a newsletter) instead of a thing. Readers have learned what that category usually means: irregular sends, company news nobody asked for, and a discount code they didn't want. A recent r/PetPeeves thread about websites that push newsletter signups, with more than ten replies, is a fair summary of that reputation.

The same logic shows up from the business side. In an r/smallbusiness discussion about where the profit is in "sign up for my free" offers, replies describe the signup as a lead magnet: it works when the free thing is specific enough to attract the right reader. A newsletter is a lead magnet that repeats, so it needs the same specificity every other offer needs.

How to write a newsletter signup people finish

Six steps, in the order a reader experiences the box. The first two carry most of the weight, so they get the most space.

Step 1: Write the promise line first

Before touching the button, write one sentence that answers three questions: what arrives, how often, and who it's for. A useful template:

[Specific content] every [interval], for [reader].

The interval matters more than most teams expect. Stating it ("every Friday", "twice a month") lowers the reader's fear of a daily blast, and it gives you a commitment you can keep. If you can't name an interval yet, you're not ready to collect addresses.

Add one line of proof if you have it: a sample issue link, the number of past issues, or a line from a reader reply. Skip subscriber counts unless they're large enough to matter to your audience; "Join 312 others" can read as small.

Step 2: Make the button finish the sentence

Read your promise line, then write the button as the reader's answer to it. First person usually works: Send me the Friday brief, Get the Tuesday tip, Add me to the job alerts. The button repeats the promise at the moment of the click, which is when doubt is highest.

A few rules that hold across newsletter types:

• Name the thing. Send me the checklist is clearer than Submit, and Get the brief is clearer than Sign up.
• Keep it under five words. Longer buttons wrap on mobile and look like body text.
• Avoid fake urgency. Only 5 spots left on a newsletter is a lie readers recognise, and it makes the next email less trustworthy.
• Match the tone of the site. Count me in fits a hobby community; it jars on a law firm's client update, where Receive the monthly update is fine.

If a colleague insists on Subscribe, keep it and make the promise line specific. A plain button under a sharp promise beats a clever button under a vague one.

Step 3: Ask for the email address and stop

Each field you add is a reason to leave. The default for a newsletter is one field: email. Add a second only if you'll use it in the next three emails:

• First name if you personalise the greeting. If you don't, the field is decoration.
• One optional choice (for example, Product updates or Industry news) if you send two different newsletters and want to route people to the right one.

Company size, job title and phone number belong in a sales form, not a newsletter box. If sales wants them, collect them later through a reply or a separate form tied to a real offer. Our guide to lead capture software covers when a longer form earns its length.

Step 4: Put consent in plain words and keep a record

Consent rules differ by market, so write the box for the strictest audience you serve:

• EU and UK readers: consent has to be freely given, specific and informed, and you must be able to show it was given (GDPR Article 7). Pre-ticked boxes don't count as consent.
• US readers: the FTC's CAN-SPAM compliance guide doesn't require opt-in, but every email needs a working unsubscribe and a valid postal address.
• Gmail and Yahoo inboxes: bulk senders need one-click unsubscribe and authenticated sending (Google's sender guidelines).

A consent line that reads like copy, not legalese: "I'd like the Friday brief by email. I can unsubscribe with one click in any issue." Link your privacy notice next to it. Behind the scenes, store when and where each person signed up and what text they saw. For a deeper look at the EU side, see our overview of GDPR compliance for US companies.

Double opt-in (a confirmation email the reader has to click) isn't legally required everywhere, but it keeps typo addresses and bot signups off your list, and it gives you a timestamped confirmation for your consent record.

Step 5: Plan the page after submit

The confirmation page is the most-read page nobody writes. Put three things on it:

• What happens next ("Check your inbox for a confirmation link from brief@yourcompany.com").
• When the first issue arrives ("Your first brief lands this Friday").
• One optional next step, such as a link to the best past issue.

Then send a welcome email within minutes. It should restate the promise line, show the sender name they'll see in future, and ask one easy question they can reply to. Replies help deliverability and tell you what readers want.

Step 6: Place the box where the reader already agrees with you

The end of a useful article converts better than a pop-up at second three, because the reader has just seen a sample of what you'd send. Good spots, roughly in order:

• End of articles, with a promise line tied to the topic they just read.
• A dedicated signup page you can link from social posts and email signatures.
• The footer, as a quiet fallback.

Pop-ups can work, but set them to trigger on exit or after meaningful scroll, and never block content on mobile.

15 newsletter signup CTAs to adapt

Each row pairs a promise line with a button that finishes it. Swap in your own interval and topic.

Notice what's missing: no row says newsletter. The reader cares about the specials, the roles or the changelog; the format is your concern.

Tools that help

You need two pieces: a form that collects the address and consent, and a sender that delivers the emails and handles unsubscribes. That split is where most setups get stuck, as in an r/webdev thread from a developer asked to add a newsletter signup to a company site, where the ten-plus replies weigh form tools against full email platforms. Dedicated email platforms bundle both and fit best once your list is large or you need landing pages and A/B testing on sends; our roundup of email marketing tools compares the main options. Standalone form builders give you more control over the form itself, covered in our guide to online form creators, with separate breakdowns of Google Forms alternatives and Typeform alternatives if you're replacing one of those.

meetergo is a scheduling and customer workspace used across sales, consulting, recruiting and service teams, and its form builder is where the signup side fits. Forms are included on the free plan, run on EU servers, and submissions land on the contact record rather than in a separate spreadsheet.

One-field forms with conditional logic

Build the email-only box first, then add an optional interest choice with conditional logic if you run more than one newsletter. The same builder handles longer routing forms when a signup should lead to a booking.

Tags written on submit

A form can write tags to the contact when it's submitted, so the signup source and the topic someone chose are stored with them. That's the record you'll want in Step 4.

Newsletter app (beta)

The meetergo Newsletter app is in beta and switched on per workspace on request. It sends campaigns through your own SMTP mailbox, checks each contact's consent at send time, adds one-click unsubscribe headers, and can start a welcome sequence when a form tag is written.

The honest limit: because the app sends from your own mailbox, it applies an hourly sending limit (200 per hour by default) and caps a campaign at 20,000 contacts. If your list is larger or you need send-time A/B testing, a dedicated email platform fits better, and a meetergo form can still sit in front of it.

Common mistakes

Promising "news" when you mean promotions. If most issues will be offers, say so: Weekly deals, every Thursday. Readers forgive promotions; they don't forgive a bait and switch.

Pre-ticking the consent box. It inflates the list and invalidates the consent for EU readers. It also fills your list with people who never meant to join.

Asking for fields you never use. A job-title field that doesn't change a single email is friction with no return.

Leaving the confirmation page as "Thanks!". Without a sender name and a first-issue date, the confirmation email lands in spam or goes unopened.

Launching the box before the first issue exists. Write two issues first. If you can't, the interval in your promise line is wrong.

If you'd like to build the one-field form from this guide, you can create a signup form on meetergo's free plan in a few minutes. No credit card required.

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

Sarah NowakManaging Director · Intro call · 30 min09:0010:3014:00

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

FAQs

Is it "sign up to" or "sign up for" a newsletter?
Both are common. "Sign up for our newsletter" is more frequent in American English and "sign up to our newsletter" in British English. On a button, you can skip the question entirely by naming what the reader gets.

What's a good alternative to "Subscribe"?
A first-person button that repeats the promise line, such as Send me the Friday brief or Get the job alerts. Keep it under five words.

How many fields should a newsletter form have?
One, the email address. Add a first name only if you personalise emails, and an interest choice only if you send more than one newsletter.

Do I need double opt-in?
It isn't legally required in every market, but it's standard practice in Germany and keeps fake and mistyped addresses off your list. Whatever you choose, keep a record of when and how each person agreed.

Should I offer an incentive for signing up?
A checklist or template related to the newsletter topic helps, as long as the newsletter itself is still described. A discount attracts discount hunters, which is fine for e-commerce and a poor fit for B2B content.

Where should the signup form go on a website?
At the end of your most-read articles first, then on a dedicated signup page you can share, then in the footer. Test a pop-up only after the static placements are working.