|
The data required for processing paid clicks and providing scores is a subset of the data found in standard Web logs and ad serving platforms. Click Forensics can collect this data in a variety of ways: Log files or database extracts
Logs or database extracts can be transferred in batches via SFTP or SCP as frequently as every 15 minutes. Processing occurs in real-time and results are available within a few minutes. Most advertisers find that daily batch processing fits their workflow. Ad networks, however, typically require more frequent updates and can make real-time blocking, routing, and publisher management decisions by transferring data multiple times each hour. Redirect URL
Many advertisers find log file transfers to be inefficient or inconvenient. Click Forensics can gather the data required for advertisers with a simple URL redirect service, which allows Click Forensics to collect data about paid click campaigns without requiring customers to upload web server log files regularly. The Click Forensics redirect service simply injects itself as an intermediate landing page in the PPC campaign. The Click Forensics redirect service is designed to integrate with existing platforms. Agency partners typically deploy the Click Forensics redirect service in conjunction with preexisting ad server redirects such as Atlas or Doubleclick. Real-time API
For ad network clients requiring real-time click transmission and instantaneous scoring, Click Forensics provides an API that accepts clicks continuously throughout the day. This avoids the constant file transmission associated with batch processing and creates a streamlined automated process. Data Required for Accurate Scoring The data required for processing traffic and providing scores is a subset of the data found in standard web logs. The following fields are required:
| Purpose | Required Field | Description | | Visitor Identification | Client IP Address | The IP address of the client that accessed your server | | User Agent | The full (not truncated) User Agent | | Persistent First-party Cookies* | The Persistent first-party Visitor Identification Cookie must be enabled to track visitors | | Source Identification | Referring Information | The full referring URL transmitted by the web browser for site on which the ad appeared | | Affiliate, sub-affiliate | For publishers to effectively manage downstream affiliate partners | | Publisher, sub-publisher | For ad networks to effectively manage downstream publisher partners | | Click Identification | Date and Time of the Request | Date, time, seconds and time zone | | Unique Click ID | ID that uniquely reconciles a click | | Destination of the ad click | Bid Keyword | Keyword that the advertiser bid on | | Ad Identifier | Ad ID that uniquely identifies ad served – required if there is no bid keyword | | Advertiser URL | URL of the landing page or the domain of the advertiser | | Keyword Analysis | Search Keyword | Recommended for keyword optimization and analysis of campaign effectiveness (not required) | | Scoring | Conversion Data | An indication of which clicks converted – Useful feedback to tune engine's predictive power with respect to client's specific traffic patterns |
|
