Partnerize

Attribute partner- and affiliate-driven sales in real time and commission your partners accurately, with server-to-server conversions sent straight to Partnerize.

Overview

Partnerize is a global partnership and affiliate marketing platform that helps brands track conversions, attribute them to publishers, and manage commissions. With the Partnerize destination, you can sync conversion (sale) events from your data warehouse to Partnerize using its server-to-server (S2S) conversion tracking, enabling accurate affiliate attribution without relying on browser-side pixels.

Conversions are recorded against a specific Partnerize campaign and support single- or multi-item orders, basket-level attributes, and vertical-specific custom parameters.

Supported syncing

For more information about sync modes, refer to the sync modes docs.

Connect to Partnerize

Go to the Destinations overview page and click the Add destination button. Select Partnerize and click Continue.

You need to provide the following credentials:

• User Application Key: The application key for your Partnerize user.
• User API Key: The API key for your Partnerize user.

Together these authenticate Hightouch with the Partnerize API (HTTP Basic authentication), which Hightouch uses to validate your connection and load the list of campaigns you can sync to.

Obtain API credentials

In Partnerize, go to Settings → Account Settings → API to find your User Application Key and User API Key. The user associated with these keys must have access to the campaigns you want to track conversions against.

Sync configuration

Once you've set up your Partnerize destination and have a model to pull data from, you can set up your sync configuration to begin syncing data. Go to the Syncs overview page and click the Add sync button to begin. Then, select the relevant model and the Partnerize destination you want to sync to.

Campaign

Select the Partnerize campaign that conversions should be tracked against. Hightouch loads the campaigns available to your account from the Partnerize API. Every conversion in the sync is recorded against the selected campaign.

Field mapping

Hightouch lets you sync conversion fields via field mapping. You can map data from any of your model columns to Partnerize's conversion fields.

Required fields

You must map the following fields to complete your configuration:

• Conversion reference (order ID): Your unique reference for the conversion — typically the order ID.
• Click reference: The click reference captured at the point of sale. It must match the originating click for Partnerize to attribute the conversion.

In addition, every conversion must include at least one item with a category and a quantity (see Items below). These item-level fields are required by Partnerize's S2S specification, but they're enforced when the conversion is sent rather than as required mappings, because items can also be supplied as an array.

Items

A conversion's line items can be provided in two ways:

• Single item — map the top-level Item category, Item quantity, Item value, and Item SKU fields. This describes one line item.
• Multiple items — map a column containing an array of line items using the inline mapper. Each entry takes the shape { category, sku, value, quantity }. When mapped and non-empty, the items array takes precedence over the single-item fields.

For each item:

• category (required) — the item category.
• quantity (required) — the number of units.
• value (optional) — the item value, excluding tax and currency symbols. Only required when the campaign awards percentage-based commission.
• sku (optional) — the product SKU.

Optional basket-level fields

These describe the order as a whole and are omitted from the conversion when left unmapped:

• Currency — ISO 4217 currency code (for example, USD).
• Country — ISO 3166 country code (for example, US).
• Customer type — new or existing.
• Voucher code — the voucher or discount code used on the order.
• Customer reference — your own identifier for the customer.
• Fulfilment date — ISO 8601 YYYY-MM-DD; drives Partnerize's auto-approval window.

Custom parameters

Use custom mappings to send additional, vertical-specific basket parameters (for example, check_in_date for travel). Each custom mapping is appended to the conversion as an extra parameter.

Sync behavior

Partnerize conversions are recorded server-to-server through Partnerize's conversion tracking host. For each row in your model, Hightouch:

• Builds a conversion from the mapped fields and validates the required fields before sending.
• Sends one tracking request per conversion (requests within a batch are sent concurrently).
• Records the conversion against the selected campaign. A successful send returns 200 OK, and the conversion then enters a pending state in Partnerize for downstream validation and approval.

Tips and troubleshooting

Value is optional

value is only required when a campaign awards percentage-based commission. A conversion with a category and quantity but no value is valid and will be sent; the value is simply omitted from the request.

Required-field rejections

Rows are rejected (and not sent) when a required field is missing. The rejection message names the missing field:

• Missing conversion reference → "A conversion reference (order ID) is required for every Partnerize conversion."
• Missing click reference → "A click reference is required to attribute a Partnerize conversion."
• Item missing a category or quantity → "Conversion item is missing required field(s): …"
• No item fields mapped at all → "Each conversion must include at least one item with a category and quantity."

Common errors

If you encounter an error or question not listed below and need assistance, don't hesitate to reach out. We're here to help.

Authentication errors

If the connection test or campaign list fails with a 401 or 403:

• Verify your User Application Key and User API Key are correct and entered in the right fields.
• Confirm the user has access to the campaigns you want to track conversions against.

Conversions not appearing

If a sync succeeds but conversions don't appear as expected in Partnerize:

• Confirm the click reference matches a real click for the selected campaign — conversions without a matching click can't be attributed.
• Remember that received conversions enter a pending state and are validated by Partnerize after they're sent.

Live debugger

Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.

Sync alerts

Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.