How to build a Marketo Subscription Center | Community
Skip to main content
Edward_Masson
Edward_Masson
Level 10
February 18, 2015

How to build a Marketo Subscription Center

With the launch of the new Forms 2.0 from Marketo, I wanted to update an oldie in Marketo Community; Subscription Management. A Marketo Subscription Center. Below is a presentation I did last February at the Boston Marketo User Group.

The old Marketo subscription center needed JQuery to check and unchecked boxes of the users unsubscribe and choices. This can be daunting to someone who does not have coding experience.

I wanted to focus around creating smart lists and smart campaigns to do the heavy lifting. Having a smart campaign trigger to listen to changes to static lists using custom fields of topics to subscribe to by opting in and opting out. And of course play with the new Forms 2.0. Feel free to download from SlideShare or attached PDF.

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

    19 replies

    Grégoire_Miche2
    Grégoire_Miche2
    Level 10
    February 10, 2016

    This idea would come handy to support the subscription center:

    Translate
    Anonymous
    December 22, 2015

    I have the same question as Maria - why create both smart and static lists?

    Translate
    Andy_Varshneya1
    Andy_Varshneya1
    Level 7
    October 6, 2015

    No, you're right about that. I actually avoided a lot of complexity by avoiding the smartlists altogether. I simply have a trigger campaign that sets the values to true when a lead is created, and then use the different opt-in fields as filters in the smart list of my outbound email campaigns.

    Translate
    Anonymous
    October 5, 2015

    Sorry if I am missing the reply to the other similar questions, but we are in the process of building a subscription center and I am very interested in why you chose to create both Smart and Static lists?  Is it to counter a delay in refreshing the Smart List? 

    Translate
    Converto_Admin
    Converto_Admin
    Level 1
    August 30, 2015

    Hi,

    this was one great write up, thanks!

    one thing that bothers me is how to enforce the use of the subscription/optout lists in email campaigns moving forward. unlike the default unsubscribe process, it seems that for this kind of process to work everyone operating marketo must be:

    1. aware of the lists and how to reference them

    2. know which type of email is being sent out in a specific campaign in order to reference the right list

    I wonder if you or anyone else can shed some light on this.

    thanks again,

    Idan.

    Translate
    Edward_Masson
    Edward_MassonAuthor
    Level 10
    August 18, 2015

    There was no webinar. I just wrote it up and made a PPT for a User Group meeting.

    Translate
      Anonymous
      August 13, 2015

      Is there a link to the archive of this webinar somewhere and not just the slides?

      Translate
      Anonymous
      June 18, 2015

      Great question! I was wondering that myself. @Ed Masson, is there a reason to do static list over smart lists?

      Translate
      Anonymous
      May 28, 2015

      In this case null = false is ok, I think since it means they have not opted in to the subscription. In other cases I could see that being a problem. I decided to use boolean instead of checkbox at first because it simply was not an option in the dropdown list of the admin area when I was creating a "New Custom Field".

      Checkbox was however an option in the form area.

      Translate
      Anonymous
      May 28, 2015

      One caveat and a major pet peeve of mine when using boolean is that if not explicitly set it will default to value = "null".

      In Marketo world, boolean = null = false but there's no way to differentiate a null/false vs. false/false. This is a nightmare for filtering or for smart campaign workflow constraints.

      I can't for the life of me understand how a boolean value can technically be 3 values (null, False, True)...seems to completely violate the boolean standard of true/false.

      Am i missing something here or should we be using a different field type to avoid this problem (such as checkbox)?

      Translate
      Show more replies
      Terms & ConditionsAccessibility statement

      Loading footer...