Add UTM parameters to 51degrees.com links - #46
Merged
Conversation
Apply the standard vocabulary so the Content Team can trace traffic to its exact source: utm_source (github|code|nuget|npm|maven|packagist), utm_medium (readme|docs|example|comment|package), utm_campaign = repo name, utm_content = file path slug, utm_term = location within the file (nearest heading, enclosing member, or resource key). Normalise http, www and protocol-relative variants to https://51degrees.com in the process.
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.
Apply the standard UTM vocabulary to navigational 51degrees.com links so the Content Team can trace traffic to its exact source.
Changes:
Functional hosts (cloud.51degrees.com), the engineering email, and test fixtures were left untouched. composer.json has no homepage field. Lint passes with scripts/utm-lint.ps1.