docs(web-sdk): note 0.1.12 and last-touch UTM persistence - #182
Open
tashviks wants to merge 1 commit into
Open
Conversation
0.1.12 mirrors last-touch UTMs into a 24h localStorage record so a purchase firing on a post-payment return page keeps its campaign. Measured on one production project, 95% of Meta-attributed purchases (70 of 74) had no campaign because the gateway returned the visitor in a fresh tab and sessionStorage was gone. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Adds a version note to the Web SDK installation section.
Do not merge before that ships.
mainand npm are both on 0.1.11 today; 0.1.12 exists only on #4's branch. Merging this early would document a version nobody can install.Why
0.1.12 mirrors last-touch UTMs into a 24-hour
localStoragerecord so they survive a payment-gateway or 3-D Secure redirect. Previously they lived only insessionStorage, which a gateway returning the visitor in a fresh tab wipes — the purchase then arrives with the right traffic source (click IDs persist 90 days) but no campaign.Measured on one production project: 70 of 74 Meta-attributed purchases (95%) had a blank campaign for exactly this reason.
No integration changes are required, so the note covers what changed and the ~24h CDN cache rollover rather than any migration steps.
Two doc bugs found nearby — not fixed here
Both are in the same Installation section and both break copy-paste. Deliberately left out to keep this scoped; happy to fix in a follow-up:
npm install @linkrunner/web-sdk; the published package is@linkrunner/web. The documented command fails.https://sdk.linkrunner.io/latest/linkrunner-sdk.min.js, butdeploy-cdn.ymlpublishes toweb/v1/lr.jsandweb/v1/lr.min.js.