Get started with offer delivery APIs about-decisioning-apis

You can deliver offers using either the Decisioning or the Edge Decisioning API. Additionally, the Batch Decisioning API allows you to deliver offers to all profiles in a given audience in one call. The offer content for each profiles in the audience is placed in an Adobe Experience Platform dataset where it is available for custom batch workflows.

In this page, you will find information on specific functionalities that are available with the Decisioning and Edge Decisioning APIs. While both allow you to deliver offers to your customers, we recommend using the Edge Decisioning API whenever possible for inbound use cases and to ensure better latency and throughput on your platform.

For more information on how to work with the APIs, refer to these sections:

Edge Decisioning API capabilities edge

Unique request for experience events and decisioning requests

With the Edge Decisioning API, you can send in one single request the experience event itself along with the decisioning request, rather than having two different requests.

For example, if a customer visits your website, the request will include the experience event (the customer’s visit to the page), and get an offer back to populate the visited page.

Context data storage into Adobe Experience Platform

Context data refers to data that you only know at the time you want an offer back. For example, the color of the purchased article, the weather at the time of the purchase, etc.

When passing context data with an Edge Decisioning API request, data is stored into the Adobe Experience Platform profile, allowing future reuse.

Frequency capping counter update

If frequency capping has been enabled for some of your offers to define how often their capping count is reset, the counter is updated and available in an Edge Decisioning API decision in less than 3 seconds. Learn how to add constraints to an offer

Decisioning API capabilities decisioning

The functionalities listed below are only available with the Decisioning API. If you need to leverage one of them to meet your requirements, use the Decisioning API. Otherwise, we recommend using the Edge Decisioning APIs.