For the complete documentation index, see llms.txt. This page is also available as Markdown.
Essentials EditionPro EditionEnterprise Edition

Create SKU Exception Lists

Create SKU exception lists to apply different payout rates to specific products.

Take the PXA course

SKU exception lists let you pay partners different rates based on the SKU associated with an action.

Create a SKU exception list

  1. From the top navigation bar, select [User profile] → Settings.

  2. In the Program column, scroll to Exception Lists and select SKU.

  3. In the upper right corner, select Add New SKU List.

  4. Fill out the following information:

    Field
    Description

    List Name

    Add a name for this list—this will only appear internally to you and other account members; partners will not see it.

    Associate Event Type

    Select 1 or more event types to associate with this exception list.

    Match Expression

    [Advanced & Optional] Enables the system to match only on a part of the SKU value via specifying a regular expression with 1 grouping. The value represented by the grouping will be matched against the SKU value in this list. If you have a use case for regex but are unsure how to configure it, contact support.

  5. Select Save and Add Items to continue.

  6. You can add a SKU and optional Display Values using the fields in the UI, or you can Upload a CSV or Excel file with your SKUs.

  7. Once you've added items or uploaded a file, select Save to complete the process. You'll now see your new SKU exception list on the SKU Lists screen.

SKU exception list format

Create a .CSV or .XLS/.XLSX file using the column names below.

Column
Type
Required
Description

SKU

String

Yes

The value that is included in tracking conversion data.

Display Value

String

No

Enter a display value if you want to show a different value in reporting. For example, if the Category value is some sort of computer-generated value, then you might want to enter a display value to make it easier to understand in reporting.

Active Start Date

Date

No

Gives you the ability to schedule this item. This is an ISO 8601 format. Example format: 2038-01-19T12:00:00-07:00

Active End Date

Date

Only if Start Date is provided

Gives you the ability to schedule this item. This is an ISO 8601 format. Example format: 2038-01-19T23:59:59-07:00

When setting end dates to SKUs, any SKUs that expire (passes the set end date) will not trigger any payouts stipulated in the contract. Be sure to remove expired SKUs to avoid payouts from not triggering as stipulated in your terms.

Example: If you want to run a promotion for a limited time on selected SKUs, you can create a SKU exception list and schedule times for when the promotion is valid for on each related SKU. Then you can set a payout group to pay the different payouts on the various SKUs. If an order with a SKU on this list is tracked outside of the scheduled time, it will not trigger the promotional payout.

Timezone

String

No

Timezone is derived from the start date, but if you want to override it with a specific timezone, enter the full name here, e.g. "America/New_York"

For example:

Last updated

Was this helpful?