Ghost on your landing pages
Ghost is built for publishers who want to own their audience, and paid traffic is how many of them grow it. But a Ghost theme isn't a test lab. When you're paying for every reader, you want a page that matches the ad, an A/B test running on it, your pixel firing on the signup and the campaign recorded with each new member.
LanderLab is that page. Each signup reaches Ghost as a member through Zapier, from LanderLab's New Lead trigger, or through a Make scenario fed by the page's webhook, with the campaign as a label and the page and variant in the member's note. Both tools have a Create Member action for Ghost. The automation tool holds your Ghost Admin API key, which is where Ghost wants it: its Admin API is meant for servers, not pages. If you'd rather skip the scenario, Ghost's own embeddable signup form can sit on a LanderLab page instead.
It fits niche media brands, independent journalists and B2B publications buying readers on Meta, LinkedIn or native ads.
Grow a Ghost publication with paid traffic you can measure
Organic growth on Ghost is slow and steady. Paid growth can be fast, but only if you measure it per page and per campaign. LanderLab gives each signup a record of where it came from: the UTMs from the ad's URL, the page, the A/B variant and the time of the submit. That's the data you need to decide which ad sets deserve more budget.
Your pixel fires on the signup on your own page, so the ad platform learns from real member signups instead of clicks.
Labels and notes that keep the campaign on every Ghost member
A Ghost member has no UTM fields, but it has labels and a note, and that's enough. Map the campaign or the source to a label and you can filter members by it in Ghost, or send an issue to one label. Put the variant and the page URL in the note so the source is on the record when you look a reader up.
Months later, when you want to know whether the LinkedIn readers or the Meta readers stayed and upgraded, the answer is already on the members.
Why Make or Zapier sits between the page and Ghost
Ghost's Admin API signs each request with a short-lived token made from your Admin API key, and Ghost is clear that the key must be kept private. That rules out putting it in a page or a fixed request header. Make's Ghost app and Zapier's Ghost integration both hold the key safely and create the member for you, and LanderLab has a documented Make setup.
You also get the automation tool's extras: Make's History tab shows every run, and you can add steps, such as a Slack message for each new paid member.
Or use Ghost's embeddable signup form on a LanderLab page
Ghost builds an embeddable signup form with labels at signup. Placed on a LanderLab page, it lets the visitor join through Ghost directly, with no scenario to run. The trade-off is attribution: the submit happens in Ghost's form, so LanderLab doesn't store it as a lead and can't count it as the page's conversion. It suits a quick test; the Make route suits scaling spend.
