We’ve developed some resources to help you work effectively from home during COVID-19 Click to learn more

What is the correct way to influence the 'isMailingRecipient' Person attribute?

Hi,

I import selection members (entity dynamicPerson) from SuperOffice storage to our internal system. What is really important for us is handle the unsubscribe process by the correct way.

I am fetching data from API:

/api/v1/Archive/ContactDynamicSelection?$filter=selectionId=ID&$format=JSON

I check the attribute 'isMailingRecipient' during the import process.

But this attribute is always set to 'true' even:

  • I've unsusbcribed my person via SuperOffice unsusbcribe link
  • I've set 'NoMailing' attribute to true via PUT /api/v1/Person/ID

I can't send another email to my unsubscribed contact in SuperOffice but how I can detect this status in the source API? (/api/v1/Archive/ContactDynamicSelection)

Environment: sod2.superoffice.com

Thanks!

RE: What is the correct way to influence the 'isMailingRecipient' Person attribute?

Hi Stanislav,

did you check the list of fields available here: https://community.superoffice.com/documentation/sdk/SO.NetServer.Web.Services/html/Reference-ArchiveProviders-ContactDynamicSelectionArchiveProvider.htm

At the bottom you will find those regarding consent, like hasEmarketingConsent which is the former field "No mailing" after GDPR:

https://community.superoffice.com/en/customer/news/product/superoffice-8.2/consent-management/

When you import a person you set it via: https://community.superoffice.com/documentation/sdk/SO.NetServer.Web.Services/html/v1PersonAgent_SetConsent.htm

And look it up via: https://community.superoffice.com/documentation/sdk/SO.NetServer.Web.Services/html/v1PersonAgent_HasConsent.htm

Does this answer your question? 

Av: Margrethe Romnes 31. maj 2019

RE: What is the correct way to influence the 'isMailingRecipient' Person attribute?

Hi, thanks for your feedback! 

I've checked the consents functionality but the problem is still the same. The API does not reflect person settings:

https://community.superoffice.com/documentation/sdk/SO.NetServer.Web.Services/html/Reference-ArchiveProviders-ContactDynamicSelectionArchiveProvider.htm

Steps to reproduce:

1. Set person consent:

URL: /api/v1/Agents/Person/SetConsent
DATA: {"PersonId": 222,"Purpose": "EMARKETING","Source": "et","LegalBase": "61A","Comment": "rerum"}
STATUS: 204

2. Check person consent status:

URL: /api/v1/Person/222/Consent/EMARKETING
DATA: true
STATUS: 200

3. Call contact dynamic selection and check the 'hasEmarketingConsent':

URL: /api/v1/Archive/ContactDynamicSelection?$filter=selectionId=22
DATA: {"PrimaryKey": "222","EntityName": "dynamicPerson","personEmail/emailAddress": "contact1@03J.com","hasStoreConsent": true,"hasEmarketingConsent": true,"isMailingRecipient": true}
STATUS: 200

4. Remove person consent:

URL: /api/v1/Agents/Person/RemoveConsent
DATA: {"PersonId": 222,"Purpose": "EMARKETING"}
STATUS: 204

5. Check person consent status:

URL: /api/v1/Person/222/Consent/EMARKETING
DATA: false
STATUS: 200

6. Call contact dynamic selection and check the 'hasEmarketingConsent':

URL: /api/v1/Archive/ContactDynamicSelection?$filter=selectionId=22
DATA: {"PrimaryKey": "222","EntityName": "dynamicPerson","personEmail/emailAddress": "contact1@03J.com","hasStoreConsent": true,"hasEmarketingConsent": true,"isMailingRecipient": true}
STATUS: 200

The value from step 5 and the value from step 6 are not corresponding.

Am I doing somethin wrong? If yes, please tell me what because I expect these two APIs should provide the same values:
/api/v1/Person/222/Consent/EMARKETING
/api/v1/Archive/ContactDynamicSelection?$filter=selectionId=22

Environment: https://sod2.superoffice.com

Thanks.

Av: Stanislav Jurica 3. jun 2019

RE: What is the correct way to influence the 'isMailingRecipient' Person attribute?

Hi Stanislav, that is a bug, it's been logged as issue id 64832

Av: Margrethe Romnes 5. jun 2019