Campaign
Retargeting tracking via AdUp pixel
With the help of the AdUp pixel, user and product activities on your website can be tracked. Depending on the configuration, this data is used for the delivery of your retargeting campaigns. Please note that transmitted product IDs must match the IDs of your product feed exactly.

Slim Retargeting
Example of a landing page
Available event options
−
Name
Required
Description
Example
account
✅
Your unique account ID. Can be set either via URL parameter on the script tag or as an event option.
account: 1234
Event
✅
The type of the recorded event.
event: ‘retargeting’
product
❌
Adds the relevant product to the tracking. The product can be passed either as an ID only or with additional details such as price and quantity. Please note that the product ID must match the ID from your product feed exactly.
product: '<PRODUCT_ID>'
product: {
id: '<PRODUCT_ID>',
price: 12.34,
quantity: 2
}
products
❌
Supplements the tracking with the relevant products. The products are passed as a list. Each entry can either contain just the ID or additional details such as price and quantity. Please note that the product IDs must match the IDs from your product feed exactly.
products: [ ‘<PRODUCT_ID1>‘,
‘<PRODUCT_ID2>‘
]
products: [
{ id: ‘<PRODUCT_ID1>‘, price: 12.34, quantity: 2 },
{ id: ‘<PRODUCT_ID2>‘, price: 56.78, quantity: 1 }
]
search
❌
Supplements the tracking with additional data on the search query. The values passed here can be mapped as tracking pixel parameters and thus used as text placeholders or segmentation filters.
search: {
query: ‘shoes’,
category: ‘running’
}
transaction
❌
Complements the tracking with the order or invoice number as well as other relevant order information.
transaction: ‘<ORDER_ID>‘
transaction: {
id: ‘<ORDER_ID>‘,
total: 123.45
}
conversion
❌
Enables additional tracking of a conversion in parallel with the retargeting event. Conversion details that are not explicitly specified are automatically supplemented from 'transaction' or 'products'. Please note that the code must exactly match an active conversion code in your account.
conversion: ‘<CONVERSION_CODE>‘
conversion: {
code: ‘<CONVERSION_CODE>‘,
orderId: ‘<ORDER_ID>‘,
total: 123.45
}
demarcate
❌
Specifies which segment should be removed from the retargeting target audience, for example after a purchase. Possible values: user, products, category.
unmark: ‘user’
device
❌
The user's device type is automatically detected by default. If necessary, however, this can be set manually. Possible values: mobile, tablet, desktop.
device: ‘desktop’
GDPR
❌
Manually submits the GDPR status. Use this parameter if automatic detection via the TCF API is not available. Possible values: true, false.
GDPR: true
GDPR consent
❌
Manually submits the IAB TCF consent string. Use this parameter if automatic detection via the TCF API is not available.
gdprConsent: ‘<CONSENT_STRING>‘
type
✅
The page type or page depth for the retargeting event. Possible values: homepage, productList, productPage, basket, sale.
type: ‘productPage’
Example of an order confirmation page (conversion)
Available event options
+
Pro Retargeting
Example of the homepage
Available event options
+
Example of the results list
Available event options
+
Example of the product page
Available event options
+
Example of the shopping basket
Available event options
+
Example of the order confirmation
Available event options
+
