Displaying the preference-center on a non-HS page isn't possible by default. iFraming could could lead to CORS errors.
A way to go could be be: recreate a form with your subscription types, modify the embed code, create one (or multiple) workflow(s) to have the same functionality as the regular preference-center and embed this form on your external page.
Hi @GLittle9 and @JLehmann , we are currently experiencing the same issue, wanting to embed the subscription preference link from HubSpot to external email software. I was wondering whether you were successful in finding the solution to this?
Displaying the preference-center on a non-HS page isn't possible by default. iFraming could could lead to CORS errors.
A way to go could be be: recreate a form with your subscription types, modify the embed code, create one (or multiple) workflow(s) to have the same functionality as the regular preference-center and embed this form on your external page.
Hi, @GLittle9👋 Thanks for the interesting question. Hey, @Anton@Jnix284@SJaeger, have you pulled this one off in past projects? I wonder if this falls under not possible due to the nature of how that link is generated.
It's been a minute since I really messed with this page type, but my gut says the page is the “same”, but part of the URL is dynamic or unique for each contact. Does that sound correct?
Thanks for taking a look! — Jaycee
Join us on March 27th at 12 PM for the Digital Essentials Lab, an interactive session designed to redefine your digital strategy!
Engage with expert Jourdan Guyton to gain actionable insights, participate in live Q&A, and learn strategies to boost your business success. Don't miss this opportunity to connect and grow—reserve your spot today!
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !
Hi, @GLittle9👋 Thanks for the interesting question. Hey, @Anton@Jnix284@SJaeger, have you pulled this one off in past projects? I wonder if this falls under not possible due to the nature of how that link is generated.
It's been a minute since I really messed with this page type, but my gut says the page is the “same”, but part of the URL is dynamic or unique for each contact. Does that sound correct?
Thanks for taking a look! — Jaycee
Join us on March 27th at 12 PM for the Digital Essentials Lab, an interactive session designed to redefine your digital strategy!
Engage with expert Jourdan Guyton to gain actionable insights, participate in live Q&A, and learn strategies to boost your business success. Don't miss this opportunity to connect and grow—reserve your spot today!
Did you know that the Community is available in other languages? Join regional conversations by changing your language settings !
We are exploring going with a two-prong approach where we will use the 'normal' subscription page and customize it to look as we need it. That is what will be linked to from emails, as usual.
Then for our external page, we'll use the API (/communication-preferences/v3/definitions) to get the list of possible subscriptions (in the order as they are defined) and display them on our page. And use the API to get the subscription choices of the current user (known by their email). This external page will then that API to subscribe/unsubscribe the subscriptions that the user chooses.
This sounds reasonable up to the point contacts try to resubscribe to any given subscription type. To my knowledge this does not work via workflows or API. The documentation says the following about this:
"The subscribe contact endpoint allows you to subscribe an email address to any given subscription type in an account, but will not allow you to resubscribe contacts who have opted out."
This creates a dilemma i would be very keen to find a solution for.