Issue in Reconciliation workflow of Triggers

Avatar

Avatar
Validate 10
Level 3
Senthil24
Level 3

Likes

21 likes

Total Posts

67 posts

Correct reply

2 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
Senthil24
Level 3

Likes

21 likes

Total Posts

67 posts

Correct reply

2 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
Senthil24
Level 3

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
Springboard
MVP
Amit_Kumar
MVP

Likes

329 likes

Total Posts

649 posts

Correct reply

231 solutions
Top badges earned
Springboard
Ignite 5
Ignite 3
Ignite 1
Validate 10
View profile

Avatar
Springboard
MVP
Amit_Kumar
MVP

Likes

329 likes

Total Posts

649 posts

Correct reply

231 solutions
Top badges earned
Springboard
Ignite 5
Ignite 3
Ignite 1
Validate 10
View profile
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
Validate 10
Level 3
Senthil24
Level 3

Likes

21 likes

Total Posts

67 posts

Correct reply

2 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile

Avatar
Validate 10
Level 3
Senthil24
Level 3

Likes

21 likes

Total Posts

67 posts

Correct reply

2 solutions
Top badges earned
Validate 10
Validate 1
Boost 5
Boost 3
Boost 10
View profile
Senthil24
Level 3

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
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile

Avatar
Give Back 50
Level 10
florentlb
Level 10

Likes

237 likes

Total Posts

1,109 posts

Correct reply

239 solutions
Top badges earned
Give Back 50
Give Back 5
Give Back 3
Give Back 25
Give Back 200
View profile
florentlb
Level 10

22-05-2017

Hi Senthil,

Have you been able to resolve your issue?

Please let us know,

Florent.

Avatar

Avatar
Establish
Employee
Adhiyan
Employee

Likes

241 likes

Total Posts

343 posts

Correct reply

124 solutions
Top badges earned
Establish
Give Back 50
Give Back 25
Give Back 10
Give Back 5
View profile

Avatar
Establish
Employee
Adhiyan
Employee

Likes

241 likes

Total Posts

343 posts

Correct reply

124 solutions
Top badges earned
Establish
Give Back 50
Give Back 25
Give Back 10
Give Back 5
View profile
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.