1. Prepare the example template
Use the same environment and AdUnit ID that returned an HTTP200 ad response in the Quickstart. Prepare a web browser and Python 3. Ad requests and click delivery do not require an access token.
Create a folder for the example file.
~/a2-banner-example/banner-ad.html using your text editor.
View and copy the HTML template
View and copy the HTML template
~/a2-banner-example folder containing the file. Port 9000 avoids a conflict with the A2 server.
2. Request and display the ad
Fill in the template’s fields and select Load ad once. You do not need to edit the HTML source.Ad request: HTTP 200, Rendering: complete, and the A2 banner. Expand Response JSON to inspect the complete response for this request.
This page requests a new ad. It stores the ext.ad_log from the ad response displayed on the page and sends it automatically when the banner is clicked. For HTTP 204, follow the Ad Serving Quickstart checklist.
imp event.3. Send the click event
Click the displayed banner once. Confirm thatexample.com opens in a new tab and the exercise page shows Click delivery: HTTP 200 — check metrics.

The shared template after entering the server URL and AdUnit ID and verifying banner rendering and click delivery.
POST /dmp/v0/log with that ad’s ad_log. The page has already sent it; do not send it again from the terminal.
200 does not guarantee collection or aggregation, so continue through the metrics check.
4. Verify recorded impressions and clicks
Open AdUnit Analytics
Select the exercise AdUnit and period
Quickstart banner. Include the exercise date in the query period. Align dates to Asia/Seoul when comparing with the console.Compare with expected counts

The Basic Analysis view of an ad unit in AdUnit Analytics. Check the date range and impression and click counts. Values shown are examples.
Completion criteria
- The banner response contains an image, landing URL, and
ext.ad_log. - The page displays the banner, and clicking opens the landing page.
- You have checked the click request and HTTP response.
- You have verified actual impression and click aggregates in AdUnit Analytics.
Troubleshooting
Requests succeed in the terminal but fail in the browser
Requests succeed in the terminal but fail in the browser
http://localhost:9000; duplicate Access-Control-Allow-Origin headers cause the browser to block the response.Click counts do not increase
Click counts do not increase
Impressions or clicks exceed expectations
Impressions or clicks exceed expectations
