​
Advertising Log Integration

To achieve effective ad modeling and metric tracking, Advertising Log Integration is essential. This integration can be performed through two methods: web-based and API-based. Each method allows the collection and analysis of logs for ad requests, impressions, clicks, and conversions. Below, we explain each approach.

​
Using Web SDK

If you are using the Web SDK, no separate ad log integration work is required.

​
Using API

The ad log integration method using API is a way to directly integrate logs for various actions such as ad impressions, conversions, and clicks. In A2, logs are tracked based on the ext.ad_log field in the ad serving response data, and impression logs can also be integrated as needed for ad effectiveness analysis.

  1. Endpoint

  2. Example

    • Click Logs
      • Data sent when a user clicks an ad.
{
    "type": "ad_log",
    "action": "clk",
    "ad_log": "YTU2ZDY2ZjctNDM4ZS00OTVjLWJiYTAtMjI4Mzk2MjQ0ZWVkfDA2NDI4NjYwLWY2NDMtNGVmNS05MzgzLTZjZmE1OGYxOGI2OXxjNTZkYzNiZi05MzVkLTRlZTYtYjFlZC1mMzFiZmMwMmJlOTF8YjM4M2M4YWYtZWUzZi00MDljLTlmOWYtODgxYTI4YWZjYmVjfDk3NGIwOGI4LTc1MjYtNDFkMC04MTg5LWQ4MTVkNTFlZGNlZnw"
}
  • Conversion Logs
    • Logs sent when a user completes a desired activity (conversion) after viewing an ad.
    • Conversions can include, but are not limited to, the following activities:
      • Product purchase
      • Adding to cart
      • App installation
      • Service subscription
      • Download
      • Link click
      • Content consumption for a certain period
{
    "type": "ad_log",    
    "action": "conv",    
    "ad_log": "YTU2ZDY2ZjctNDM4ZS00OTVjLWJiYTAtMjI4Mzk2MjQ0ZWVkfDA2NDI4NjYwLWY2NDMtNGVmNS05MzgzLTZjZmE1OGYxOGI2OXxjNTZkYzNiZi05MzVkLTRlZTYtYjFlZC1mMzFiZmMwMmJlOTF8YjM4M2M4YWYtZWUzZi00MDljLTlmOWYtODgxYTI4YWZjYmVjfDk3NGIwOGI4LTc1MjYtNDFkMC04MTg5LWQ4MTVkNTFlZGNlZnw",
    "price": 18123,
}
  • (Optional) Impression Logs
    • Impression logs are not mandatory in A2, but are recommended for accurate metric measurement.
    • Impression logs are sent when an ad is actually displayed to a user.
      • It is recommended to measure whether an ad is displayed based on whether more than 50% of the ad is visible on the user’s screen for at least one second.
      • If the above criteria cannot be met due to system constraints or other reasons, it is recommended to measure impressions using at least the same criteria.
{
    "type": "ad_log",
    "action": "vimp",
    "ad_log": "YTU2ZDY2ZjctNDM4ZS00OTVjLWJiYTAtMjI4Mzk2MjQ0ZWVkfDA2NDI4NjYwLWY2NDMtNGVmNS05MzgzLTZjZmE1OGYxOGI2OXxjNTZkYzNiZi05MzVkLTRlZTYtYjFlZC1mMzFiZmMwMmJlOTF8YjM4M2M4YWYtZWUzZi00MDljLTlmOWYtODgxYTI4YWZjYmVjfDk3NGIwOGI4LTc1MjYtNDFkMC04MTg5LWQ4MTVkNTFlZGNlZnw"
}

Hope this guide helps with advertising log integration. If you have any further questions or need additional support, please feel free to contact us. Thank you.

Was this page helpful?