To Brandon · cc Glenn, Joe Paradis · replies on his own thread
▸ What Brandon sent · 24 Jul 2026, 15:27 UTC · to Joseph, cc Glenn + Joe
Good morning Joseph,
Our team has deployed the PRs. Can you please validate?
Thank you,
Brandon
↓ our reply
TRIMMED: 402 → 219 words. Cut the test-site paragraph out of the body and moved it into the note Fred actually reads.
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 serve now carries the fix, with nothing left on the old version. Please pass my thanks to your team.
What it fixes: the first event in the visit trail was recording, so the campaign source was being captured. The two that follow it, the last touch and the landing page, were not. That is now fixed. One unplanned bonus, the Large Group page on costcoquote had a script error switching its tracking off entirely, and the same change clears it.
The honest limit: this restores the visit trail going forward. It does not label sales that come through agents, renewals and partner referrals, and several quote pages still have nowhere to store the campaign values. I will bring that list to the next call.
One ask, smaller than a test. Those events are written on your side, so only your team can confirm them. The exact check is below.
One more, separate. The stuck cart fix for the individual quote pages is already live on costcoquote but was never merged, so master still carries the old version and any rebuild from it brings the bug back. Merging that pull request closes it, 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 July 24 deploy, can you confirm LeadUtmTrackLog is now carrying last_touch and landing_page rows, not just first_touch? Real traffic has flowed since, so the rows should already be there.
Two notes while you are in there. 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 automated build for the individual quote project has failed on every run since at least July 13, well before our changes, so whatever puts code on the live sites is not that build.
QUESTION
Send it? Keep Glenn + Joe on cc, or Brandon only?
2 · Email to Robin, Ken, Brandon, Jessica
The milestone you promised them on 23 Jul
To Robin, Ken, Brandon, Jessica · cc Glenn · replies on the "Where your sales come from" thread
▸ What WE told them · 23 Jul 2026, 23:16 UTC · this is the promise we now owe an update on
Timeline
Web visibility: our estimate is 2 to 4 weeks after your team reviews, merges, and deploys, at which point every new web sourced sale carries its source on both sites.
Whole book: the offline majority will never carry a web tag, but it can be labeled with information your systems already hold.
↓ the update, now that the merge + deploy happened
TRIMMED: 237 → 164 words.
Subject: RE: Where your sales come from: our findings and when you will have full visibilityHi Robin, Ken, and team,
A short 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.
That was the piece that had to land first. The break that stopped the visit trail after its first step is fixed, and your team is confirming it in the data. I will report back once they do.
Two honest notes. Several quote pages still have no field to hold the campaign values. And on cbcins, connecting a visit to the sale record needs one more piece that is not built yet, so full visibility there lands later than costcoquote. I will bring the exact list to the next call.
The offline majority of your book is unchanged by this and still the bigger half. That is the next piece of work, and the one I want call time for.
Best,
QUESTION
Send it? This is what quietly resets the "2 to 4 weeks" before it goes late.
3 · MONDAY — B0 · kills the "Whose turn" AI note
Rewrites our subitem under UTM Code Discovery
Subitem 12615567049 · the one you asked me to find
▸ What is LIVE on their board right now · our own subitem, posted 23 Jul · pulled fresh today
NAME: Tracking fixes are in review: three pull requests are with the team
STATUS COLUMN: Working on it
The individual quote tracking fixes are verified and open as three pull requests, one per site, with Brandon as the reviewer. Each PR carries its own description of what it changes and how to verify it. Deploy detail for each site came back from the team on July 23. Next step is review, merge, and include each fix in that site's next deploy. After deploy, one test quote should record the full visit trail. Whose turn: CBC, review and deploy.
TWO PROBLEMS WITH IT: it ends with "Whose turn: CBC, review and deploy." — our internal column wording, live where 49 CBC staff can read it. And it is now false: it says the PRs are "in review" and status "Working on it", but they merged and went live on 24 Jul.
↓ the replacement
REPLACEMENT 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.
QUESTION
Post it? And the status column: Done, or leave it Working on it until they confirm the data? I lean Done, since the text says plainly the confirmation sits with them.
4 · MONDAY — B1 · KILLED
Reply to Jessica, mobile form launch
▸ What Jessica posted · 14 Jul 2026 · 11 days, no reply from us, and staying that way
Update from Fred 7/14/2026
Please see updates:
1.CQ_IDV_SG_LG_07_10_2026: CostcoQuote mobile-ready IND/SG content to Stage
Work in progress, focus on the family plan result & dental plan result, plan detail page for Individual
You said leave it: that is what Joe and their team are working on. Killed, marked do-not-revive, shown here only so nothing is invisible. It had offered to map our 18-page rebuild against what their team is staging, which is us positioning our work against theirs on their own board.
5 · MONDAY — B2 · Joe Paradis, trimmed
Reply under his demo links
He posted 14 days ago and has had silence from us
▸ What Joe Paradis posted · 11 Jul 2026 · 14 days, no reply from us
You can preview the demo of the Update here:
https://www.cbcins.com/Costcoquote_mobile_demo/
Also of note is the alternate version of the large group Landing page which we are aiming to use as a starting point for future expansion, similar to what was done for the CBCins large group landing page.
https://www.cbcins.com/Costcoquote_mobile_demo/LargeGroups2.html
↓ our reply
CUT: "Worth lining that up against our own rebuild before either goes further, so the two do not drift." Same move B1 was killed for.
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.
QUESTION
Your reason for killing B1 named Joe, and this is the Joe one. Post this, or stay off the mobile item entirely and kill it too?
6 · MONDAY — B3 · Paid Ad tracking
New reply under that item
Our 23 Jul comment still says the fixes are "in review" · I am not editing it, it stays as a dated record
▸ What Jessica asked · 9 Jul 2026
It doesn't look like the paid ads have trackers embedded and we cannot tell if the ads are generating activity/leads. Is this something we need from WeGotU?
Recommendation was to ad trackers to these ads or ask for any reporting that may be available on them.
▸ What WE replied · 23 Jul · now stale, this is what needs updating
Quick status: the link tagging standard is in motion with the WeGotU team so every ad link carries its source going forward, and the tracker fixes that record those tags on the quote pages are in review as pull requests now. Between the two, each paid click that becomes a quote will carry its source end to end.
↓ the new reply
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.
QUESTION
Post it?
The one I will not decide for you
The security email
QUESTION
Two of our own rules contradict each other. The outbound queue says security never goes out in writing, verbal via Brandon always. The open-loops file says an email may name findings and locations as long as it carries no values. The drafts are written to the second rule. I am not overriding either. Five items have been held about 23 days.
What I caught before it reached them
"That fix has not shipped yet" — false
The stuck cart fix went live 24 Jun. Only the merge is missing. It also contradicted our own live board.
"The events that tell you which campaign a visitor came from were never recorded" — false
Caught by the 25-agent audit, then verified in the live code myself. The first event always fired and always carried the campaign source. Brandon could have disproved it from the report we sent him on 23 Jul.
The "top blockers" email — pulled
Its main ask was "please merge the fixes." They merged them the next morning. Its number was wrong grain and 20 days stale. Live: 2,728, not "around 2,800."
My own error: "board corrections were never applied"
They were, 13 Jul, on your "Fire". The receipt was in the same folder I was writing into.