The tracking plan
In plain English
Tracking is how we find out which page does better. Four things get counted:
- The first step a parent takes toward you. This is the number that decides the test.
- An enquiry.
- A booked consultation.
- A visitor leaving for your Wyzant profile.
The counts live in Google Analytics, in the set called Crimson SAT, and in Google Ads. Nothing has been changed on your accounts yet.
For your developer
What's there today. Your site loads one Google Tag Manager container, GTM-NTBPSWCS. It holds the Google Ads tag, a conversion linker and three Ads conversions: a view of the thank-you page, a click on your Wyzant link, and 60 seconds on the page. A fourth conversion, triggered by a custom "lead" event, is paused. There's no Analytics tag in the container, because Wix sends Analytics data on its own. It sends it to both properties.
What needs fixing.
- The Wyzant tag only fires on the exact link http://wyzant.com/tutors/flagstaffmathtutor. The new page uses the https://www version, so Ads wouldn't count those clicks.
- The thank-you tag only fires on /thank-you. Parents on the new page go to the booking calendar, so Ads would count no enquiries from it, and Google would think the new page does worse than it does.
- The new page doesn't carry the Tag Manager snippet yet.
Which property. Crimson SAT (496487869). Its address matches the live site. Crimson Tutor (497851341) gets the same visits and points at a domain that isn't connected, so leave it alone and stop reading it. Set Crimson SAT's reporting time zone to Eastern before Nov 9.
The events.
| Event | Role | How it's made |
|---|---|---|
first_step |
Key event, decides the test | Tag Manager. New page: click on any button that goes to the booking calendar. Current page: first touch of a contact-form field. |
generate_lead |
Key event | In Analytics, from page_view where the address contains /thank-you. Excludes sessions that land straight on it. |
booking_confirmed |
Key event | In Analytics, from the page Wix shows after a booking. The address is known after a test booking. |
wyzant_click |
Not a key event | In Analytics, from the automatic outbound-click event where the link domain is wyzant.com, so both link forms count. |
The steps.
| # | Step | Where |
|---|---|---|
| 1 | Create generate_lead, booking_confirmed and wyzant_click. Mark first_step, generate_lead and booking_confirmed as key events. |
Analytics |
| 2 | Set the reporting time zone to Eastern. | Analytics |
| 3 | Add the first_step triggers and one Analytics event tag using the Crimson SAT measurement ID (no configuration tag, so page views aren't counted twice). Test in Preview, then publish as a named version. |
Tag Manager |
| 4 | Change the Wyzant trigger to fire on links containing wyzant.com/tutors/flagstaffmathtutor. |
Tag Manager |
| 5 | Fire the existing Ads lead conversion on the booking-confirmed page too, with the existing conversion label. | Tag Manager |
| 6 | Add the Tag Manager snippet to the new page, load it only on the real address (never pages.dev), and deploy. |
New page |
| 7 | Visit both pages and check all four events in Analytics DebugView and the Ads tags in Tag Manager Preview. Make a test booking and cancel it. | Both pages |
Address. On go.crimsonsat.com, visitor and ad-click identity carry over to the Wix booking calendar on their own, because both sit under crimsonsat.com. On a pages.dev address the visit breaks at the jump to Wix unless cross-domain linking is set up on both sides, and Safari can still drop it. Use pages.dev for review only.
Form data. For test 1 the new page collects nothing. Its buttons go to the Wix booking calendar, and the grade and score questions move into the booking form. No parent data touches the new hosting. A parent who abandons the calendar leaves no trace, which is also true of the Wix page today.
Timing. GA doesn't backfill events, so all of this has to be live by Thursday, Nov 5. That gives the current page four days of first-step data before the test starts on Mon, Nov 9.