Issue in Reconciliation workflow of Triggers

Avatar

Avatar

Senthil24

Avatar

Senthil24

Senthil24

12-05-2017

Hi ,

we are working on marketing cloud triggers and campaign. We came across this article 

https://helpx.adobe.com/campaign/kb/triggers-and-campaign.html and following the guidelines and help of adobe support we have set up the Triggers configuration at the campaign side .

we are able to receive the Triggers data from analytics , it is visible in Pipeline events folder. However we are facing some issue in the reconciliation workflow.

PFA the details of the issue..

Any help is appreciated.

Senthil

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

Amit_Kumar

MVP

Avatar

Amit_Kumar

MVP

Amit_Kumar
MVP

14-05-2017

Hi Senthil,

I agree with Adhiyan, the information you provided is not enough. Although a quick tip, it's seems your enrichment is not correctly configured; you should remove the identify the document as recipient and use the refine the data using the additional data i.e using link you can add a inner join which will give you desired results or use split or intersection activity first to test it.

Regards,

Amit

Answers (3)

Answers (3)

Avatar

Avatar

Senthil24

Avatar

Senthil24

Senthil24

23-05-2017

Hi Florent,

Not yet. We are working on this. Meanwhile please let us know your suggestions for resolution.

Regards,

Senthil

Avatar

Avatar

florentlb

Total Posts

1.1K

Likes

235

Correct Answer

239

Avatar

florentlb

Total Posts

1.1K

Likes

235

Correct Answer

239
florentlb

22-05-2017

Hi Senthil,

Have you been able to resolve your issue?

Please let us know,

Florent.

Avatar

Avatar

Adhiyan

Employee

Avatar

Adhiyan

Employee

Adhiyan
Employee

12-05-2017

Hi Senthil,

This will need a deeper look into the workflow design and schema details . The attribute username is not OOTB in nms:recipient so we need to check how the structure is updated and many other things.

It will be best if you can open a support ticket regarding this. Else , please share the workflow logs so that we can guide further.

HINT : You can enable SQL logging to see the exact query being fired on Database and we can have some idea about where the data is getting lost.