0

We are currently evaluating if we should use the default MC subscription / profile center or develop a custom branded one.

Can anyone share their experience with building it on their own? What are the pros/cons and how much effort does it imply?

7

Building a basic custom preference/subscription center that replicates the existing functionality generally takes 30-50 hours of development time, depending on how much front-end work needs to be done.

I start with this boilerplate for most of the time.

A few tips:

  • Understand the SFMC data model and how subscriber statuses are handled for your account type (global, business unit, publication). Things are handled differently in an Enterprise 1.0 account than they are in an Enterprise 2.0 account.
  • Use Server-Side JavaScript to leverage arrays and functions. The coding can be done entirely in AMPScript, but it's easier to create object-oriented code in SSJS.
  • Utilize the SOAP examples when structuring your API calls
  • Log unsub events instead changing the status to unsubscribed. You should opt subscribers down instead of out if the sends are associated with a List or Publication.
  • Utilize the micrositeURL() function to link to new profile center pages in your email footers. If you're preference center serves multiple business units, you can use it to pass the MID (and anything else).
  • I normally build preference centers in 4 pages:

    1. Subscription Center Page - subscribers opt-in and out of lists or publications marked as Public.
    2. Profile Center Page - subscribers update their information (email address, name, zipcode, etc).
    3. One-Click Unsubscribe Page - subscribers are immediately unsubscribed from the publication used as the send audience in your SFMC account (or globally if it's not specified) and
    4. Results Page - a thank your or error page depending on the action taken on pages 1-3.
2

This greatly depends on your needs. If you just want to integrate the profile, preference and subscription center in your own website (as the customization options in the default version are pretty restricted), the main development effort is for the frontend as your backend then just needs to interact with the API and you can use the same data structures as the default PPSC does. In that case you can even implement it using microsites and don't have to write and deploy your own backend, as you can do all the work using AMPscript/SSJS.

However, if you need to add additional functionality such as frequency preferences, hierarchical subscription options that can be configured from within marketing cloud and so on, you will need to also set up the data structures in marketing cloud and build your own logic, etc. This requires quite some time planning and implementing everything.

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.