Partnerize
Partnerize provides a global affiliation network connecting businesses with customers. Using this destination you can implement server-side tracking.
Key features
The Partnerize destination provides the following key features:
Events structure: our Events reference leverages Partnerize lead and sale tracking, meaning that your data is properly bridged to the expected fields in an optimized way.
Prebuilt mappings: data mapping for event-based destinations happens automatically, which simplifies user inputs.
Smart mapping: data mapping can be readjusted using your datalayer defined fields.
Support for multi-item data: information included in the item array is bridged to Partnerize.
Commission group: remunerate different products based on your categories.
Destination setup
Configuration
Campaign Id
Required
A unique identifier assigned to the campaign and provided by Partnerize. This setting supports dynamic values [1].
Select your click ref holder
This can be either Cookie
or Event property
, depending on how you provide CJ "Click Reference" value.
Cookie Name for Click Tracking
If you select Cookie
in Select your click ref holder
, you can set your cookie name here.
Event property containing click ref
If you select Event property
in Select your click ref holder
, you can set your event property here. [2]
Custom Conversion URL String
The Partnerize "Conversion URL" may differ based on your specific requirements. Using this setting, you can add a custom string before the campaign parameter (E.g. https://prf.hn/conversion/tracking_mode:api/[CUSTOM_STRING]campaign:...).
Optional: Partnerize Device (device)
You can set a property holding the following allowed values: "bot", "desktop", "mobile", "tablet" and "Other". More details are available following this LINK. [2]
Optional: Partnerize Context (context)
You can set a property holding the following allowed values: "web", "m_web", "m_app", "in_app", "cd_d", "cd_p", "other" and "offline". More details are available following this LINK. [2]
Custom Event Properties
Map your custom event properties by setting their field names in Partnerize property name
and adding the field name holding the value in Your event property
. E.g. if you inputsize
in the Partnerize property name
and items.0.product.size
in Your event property
, you'll have a custom event property in Partnerize calledsize
with a value based on the content of the field items.0.product.size
[2].
In the column Your event property path
you should keep the default value Default (root)
as this will add a custom parameter at the Base Level (E.g. see campaign) which better fits most scenarios. In case you select either In "items" {items.X}
or In "product" {items.X.product}
this destination will look for the input event property starting from the items or product level respectively and add it as a custom Basket Data parameter.
The advanced operation As Partnerize Basket Data
can be paired with the property path option Default (root)
so your property value is set as a custom entry in the Partnerize "Basket Data" for each item.
Quick reference
generate_lead
lead
purchase
sale
Field mappings
Campaign Id
campaign
[*]
Cookie Name for Click Tracking
or
Event property containing click ref
clickref
[*][1]
id
conversionref
[*]
currency
currency
[*]
items.X.affiliation
category
[*]
items.X.quantity
quantity
[*]
partners.partnerize.device
device
[2]
partners.partnerize.context
context
[2]
user.type
customertype
coupon
voucher
country
country
[3]
items.X.id
sku
items.X.product.price
value
Your event property
conversion_time
[4]
Your event property
Partnerize property name
[5]
Last updated
Was this helpful?