Repository navigation
Preserve social attribution and coordinate LinkedIn Page publishing - #6051
Merged
Merged
Conversation
Contributor
Cloudflare Preview
|
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.
Social campaign parameters were lost when readers navigated the website and opened BuildCloud. Preserve the first tagged acquisition for 24 hours with existing analytics consent and forward it only to allowlisted BuildCloud entry links. Keep pricing parameters, handle dynamic links and clear attribution on consent withdrawal. Add a per-post link generator and an aggregate-only report for the existing BuildCloud signup/build funnel.
Page publishing also needs one owner: add a private, atomic calendar guard that checks published and future scheduled items on both sides of a proposed slot, requires fresh native evidence, and preserves ambiguous reservations. The local legacy-runner handoff is already installed with a private backup; it delegates LinkedIn before browser initialization. Existing queue/state, public content and cadence are unchanged. Document the shared coordination requirement for ad hoc promotions.
Validation: website Hugo build; acquisition navigation/consent/expiry/origin tests; existing Crisp consent tests; 9 calendar/report/handoff tests; 72 local legacy-runner regression tests. Syndication health is clean and the LaunchAgent last exit is 0. No native CI tests were run or added.
BuildCloud's companion change captures direct registration/login and pricing entries. These branches are not deployed; live tracking verification remains required after deployment. Consent refusal, cross-device and tooling journeys without the website handoff remain unattributed. Reported successes are unique users in a signup cohort, not weekly build events or causal lift.