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.
Is this expected or a bug?
If its expected, what is the reason for not having the Campaign link on the continuous delivery?
Solved! Go to Solution.
Views
Replies
Total Likes
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
Views
Replies
Total Likes
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
Views
Replies
Total Likes
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
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Replies
Total Likes
@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();
Views
Replies
Total Likes
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies