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 are more engaged.

Optimize Ad Budget

• Exclude traffic that doesn’t convert → lower CAC (customer acquisition cost).
• Pay higher eCPC bids for better-quality traffic.

How to Set Up IP Targeting in the Advertiser’s Account

1. Go to the Targeting tab when creating a new campaign.

In the IP Targeting section, you can:

• Include an IP address or range → to receive traffic only from these IPs.
• Exclude an IP address or range → to block traffic from these IPs.

Example: You can add a range in CIDR format, such as:

192.168.0.0/16

This covers all IPs from 192.168.0.0 to 192.168.255.255.

1. You can add a single IP (e.g., 192.168.10.25) or an entire range.
2. If the entered IP or range is invalid, the system will show an error and won’t let you save the campaign.
3. Once the settings are saved, IP targeting will be applied to the campaign automatically.

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 password and returns access tokens required for further requests.

Fields to provide:

• email — your email (same as used during registration).
• password — account password.

Example:

{
  "email": "example@company.com",
  "password": "MyPassword123"
}

How to authorize:

Use the obtained token for authorization. To do this, click on Authorise:

In the pop-up window, enter the obtained token and click Authorise:

From this point, the you are ready to use our API.

2. Token Refresh

Request: POST /api/rest/auth/refresh
What it does: refreshes the token pair (access + refresh) so you don’t need to log in again using email and password.

Fields to provide:

• token — valid refresh token obtained during authorization.

Example:

{
  "token": "eyJhbGciOiJIUzI1..."
}

3. Updating Blacklists and Whitelists

Request: POST /api/rest/campaign/sources
What it does: replaces the list of traffic sources (source IDs) in a campaign. Sources can be added to the whitelist (include) or blacklist (exclude).

Fields to provide:

• id — campaign ID.
• mode — "include" or "exclude".
• values — array of source IDs.

Example:

{
  "id": 12345,
  "mode": "include",
  "values": [1001, 1002, 1003]
}

IMPORTANT! This request replaces the list.
Everything that was set before this request will be deleted.
In other words, the previous blacklist or whitelist will be overwritten.

Therefore, you should always send the current updated list — meaning you must take the already configured sources, add new ones, and then apply the request. To check the current whitelist or blacklist, you can use the request Getting Campaign List (endpoint #6)

4. Bulk Update of Campaign Statuses

Request: POST /api/rest/campaigns/status
What it does: updates the status of multiple campaigns at once — convenient for mass launch, stop, or pause.

Fields to provide:

• ids — array of campaign IDs.
• status — "active" or "inactive".

Example:

{
  "ids": [12345, 67890],
  "status": "inactive"
}

5. Updating Campaign Bid

Request: POST /api/rest/campaigns/bid
What it does: updates the bid in a specific campaign.

Fields to provide:

• id — campaign ID.
• bid — new bid.

Example:

{
  "id": 12345,
  "bid": "2.50"
}

6. Getting Campaign List

Request: GET /api/rest/campaigns/list/{limit}/{offset}
What it does: returns a paginated list of campaigns with their current targeting settings.

Fields to provide:

• limit — how many campaigns to return per request (e.g., 50).
• offset — position to start from (e.g., 0 — from the beginning, 50 — from the second page).

Example request:

GET /api/rest/campaigns/list/50/0

📌 Important:

• For all requests (except authorization), you must use the access token in headers.
• All examples above are simplified — you can check the actual response format in Swagger API Adness.

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 default bid set at the campaign level.

What Smart Bids can do:

• Set higher or lower bids than the default CPC for selected source IDs.
• Enable more efficient budget allocation by prioritizing sources with better performance.
• Avoid completely blocking a source by simply lowering the bid — a softer control mechanism.

How it works:

• Smart Bids only influence the bid amount used in the auction.
• If the campaign wins the auction, the custom bid amount is charged.
• In campaign reports, the actual cost is logged in the cost field.

Example

• Default CPC: $0.01
• Smart Bid for one source: $0.02
• Campaign gets:
  800 clicks at the default bid
  200 clicks at the Smart Bid rate
• Final cost: = (800 × $0.01) + (200 × $0.02) = $12

When to Use Smart Bids

Smart Bids are useful in the following scenarios:

How to Set Up Smart Bids

Smart Bids are available for all campaign types:  (Segmented & Unsegmented)

Setup steps:

1. Go to the Targeting tab (this is also where source blacklisting is managed).
2. Scroll down to the Smart Bids section.
3. Click Add Smart Bid.

4. In the pop-up window:

• Enter source ID (in the format {affiliate_id}_{source_id}, for example 1752_2285193)
• Select one or more countries (from those already targeted in the campaign)
• Set the desired CPC bid

5. Click Save.

Once saved, your bid will appear in the Smart Bids list. From there, you can:

• Edit bid values
• Delete or add new Smart Bids as needed

How to Analyze Performance

Filter by GEO and Source ID

Summary

Smart Bids are available for all campaign types:  (Segmented & Unsegmented)

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 list:

GET|POST /adv/v1/campaigns

Request example:

https://panel.adness.co/adv/v1/campaigns?apiKey={apiKey}

Response example:

• id (string) – campaign id
• name (string) – campaign name

JSON

[{"id":"{idCampaign1}","name":"{nameCampaignId1}"},...

Get costs by campaigns:

Get costs grouped by day for requested period. Max days per request – 31.

GET|POST /adv/v1/campaigns/costs

d’s you got by “get user’s campaigns list” method

• dateFrom (string) – period start date in Y-m-d
• dateTo (string) – period end date Y-m-d

http://panel.adness.co/adv/v1/campaigns/costs?apiKey={apiKey}&dateFrom={dateStart}&dateTo={dateEnd}&campaigns[]={campaignId1}&campaigns[]={campaignId2}&campaigns[]={campaignId3}

Response example:

• date (string) – date in y-m-d
• campaign (string) – campaign id
• cost (float) – cost in cents

JSON

{
  "result":"OK",
  "сost":[
     {
        "date":"2020-11-10",
        "campaign":"\\{campaignId1}",
        "cost":{
           cost for campaign 1 in cent by 10 november
        }
     },
     {
        "date":"2020-11-11",
        "campaign":"\\{campaignId1}",
        "cost":{
           cost for campaign 1 in cent by 11 november
        }
     },
     {
        "date":"2020-11-12",
        "campaign":"\\{campaignId1}",
        "cost":{
           cost for campaign 1 in cent by 12 november
        }
     }
  ]
}

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]&id=[OPTIONAL]

Parameters:

• clickid – unique click ID provided by us (required parameter).
• revenue – conversion amount. Default value = 0.
• type – event type. Can be any text value (e.g., signup, sale). Default = default.
• id – conversion identifier (any text value). Default = empty.

How to pass multiple events?

If you have several types of events (e.g., signup and sale), you can distinguish them using the type parameter. If you want to pass both events, you will need to set up two links for each event in your platform.

Examples (static values):

• Event: Signup

https://s2s.adness.co/v1/conversion?clickid={your_clickid_parameter}&type=signup&revenue=0

• Event: Sale

https://s2s.adness.co/v1/conversion?clickid={your_clickid_parameter}&type=sale&revenue={payout}

Examples (dynamic values):

If your tracking system defines events with its own codes or names, you can dynamically pass them in the type parameter:

https://s2s.adness.co/v1/conversion?clickid={your_clickid_parameter}&type={event_name}&revenue={payout}

👉 In this case, the {event_name} value you send (e.g., signup, sale, deposit) will be saved and displayed in our system exactly as you pass it.

Best Practices

1. Use clear and consistent names for events in the type parameter (e.g., signup, sale, deposit).
2. For non-monetary events, use revenue=0.
3. For paid events, pass the actual value in the revenue parameter (static or dynamic).

💡 Placeholders are not case-sensitive, which means that {impressionID}, {impressionid}, {ImprEsSionID} will be mapped to the same value.