New broadlog status for custom deliveries

Avatar

Avatar

Florian_Courgey

MVP

Avatar

Florian_Courgey

MVP

Florian_Courgey
MVP

03-07-2020

Hi,

 

We would like to add new broadLogRcp status for custom Phoning deliveries:

- To contact (by phone call) => equivalent to standard "pending" status 

- Contacted with success (by phone call) => "sent"

- Contacted with failure (by phone call) => "failed"

and 10 other status with either pending/sent/failed meaning.

 

We could successfully extend the nms:broadLog enum with:

- cus:broadLog <enumeration name="deliveryStatus"><value label="To contact (by phone call)" name="toContact" value="10"/>

- cus:broadLogRcp <element name="broadLogRcp" template="cus:broadLog">

 

It works well and we can read/update our broadlogs with custom status.

 

However, it is not mapped to the delivery statistics which are all set to 0:

20200703-113638-screenshot-3.jpg

 

I believe there is a mapping between broadlog status and delivery indicators "to send"/"processed"/"success"/"errors", but how to edit this mapping?

 

We found nothing in config: service provider/target mapping/data schema/option/js api recomputeStats/tracking workflow...

 

Do you have any lead? How the indicators are computed? All the status seem to be hard coded in https://docs.adobe.com/content/help/en/campaign-standard/using/reporting/about-reporting/indicator-c...

 

Best regards

Florian

broadlog custom custom delivery status

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

wodnicki

MVP

Avatar

wodnicki

MVP

wodnicki
MVP

04-07-2020

Hi,

 

Yes, the math is hardcoded in the nlserver binary: RecomputeStats.

Easy way to make it work is align your enum with the ootb one, e.g. @Status = 1 means 'sent' in both definitions, and use the same field names, i.e. @Status.

If that's not possible, just diy the aggregates in a periodic workflow: scheduler -> query activity with counts and conditional sums (for sent: sum(iif(@status=1, 1, 0)) -> update nms:delivery. The ootb system will interfere with this, so turn it off by using a db trigger to set the @DIRTY field in nms:delivery to constant 0 for custom deliveries.

 

Thanks,

-Jon

Answers (1)

Answers (1)

Avatar

Avatar

Florian_Courgey

MVP

Avatar

Florian_Courgey

MVP

Florian_Courgey
MVP

05-08-2020

Thanks @wodnicki , I confirm your solution works. We ended up with the following workflow:

20200805-165234-screenshot-11.jpg

 

that updates the following fields:

  • [indicators/@dirty] = 0 (Up To Date)
  • [indicators/@sent]
  • [indicators/@success]
  • [indicators/@processed]
  • [indicators/@error]
  • [properties/@toDeliver]

The Enrichment activity creates 3 column, one for each stat with an Aggregate Count(@id):

20200805-165607-screenshot-12.jpg

 

This way, we are able to configure it with the standard query editor, instead of a db trigger.

 

It ends up with well formated delivery stats:

20200805-165806-screenshot-13.jpg

 

Thank you

Florian