Awardspace

AwardSpace is a free shared hosting provider with cPanel-style file management. Edit your HTML or PHP files through the File Manager or FTP and paste the snippet before the closing body tag.

Using AwardSpace File Manager

Log in to your AwardSpace hosting panel at www.awardspace.com. Navigate to Hosting Tools → File Manager. Your website files live in the www directory under your domain folder. Find the HTML or PHP file you want to edit — usually index.html or a shared PHP include for the footer.

Click the file name to select it and then choose the Edit action. The built-in editor opens in your browser. Scroll to the bottom of the file, find the </body> tag, and paste the StatelessID snippet just before it. Click Save to apply the change.

AwardSpace's File Manager is straightforward for single-file edits. If your site is large, the FTP method below may be faster for editing multiple files at once.

Editing PHP template files

If your AwardSpace site uses PHP and a shared footer include, find the footer file and add the snippet there. Look through your index.php and other page files for an include or require statement that loads a shared footer. Edit that shared file, add the snippet before the HTML it outputs near the page bottom, and save.

This one change covers every page on the site that uses that include. It is the most efficient path for PHP sites with more than a few pages.

AwardSpace supports PHP on all plans. There are no restrictions on PHP that would interfere with the snippet — it runs entirely in the visitor's browser as client-side JavaScript.

FTP access on AwardSpace

AwardSpace provides FTP access on its free and paid plans. Find your FTP credentials in the hosting control panel under FTP or Hosting Settings. The server is typically ftp.awardspace.com or your domain-specific FTP address.

Connect with FileZilla or another FTP client, navigate to the www folder for your domain, download the files you need to edit, add the snippet locally, and upload the modified files. The changes go live as soon as the upload finishes.

AwardSpace's FTP server may have a rate limit on connections from free accounts. If you encounter connection errors, wait a minute and try again, or reduce the number of simultaneous FTP connections in your client settings.

AwardSpace domains and site registration

AwardSpace free accounts come with a subdomain under awardspace.net or one of their shared domains (e.g., yoursite.awardspace.net). Register that URL in your StatelessID dashboard. When you upgrade or add a custom domain through the AwardSpace control panel, register the custom domain as a new or updated site in StatelessID and update the key in your HTML files.

AwardSpace provides free SSL on most of their hosting plans. Once the SSL certificate is issued for your domain (usually within a few minutes to a few hours after adding it), your site will be accessible at https://. Update your StatelessID site registration to use the https:// URL at that point.

Check your site's active URL by opening it in a browser and reading the address bar. Whatever appears there — including the exact subdomain and protocol — is the origin that must match your StatelessID site registration.

Troubleshooting

I saved the file but my browser still shows the old version. Do a hard refresh (Ctrl+Shift+R on Windows/Linux, Cmd+Shift+R on Mac). AwardSpace uses server-side caching and your browser may also be caching the old HTML. A hard refresh bypasses both.

The snippet is in the PHP footer include but only some pages show the tracking. Some pages on your site may use a different footer include or no include at all. Open each page that is not tracking and check whether it includes the shared footer file. Add the snippet directly to any page that does not use the shared include.

My AwardSpace free account shows bandwidth warnings after installing tracking. The StatelessID beacon is approximately 200 bytes per page view — extremely small. It will not materially affect your bandwidth usage on a typical personal site. If you see bandwidth warnings, the cause is visitor traffic volume, not the beacon itself.