Campaign
Engagement tracking via AdUp Pixel
Measure important user interactions on your website and analyse the quality of your campaign traffic.

How it works
With the help of the AdUp pixel, user engagement can be recorded based on session length and subsequent page impressions. This data forms the basis for the engagement score in your campaign statistics. Please note that the pixel script must be integrated on all pages of your website so that engagement can be fully recorded.
Engagement Score
The “Engagement Score” provides information about user behaviour after clicking on your ad. This is an initial indicator of performance, even before conversion information is available.
Preferably try to acquire traffic with high engagement in order to purchase as many active users as possible. For this purpose, compare your creatives using the engagement score. A comparison is particularly useful between two campaigns, ad groups, ads, keywords, or direct placements, as this is a relative value. A single temporal comparison (e.g. engagement of “Ad 1” 14 days ago and 7 days ago) is therefore not useful.
Please note that engagement is not a trend, but reflects the activity of the purchased users for the selected period. Also, a lower CPC and thus less purchased traffic will not change the engagement score.
The engagement model always refers to the average activities of the last 30 days. The values are therefore constantly updated.
Conditions
In order for a score to become visible in the frontend, two conditions must be met:
An engagement model must exist for your advertiser, which in turn requires at least 100 clicks.
An engagement score is only displayed for an entity (campaign, ad group, placement, keyword, or ad) once it has collected approximately 30 clicks with engagement.
Integration of the AdUp Pixel
To be able to evaluate engagement, you only need to place the following script on your website.
Please note that the AdUp pixel must be integrated on all pages (including subpages and booking confirmation pages). This can easily be done, for example, via (Google) Tag Manager.
The working integration code for your account ID can be viewed on the “Tools” > “Engagement Tracking” page in the Advertiser Frontend.
Simple Integration
Insert this HTML script tag on all pages of your website.
Available query parameters
−
Name
Required
Description
Example
account
✅
Your unique account ID.
account=1234
GDPR
❌
Submits the GDPR status manually. Use this parameter if automatic detection via the TCF API is not available.
gdpr=1
GDPR consent
❌
Manually submits the IAB TCF consent string. Use this parameter if automatic detection via the TCF API is not available.
gdpr_consent=<CONSENT_STRING>
Normally, we determine the required GDPR data automatically via the TCF API integrated on the website.
If this is not available or if it is not possible to use it for technical reasons, you have the option of passing the GDPR data manually. The values can simply be specified as additional query string parameters when calling the pixel script:
Name
Required
Description
Example
GDPR
❌
1 = GDPR applies
0 = GDPR does not apply
(omit) = Unknown (default)
gdpr=1
GDPR consent
❌
The IAB Consent String (base64url-encoded)
gdpr_consent=<CONSENT_STRING>
Advanced Integration
Your unique account ID is passed as an event option via window.adup.push().
Available event options
−
Name
Required
Description
Example
account
✅
Your unique account ID. Can be set either via URL parameters in the script tag or as an event option.
Account: 1234
GDPR
❌
Submits the GDPR status manually. Use this parameter if automatic detection via the TCF API is not available.
GDPR: true
GDPR consent
❌
Manually submits the IAB TCF consent string. Use this parameter if automatic detection via the TCF API is not available.
gdpr_consent: '<CONSENT_STRING>'
Examples
Simple
In this case, the options are passed via URL parameters directly when the script is called.
Advanced
Alternatively, the desired parameters can also be passed subsequently (i.e. during runtime) via the global JSON object “adup”.


