Using string field for preference center | Community
Skip to main content
Kim_Gandy1
Kim_Gandy1
Level 6
June 7, 2017
Question

Using string field for preference center

  • June 7, 2017
  • 1 reply
  • 4057 views

We're looking update how we auto opt-in subscribers to fulfillment emails they're paying to receive. If a subscriber is new or renews, we want to auto opt-into the fulfillment newsletters UNLESS they've manually requested to opt-out via their preference center.

Currently all newsletters in our preference center are managed by boolean fields in a form, which do not allow for a NULL value.  I'm considering changing them to string fields that display a checkbox. The string  would allow "yes, no, null" values in the field. This would help in the trigger campaign opting in users, and leaving preferences as is if the value is "no".

Smart list

Trigger = subscription date updated

Flow

Change data value, if newsletter preference is "yes or null" to = "yes"

Any thoughts on using a string field vs boolean? Possible changes I should think thru? I've reviewed @Josh Hill​'s Building a Full Subscription Center in Marketo - Marketing Rockstar Guides and multiple community threads, but didn't see anything on my question.

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

1 reply

SanfordWhiteman
SanfordWhiteman
Level 10
June 7, 2017

I'd sooner use an integer field as an enumeration. Values can be -1 (null) 0 (false) 1 (true).

Kim_Gandy1
Kim_Gandy1Author
Level 6
June 7, 2017

So by default, all new leads would have to be changed to show -1 until subscribed? How would I backfill this value?

SanfordWhiteman
SanfordWhiteman
Level 10
June 7, 2017

Smart Campaign? Or you could switch it so -1 is false and 0 null. Just saying I tend to use enumerations instead of freeform strings, because it's faster, smaller, and has no possibility of typos.

Terms & ConditionsAccessibility statement

Loading footer...