Turn blog readers into email subscribers
Posts get read. A bar asks once. The report says what to write next.
A reader finishes a post and leaves. The blog, the popup, the list and the report already share one script tag. What turns them into a loop is a handful of settings: whether the widget runs on the blog, which pages the bar may appear on, and which goal the report counts. This is the whole loop, stop by stop, with two things to try and what a month costs.
A blog on its own address.
The widget still comes along.
A Builderify blog is a separate site. It is served from a free address like yourname.builderify.blog, or from a subdomain of your own domain, not from the pages your script tag is on. So the connection to everything else is one switch. With Builderify widget on, the same snippet your site uses is added to every page of the blog, and the bubble, the popups and the cookie notice you have set up run on the posts too.
- The switch
- Builderify widget sits in the blog’s General settings and is on for a new blog. Turn it off and the snippet is taken out of the blog’s pages, popups included.
- The post
- A post is a draft until you publish it, then it is live at
/posts/followed by its slug. That fixed path is what a popup’s page rule can aim at. - The address
- Every blog starts on a free
builderify.blogaddress, and can move to your own domain later. A subdomain of a domain you own, likeblog.acme.co, keeps the posts under your brand. - The count
- Statistics counts a post once per reader per day and ranks your Top posts. That is a view count. It does not know who subscribed.
Ask once, low on the page.
Only on posts.
The template New Posts by Email is a slim bar that slides up from the bottom with a one-line signup. It does not dim the page or cover the text, which is why it suits a reader in the middle of a post. Two settings decide where it appears: how far the reader has scrolled, and which pages it may appear on.
- The template
- Find it in the popup gallery under Lead capture: a heading, one email field, a Subscribe button and a note. Every word is yours to change.
- The moment
- Under Triggers choose Scroll and set Show after scrolling. The percentage is of the distance the page can scroll. Leave it at 0 and the bar waits for 50%.
- Only posts
- Under Audience switch on Page Rules, then choose Include, contains and
/posts/. The rule reads the whole address, so it keeps the bar off the home page and off the post list, whose address ends at/posts. - One ask
- Closing the bar hides it for that browsing session. A signup hides it for a year in that browser. A reader who does neither sees it again on the next post.
A subscriber is a person on a list.
Open one to see what they read.
Everyone who subscribes lands on the list you chose, with a note of the popup that captured them. What they read is not on the lead: it lives on the visit, which is what User Journey keeps, and the lead links to it. Open any subscriber and a panel called Their journey names the pages they opened, newest first. On a blog, those are your posts.
- The list
- Everyone who joined sits on Blog subscribers. The submission is always stored with the popup as well; the list is what lets you write to them.
- The reading
- Latest pages shows up to eight pages by title, with how long ago. First came from says how they found you: a search engine, another site, a tagged link.
- The match
- A lead is matched to the visitor they signed up as, or to one who identified with the same email. If that visit was never recorded, the panel is left out.
- The email
- The bar’s own words promise one email per new post. Builderify does not send it by itself: write it as a Broadcast campaign to this list when a post goes live, and change the words if you will not. For a welcome that sends itself, add a Sequence.
Two panels name a post.
Often not the same one.
When someone subscribes, the goal Leaves their email is counted for the visit they are in. The goal’s own report then answers two questions with two panels, and on a blog both answers are posts: the one the visit began on, and the one the signup happened on.
- Started
- Where converting visits started counts the visits that ended in a signup by the page each one began on, with its share. It is the page that visit began on, not the page where the reader first met you.
- Reached
- Where it was reached counts the page each signup happened on: the post the bar was showing on.
- Views
- In the blog’s Statistics, Top posts ranks posts by views. Put the two lists side by side. Views are counted when a page is served and visits when your script runs, so read the gap as a hint, not as a rate.
- Reading
- Optional: add the goal template Read an article and change its pattern from
/blog/*to/posts/*. It counts a post as read when the visitor scrolls three quarters of it. - Then
- Write more like the posts at the top, and rewrite the ask on one that is read and not subscribed to. That is the loop.
Two things to try.
When the bar appears, and who gets the credit.
Both tools are built from rules the product applies. The first is the scroll trigger: set a percentage, scroll the sample post and see when the bar slides up. The second is the report: choose where a reader starts and where they subscribe, and see which post each panel names. They are models of those rules, not the product.
The bar waits for 50% of the distance the page can scroll.
A few screens long.
How to pick a blog theme
Waiting. The reader has scrolled 0% of the distance, and the bar needs 50%.
Posts have no rate.
Readers and emails do.
Page loads with the widget on them are 10 credits per 1,000, and on a blog every post a reader opens is one. A new person who joins a list is 1 credit, and only once. Each tracked visitor journey is 0.1 credits, and each recipient of a campaign email is 0.5 credits. The blog, its posts, the popup, the goal and the reports have no rate of their own. Every account gets 250 free credits a month, and packs start at $9.
Every post, list page and home page a reader opens with the widget on it.
Each new person who joins a list through the bar.
Each tracked visitor journey is one unit.
One recipient on one campaign email: 400 subscribers and two campaigns is 800.
- Page loads 10 credits per 1,000 200
- New subscribers 1 credit per new person, once 120
- Visitor journeys 0.1 credits per tracked visitor 600
- Campaign emails 0.5 credits per recipient 400
It fits inside the free credits, with -1,070 to spare.
Over by 1,070 credits. One Growth pack (5,000 credits, $29) covers that for about 4 months at this size. Purchased credits never expire.
- A blog is often the busiest part of a site, so page loads are usually the biggest line. The Builderify widget switch is what puts the widget, and the meter, on the posts.
- The email line is only what you send. The bar collects subscribers and sends nothing by itself.
- If credits run out, the widget stops loading on every post, the bar included. The cookie notice, if you use one, keeps running.
- A person who is already on your lists, or who joins a second list, is not charged as a new person again.
Six ways the loop stalls,
and the setting behind each.
- Cause
- The snippet only reaches the blog while Builderify widget is on in its General settings. And if you locked your widget to certain domains with Allowed Domains, the blog’s address has to be on that list or under a domain on it:
acme.cocoversblog.acme.co, but notacme.builderify.blog. The widget is then refused there, and no popup loads. - Fix
- Check the switch first. Then either add the blog’s address to Allowed Domains in the widget settings, or move the blog to a subdomain of your own domain, where the list you already have covers it.
- Cause
- The scroll trigger is a share of the distance the page can scroll, so the same number lands in a different place on a long post and on a short one. A post that fits on the screen has no distance to scroll, and the bar never appears. And a setting of 0 is not read as 0: the snippet treats it as not set and waits for 50%.
- Fix
- Choose a number you meant, such as 40. For short posts use the Delay trigger instead, with a few seconds. The first tool above shows all three cases.
- Cause
- A page rule is checked against the whole address, and contains is a plain match.
/postsis inside/posts/pick-a-theme, but it is also the whole address of the post list. With Page Rules switched off, or no value saved, the bar is allowed everywhere on the blog. - Fix
- Use
/posts/, with the closing slash. Every post has it, and the home page, the post list, tags and categories do not. Make sure Page Rules is switched on and the rule is saved.
- Cause
- Both are right. Statistics counts a post when the page is served, once per reader per day. User Journey records a visit only when your script runs for a visitor who can be tracked, and one visit can span several posts: it ends after 30 minutes without a page view. Nothing new is recorded once your credits run out.
- Fix
- Use each for what it is. Statistics says what is read, and User Journey says what readers did next. Compare which posts rank highest in each, not the totals.
- Cause
- The bar’s own words, taken from the template, promise one email when you publish. Builderify keeps the person on the list and does not send that email by itself. The popup only collects the address.
- Fix
- When a post is live, write a Broadcast campaign and choose the list as its audience. Or give every new subscriber a welcome with a Sequence. Either way, change the bar’s words to promise only what you will send.
- Cause
- Where converting visits started credits the page the converting visit began on. A reader who found that post, left without subscribing and came back another day began a new visit somewhere else, and the signup was counted for that one. Where it was reached only names the page the signup happened on.
- Fix
- Open a few subscribers and read Latest pages: it lists everything they read, across visits. Read the two panels as where visits that convert begin and end, not as who introduced the reader.
Blog signups, before you ask.
Keep the Builderify widget switch on in your blog's General settings, so your popups run on its pages. Create a popup from the New Posts by Email template, set its trigger to Scroll and its page rule to contain /posts/, and switch on Save to a lead list. Then add a User Journey goal of the type Uses your widget and choose Leaves their email. That goal's report names the posts that start the visits that end in a signup.
Yes. Every blog has a Builderify widget switch under Settings, General, and it is on for a new blog. It adds the snippet your website uses to every blog page, so your popups, bubble and cookie notice run on the posts. If you locked your widget to certain domains with Allowed Domains, the blog's address has to be on that list or under a domain on it, or the widget will not load there.
No. The popup collects the address and keeps the person on a list, and writing to them is your step: send a campaign to that list from Broadcast when a post is live. A sequence can send a welcome email on its own to everyone who joins. The New Posts by Email template says one email when we publish something, so reword it if that is not what you will send.
Open the goal Leaves their email in User Journey. Where converting visits started lists the pages those visits began on, with their share, and Where it was reached lists the pages people subscribed on. Open any subscriber to see the posts they read under Their journey, newest first.
They count different things. Blog statistics counts a post when the page is served, once per reader per day. User Journey records a visit only when your script runs for a visitor who can be tracked, and it groups pages into visits that end after 30 minutes without a page view. Compare which posts rank highest in each rather than the totals.
The blog, its posts, the popup, the goal and the reports have no rate of their own. Page loads with the widget on them are 10 credits per 1,000, and on a blog every post a reader opens is one. A new person who joins a list is 1 credit, once, each tracked visitor journey is 0.1 credits and each campaign email is 0.5 credits per recipient. Every account gets 250 free credits a month, packs start at $9 and purchased credits never expire.
4 modules, in the order a visitor meets them.
- 01 · Hosted blog on your own subdomain Blogs Serves each post at its own address and loads your widget on it while the Builderify widget switch is on.
- 02 · Free popup builder Popups Slides the subscribe bar up on posts only, once the reader has scrolled, and files the email in a list.
- 03 · Lead capture and lead lists Leads Keeps the person on the list, and links to the posts they read.
- 04 · Visitor-level website analytics User Journey Counts each signup for the visit it happened in, and names the posts that start and end those visits.
Same script tag. A different job.
The lead line
Someone leaves their email. Then what?
Popups Leads Sequences User Journey Open this flowThe answer loop
A visitor asks something the bot cannot answer. Then what?
AI Chatbot Support Tickets Live Chat Callbacks Open this flowThe booking fork
Not every visitor should get the same calendar.
Quizzes Bookings Callbacks Sequences Open this flowThe page fork
A pricing page and a checkout need different doors.
Bubble Bookings Live Chat User Journey Open this flow
Stop losing the visitors
you already paid for.
More leads from the traffic you already have, and follow-up that sends itself. Free to start. No card, no monthly fee.