Skip to main content

Adtraction

Adtraction is an affiliate marketing network that connects advertisers with partners (publishers) across the Nordics and Europe. The Adtraction connector reads transactions, clicks, statistics, programs, channels, applications, coupons, payments, and account balances for partners, and transactions, clicks, statistics, channel applications, adjustments, and segments for advertisers. It can also file partner claims and approve or reject advertiser transactions and channel applications.

Adtraction icon

Power end-to-end data operations for your Adtraction API with Nexla. Our bi-directional Adtraction connector is purpose-built for Adtraction, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Adtraction or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Adtraction workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Nexla connects to the Adtraction API with an API token from your Adtraction account. Adtraction has two kinds of account, and the token you create decides which templates work:

AccountTemplates
Partner (publisher)The templates whose names start with Partner:, such as Partner: List Transactions (Conversions) and Partner: Create Claim.
AdvertiserThe templates whose names start with Advertiser:, such as Advertiser: List Transactions (Conversions) and Advertiser: Approve/Reject Transaction.

A partner token can only call partner endpoints, and an advertiser token can only call advertiser endpoints; Adtraction rejects the other side's requests with HTTP 403. If you work with Adtraction as both a partner and an advertiser, create one Nexla credential for each token.

To create a token:

  1. Sign in to your Adtraction partner or advertiser account. Partner accounts are free but are reviewed by Adtraction before approval; advertiser accounts are set up by Adtraction under an advertiser agreement.

  2. Go to Account > Settings > API, and click Create new API token.

  3. Copy the token, and store it securely.

For details, see Adtraction's Get started with the Adtraction API article.

Adtraction API rate limits

Adtraction limits each token to a number of requests per minute, mostly 30 requests per minute and 10 per minute for some endpoints such as adjustments, and returns HTTP 429 when the limit is used up. Each Nexla template makes one request per run, but many flows on the same token can reach the limit.

Authenticate​

Credentials required​

Adtraction advertiser API token in the X-Token header. Use for the advertiser_* endpoints. The connection test reads your account details (GET /v2/advertiser/account/).

FieldRequiredSecretDescription
API TokenYesYesYour Adtraction advertiser API token, from Account > Settings > API > Create new API token. Sent as the X-Token header. Partner tokens only reach partner endpoints, advertiser tokens advertiser ones.

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

  2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

  3. Select the Authentication Type that matches your token: Partner (Publisher) API Token for a partner account, or Advertiser API Token for an advertiser account. Nexla tests a partner credential by listing Adtraction markets, and an advertiser credential by reading your advertiser account.

  4. Paste the token into the API Token field. Nexla sends it in the X-Token header on every request. Do not add a prefix such as Bearer.

    The API token is sensitive and should be kept secure. If it is exposed, create a new token in Adtraction under Account > Settings > API, and update this credential.

  5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Adtraction connector tile, then select the credential that will be used to connect to your Adtraction account, and click Next; or, create a new Adtraction credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Adtraction endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below, grouped by area.

Each template makes a single request per run and returns every record in the response; Adtraction does not page these endpoints. Dates use the yyyy-MM-dd format in Stockholm time, and date ranges default to the last 30 days ({now-30} to {now}). Templates that need an ID, such as a program or payment ID, read data for that one object; use the matching list template to find the ID.

Partner templates​

These templates need a credential with a Partner (Publisher) API Token.

Partner: List Transactions (Conversions)

Lists the sales and leads (conversions) tracked to your channels in a date range, with commission, order value, transaction status, payment status, and click details. Use it for earnings and conversion reporting.

  • Calls POST /v2/partner/transactions/.
  • From Date (required; default {now-30}): Start of the transaction date range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the transaction date range, yyyy-MM-dd. Default {now} = today.
  • Transaction Status (required; default 0): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected, 0 all. Clicks and impressions are not affected. Options: All (0), Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Partner: List Clicks

Lists the clicks tracked on your tracking links in a date range, with the program, channel, ad, click date, cookie status (Fresh or Stale), gclid, EPI, and any click commission.

  • Calls POST /v2/partner/clicks/.
  • From Date (required; default {now-30}): Start of the click date range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the click date range, yyyy-MM-dd. Default {now} = today.
  • Currency (required; default SEK): ISO 4217 currency code amounts are returned in, e.g. SEK, EUR, NOK, DKK.
  • Adtraction returns clicks from the last 14 months only.
  • See the Adtraction API reference for the response fields.

Partner: Get Statistics Totals

Returns one totals record for a date range in one market and currency: impressions, clicks, leads, sales, order value, commission, EPC, and CTR.

  • Calls POST /v2/partner/statistics/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Currency (required; default SEK): ISO 4217 currency code amounts are returned in, e.g. SEK, EUR, NOK, DKK.
  • Market (required; default SE): The two-letter ISO 3166-1 market code, for example SE, NO, DK, FI, DE, or NL.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Partner: Statistics by Day

Returns the same statistics as Partner: Get Statistics Totals, with one record per day.

  • Calls POST /v2/partner/statistics/days/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Currency (required; default SEK): ISO 4217 currency code amounts are returned in, e.g. SEK, EUR, NOK, DKK.
  • Market (required; default SE): The two-letter ISO 3166-1 market code, for example SE, NO, DK, FI, DE, or NL.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Partner: Statistics by Program

Returns the same statistics as Partner: Get Statistics Totals, with one record per advertiser program.

  • Calls POST /v2/partner/statistics/programs/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Currency (required; default SEK): ISO 4217 currency code amounts are returned in, e.g. SEK, EUR, NOK, DKK.
  • Market (required; default SE): The two-letter ISO 3166-1 market code, for example SE, NO, DK, FI, DE, or NL.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Partner: List Programs

Lists the advertiser programs available in a market, with each program's name, URL, currency, category, marketing rules (PPC, social, email, cashback, and coupon sites), commission levels, and whether a product feed is available.

  • Calls POST /v3/partner/programs/.
  • Market (required; default SE): The two-letter ISO 3166-1 market code, for example SE, NO, DK, FI, DE, or NL.
  • See the Adtraction API reference for the response fields.

Partner: List Commission Types

Lists the commission types an advertiser program pays in its standard segment: ID, name, value, whether the value is a percentage or a fixed amount, and whether it applies to sales or leads.

  • Calls GET /v3/partner/programs/commissions/{Program ID}/.
  • Program ID (required): The numeric ID of the program. Use Partner: List Programs to find it.
  • The commission type id is the commissionId that Partner: Create Claim needs.
  • See the Adtraction API reference for the response fields.

Partner: List Channels

Lists the approved channels (websites, newsletters, and social accounts) in your partner account, with each channel's ID, name, URL, and type. Many other requests need the channel ID.

Partner: List Program Applications

Lists the status of each of your channels' applications to advertiser programs (0 rejected, 1 approved, 2 pending), with the program and category. Use it to see which programs have approved you.

Partner: List Coupons and Offers

Lists the coupon codes, vouchers, and offers that programs make available to you, with the code, description, terms, landing page, validity dates, program, and category.

Partner: List Payments

Lists the payouts Adtraction has sent you, with the payment ID, payment date, total, currency, exchange rate, tax, and VAT. Use it for payout reconciliation.

Partner: List Transactions in a Payment

Lists the transactions included in one payout, with commission, order value, program, click, and status. Use it to see what a payment paid for.

  • Calls GET /v2/partner/transactions/payment/{Payment ID}/.
  • Payment ID (required): The numeric ID of the payment. Use Partner: List Payments to find it.
  • See the Adtraction API reference for the response fields.

Partner: Get Account Balance

Returns your account balance in one currency: pending, confirmed, invoiced, payable, and total commission.

  • Calls GET /v2/partner/balance/{Currency}/.
  • Currency (required; default SEK): ISO 4217 currency code amounts are returned in, e.g. SEK, EUR, NOK, DKK.
  • See the Adtraction API reference for the response fields.

Advertiser templates​

These templates need a credential with an Advertiser API Token.

Advertiser: Get Account

Returns your advertiser program's ID, name, currency, and market. Use it to find your program ID and reporting currency.

Advertiser: List Transactions (Conversions)

Lists the sales and leads tracked for your program in a date range, with order ID, order value, cost, status, auto-approval date, payment status, and channel. Use it to review pending conversions.

  • Calls POST /v2/advertiser/transactions/.
  • From Date (required; default {now-30}): Start of the transaction date range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the transaction date range, yyyy-MM-dd. Default {now} = today.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Advertiser: List Clicks

Lists the clicks partners sent to your site in a date range, with channel, ad, click date, and cookie status (Fresh or Stale).

  • Calls POST /v2/advertiser/clicks/.
  • From Date (required; default {now-30}): Start of the click date range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the click date range, yyyy-MM-dd. Default {now} = today.
  • Adtraction returns clicks from the last 14 months only.
  • See the Adtraction API reference for the response fields.

Advertiser: Get Statistics Totals

Returns one totals record for a date range: impressions, clicks, leads, sales, order value, cost, CTR, conversion ratio, and average order value.

  • Calls POST /v2/advertiser/statistics/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Advertiser: Statistics by Day

Returns the same statistics as Advertiser: Get Statistics Totals, with one record per day.

  • Calls POST /v2/advertiser/statistics/days/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Advertiser: Statistics by Channel

Returns the same statistics as Advertiser: Get Statistics Totals, with one record per partner channel.

  • Calls POST /v2/advertiser/statistics/channels/.
  • From Date (required; default {now-30}): Start of the statistics range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the statistics range, yyyy-MM-dd. Default {now} = today.
  • Transaction Status (required; default 3): Which transactions to include: 1 approved, 2 pending, 3 approved + pending, 4 open claims, 5 rejected. Clicks and impressions are not affected. Options: Approved (1), Pending (2), Approved + pending (3), Open claims (4), Rejected (5).
  • See the Adtraction API reference for the response fields.

Advertiser: List Channel Applications

Lists the partner channels that have applied to your program, with partner, channel name, URL and type, application date, approval status (0 rejected, 1 approved, 2 pending), and reject reason.

Advertiser: List Adjustments

Lists costs booked outside transactions, such as partner commission adjustments and platform fees (monthly fee or minimum spend), with cost, network fee, accounting date, and invoice status.

  • Calls POST /v2/advertiser/transactions/adjustments/.
  • From Date (required; default {now-30}): Start of the accounting date (max 365 days) range, yyyy-MM-dd (Stockholm time). Default {now-30} = 30 days ago.
  • To Date (required; default {now}): End of the accounting date (max 365 days) range, yyyy-MM-dd. Default {now} = today.
  • The date range filters on the accounting date and can span at most 365 days.
  • See the Adtraction API reference for the response fields.

Advertiser: List Segments

Lists the commission segments in your program and the partner channels assigned to each.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration​

Adtraction data sources can also be manually configured to ingest data from any valid Adtraction API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Adtraction data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination​

Click the + icon on the Nexset that will be sent to the Adtraction destination, and select the Send to Destination option from the menu. Select the Adtraction connector from the list of available destination connectors, then select the credential that will be used to connect to your Adtraction account, and click Next; or, create a new Adtraction credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Adtraction endpoints. Select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

These templates change data in Adtraction, and the other party (the advertiser or the partner) sees the result. Test them with a single record before sending a full Nexset.

Advertiser: Approve/Reject Channel

Approves or rejects a partner channel's application to your program. Adtraction notifies the partner.

  • Credential: Advertiser API Token.
  • Sends PUT /v3/client/channels/.
  • Each record is sent as the JSON request body, one request per record. Include channelId and approvalStatus (1 to approve, 0 to reject). A rejection also needs rejectReason, a code from 0 to 12 listed in the Adtraction API reference.
  • Use Advertiser: List Channel Applications to find pending applications.
  • See the Adtraction API reference for the request fields.

Advertiser: Approve/Reject Transaction

Approves or rejects a pending transaction or open claim, or changes its order value. The partner sees the result.

  • Credential: Advertiser API Token.
  • Sends PUT /v2/advertiser/transactions/.
  • Each record is sent as the JSON request body, one request per record. Include orderId and transactionStatus (1 to approve, 5 to reject); rejectReason and orderValue are optional.
  • Only pending transactions and open claims can be changed. Adtraction returns a success status with a message when the order ID is not found, so check the response if a change does not appear.
  • See the Adtraction API reference for the request fields.

Partner: Create Claim

Files a claim for an order that was not tracked, for the advertiser to review. Each record creates one claim.

  • Credential: Partner (Publisher) API Token.
  • Sends PUT /v2/partner/claims/.
  • Each record is sent as the JSON request body, one request per record. Include programId, channelId, orderId, commissionId, transactionDate, orderValue, and currency; expectedCommission and epi are optional.
  • Use Partner: List Commission Types to find the commissionId, and Partner: List Channels to find the channelId.
  • See the Adtraction API reference for the request fields.

Manual configuration​

Adtraction destinations can also be manually configured to send data to any valid Adtraction API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks.

Save & activate​

Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Adtraction endpoint, open the destination resource menu, and select Activate.

The Nexset data will not be sent to the Adtraction endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.