Expand my Community achievements bar.

Never miss an update of the Adobe Journey Optimizer Community Lens! Subscribe now to get the latest updates, insights, and highlights delivered straight to your inbox every time a new edition drops.
SOLVED

Batch Decisioning API questions

Avatar

Level 10

Is it possible:

- to write output to custom dataset? In UI available in only system dataset - in API dos I see that it might be custom 

- activate that dataset to cloud destination? Would like to confirm 😄 

- is it possible to somehow schedule it to run it repeatably? 

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Michael_Soprano 

- to write output to custom dataset? In UI available in only system dataset - in API dos I see that it might be custom -

While the AJO UI restricts dataset selection to the "Offer Decisioning Export" dataset (which is system-managed), the Batch Decisioning API provides more flexibility, allowing you to specify a custom datasetId directly in its payload.

- activate that dataset to cloud destination? - Yes you can do that. It will be in the AEP data lake and activated through cloud destinations. If it's a system dataset not available to export the work around is to use data distiller and copy what you need to another dataset and then export it to cloud destinations.

- is it possible to somehow schedule it to run it repeatably? - No. It's based on the profile snapshot that runs once a day.

  • The number of running batch jobs per dataset: Up to five batch jobs can be run at a time, per dataset. Any other batch requests with the same output dataset are added to the queue. A queued job is picked up to process once the previous job has finished running.
  • Frequency capping: A batch runs off of the profile snapshot that occurs once a day. The Batch Decisioning API caps the frequency and always loads profiles from the most recent snapshot.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/api...

 
Thanks, Sathees

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

@Michael_Soprano 

- to write output to custom dataset? In UI available in only system dataset - in API dos I see that it might be custom -

While the AJO UI restricts dataset selection to the "Offer Decisioning Export" dataset (which is system-managed), the Batch Decisioning API provides more flexibility, allowing you to specify a custom datasetId directly in its payload.

- activate that dataset to cloud destination? - Yes you can do that. It will be in the AEP data lake and activated through cloud destinations. If it's a system dataset not available to export the work around is to use data distiller and copy what you need to another dataset and then export it to cloud destinations.

- is it possible to somehow schedule it to run it repeatably? - No. It's based on the profile snapshot that runs once a day.

  • The number of running batch jobs per dataset: Up to five batch jobs can be run at a time, per dataset. Any other batch requests with the same output dataset are added to the queue. A queued job is picked up to process once the previous job has finished running.
  • Frequency capping: A batch runs off of the profile snapshot that occurs once a day. The Batch Decisioning API caps the frequency and always loads profiles from the most recent snapshot.

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/decisioning/offer-decisioning/api...

 
Thanks, Sathees