Custom Tracking to Capture All Parts of the User Journey

Posted by: Gina Bennett Date Posted: May 28, 2025
Back to Case Studies

Issue

This is a comeback client!  Previously, they didn’t have an Architect, and we were missing tracking on everything except for initial account creations.

The main issues were:

  • The client collects information on minors — for legal purposes, they didn’t want us to track the application form at all.  We didn’t even have the pixel on the page, which was causing issues with having continuous page paths and user journeys
  • The payment for the application happens off the website
  • The client must then approve the application after it’s paid for, which also happens off the website

Solution

With help from Gerard, Alejandro, and the client’s developer, we were able to come up with a solution to track all steps in the process (excluding the application form)!   We have full end-to-end tracking!

Here’s the user journey and how we’re tracking each step in the process.

  • User must first Create an Account -> Tracks in LMFX as “Create a Camp Parent/Guardian Account”
    • Implementation: standard. No custom script or tracking
  • User then must fill out an application -> Not tracking in LMFX
    • This is due to legal reasons
    • Form ID (camper-info-form) is blocked from tracking in LMFX due to legal reasons
    • Our RCFX pixel is on the page though, which gives us continuous attribution and user journeys!
  • User then must pay for tuition / request a scholarship -> Tracks in LMFX as “Camp Registration”
    • Implementation: When the user clicks on one of the “pay now” buttons, the client fires custom JavaScript to sends useinformation about the logged-in user and the application they’re paying for
    • Dev Task for original set up
  • Client must approve the application -> updates matching (based on Application ID) “Camp Registration” lead to Closed Won. If matching lead doesn’t exist, it creates a new Closed Won “Camp Registration” Lead
    • This does not happen on the website, and we otherwise would have no visibility into this
    • Implementation: Client fires server-side JavaScript as a webhook. Workato processes and updates as needed
    • Dev Task for original set up

Our next step is to get conversion and audience feeds set up so the Meta and Google Ads can have visibility into which applications are actually being approved!

Achievement

Custom tracking to capture (almost) all parts of the user journey and give us revenue reporting!

Snippet/Screenshot/Link