Adness Documentation

Adness Documentation

Basic Documentation

API Guide

This guide will help you understand which features are available through the API and what needs to be included in each request for it to work correctly. Public documentation is available here: Swagger API Adness. 1. User Authorization Request: POST /api/rest/auth/signin What it does: verifies email and

IP Targeting Guide

What is IP Targeting? IP targeting is a method of showing ads to users from a specific range of IP addresses or excluding unwanted IP ranges. Why Use IP Targeting? Improve Audience Quality * Exclude low-performing regions (e.g., countries/regions/cities with poor conversion rates). * Focus on locations where users

Smart Bids Feature Overview & Setup Guide

Purpose and Capabilities Smart Bids allow advertisers to set a custom CPC (cost-per-click) bid for specific traffic sources (source IDs) within the same campaign, without the need to create a new one. The bid can be set based on the performance of a particular source and can differ from the

Statistics API

Authorization Request parameters: * campaigns[] (string) – array of campaigns * API domain: https://panel.adness.co Authorization key is required for all API requests to get costs. API key should be sent in “apiKey” get-parameter. API key is unique for each user and is activated by personal manager. Get user’s campaigns

Basic Documentation

Campaigns Postback

What is a Postback URL? A Postback URL is used to send information about conversions (e.g., registrations, sales) from the advertiser to our system. This allows us to track events and build analytics. Basic Postback URL format https://s2s.adness.co/v1/conversion?clickid=[REQUIRED]&revenue=[OPTIONAL]&type=[OPTIONAL]

Basic Documentation

Advertiser tracking URL placeholders

These are the tracking URL placeholders that are used to track interesting data through the campaign URL and advertiser's tracking system: Placeholder Description {impressionID} id of the impression {clickID} id of the click {publisherID} id of the source {sourceID} id of the subsource {siteID} id of the site {spotID} id