For Email Channel, in status column of Proposition table Presented is not coming but accepted is coming.

Avatar

Avatar

Greeshma_Sampath1

Avatar

Greeshma_Sampath1

Greeshma_Sampath1

30-12-2020

Hi Team,

1. For Email Channel Offer, we are trying to get other status that can be populated on the proposition table based on the level of interaction with the donor. Some Example of what we are trying to get is,

    • Ex1: If the proposition is simply sent to the donor it would = Generated
    • Ex1: if the donor opens the email and sees the proposition it would = Presented
    • Ex2: If the donor opens the email and clicks on the offer hyperlink it would = accepted

In our testing, we are able to get the "Accepted" status in proposition tables status column when the donor clicks on the offer link in the email. But when the donor opens the mail without clicking the offer link, we are getting status as "Generated" instead of getting "Presented" as status in proposition table.

 

Below shown is the offer space storage setting we did.

Offer Space storage.JPG

 
 

 

 

2.  In case of outbound interaction how can we apply "Interested" or "Rejected" or any other status to an offer proposition other than the 2 added in the storage tab in offer space?

 

3. Can someone also please tell me how to add the below-mentioned statement in Offer/Offer space?And also how to use this for other statuses if it is only for 'Interested'?

outbound1.JPG

 

Thanks.

 

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

wodnicki

MVP

Avatar

wodnicki

MVP

wodnicki
MVP

01-01-2021

Hi,

 

  1. Make a periodic workflow that reads open/click events out of nms:trackingLogRcp and updates the matching nms:propositionRcp entries with Presented/Accepted status (key=recipientId+deliveryId). Should be how things work ootb though.
  2. Offline hacking, as above.
  3. OOTB urlType 11 is coded 'Proposition update' and is the only one available in the enum. You can add more enums in schema extension and map them with the workflow approach above. Using a workflow on top of the whole system is much easier and safer than altering nms:offer.js.

 

Thanks,

-Jon

Answers (0)