We set up our email preference center based on the types of emails that we send so I feel like it is somewhat custom to each user. Just make sure the customer can understand what they would sign up for with the email preferences.
Thanks for the response.
Say we have an idea in place on this in terms of the different categories involved. How do we actually tag emails to identify if it's actually a Product Email, Educational Email, etc?
Is there somewhere in the Email Asset that I can state "Category of Email" or something like that? And then the Subscriber Preference Center would correspond with that?
The tie-ins between user preference fields and, for example, Program Tags will not happen automatically.
Even if you use the exact same nomenclature in both places (and you should, for clarity's sake) you still need to build Smart Campaign filters and flow actions accordingly.
And at the email level, other than naming conventions for the email itself there's no way to signal such a connection.
Building and maintaining these connections is an important part of a well-run instance, but if you're hoping you're missing something that'll make it happen automatically, you're not.
As Sanford mentioned, once you deploy a preference center, you really need to ensure each and every one of your programs/email-send campaigns have the required filters to make sure you're suppressing those people who have not subscribed to that type of content (if they haven't opted in to all). There are a couple of existing ideas posted by Grégoire Michel that would make this process much easier to manage:
1 of 1 people found this helpful
The thing to understand about a Preference Center is that you have to manage it internally. Everything is based off field value and smart lists. It is very easy to ignore preferences when sending an email if you're not careful.
I recommend coming up with a strategy and documenting it. Brainstorm every type of email you think you'll send, and match it to a preference category. And then have a ruthless QA process when you do your sends to make sure you're respecting those categories.
It might make sense to create program templates for different categories so you don't have to think about the smart list when you create the program. A simple example would be if you send mailbox blasts in categories "Resources", "Webinars", and "Events". So your program templates would be this:
1. Name: EB YYYY-MM-DD Resource Email
Smart List: Resources = True
2. Name: EB YYYY-MM-DD Webinar Email
Smart List: Webinars = True
3. Name: EB YYYY-MM-DD Event Email
Smart List: Events = True
We don't use any program tags (other than Channel, of course) but you could add tags to the templates too.
As for how you actually set up the fields and landing page, there are lots of blog posts on the Nation and external sites.
1 of 1 people found this helpful
Unfortunately Marketo doesn't come with certain pre-built features like Hubspot does, a pre-built preference centre being one.
We spent a good couple of days setting up and testing our preference centre and the result was way better than any out of the box solution. Managing lists is an ongoing task though.
You will need a developer or consultant to build something decent though.
It's almost impossible to answer this question in simple way because so many things will influence the design of your PC:
- What type of org are you in? An SMB with a local market ? A large multi-national company having to deal with different opt-in/opt-out regulations?
- What is you marketing plan made of and what kind of preferences do you want to offer?
- How skilled are you local and central Marketo users?
- How evolutive to do you think the options list will be in the future?
- Can you get hold of a JS developper to assist with the implementation of some more sophisticated features?
Based on the answers to these questions, your PC will have to be setup completely differently (from a simple PC with a limited set of functionality to a PC frameworks that can be rolled out in multiple countries with significant local adaptation. And the only thing that is certain is that there is no one-size-fits all approach.