How do I use the engagement pixel?

Overview

In order for you to track engagement on your website, you must have at least one active campaign in your advertiser account.

How it works

With the help of the AdUp pixel, the engagement of the respective traffic source can be integrated even more heavily into the optimisation process. Engagement is evaluated based on session length and subsequent page impressions. The tracked data serves as the basis for the engagement score in your campaign statistics.

Engagement Score

The “Engagement Score” provides information about user behaviour after they have clicked 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. 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 this is a relative value. A single comparison over time (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 activity over the last 30 days. The values are therefore constantly updated.

Conditions

For a score to be visible in the frontend, 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 accumulated approximately 30 clicks with engagements.

Integration of the AdUp Pixel

In order to evaluate engagement, you only need to place the following script on your website.

It should be noted 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.

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

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

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

Normally, we automatically determine the required GDPR data 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:

gdpr

1 = GDPR applies

0 = GDPR does not apply

(omit) = Unknown (default)

gdpr_consent

The IAB consent string (base64url-encoded)

<script type="text/javascript" 
        async="true"
        src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]&gdpr=1&gdpr_consent=[CONSENT_STRING]">
</script>

<script type="text/javascript" 
        async="true"
        src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]&gdpr=1&gdpr_consent=[CONSENT_STRING]">
</script>

<script type="text/javascript" 
        async="true"
        src="https://s.d.adup-tech.com/services/pixel.js?account=[ACCOUNT_ID]&gdpr=1&gdpr_consent=[CONSENT_STRING]">
</script>

Examples

Simple

In this case, the options are passed via URL parameters directly when the script is called.

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

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

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

Advanced

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

<script type="text/javascript" 
        async="true" 
        src="https://s.d.adup-tech.com/services/pixel.js">
</script>

<script>
    var adup = window.adup || [];
    adup.push({"account": 1234});
</script>

<script type="text/javascript" 
        async="true" 
        src="https://s.d.adup-tech.com/services/pixel.js">
</script>

<script>
    var adup = window.adup || [];
    adup.push({"account": 1234});
</script>

<script type="text/javascript" 
        async="true" 
        src="https://s.d.adup-tech.com/services/pixel.js">
</script>

<script>
    var adup = window.adup || [];
    adup.push({"account": 1234});
</script>