With the help of the AdUp Pixel, the engagement of the respective traffic source can flow even more strongly into the optimization. The engagement is evaluated on the basis of session length and subsequent page impressions. The tracked data serves as the basis of the engagement score for your campaign statistics.
The "Engagement Score" provides information about the behavior after the click on your ad. This is a first indicator of performance, even before conversion information is available.
Try to preferentially obtain traffic with high engagement in order to buy in as many active users as possible. To do this, compare your ads using the engagement score. A comparison is especially useful between two campaigns, ad groups, ads, keywords or direct placements, as it is a relative figure. 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 shopped users for the selected time period. Also, a lower CPC, and therefore less purchased traffic, will not change the engagement score.
The engagement model always refers to the average activity of the last 30 days. The values are therefore constantly updated.
In order for a score to be visible in the frontend, two conditions must be met:
- There must be an engagement model for the advertiser, which in turn requires at least 100 clicks.
- An engagement score is only displayed for an entity (campaign, adgroup, placement, keyword or ad) when it has collected about 30 clicks with engagements.
In order to be able to evaluate the engagement, you only have to store the following script on your website. Please note that the AdUp Pixel must be stored on all pages (including subpages and booking confirmation pages). This can be done easily via (Google)Tag-Manager, for example.
The functioning integration code for your account ID can beviewed on the "Tools" > "Engagement tracking" page in the advertiser frontend.
Normally, we determine the required GDPR data automatically via the TCF API built into the website.
If this is not available, or it is not possible to use it for technical reasons, then you have the option to pass the GDPR data manually. The values can simply be specified as additional query string parameters when calling the pixel script.
1 = GDPR applies
0 = GDPR does not apply
(omit) = Unknown (default)
The IAB Consent String (base64url-encoded)
Alternatively, the desired parameters can also be passed subsequently (i.e. during runtime) via the global JSON object "adup".