Expand my Community achievements bar.

SOLVED

Datafeed not exported to S3 bucket

Avatar

Level 2

Hi All,

I setup one S3 destination dataflow and activated one segment using profile attributes.

As per schedule dataflow runs and it get success, however I can see zero profiles received and not seen any files on S3 bucket folder.

Please help here.

shubham10_0-1676292555682.png

 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@shubham10 Interesting, I just tested it on my instance, and it worked without any issues.

Manoj_Kumar__0-1676352453490.png

 

The only possible things that can happen are.

  • segment is not evaluated before activation data flow run.
  • Policy violation
  • Missing attributes

You won't see any information in the first point, but monitoring should show some reason for the last 2 points.


     Manoj
     Find me on LinkedIn

View solution in original post

7 Replies

Avatar

Community Advisor

Hello @shubham10 

 

I believe you are using a batch segment type and Evalution did not happen before the data flow run and that is why you don't see any export.


     Manoj
     Find me on LinkedIn

Avatar

Level 2

Hi Manoj,
Thanks for your response. We are using batch segment only and before dataflow runs we 're qualifying the segment using on-demand evaluation API.

POST: https://platform.adobe.io/data/core/ups/segment/jobs

Avatar

Community Advisor

Hello @shubham10 

 

Then check the data flow details. May be the identities were excluded because of some policy violation.

 

You should be able to see the details of run and exclusions under monitoring.


     Manoj
     Find me on LinkedIn

Avatar

Level 2

Hi Manoj,

We are not using any marketing action or duel policies and also in dataflow details we are not seeing any excluded identities or any error.

Avatar

Correct answer by
Community Advisor

@shubham10 Interesting, I just tested it on my instance, and it worked without any issues.

Manoj_Kumar__0-1676352453490.png

 

The only possible things that can happen are.

  • segment is not evaluated before activation data flow run.
  • Policy violation
  • Missing attributes

You won't see any information in the first point, but monitoring should show some reason for the last 2 points.


     Manoj
     Find me on LinkedIn