New broadlog status for custom deliveries | Community
Skip to main content
F
Florian_Courgey
Level 4
July 3, 2020
Solved

New broadlog status for custom deliveries

  • July 3, 2020
  • 2 replies
  • 3137 views

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:

 

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-calculation.html

 

Best regards

Florian

    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 Jonathon_wodnicki

    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. @2498346 = 1 means 'sent' in both definitions, and use the same field names, i.e. @2498346.

    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 @12785342 field in nms:delivery to constant 0 for custom deliveries.

     

    Thanks,

    -Jon

    2 replies

    Jonathon_wodnicki
    Community Advisor
    Jonathon_wodnickiCommunity AdvisorAccepted solution
    Community Advisor
    July 5, 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. @2498346 = 1 means 'sent' in both definitions, and use the same field names, i.e. @2498346.

    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 @12785342 field in nms:delivery to constant 0 for custom deliveries.

     

    Thanks,

    -Jon

      Jonathon_wodnicki
      Community Advisor
      Jonathon_wodnickiCommunity Advisor
      Community Advisor
      July 6, 2020
      Yes but you don't know the timing of whatever's setting it to 1. Cleanest to fix the col so it's always 0.
      F
      Florian_CourgeyAuthor
      Level 4
      August 5, 2020

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

       

      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):

       

      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:

       

      Thank you

      Florian

        Terms & ConditionsAccessibility statement

        Loading footer...