A/B test - Final send broadlog fields not populated

[#1]

I ran an A/B test and it chose the proper winner for the final send and completed the delivery.  The extended broadlog fields were populated from the enriched target data appropriately for the initial sends, but not for the final delivery.  Do I need to add something to the JavaScript to populate the extended broadlog fields for the final delivery since it didn't pick them up from the Enrichment?

[#2 · Accepted solution]

@pfrew 

If you have extended your broadlog, you may have used different target mapping(and different storage for broadlog and tracking logs), but the code you used will only use out of the box target mapping, and OOTB recipient broadlog. Hence it was not able to add the data to OOTB broadlog which does not have those fields. You may have to update targetmapping for this winner delivery using jscode. Something like-

delivery.mapping_id=primary key of target mapping you have used for first two deliveries. 

[#3]

Hi @pfrew,

Were you able to resolve this query with @prasannakumarmarru 's given solution? Do let us know.

Thanks!

[#4]

@_Manoj_Kumarthe final delivery sent just fine.  The issue I'm asking about is that the enriched target data fields (i.e. @initiativeName) from Enrichment 3 did not get added to the extended broadlog fields for the 'final' send like it did for the test sends.

[#5]

Hello @pfrew 

Your final delivery didn't go out because in the JS code, you have used validationMode as manual.

The delivery is waiting for your confirmation. Go to the campaign dashboard and click the confirm delivery button.

Thanks,