Stop the delivery if target has been deleted from the recipient table | Community
Skip to main content
G
gunjans6748888
New Participant
July 19, 2018
Solved

Stop the delivery if target has been deleted from the recipient table

  • July 19, 2018
  • 9 replies
  • 5839 views

Hi All,

How can we delete a delivery if the target has been deleted from the recipient table. We are trying to make environment GDPR ready. So, if a customer requests us to delete his/her records, how can we make sure that the scheduled deliveries, pertaining to him, also gets deleted/stopped.

Thanks,

Gunjan

    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 david--garcia

    Hi Gunjan,

    I've not had time to test it thoroughly but it should work in theory, you can have a look at the typology's section in the documentation.

    https://docs.campaign.adobe.com/doc/AC/en/CMP_Campaign_Optimization_About_campaign_typologies.html

    Around the following lines, you add a custom rule, add that to your typology used in the campaigns, specify the channel or all channels. so anyone who exists in the privacy request schema will be excluded. you need to play around with the reconciliation value.

    9 replies

    G
    gunjans6748888Author
    New Participant
    July 25, 2018

    Sure thing David. Thanks a lot!

    david--garcia
    david--garciaAccepted solution
    New Participant
    July 25, 2018

    Hi Gunjan,

    I've not had time to test it thoroughly but it should work in theory, you can have a look at the typology's section in the documentation.

    https://docs.campaign.adobe.com/doc/AC/en/CMP_Campaign_Optimization_About_campaign_typologies.html

    Around the following lines, you add a custom rule, add that to your typology used in the campaigns, specify the channel or all channels. so anyone who exists in the privacy request schema will be excluded. you need to play around with the reconciliation value.

    G
    gunjans6748888Author
    New Participant
    July 24, 2018

    Thanks David, I might sound like a noob. But, could you please guide me how to do that.

    david--garcia
    david--garcia
    New Participant
    July 20, 2018

    You can also explore adding a new rule to your campaign's typology, by filtering out any recipient which is set for deletion and exist in the privacy requests targeting dimension.

    G
    gunjans6748888Author
    New Participant
    July 20, 2018

    Hi Adhiyan,

    Could you please guide me how to do this part 'have a simple personalization condition based on the recipient table in the delivery content so that if the recipient is not present , the message sending to that recipient will fail.'

    Adhiyan
    Adhiyan
    Employee
    July 20, 2018

    Hi Gunjan,

    because there is no PII information stored in that table. GDPR workflows only take into consideration tables where we have PII data.

    To answer , your initial query you can rather schedule the workflow so that only the current target is picked up by the delivery or have a simple personalization condition based on the recipient table in the delivery content so that if the recipient is not present , the message sending to that recipient will fail.

    Regards,
    Adhiyan

    G
    gunjans6748888Author
    New Participant
    July 20, 2018

    Hi Adhiyan,

    The XML is showing the schduled delivery in nms:broadLogRcp table. However, after processing, I can still see the scheduled delivery.

    why is it not taking nms:delivery into consideration?

    G
    gunjans6748888Author
    New Participant
    July 19, 2018

    Thank you Adhiyan!!

    Adhiyan
    Adhiyan
    Employee
    July 19, 2018

    Hi Gunjan,

    For taking care of the GDPR compliance , Campaign provides a separate package altogether which will take care of all Data deletion requests automatically.

    Please read this documentation to understand how it works :

    Campaign Classic - General Data Protection Regulation

    Regards,

    Adhiyan

      Terms & ConditionsAccessibility statement

      Loading footer...