← All work

Mogo · Senior Marketing Operations Manager (Lifecycle and MarTech) · 2024 – present

Mogo web ecosystem rebuild

Marketing needed to ship pages in hours while the website sat with DevOps, and that ownership question turned out to be central rather than incidental.

What they asked for

Lifecycle conversion is weak. The emails probably need work.

What was underneath

The emails were performing. The pages they sent people to weren’t, and the site sat with DevOps, so Marketing couldn’t move at campaign speed.

The starting point

Lifecycle conversion was weak, and email was the reasonable first suspect. Looking upstream, the emails were performing reasonably; what wasn’t performing was where they sent people. Campaign traffic landed on generic product pages with little relation to the message someone had just read.

The second issue was structural. The website was owned by DevOps, so any change needed an engineering ticket and a campaign landing page took weeks. Marketing had no way to move at campaign speed.

Two problems at once, then: a conversion problem from lifecycle-web misalignment, and an ownership problem from the tool sitting with the wrong team for the job.

The decision

Rebuild the web ecosystem in Webflow and move ownership to Marketing, with a component system that let any team member launch a page without engineering involvement, and lifecycle alignment and conversion intent designed into every page from the start.

Use the migration as the forcing function to fix the tracking layer at the same time. GA4 and GTM carried years of undocumented tag debt, and rebuilding the site without fixing tracking would only have made the same attribution problem faster.

How I measured it

Conversion rate from lifecycle traffic: the specific failure the rebuild was meant to address. If lifecycle emails sent people to pages that matched the message and the intent, that number would move.

Secondary: time to launch for a new page. The ownership problem was only solved if Marketing could ship without waiting on engineering.

The build

Rebuilt five properties: MogoTrade first as the proof of the Webflow model, then Moka, Intelligent Investing, orion-digital.com, and mogo.ca.

Built a component system rather than individual pages: reusable sections, governed naming, and a CMS structure that let anyone assemble a page from the library in hours. Defined URL structures, content models, and metadata templates before touching layouts, so SEO and tracking were built in rather than retrofitted.

Applied SEO, AEO, and GEO across all five properties: schema markup, canonical structures, internal linking, metadata by page type. Rebuilt GA4 and GTM in parallel, bringing Analytics, DevOps, Product, and Legal into the tracking architecture during the migration rather than after. Every page launched with clean event tracking on day one.

+15%

Conversion from lifecycle traffic

+30%

Conversion on campaign-specific landing pages

~5% → ~14%

MogoTrade organic traffic share, within 90 days


The lifecycle conversion problem turned out to be a destination problem. Once the pages matched the message and Marketing owned the ability to change them, conversion followed, and the component system meant the fix held for every campaign after, not just one.

Tech

Webflow

Full web ecosystem and component system

GA4 + GTM

Rebuilt tracking infrastructure

Braze

Lifecycle-to-web traffic coordination

Semrush / Ahrefs

SEO audit and organic performance

Schema.org

Structured data and AEO implementation

Branch Metrics

App deep-link attribution

Previous

Email validation and compliance workflow

Next

DTC Newsletter web and SEO rebuild

Tell me what you’re working on.

If you’re working through a customer journey, system, or operational problem and think my experience might help, I’d like to hear about it.

Consulting on lifecycle, conversion, and automation—and open to the right senior role.