---
title: "Parameter guidance"
slug: "parameter-guidance"
updated: 2026-04-28T09:19:56Z
published: 2026-04-28T09:20:10Z
canonical: "help.awin.com/parameter-guidance"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.awin.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Parameter guidance

## Overview

This page will cover each parameter that our tags make use of, their definitions and best data integrity practices.

Some parameters are expanded out to their own pages as they require more information that can comfortably fit here.

---

## Global parameters

These parameters are global across all Awin tracking methods.

#### totalAmount

`totalAmount` is responsible for reporting the sale subtotal on a given transaction after any applicable discounts are applied.

We recommend that this value excludes tax, shipping, or relevant service charges. This value **must** be a float. No thousands separator is allowed and the decimal place must be a standard “dot” character.

Example: `1083.29`

#### channel

For guidance on this parameter, please see our [article on the Channel parameter](/developers/docs/channel-parameter).

#### orderReference

`orderReference` should receive the related order identifier for a given transaction. We recommend that this value is one identifiable internally, by your team for the easiest comparison.

This value **must** be unique per transaction and value must be URL-encoded.

We recommend using a maximum of 50 characters within the order reference identifier to prevent (display) errors or truncated values ​​(e.g., in some platform reports or export files).

#### commissionGroupCode

`commissionGroupCode` should receive the desired Commission Group code for the transaction’s attribution. These codes are defined and configured within the Awin platform. For guidance on this parameter, please see our [article on Commission Groups](/developers/docs/commission-groups).

#### currencyCode

`currencyCode` should report the conversion’s applicable currency. This value must be the **ISO 4217** currency code for a given currency.

Multiple currencies may not be used on a single transaction.

If your site uses a single currency, you may hardcode this value. For example, if all transactions are completed in US Dollar, please hardcode this value as `USD`.

#### voucherCode

`voucherCode` should be populated with the related voucher / coupon code in use on a given transaction.

While populating this field is optional, you **need** to return the parameter even if empty.

This value must be URL-encoded and return a `NULL` value if empty. See for more about the [Voucher Attribution](/developers/docs/voucher-attribution).

#### isTest

`isTest` should be populated with “0” at all times unless otherwise instructed, especially in a live program.

When set to “1”, conversions will not be processed.

---

### optional parameters

#### customer acquisition

`Customer acquisition` should be filled with the relevant customer type data (value: `NEW` for new customer or `RETURNING` for returning/existing customer). [See for more here](/developers/docs/customer-acquisition).

#### product level

`product level data` - For the transfer of ordered individual items (shopping cart details), as described on the help page for [product level tracking](/developers/docs/product-level-tracking-2). These can be used for the [product trend report](/advertisers/docs/product-level-tracking) or by partners for their advertising optimization.

#### custom parameters

`Custom parameters` allow you to add depth to your reporting and, in some cases, control the associated [Commission Groups](/developers/docs/commission-groups) via [Commission Flexibility](/advertisers/docs/commission-flexibility). This value must be URL-encoded. See for more about [Custom parameters](/developers/docs/custom-parameters).

---

## S2S-specific parameters

These parameters are specific to [Server-to-Server (S2S)](/developers/docs/server-side-tracking) tracking. Other, transaction-related variables included in S2S tracking, have identical definitions to those applicable for [client-side tracking](/developers/docs/client-side-tracking-1).

#### cks

`cks` inside the Awin [direct S2S integration](/developers/docs/direct-s2s) (tt=ss for trackingtype=serverside) only should be populated with the associated Awin Click Checksum. This value is appended to the landing URL of each Awin redirect to your site and can be accessed via the parameter `&awc=`.

#### awc

`awc` inside the [Awin S2S Conversion API](/apis/apidocs/conversion-api) (tt=api for tracking-type=conversion-api) only should be populated with the associated Awin Click Checksum. This value is appended to the landing URL of each Awin redirect to your site and can be accessed via the parameter `&awc=`.