What method for using custom fonts is NOT supported for dynamic text?

The method for using custom fonts that is NOT supported for dynamic text is Fonts stored on a File Transfer Protocol(FTP).Dynamic text in Studio requires fonts to be accessible and loaded directly from reliable and secure sources that can be accessed during ad serving.Fonts stored on an FTP server do not meet this criterion because FTP servers are typically used for file storage and transfer rather than serving web fonts dynamically.For dynamic text in Studio,fonts are ideally sourced from platforms like Google Fonts,which provides a reliable and widely supported method for embedding fonts via CSS.Additionally, fonts added to the Asset Library and linked to a creative in Studio are supported because they are hosted and managed within Google's infrastructure,ensuring accessibility and reliability during ad delivery.Similarly,any fonts uploaded with a creative in Studio are supported because they are integrated into the creative's assets and managed by Studio's environment.Incontrast, fonts stored on FTP servers lack the necessary infrastructure and integration capabilities to ensure consistent availability and proper rendering across different devices and browsers,which are essential for dynamic text functionality in digital advertising campaigns.Therefore,relying on fonts stored on an FTP server is not supported for dynamic text in Studio,emphasizing the importance of using approved methods like Google Fonts or Studio's Asset Library for ensuring reliable and consistent font rendering in dynamic ad creatives.