Displaying Ads on the placement via API
Explains the process from requesting ads to displaying them using the API.
Ads Integration
There are two ways to request ads on the A2 platform: directly calling the Decision API or using the Web SDK. Directly calling the Decision API has the advantage of being able to directly control most aspects of the ad request, but it is relatively more complex because you need to develop both the process of requesting and displaying ads, as well as integrating logs.
Preparation
Before requesting ads via API, ad placement must be completed. Please refer to the guide below.RetryClaude can make mistakes. Please double-check responses.
Ad Request
The tagid required when calling the Ad Serving API is the id
in the Placement Information
section on the detail page of Ads > Placements > Placement List > (Click on placement)
.
If you are currently using A2 service, you can directly test the actual service API using the Developer Portal.
Displaying Ad
When the ad serving API responds normally, you can obtain results like the following.
You must proceed with appropriate impression processing using the received ad data.
When using the web SDK, materials are actually displayed according to the placement settings, but when using the API, you must directly implement the business logic needed for impressions. It is strongly recommended that the work required for impressions be done on the server side rather than on the service app or web side.
If you need additional support, you can contact the A2 support team through the following channels:
- Email: a2support@aiderx.io
- Slack: https://a2cloudsupporthub.slack.com