SOLVED

Re: Custom Unsubscribe By Business Unit

Go to solution
Ariel_Sasso
Level 4

Custom Unsubscribe By Business Unit

Howdy Ya'll,

Has anyone used UTM"s to manage unsubscribes by products? We have multiple domains in one instance, and we want a single unsubscribe page for each company product so that if they are unsubsribed from product A by brand A they are still qualified to receive emails from product B by Brand B.

Has anyone achieved this in a scalable manner?

Ariel Sasso
1 ACCEPTED SOLUTION

Accepted Solutions
SanfordWhiteman
Level 10 - Community Moderator

Re: Custom Unsubscribe By Business Unit

But for achieving the above scenario. you have to create multiple unsubscribed fields, 1 for each business unit.

You don't need multiple subscription fields. It might seem easier to manage in the Marketo UI if you do it w/separate fields, at least at first, but as the number of possible subs increases a single multivalued field becomes more practical.

Also, a single segmentation won't work, since the same person can only be in one segment at a time, and the explicit requirement here is that someone can be unsub'd from one and sub'd to another. You could use multiple segmentations though, if you have enough to spare.

View solution in original post

8 REPLIES 8
SanfordWhiteman
Level 10 - Community Moderator

Re: Custom Unsubscribe By Business Unit

It's not necessarily h​a​r​d on the input side: if it's just a small number of BUs you can use individual checkbox fields and hide the inapplicable ones (based on query params) with a little JS+CSS.

The prob I think is a procedural one: getting people to include the right field in Smart Lists instead of relying on the system field.

Dominique_Gilli
Level 2

Re: Custom Unsubscribe By Business Unit

@SanfordWhiteman can you elaborate on the solution you propose?

Dominique Gaillard
SanfordWhiteman
Level 10 - Community Moderator

Re: Custom Unsubscribe By Business Unit

@SanfordWhiteman can you elaborate on the solution you propose?


Well, the simplest way (without even any custom JS or CSS) is to have a String field Business Unit that's a Hidden field on the form, Auto-Filled from a query param. Then use Visibility Rules to show only the Business Unit-specific unsubscribe.

Josh_Hill13
Level 10 - Champion Alumni

Re: Custom Unsubscribe By Business Unit

There are a lot of threads on multi BU situations like this as well as subscription management. Take a look at those and Sanford's suggestion.

Grégoire_Miche2
Level 10

Re: Custom Unsubscribe By Business Unit

As Sanford wrote, the key issues is to have the users using the preferences as filters.

Vote here for a mechanism that automates the blocking of emails when some fields a checked:

With the GDPR, everyone is now setting up preferences centers, which drives an urgent need for this mechanism.

-Greg

Anonymous
Not applicable

Re: Custom Unsubscribe By Business Unit

You may try creating different multiple check box fileds, one for each business unit in the forms so that a lead unsubscribes from on business unit it does not unsubscribes from the other and then You can create a segment for all the marketable leads for each business unit.

For eg: If a person has Unsubscribed for business unit A.

Segment for business unit B will check a lead only for unit B. It will not matter whether he is subscribed or unsubscribed for  A.

But for achieving the above scenario. you have to create multiple unsubscribed fields, 1 for each business unit.

Thanks

Grégoire_Miche2
Level 10

Re: Custom Unsubscribe By Business Unit

This what Sanford suggested already, although is a more laconic style But this does not remove the key pain point about relying on user discipline to comply with preferences.

-Greg

SanfordWhiteman
Level 10 - Community Moderator

Re: Custom Unsubscribe By Business Unit

But for achieving the above scenario. you have to create multiple unsubscribed fields, 1 for each business unit.

You don't need multiple subscription fields. It might seem easier to manage in the Marketo UI if you do it w/separate fields, at least at first, but as the number of possible subs increases a single multivalued field becomes more practical.

Also, a single segmentation won't work, since the same person can only be in one segment at a time, and the explicit requirement here is that someone can be unsub'd from one and sub'd to another. You could use multiple segmentations though, if you have enough to spare.