CBC — approve or reject

Subject: RE: Tracking fixes are verified and ready — one question before go-liveHi Brandon, Validated. I checked the live sites directly, not just the merge. Every copy of the tracking script that costcoquote.com and cbcins.com actually serve to a visitor now carries the fix, on both brands, with nothing left on the old version. Please pass my thanks to your team. Here is what that fixes in plain terms. The first event in the visit trail was still recording, so the original campaign source was being captured. What never recorded were the two events that follow it, the last touch and the landing page, so the trail stopped after the first step. That is now fixed. One useful side effect we did not plan: the Large Group page on costcoquote had a script error that was shutting off its tracking entirely, and the same change clears that error, so the visit trail can run there again. One honest limit so nobody reads this as more than it is. This restores the visit trail going forward. It does not label the sales that come in through agents, renewals and partner referrals, because those never touch the website. And several of your quote pages still have no place to store the campaign values, so those flows are not fully wired yet. I will bring the list of what remains to the next call. One ask, and it is smaller than a test. Your quote pages have been taking real traffic since the fix went live, so if it is working, the rows are already in your own tracking log. Those events are written on your side, so the confirmation has to come from your team. I have put the exact thing to check in the short note below. Three smaller things for your side. The automated build for the individual quote project has failed on every run since at least July 13, well before our changes went in, so whatever puts code on your live sites is not that build. The test site at cbc-quote.azurewebsites.net is still serving a July 1 version, so it is not a reliable place to check this. And the stuck cart fix for the individual quote pages is already live on costcoquote.com but was never merged, so master still carries the old version there and on the other individual portals it covers. Any rebuild from master would bring the bug back, and merging that pull request closes it with no code change. Best, - - - - - - - - - - - - - - - Forward to whoever owns the quote database: The site records each visit by posting to /api/tracking, which writes to the LeadUtmTrackLog table. Before the fix, that trail stopped after the first event, so last_touch and landing_page were never written. For visits since the deploy on July 24, can you confirm LeadUtmTrackLog is now carrying last_touch and landing_page rows, and not just first_touch? The sites have taken real traffic since then, so the rows should already be there. If those two event types are landing, the fix is confirmed end to end and nothing else is needed.

Subject: RE: Where your sales come from: our findings and when you will have full visibilityHi Robin, Ken, and team, A short milestone update on the timeline in my last note. Your team merged the three tracking fixes on July 24 and they are live on both sites. I checked the live sites directly rather than trusting the merge: every copy of the tracking script that costcoquote and cbcins serve to a visitor now carries the fix. What that changes is the foundation. The break that was stopping the visit trail after its first step is fixed on your individual quote paths. Your team is confirming it in the data on their side, and I will report back once they do. Source labelling sits on top of that trail, so this was the piece that had to land first. Two honest notes on the rest of the window. Several of your quote pages still have no field to hold the campaign values, so those flows are not fully wired yet. And on cbcins specifically, connecting a visit to the sale record needs one more piece that is not built yet, so full visibility there will land later than the web fixes on costcoquote. I will bring the exact remaining list to the next call rather than guess at it here. The offline majority of your book is unchanged by any of this and is still the bigger half. That is the next piece of work, and it is the one I want the call time for. Best,

New name: Tracking fixes are merged and live on both sitesMerged by your team on July 24 and live on both sites the same morning. We checked the live sites directly, not just the merge: every copy of the tracking script that costcoquote and cbcins serve to a visitor now carries the fix. What it repairs is the visit trail. The first event was still recording, so the original campaign source was being captured. The two that follow it, the last touch and the landing page, were not, and that break is fixed. One side effect we did not plan: the Large Group page on costcoquote had a script error that was switching its tracking off entirely, and the same change clears it. Confirming the data itself has to come from your side, since those events are written to your own tracking log. The check has gone to Brandon.

Joe, thanks for both links, and sorry for the slow reply here. We went through the demo and the alternate Large Group landing page you flagged as the pattern for future expansion. One thing worth knowing while you are in these pages: the Large Group page on costcoquote had a script error that was switching its tracking off completely. That is cleared as of the July 24 deploy, so it is worth carrying forward into anything staged from here.

Quick update on the tracker half of this. Those fixes were merged and deployed on July 24 and are live on both sites. The break that was dropping the visit trail after its first step is fixed, so a tag that arrives can carry through it. Your team is confirming that in the data. The link tagging standard with the WeGotU team is the other half and is still in motion. Between the two, a paid click that becomes a quote carries its source end to end.