Using link tracking is an easy way for us to find out how people are getting to our download page. People might click over to our download page from any of a number of areas, and knowing the relative usage of those links can help us understand what materials we're producing are more effective than others.
|Link||Goes to where?||Use this link where?|
|http://ur1.ca/03ajw||Download page||Blogs, status, microblogs (Identi.ca, Twitter, Facebook, etc.)|
|http://ur1.ca/03akl||Join page||Blogs, status, microblogs (Identi.ca, Twitter, Facebook, etc.)|
Each link should be constructed by adding ? to the URL, followed by a short code that includes:
- an indicator for the link source (such as the wiki release notes)
- an indicator for the Fedora release in specific (such as F37 for the final, or F37a for the Alpha test release)
So a link to get.fp.o from the one-page release notes would become http://get.fedoraproject.org/?opF37.
- I want to copy a link to my status update for social networking, or my blog.
- If you're posting a status update to identi.ca, for example, use the link tracking code for status updates. Don't copy a link straight from an announcement that includes link tracking from the announcement. You can copy the link itself but remember to change the portion after the ? to instead use the st code for status updates and blogs, followed by the Fedora release version (such as F38a, F38b, or F38), like this:
- I want to point people to the announcement from my blog. Should I use the announcement link tracking code?
- The actual URL link itself is the announcement URL. Add the link tracking code for blogs, which would start with ?st and end with the Fedora release version, like this:
|Front page of wiki||wkfp|
|The press release Red Hat makes||rhpr|
|Test phase release notes on wiki||wkrn|
|Official release notes||rn|
|Official installation guide||ig|
|One-page release notes||op|
|Status links (Identi.ca, Twitter, Facebook, etc.),
blog posts, other social networking