How do I use the engagement pixel?

Overview

With the Engagement Pixel from AdUp Technology, you measure interactions that are not directly considered a conversion but still provide crucial signals for campaign evaluation.

These include, for example:

• Page views

• Scroll depth

• Time on page

• Clicks on specific elements

• Views of individual content areas

The Engagement Pixel helps you better understand user behaviour and optimise campaigns based on data.

How Engagement Tracking Works

The Engagement Pixel is triggered on specific pages or during defined user actions.

Unlike the Conversion Pixel, the Engagement Pixel does not measure completed conversions, but rather interactions along the customer journey.

This allows you to analyse, for example:

• which content is particularly relevant

• how far users scroll on a page

• which landing pages perform well

• which campaigns deliver high-quality traffic

Tracking is carried out via an embedded pixel.

Creating Engagement Code

Step 1: Log in

Log in to the Advertiser Frontend using your credentials.

Step 2: Open Pixel Management

Navigate to:

Tools → Engagement Tracking

Step 3: Create New Engagement Code

Click on:

Create Engagement Code

Step 4: Configure Engagement

Assign:

• a unique name

• a description of the engagement goal

Examples:

• Scroll depth 75%

• Blog article read

• Product detail page viewed

• CTA clicked

Step 5: Save

After saving, the new engagement code will automatically appear in the overview.

There you will also find the completed integration code.

Installing the Engagement Pixel on Your Website

Standard Integration

Embed the Engagement Pixel on the desired page or during the corresponding event.

Example:

<img

src="https://d.adup-tech.com/campaign/engagement/[USER_ID]?[PARAMETER]"

width="1"

height="1"

border="0"

alt=""

/>

You can find the individual integration code in the Advertiser Frontend under:

Tools → Engagement Tracking → Actions → Integration Code

Triggering Engagement Pixel Dynamically

The Engagement Pixel can also be loaded event-based via JavaScript.

This is particularly useful for:

• Scroll tracking

• Click tracking

• Video interactions

• dynamic content

• Single Page Applications

Example:

<script>

const img = new Image();

img.src = "https://d.adup-tech.com/campaign/engagement/[USER_ID]?t=ABCDEF";

</script>

Typical Areas of Application

Measuring Scroll Depth

The pixel is triggered as soon as users reach a specific area of the page.

Evaluating Content Engagement

Measure which content is most frequently consumed or read in its entirety.

Recording Clicks on Call-to-Actions

Track interactions with:

• Buttons

• Forms

• Download links

• external links

Measuring Video Interactions

The Engagement Pixel can, for example, be triggered on:

• Video start

• 50% playback

• complete playback

Required Parameters

Parameter: t

The parameter t contains your unique engagement code.

Requirements

• maximum 255 characters

• UTF-8 and URL encoded

Example

t=ABCDEF

Optional Parameters

Parameter: label

Optional label for a more precise description of the engagement.

Examples:

• scroll_75

• video_complete

• cta_click

Requirements

• maximum 255 characters

• UTF-8 and URL encoded

Example

label=scroll_75

Parameter: value

Optional numerical value for the measured engagement.

Examples:

• Scroll depth

• Percentage value

• Time on page

Example

value=75

Best Practices

Track only relevant interactions

Only measure engagements that actually allow conclusions to be drawn about user interest or campaign quality.

Use uniform naming

Use consistent names and labels so that reports can be analysed more easily later on.

Example:

• scroll_25

• scroll_50

• scroll_75

• scroll_100

Do not trigger pixels unnecessarily often

Avoid triggering the same event multiple times within a session, unless this is explicitly required.

Test tracking after integration

Check after installation:

• whether the pixel is loaded correctly

• whether the parameters are transferred correctly

• whether events are triggered only once

Common Sources of Error

Pixel is triggered multiple times

This can distort engagement values.

Missing event-logic

For dynamic events, make sure that the pixel is only triggered under the desired conditions.

Invalid parameter values

Ensure that values are transmitted correctly URL-encoded.

Differences to the Conversion Pixel