Behind the page This page is me, Nathan, talking to the business owner. Families never see it. The funnel is Lanternhill's page; this is what runs it.
Behind the funnel:the ads, CRMand follow-upthat run it.
Meta ads, a Zapier route and a GoHighLevel pipeline, set up as one system for a funeral home or senior care community. Concept build for the Lanternhill template.
Behind the page This part is me, Nathan, talking to the business owner. Families never see it: everything above is Lanternhill's page, everything here is what runs it.
The stack, wired
Watch one leadmove throughthe whole stack.
Meta ads bring the visitor in, the page captures the answers, Zapier cleans and routes them, GoHighLevel runs the pipeline and follow-up, and the booked call goes back to Meta so the ads learn what a good lead looks like.
Meta adAd set per door, UTM tags and click ID keptWaiting
Landing pageThe answers, consent and one shared event IDWaiting
ZapierCatch, route by door, format, send to the CRMWaiting
Back to MetaLead and booked call sent by Conversions APIWaiting
Event logexample lead, planning ahead door
Meta Ad click on "Plan it once". utm_source meta, utm_campaign planning, click ID stored
Page Form submitted. Planning for: a parent. Leaning: cremation. Text consent: yes. event_id lh-7f3a
Pixel Lead fired in the browser with event_id lh-7f3a
Zapier Catch Hook, then Paths by door, then Formatter: phone to +1 format, names to title case
GoHighLevel Contact created, tags door-plan and parent, opportunity in Pre-need: New lead
Workflow Guide email sent, text sent because consent is yes, planner assigned
Conversions API Lead sent from the server with the same event_id, so Meta counts it once
Booked Call booked on the GoHighLevel calendar. Schedule event sent to Meta to optimize on booked calls
Meta ads
One campaign, an ad set per door, each linking straight to its door on the page
Pixel and Conversions API share one event ID, so a lead is counted once
Optimized on booked calls and tours, not on clicks or form starts
Plans funded by insurance run under Meta's financial products special ad category, which limits targeting
Zapier
Connects a page that lives outside the CRM: one Zap, a path per door
Phone numbers and names are cleaned before they reach the CRM
LeadConnector, GoHighLevel's Zapier app, writes each answer to its own field
Failed runs alert by email; Zap history is checked weekly
GoHighLevel
A pipeline per door, with stages that match how the team works
Workflows branch on consent and stop on a booking, a reply or an opt-out
Calendar booking moves the opportunity and sends the booked event to Meta
At-need contacts never enter a marketing workflow
Add-ons
What else plugs intoGoHighLevel.
Tap the ones your business needs and I'll set them up with the funnel. Each card says what it does for a funeral home or care community, and whether it's built into GoHighLevel or connects to it.
0 add-ons pickedTap a card to add it to your setup.
Built in means it ships with GoHighLevel. Connects means a native integration or a Marketplace app. Premium means it needs GoHighLevel's premium workflow actions. Plans and add-on fees vary by account. Sources: HighLevel integrations, SupplyGem's integration guide.
Want this funnelfor your business?
I set up the ads, the page, GoHighLevel and the Zaps together, then run test leads through every door before Meta spends anything.
Concept build showing how I wire it for a client. Meta, Zapier and GoHighLevel are trademarks of their owners; this page is not affiliated with them.
Behind the page again The ads, pipelines and follow-up a business owner pays for. A family on Lanternhill's site never sees this part.
Behind the funnel
Where the leads goafter they click.
The ads that send each visitor to the right door, the CRM pipeline every lead lands in, the follow-up that runs on its own, and the report the owner reads on Monday.
One rule for every door: nobody who just lost someone is ever shown an ad, a countdown or a sales sequence. At-need contacts are suppressed from planning ads and planning emails for twelve months.
LanternhillSponsored
Writing your wishes down is one of the kindest things you can leave. Our free guide walks you through it, with every price listed.
Plan it once. Spare them the guessing.
Free planning guidelanternhill.exampleDownload
Ad set
Planning ahead
Who
Adults in the service area, broad. Age and location only.
Goal
Leads, on the website (not an instant form), so every lead sees the price list
Lands
Planning ahead door
LanternhillSponsored
When Mom needs more help than you can give, start with a short care-fit check and an in-person tour. No pressure, no forms to sign.
See it in person before you decide.
Book a tourlanternhill.exampleBook now
Ad set
Senior care
Who
Adults in the service area, broad, plus a lookalike of past tour bookers
Goal
Leads, optimised for "tour booked", not "form started"
Lands
Care for a parent door
LanternhillSponsored
You came by last week. Your planning guide and our price list are still here whenever you want them, and a call is always optional.
Whenever you're ready, we're here.
Pick up where you left offlanternhill.exampleLearn more
Ad set
Retargeting, 30 days
Who
Planning and care visitors who did not finish. Excludes at-need contacts and anyone who already booked.
Goal
Leads; frequency capped low
Lands
The step they left
Ad wording rule: copy never states or implies a viewer's health, age or loss ("Did you just lose your mother?"). Meta's personal attributes policy prohibits it, and families find it cruel. Meta's policy. There are no at-need ads at all: those families find you through search, Maps and hospice referrals.
Pre-need pipeline
GoHighLevel, one opportunity per family
New leadGuide sent, tagged by who and what they lean toward
R. Alvarez · parent
EngagedOpened the guide or viewed prices twice
Call bookedPlanner assigned, reminder set
Plan presentedWritten estimate sent, 7-day check-in task
SignedContract in place, family contacts added
Not nowMoved to the quarterly letter, never deleted
At-need pipeline
Speed first: the director is paged the moment it lands
Call receivedSMS and push to the on-call director
Callback · hospice
Director assignedCallback logged with time to first call
ArrangementMeeting held, price list given in person
Service heldThank-you note task for the director
AftercareGrief resources at 30, 90 and 365 days
Senior care pipeline
Optimised to tours, not form fills
InquiryCare-fit result saved to the contact
J. Kim · memory care
Tour bookedConfirmation, reminder the day before
TouredSame-day follow-up from the guide who led it
AssessmentNurse visit scheduled
Move-inWelcome sequence for the family
Clean data in: each answer on the page maps to one custom field (planning for, leaning toward, timing, care needs, served). Staff never retype what a family already told the website.
Planning ahead
Email, plus text only if they ticked the box.
Minute 0Guide and price listemail, and a text if consented
Day 2"Questions families ask us"email
Day 5Optional call offer, three timesemail
Day 14A worksheet to share with familyemail
Day 30Check-in from a named planneremail; then quarterly
Help now
No marketing. Only care, and only from people.
Second 0Director paged with name, number, whereSMS and app push
Minute 10Escalate to backup if no callback loggedinternal alert
Day 30Grief resourcesletter or email
Day 45One review request, same link for every familyemail, never text
Days 90, 365Remembrance notesletter
Senior care
Built around the tour.
Minute 0Tour confirmed with directionsemail, text if consented
Day -1Reminder with what to bringtext or email
Same dayThank-you from the tour guideemail
Day 3Pricing and care-level sheetemail
Day 10Second visit or a meal inviteemail
Every workflow has an exit: a booking, a reply, an opt-out or a death in the family stops the sequence at once. Review requests go to every family with the same link, and low ratings alert the owner; Google prohibits asking only happy customers.
Cost per leadCPLby ad set, weekly
Speed to leadMinutesform in to first call, at-need
Lead to bookedRatecalls and tours booked per lead
Booked to signedRatepre-need plans and move-ins
Shown as definitions, not results. Lanternhill is a concept; real numbers come from the client's own accounts.
The Monday report,one page
Leads by door and by source, against last week
Spend, cost per lead and cost per booked call or tour, by ad set
Median time to first call on at-need callbacks, with any over ten minutes named
Pipeline movement: what advanced, what stalled, who owns the next step
One change for this week, and what we expect it to move
Tracking: the page fires one event per step to the ad platform and the CRM (door chosen, step reached, submitted, booked), so cost is measured to booked calls, not to clicks.