Campaign

Engagement tracking via AdUp Pixel

Measure important user interactions on your website and analyse the quality of your campaign traffic.

A man is working on a laptop

How it works

With the help of the AdUp pixel, user engagement can be tracked 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 serves as an initial performance indicator even before conversion information is available.

Try to prioritise acquiring traffic with high engagement in order to purchase as many active users as possible. To do this, compare your advertising materials using the engagement score. A comparison is particularly useful between two campaigns, ad groups, ads, keywords, or direct placements, as it is a relative metric. An isolated chronological comparison (e.g. engagement of “Ad 1” 14 days ago versus 7 days ago) is therefore not meaningful.

Please note that engagement is not a trend, but reflects the activity of the acquired users for the selected period. Similarly, a lower CPC and thus less acquired traffic will not change the engagement score.

The engagement model always refers to the average activity over the last 30 days. The values are therefore continuously updated.


Requirements

For a score to become visible in the front end, two conditions must be met:

  1. An engagement model must exist for your advertiser, which in turn requires at least 100 clicks.

  2. An engagement score is only displayed for an entity (campaign, ad group, placement, keyword, or ad) once it has gathered around 30 clicks with engagements.


Installing the AdUp Pixel

To be able to evaluate engagement, you only need to add the following script to your website.

Please note that the AdUp pixel must be added to 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 front end.


Simple Integration

Insert this HTML script tag on all pages of your website.

<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]">
</script>
<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]">
</script>
<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]">
</script>

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>

GDPR consent granted

❌

Manually submits the consent status. Only use this parameter if no IAB TCF consent string can be passed and consent is given both for storing user data and for personalising advertising.


Please note that this parameter will only be considered if neither gdpr nor gdpr_consent is specified.


Permitted values: 0, 1.

gdpr_consent_granted=1

Normally, we determine the required GDPR data automatically via the TCF API implemented on the website.

If this is not present or cannot be used 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>

GDPR consent granted

❌

Manually submits the consent status. Only use this parameter if no IAB TCF consent string can be passed and consent is given both for storing user data and for personalising advertising.


Please note that this parameter will only be considered if neither gdpr nor gdpr_consent is specified.


Permitted values: 0, 1.

gdpr_consent_granted=1


Advanced Integration

Your unique account ID is passed as an event option via window.adup.push().

<script async src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>
<script async src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>
<script async src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>

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>'

GDPR consent granted

❌

Transmits the consent status manually. Only use this parameter if no IAB TCF consent string can be passed and consent has been granted both for the storage of user data and for the personalisation of advertising.


Please note that this parameter is only taken into account if neither gdpr nor gdprConsent is specified.


Permitted values: true, false.

gdprConsentGranted: true


Examples

Simple

Here, the options are passed via URL parameters directly upon the script call.

<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=1234">
</script>
<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=1234">
</script>
<script
    async
    src="https://s.d.adup-tech.com/services/pixel.js?account=1234">
</script>

Advanced

Alternatively, the desired parameters can also be passed subsequently (i.e. at runtime) via the global JSON object “adup”.

<script async src="https://s.d.adup-tech.com/services/pixel.js?account=1234"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>
<script async src="https://s.d.adup-tech.com/services/pixel.js?account=1234"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>
<script async src="https://s.d.adup-tech.com/services/pixel.js?account=1234"></script>
<script>
    window.adup = window.adup || [];
    window.adup.push({
    });
</script>