Repository navigation
Fix booking CTA attribution and preserve interrupted checkout identity - #73
Merged
ChristFollower873461 merged 1 commit intoSep 27, 2026
Merged
Conversation
Deploying aissisted-website with
|
| Latest commit: |
d873cd7
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://9cad8606.aissisted-website.pages.dev |
| Branch Preview URL: | https://codex-website-booking-attrib.aissisted-website.pages.dev |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Booking links such as the Contact sidebar lose their page/button labels or inherit an earlier visit's labels. Validate each route and CTA as one approved pair in the browser and server, covering all 31 combinations currently emitted by public pages. Explicit invalid or partial URL values clear stale attribution; visits without those parameters retain only a valid saved pair. Existing campaign URL limits remain unchanged.
Keep an interrupted checkout's original body, key, and measurement. Since measurement participates in the stored request fingerprint, eligible existing records can match the complete original request under the previous normalization rules. New records carry a server-owned normalization version and cannot use that compatibility path. Changed contact, intake, consent, amount, or meaningful attribution still cannot reuse an accepted checkout identity.
Validation: offline regressions cover emitted links, stale/invalid storage, cross-page browser retries, legacy full-request matching, and new-record conflict protection. The full repository suite passes 548 tests, required source/public-truth/migration/preview checks pass, and the local D1 recovery case resumes the original booking/Session with unchanged Stripe body/key/version and one synthetic Session total. No live checkout or payment is used for validation.