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!