operation-id (Campaign) link is empty for Continuous...

[Darren_Bowers]

I have noticed that @Operation-id is "0" for all Continuous deliveries. Normal deliveries or recurring deliveries have the @Operation-id link to the parent campaign as normal. These then have blank Campaign values over in Analytics, so analysts have to do different searches to wrap up deliveries at the Campaign level.

https://experienceleaguecommunities.adobe.com/t5/adobe-campaign-classic-questions/looking-for-delive...

Is this expected or a bug?

If its expected, what is the reason for not having the Campaign link on the continuous delivery?

[DavidKangni · Accepted solution]

Hi Darren,

It's expected for deliveries under actions tab as they can be use in standalone workflows (workflows not linked to a campaign).

If you need to attached them just add a js activity after the delivery and write a code.

delivery.operation_id = instance.operation_id;

Thanks

David

[Darren_Bowers]

Thanks @DavidKangni - Surely a delivery can tell if there is a parent Campaign to associate itself with? Having to add Javascript to every continuous delivery workflow, seems kind of...hacky?

[DavidKangni]

Hi Darren,

deliveries under Deliveries tab are automatically attached to Campaign. But deliveries under actions tab are not automatically linked as you can linked them in the technical workflows.

So if you want to use them in a campaign, then you need to use a code.

Thanks

David

[DimitrisChatzos]

Hey, The continues delivery dont have a delivery delivery script so where should i put that code?

[DimitrisChatzos]

the code doesnt work if i put in a java script activity after the continuous delivery: delivery.operation_id = instance.operation_id;

[Darren_Bowers]

@DimitrisChatzosThe full code you need to insert after the delivery is

var delivery = NLWS.nmsDelivery.load(vars.deliveryId);
delivery.operation_id=instance.operation_id;
delivery.workflow_id=instance.id;
delivery.save();

[dimitriosc21803]

Yes, that is working fine. Thanks a lot for that 😊