Can I use the prefix in my Backtracks Switchboard with existing prefixes?

Yes, but we highly recommend using your Backtracks Switchboard™ feed instead as it will just work, has enhanced capabilities, and will take care of many complex issues. That being said, you may use Backtracks Switchboard™'s tracking prefix with any other prefix-based solutions you may use.

Your enclosure URLs will look similar to the following:

https://bktrks.co/t/abc123/https://example.com/file.mp3

From this example enclosure URL (aka URL to your media), the Backtracks Switchboard™ enclosure prefix is:

https://bktrks.co/t/abc123/

If you are manually editing your RSS feed and adding your Backtracks Switchboard™ prefix to an existing RSS feed with prefixes it's useful to note that Backtracks Switchboard™ is flexible and works before or after existing prefixes. We recommend testing the combined URL with any prefixes in your browser before changing your RSS feed if you are building your RSS feed manually.

For example, here's one way to use your Backtracks Switchboard™ prefix with an existing tracking prefix. Just in case you cannot use the Switchboard™ RSS feed URL and you the have the ability to control prefixes, suffixes, and can build your enclosure URLs: 

https://bktrks.co/t/abc123/dts.example.com/redirect.mp3/feeds.example.com/ep1.mp3

Here's another way: 

https://bktrks.co/t/abc123/https://feeds.example.com/ep1.mp3

Matching HTTP and HTTPS

In "internet land" redirecting from HTTPS (secure) to HTTP (insecure) is frowned upon. Browsers and apps are increasingly strict and do not allow this. In the past you may have seen a warning or message like "parts of this page are insecure," with the ability to proceed, but over time this will be removed.

We recommend matching the scheme/protocol (that's that's the technical term for what HTTP and HTTPS actually mean) for redirects. The P in HTTP stands for protocol which you may or may not already know.

If you redirect or serve any files under HTTP instead of HTTPS, we recommend making the protocols HTTP (not HTTPS) "all the way down."

For example, if you audio is located at http://example.com/episode.mp3  and the protocol or scheme is HTTP then your redirects or prefixes should look like this:

http://bktrks.co/t/abc123/http://feeds.example.com/ep1.mp3