What is a Custom protocol link?

Custom Protocol is the option to trigger applications or custom URL schemes and locations that do not have an http or https address.

You can use the Custom Protocol link type whenever you want to hyperlink something that is not a regular website. 

You can use Custom protocol links in several tools within GetResponse, including email messages, landing pages, and the website builder. 

Some useable examples include, but are not limited to: 

SchemeSample purposeExample
mailto:compose an email messagemailto:test@example.com?subject=your subject line!&cc=ken@lee.com&bcc=tulibudibu@douchoo.com&body=Your email body text
tel:initiate a phone calltel:+48123123123
sms:compose an SMS messagesms:+17775555555?body=hello%20there
ftp://to link to FTP server, file-sharingftp://foo:@host.com
smb://link to an SMB server, file-sharingsmb://local-server-name/share-name
magnet:typically used to initiate Torrent p2p downloads without a .torrent filemagnet:?xt=urn:btih:5dee12345db281ac1c23456cd6b175cdcad53426&dn=download
whatsapp://compose a message in WhatsApp with specific content on supported deviceswhatsapp://send?text=Text example here
javascript:execute a JavaScript
yourown://if you’re a developer, you can create a custom scheme for your own app

When you use the Custom Protocol option in GetResponse, http:// or https:// scheme in links is not enforced.

While you can still use web addresses in Custom Protocol links, they will not be click-tracked by default unless Dynamic Content links syntax is used. 

For web URLs, we suggest using the regular Web address link type to ensure automatic click tracking, unless you have the entire URL as a custom field with the protocol. For more info, see Dynamic links.