At a glance: Ad networks responsible for user acquisition and retargeting can receive data regarding blocked clicks and impressions.
Protect360 reports for ad networks
Disclaimer: This article provides information on Protect360 reports available only to ad networks. For data that is also available to advertisers, see Protect360 for integrated partners.
Ad networks can receive reports via Data Locker for Partners with valuable information regarding clicks and impressions that are blocked either because of:
- Blocked clicks and impressions that occur when ad networks cross their fraud limit. The report includes total blocks, as well as blocks due to click and impression capping. Learn more about capping
- Failed click signatures that occur when a click with the network's PID parameter networks and a click signature to validate clicks can't be validated. Learn more about click signing
Ad networks can then ingest this network-level data with cross-customer visibility of their blocked clicks and impressions and use it to protect against fraud.
Report considerations
- Data arrives in CSV format to the UA/retargeting partner's bucket.
- Contains dimensions and metrics relevant to the ad network (that is cleaned of all dimensions irrelevant to the ad network).
- Available via Data Locker for Partners.
- Data freshness: Daily, meaning data for Day 0 arrives on Day 1. Data is written daily at 07:00 UTC time to the h=23 of your Data Locker bucket.
- Apps included: A single report contains the data of all apps.
Report types
Blocked clicks and impressions
This report contains aggregate level data about clicks and impressions that are blocked due to capping or any other reason.
Report structure: Fields/Dimensions
|
Field |
Remarks |
|---|---|
|
app_id |
App ID in the AppsFlyer platform. |
|
site_id |
ID that identifies the publisher that displays the ad. |
|
date |
Blocked date |
|
agency |
|
Report structure: Metrics
|
Field |
Remarks |
|---|---|
|
number_of_blocked_clicks |
Total number of the network’s blocked clicks |
|
number_of_blocked_impressions |
Total number of the network’s blocked impressions |
|
number_of_capped_clicks |
The number of the network’s capped clicks (out of the total blocked clicks) |
|
number_of_capped_impressions |
The number of the network’s capped impressions (out of the total blocked impressions) |
Failed click signatures
This report contains user-level about failed click signatures. Meaning, when ad networks use the AppsFlyer click signing method, the report contains clicks of URLs with the network’s PID that don't have validated click signatures, either because the signature is invalid or expired, or the click is not signed at all. Click signing failures could occur when there are technical errors in the implementation of click signatures by the ad network, or when clicks are sent on behalf of the network (with its PID) by another party.
Report structure: Fields/Dimensions
|
Field |
Remarks |
|---|---|
|
event_time |
|
|
original_url |
|
|
failed_signing_reason |
For example:
|
|
is_blocking_enabled |
Refers to the configuration mode of the click signature API:
|