Identify opt-out delivery_id | Community
Skip to main content
Milan_Vucetic
Milan_Vucetic
Level 9
September 16, 2019
Solved

Identify opt-out delivery_id

  • September 16, 2019
  • 3 replies
  • 5084 views

Hi all,

What is the best way to identify delivery_id from which customer started opt-out? I want to enrich each opt-out record from subHisto table with delivery_id from which customer done opt-out?

I assume that tracking data is needed for this. Note that customer can reiceive multiple deliveries from same or different service and I need to pick correct one.

Thanks in advance.

Regards,

Milan

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Jean-Serge_Biro

Hi Milan,

Please use [url/@type] from nms:trackingLogRcp with value = optout in your Query activity.

That is for the unsubscribe link in a delivery that leads either to directly set nms:recipient.@blacklist to 1, or per blacklist per channel, or nly unsubscribe for a dedicated service (and so subHisto data) if you define a webApp for questioning about unsubscribe reasons or unsubscription from specific services.

But there is another use case, it is when the contact unsubscribes by using the client mail functionality instead the unsubscribe link.
So the feedback_loop process sets the recipient.blacklist automatically.


Regards
J-Serge

3 replies

kapilKochar
kapilKochar
Level 6
September 17, 2019

Hi ,

*Thinking out loud*

In delivery schema under indicator there is one attribute

<attribute desc="Total count of clicks on the unsubscription link" label="Opt-Out" name="optOut" type="long"/>

This calculates total count of click on Unsub links, So if you use this and build you logic like

if indicators/@optOut >0, select deliveryID .

Thanks,

Kapil

    Milan_Vucetic
    Milan_VuceticAuthor
    Level 9
    September 17, 2019

    Hi Kapil,

    this is helpful but this is on delivery level.
    Right now, in the join, there is one customer with three deliveries where @optOut>0 therefore what to choose?

    Regards,

    Milan

    Jean-Serge_Biro
    Jean-Serge_BiroAccepted solution
    Level 10
    September 17, 2019

    Hi Milan,

    Please use [url/@type] from nms:trackingLogRcp with value = optout in your Query activity.

    That is for the unsubscribe link in a delivery that leads either to directly set nms:recipient.@blacklist to 1, or per blacklist per channel, or nly unsubscribe for a dedicated service (and so subHisto data) if you define a webApp for questioning about unsubscribe reasons or unsubscription from specific services.

    But there is another use case, it is when the contact unsubscribes by using the client mail functionality instead the unsubscribe link.
    So the feedback_loop process sets the recipient.blacklist automatically.


    Regards
    J-Serge

    Terms & ConditionsAccessibility statement

    Loading footer...