Hello,
Our current setup for optout is through Services and Subscriptions. We get profiles in real time in those subscriptions and then exclude customers in wkfs based on if they are present or not in those lists:
Here is the filter we use in marketing wkf for excluding customers that opted-out from survey communication:
Now my question is:
Is it possible to implement this rule in the target mapping for recipient so we check these lists instead or how can we do it?
Right now we use old @blacklist attributes that are not updated anymore so we need to change this:
I cannot find the NmsSubscription table when trying to change this expression.
トピックはコミュニティのコンテンツの分類に役立ち、関連コンテンツを発見する可能性を広げます。
表示
返信
いいね!の合計
Hello @ParthaSarathy and thanks.
How would you do it? I'm guessing that we need a new attribute in nms:delivery table that specify the optout category for the given delivery template. Today we have a customized attribute on the template that we use when specifying a optout category:
表示
返信
いいね!の合計
@A_B_SE , you can create a 'filtering' rule type typology rule and in filter you can select the 'service and subscription' in 'Filter' (tab) > Edit the query from targeting dimension > you can select a predefined filter if you have (or can create it) or use subscribers of a service.
Then, add this typology rule in your typology and configure the same typology in delivery property's typology tab.
@ParthaSarathy I would need to add in the filtering that if @userPreference = Event then subscriptions equal to OptoutEvent if you understand what I mean. I cannot choose though userPreference field since it is a field created in a particular schema:
表示
返信
いいね!の合計
Hi @A_B_SE, you can use Filtering rule suggested by Parthasarathy.
Create a rule, choose the 'Subscribers of an information service' and choose the service. Or if you want to add custom rules from subscription services table, you can navigate from nms:recipient -> Subscriptions(nms:subscriptions) table and configure your query.
The screenshot you shared above for the schema - that should have your content of the delivery and all other parameters of the delivery. It is not related to the recipient dimension. You do not have to use the schema(newsletter2019) to check recipient subscription as that will have only delivery information. Hope that helps.
Hello @somasundaram_h , I get what you are saying but I need to apply different rules based on the delivery template (userPreference attribute in newsletter2019 schema).
For example:
if userPreference = X then typology rule X applies
if userPreference = Y then typology rule Y applies
表示
返信
いいね!の合計
Any input @ParthaSarathy ?
表示
返信
いいね!の合計