Is the HTML Preference Center hosted by Braze or is it a page hosted by the brand?
The preference center is hosted by braze on emailinboundprocessing.com. In the future we will build support custom domains (i.e. companies can delegate their own domains to Braze)
More context from our Fall Release here:
Uplevel your retention strategy with HTML Preference Center. Audience retention is paramount at the end of the year, and a preference center that matches your brand and caters to your customers’ needs is a key part of any retention strategy. This update opens up the preference center page via a REST API endpoint, which you can use to fully build a flexible, powerful, on-brand preference center.
The REST API control of preference centers is incredible. With the addition of changing the favicon, there's another feature that's on the cusp of being capable, if only the request gets to the right software dev.
We desperately need the ability to add a CSP (content security policy) meta tag via API the same way we can update the Favicon.
I've added the necessary meta tags to our preference center and confirmation page, but since the preference center guts are technically iframed onto a emailinboundprocessing.com, they're no good. Just like adding the favicon to the HTML would not function.
Duplicating the favicon link-tags API ability to a meta-tags ability would let me approve our CRM to iframe an internal-facing preference center so our phone agents will have our subscribers' email preferences at their fingertips.
The preference center is hosted by braze on emailinboundprocessing.com. In the future we will build support custom domains (i.e. companies can delegate their own domains to Braze)
