Blackthorn
Turning a Salesforce-native SaaS marketing site into a fast, measurable growth channel that marketing can run on its own
Project Overview
Blackthorn builds event management software that runs natively inside Salesforce. I was their embedded web engineer: one person covering work that’s usually split between an in-house team and an agency. That meant WordPress engineering, content architecture, analytics and tag management, technical SEO, and performance.
What changed for Blackthorn: Marketing can launch pages and gated campaigns without a developer. Video views are built to land in Salesforce as sales Tasks. When a quarter-end conversion scare hit, leadership had data trustworthy enough to tell a real problem from a measurement error, and avoided fixing the wrong thing. And the homepage’s mobile performance score doubled.
All of it shipped across 249 commits and 36 pull requests, with documentation that let the team keep going after handoff.
Challenges & Objectives
Challenges
- Content without structure – Events, customers, and stories lived in generic pages, with no gated content and no clean data model.
- Page builder overhead – Elementor loaded its full CSS and JS on every page, and every button was styled one at a time.
- Tracking that couldn’t answer executive questions – Four near-duplicate form events, no CTA attribution, and no way to connect a video view to an earlier form fill.
- A performance and conversion scare – Mobile Core Web Vitals fell from about 150 “good” URLs to zero, while reports showed conversions down 29%.
Objectives
- Make key content types first-class, editable, and measurable.
- Give marketing a fast, on-brand way to build pages without a developer.
- Track the lead journey from first click to Salesforce.
- Find the real causes of the regression and fix them in phases.
- Make the site legible to AI search engines as well as people.
Business Impact & Strategy
Helping leadership avoid fixing the wrong thing
In Q1 2026, reports showed form submissions down 29% while traffic was up, and the new sitewide popup was getting the blame. Because I’d built per-form tracking months earlier, I could break the number apart. The popup was actually up 24%. A few page-embedded forms were down for separate reasons. And the March baseline had been inflated by tag deployments firing at 5–10× normal volume. Leadership stopped treating it as one crisis and focused on the forms that were really declining, instead of pulling a popup that was working.
A content platform built for lead generation
I modeled the site’s content as seven content types: Events, Customers, Customer Stories, FAQs, Resources, Landing Pages, and Blog CTAs, plus a Content Hub that brings posts and stories together. Events became a full gated-content platform. Visitors unlock on-demand videos through a Pardot form, access is remembered across visits, and each view carries its campaign source into GA4 and, as a Task, into Salesforce. No third-party webinar gating tool required. I also built two reusable FAQ plugins (an Elementor widget and a Gutenberg block) that output FAQ structured data.
A modular page system instead of a page builder
Blackthorn didn’t have to pick between Elementor, Gutenberg, or a full rebuild. I proposed a hybrid: high-value marketing pages move to a curated set of ACF modules, and Elementor stays available for one-off pages. The system launched with nine modules and grew to 17. It runs on a fluid SCSS token system, with a shared button helper so CTAs stay consistent and per-module asset loading so pages only load what they use. Along the way I cut functions.php from 1,612 lines to 638 and decoupled the theme from Elementor’s stylesheet.
Tracking leadership could trust
I owned the GTM container and GA4 setup: one consistent event taxonomy, a unique ID for every form, per-CTA UTM tagging, a first-party cookie that keeps campaign attribution across pages, internal-traffic exclusion, and a reusable BlackthornAnalytics JavaScript module used across the theme.
Finding and fixing the performance regression
Mobile Core Web Vitals fell from about 150 “good” URLs to zero. I tied the drop to specific deployments and mapped every cause: 14 render-blocking resources, 13+ third-party scripts (three doing the same job), duplicate tag loads, and about 1.8 seconds of avoidable delay in the form-submit path. I delivered a plan tiered by how easily each fix could be undone, shipped the homepage on the modular system, and followed up with code-level fixes (video facades, lazy-loaded form iframes, conditional icon and block CSS).
Ready for AI search
I added an llms.txt file, shipped FAQ structured data through the FAQ plugins, and ran two AI-visibility (GEO) audits to prioritize schema and trust fixes for how AI engines understand the brand.
Built to outlast the engagement
Every investigation lived in a working kit (action plan, open questions, decisions log, measurement log), and the theme ships with in-repo documentation. I ran an AI-assisted workflow throughout: an agent rules file in the repo, AI code review on every pull request (it caught a real regression before it shipped), and session recaps written back into the docs. The team could keep executing after I left.
Results
- 40 → 81 mobile homepage performance score (Lighthouse), the day the homepage launched on the modular system
- 77 → 96 Lighthouse Best Practices score
- +24% popup form growth, found inside a misread “29% decline”
- ~1.8s of form-submit delay traced to specific, reversible config settings
- 7 content types and a 17-module page system marketing runs without a developer
- 60% smaller
functions.php(1,612 → 638 lines) - 2 reusable FAQ plugins with FAQ structured data
- 249 commits and 36 pull requests across 11 months
My Role
As the sole developer on the site, I owned architecture, implementation, and the analysis behind it.
WordPress Engineering
- Built seven content types (Events, Customers, Customer Stories, FAQs, Resources, Landing Pages, Blog CTAs) plus a Content Hub.
- Designed and built a 17-module ACF page system on a fluid SCSS token system.
- Refactored the theme and decoupled it from Elementor so modular pages skip Elementor’s assets.
- Shipped two reusable FAQ plugins (Elementor and Gutenberg) with FAQ structured data.
- Ran an AI-assisted workflow: an agent rules file, AI review on every PR, and in-repo docs.
Lead Generation & Analytics
- Built Pardot-gated on-demand video with returning-visitor access, built to sync views to Salesforce as Tasks.
- Designed a five-state cookie model so GA4 can tell new leads from returning ones.
- Owned the GTM container and rebuilt CTA and form tracking with per-CTA UTMs and per-form IDs.
- Excluded internal traffic and removed an event that was inflating conversion rates.
Performance & Conversion
- Audited the network waterfall, the tag inventory, and the form-submit timing.
- Reframed the Q1 conversion story with form-level data.
- Delivered a tiered action plan, with every item scoped as a ticket with acceptance criteria.
- Shipped code-level fixes: video facades, lazy-loaded form iframes, and conditional CSS.
- Added
llms.txtand ran two AI-visibility (GEO) audits.
Key Features & Solutions
✅ Gated Event Video Platform – Pardot gating, remembered access, and campaign-source attribution through to Salesforce.
✅ Modular Page System – 17 ACF modules on design tokens, so marketing builds pages without a developer.
✅ Elementor Decoupling – Modular pages skip the builder’s CSS and JS entirely.
✅ Lead Attribution – Per-form IDs, per-CTA UTMs, a persistent campaign cookie, and cookie-state tracking.
✅ Content Hub – Blog posts and customer stories in one browsable library.
✅ AI-Ready Structured Data – llms.txt plus FAQ schema from two reusable plugins.
✅ Phased Performance Roadmap – Fast, reversible fixes first, measured at each step.
✅ Handoff-Ready Docs – Investigation kit and in-repo documentation the team kept using.
Before

After

Related Works:
Synack