morningman opened a new pull request, #67430: URL: https://github.com/apache/doris/pull/67430
### What problem does this PR solve? Issue Number: close #xxx Related PR: apache/doris-website#4101 Problem Summary: `https://doris.apache.org/slack` is no longer a plain redirect. Since apache/doris-website#4101 it is a small tracking page that records one Matomo event per click (`Category=Community Acquisition`, `Action=Slack Click`, `Name=source|medium|campaign|content`) and then forwards the visitor to the real Slack invite, so we can finally see where new Slack members discover Apache Doris. Attribution priority is `utm_source` > `document.referrer` > direct. The three Slack links in this README carried no UTM parameters at all, so the GitHub channel could not be told apart from anything else. The numbers confirm it. Over the first two days after the tracking page went live, **every** recorded event came from a link the website itself renders (homepage hero, footer, docs TOC, community docs, blog posts) or from the newsletter — not a single one was attributed to GitHub, even though this README is one of the most visible Slack entry points the project has. This PR tags all three links with the values the convention documents for this channel: ``` utm_source=github&utm_medium=community&utm_content=github_readme ``` which the tracking page records as the event name `github|community||github_readme`. The three links are: | Line | Placement | |---|---| | 30 | `Join Our Community - Slack` badge in the top badge row | | 48 | Slack entry in the social icon row | | 153 | `Join Slack` under `## 💬 Contact Us` | The public entry URL is unchanged, only the query string is added, so nothing about where the links point changes for a reader. Convention reference: `developer_docs/slack-utm-convention.md` in apache/doris-website. ### Release note None ### Check List (For Author) - Test - [x] No need to test or manual test. Explain why: - [x] Other reason: documentation-only change. Verified manually that `https://doris.apache.org/slack?utm_source=github&utm_medium=community&utm_content=github_readme` returns HTTP 200 with the query string preserved through the trailing-slash redirect, and that the tracking page's attribution logic resolves it to the event name `github|community||github_readme`. - Behavior changed: - [x] No. - Does this need documentation? - [x] No. ### Check List (For Reviewer who merge this PR) - [x] Confirm the release note - [x] Confirm test cases - [x] Confirm document - [ ] Add branch pick label 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01HxD4tbWWoVfy6nnfkaE8Zu -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
