XING Tracking Pixel
The XING Tracking Pixel monitors and records the specific actions of the visitors you want to track. These actions or events are then displayed in XING AdManager, allowing you to analyse and gain insights into how users interact with your website or content. This data is valuable for evaluating the effectiveness of your online campaigns and making informed decisions to improve your marketing strategies.
For conversion tracking with the tracking pixel, XING visitors must go directly to your website after clicking on an advert placed on the XING website. Important:
To ensure accurate conversion tracking, please use links without redirects.
Please note that a pre-test for this function is currently not available.
Implementation
Step 1: Installing the base code
To begin the implementation process, the first essential step is to install the base code. This step is important as it sets up the main structure of the XING Tracking Pixel. To install the base code, copy and paste the JavaScript code below from the Tracking Pixel installation page in XING AdManager between the <head> </head> tags of your website. Install the base code on every page of your website to ensure consistent tracking across all pages. Once the code has been implemented correctly, a success message in the browser console will confirm the activation of the code.
Basis code (example)
Step 2: Check the installation
Once you have installed the base code on your website, a ‘Validation successful’ message will appear in the browser console to indicate that the installation has been carried out correctly. If, on the other hand, a message with ‘Validation failed’ appears, please check that the installation was carried out correctly.
Message ‘Validation successful’ (example)
Step 3: Installing the event code
Standard events act as universal triggers and capture basic user interactions in a system. These events represent different user actions. For example, ‘Purchase’, which occurs when a user completes a transaction and provides insights into purchasing behaviour. To enable the functionality of the event-specific code, it is necessary to install the base code first.
XING offers 8 standard events, which are listed below. To track these events, insert the event code at the specific location where you want to capture the desired events.
Please note: At least one standard event is required to receive data in the dashboard. For events such as ‘Page views’, ‘Add to basket’ and ‘Purchases’, a single user can generate multiple conversion events. For all other events such as: ‘Sign-ups’, ‘View content’, ‘Lead conversion’, ‘Submit application’ and ‘Apply for job’, each action represents a unique value.
A page call occurs when a user loads a page. In this case, you can add the base code and the ‘Page call’ event between the <head> </head> tags.
Eventcode (example)
Installation of the tracking pixel via the Google Tag Manager
Setting up Google Tag Manager tags for the base code
Setting up Google Tag Manager tags for the event code
Completing the setup of Google Tag Manager tags
Integration of Google Tag Manager scripts on the landing page
You will see corresponding events in the AdManager dashboard as soon as a XING user interacts with the desired element on your landing page.
Tracking scenarios with identical elements on a website
If a user encounters two identical buttons on the same website, such as two ‘Log in’ buttons, it is possible to distinguish and track each event as a unique event. This is made possible by adding an additional parameter to the code. With this parameter, it is possible to determine which particular ‘Sign In’ button the user has interacted with to allow for more detailed tracking. This method ensures that even in scenarios with multiple identical elements on a web page, our tracking system can differentiate between them, providing more accurate insights into user behaviour and interactions.
Method
xtp.xingTrk(<EVENT_TYPE_CODE>, <UNIQUE_EVENT>?)
Parameters of the method
<EVENT_TYPE_CODE> - String
The event code that identifies the event type. Check the table below for available parameters.
<UNIQUE_EVENT> - optional string
User-defined string to identify and distinguish a unique event. Check the table below to find out which events can use it.
| Event type | Event code | Tracking of identical elements | Description (example) |
| Signups | 'signups' | ✅ | Number of users who have signed up for your product or service. Each signup counts as a separate interaction. |
| Show content | 'view_contents' | ✅ | Number of users who have viewed your content. Each ‘view’ is a single interaction. |
| Page views | 'page_views' | Number of users who have viewed your page. There can also be several views per user. | |
| Add to carts | 'add_to_carts' | Number of users who have added items to the shopping basket. This can also be multiple items per user. | |
| Leads | 'leads' | ✅ | Number of completed lead-related actions. Each action is a single interaction. |
| Submit applications | 'submit_applications' | ✅ | Number of successfully submitted applications. Each application is a single interaction. |
| Purchases | 'purchases' | Number of purchases made. There can also be several purchases per user. | |
| Apply jobs | 'apply_jobs' | ✅ | Number of applications submitted. Each application is a single interaction. |
Beispiele
xtp.xingTrk('signups')
xtp.xingTrk('signups', 'foobar')
Find out more
Please refer to the FAQ page if you have any questions.
Click here for the FAQs