Overview
This pixel is focused on tracking a single, specific conversion event (via page view) that results from your ad campaign, such as a page view on a confirmation or “thank you” page.
-
Best Used For:
- Measuring the success of a specific campaign goal
- Tracking both click-through and view-through conversions
- How it Works: Place this pixel on the page where ad traffic is directed and the page that loads after a user completes a desired action (like a form fill confirmation page). The pixel fires and records a conversion when a user who was exposed to your ad reaches the page(s) where the pixel is placed.
- Reporting: Reporting is available directly in the Ads Manager campaign dashboard under the “Web Conversions” report. It includes both click-through conversions (user clicked the ad) and view-through conversions (user saw the ad, didn’t click, but visited website later).
Please Keep in Mind
- There are 3 steps: (1) Create the Pixel, (2) Place the Pixel, (3) Add the Pixel to your campaign
- The conversion pixel is placed via an image tag.
- The conversion pixel begins tracking activity only once the associated campaign begins (and after the pixel is added to the campaign).
Create the Conversion Pixel Code
In order to create a conversion pixel, please follow these steps:
- In Ads Manager, click on the hamburger menu (
, 3 horizontal lines in the top left corner)
- Click on Manage Accounts
- Click anywhere in the row of the account you wish to generate the pixel code for.
- Navigate to the Tracking Pixels tab, then click on + New pixel
- Enter your Website URL with http:// or https:// (recommended) or it will not save. You can create as many pixels as you need and label them in such a manner that makes sense for your website.
- Name your pixel. This will be the name of the audience created.
- Select Conversion tracking pixel as the pixel type and click Save.
- All created pixels will appear under Existing pixels. You can click on each individual pixel created to view its details.
- To place the code on your webpage(s), click on Export Pixel Tags export button. This will download an Excel file containing the code details.
Install the Conversion Pixel Manually
If you’re not using Google Tag Manager, follow the instructions below to place the pixel code directly on your website.
- In the Excel file, copy the corresponding Image Tag code for your Conversion tracking pixel.
-
Replace {TIMESTAMP} with a cache-busting value (such as a timestamp). You can use the following code with the JavaScript-based timestamp:
<img src="https://bidagent.xad.com/conv/XXXXXX?ts=' + new Date().getTime() + '" width="1" height="1" style="display:none;"/>
Please note: Replace the XXXXX with your corresponding unique pixel ID
- Paste the pixel code, with the updated macro, into the header section of each page you wish to track.
- Navigate to the main HTML file (typically named header.php for WordPress or index.html), which controls the site’s header section.
- Carefully paste the entire pixel code exported from Ads Manager before the closing </head> tag. Be sure not to alter any of the surrounding code.
-
Example code below:
<!-- GT Conversion Pixel -->
<script>
document.write('<img src="https://bidagent.xad.com/conv/XXXXXX?ts=' + new Date().getTime() + '" width="1" height="1" style="display:none;"/>');
</script>
Please note: It is optional to include <!-- GT Conversion Pixel --> but may be useful to add for future reference, especially if you're using multiple pixels)
- Confirm that the pixel is firing on all site pages where you want tracking using these Validation Steps.
Install the Conversion Pixel via Google Tag Manager (GTM)
Create RegEx Matching Trigger
Always configure pixel triggers in GTM to match URLs with regex instead of exact match. Regex ensures the pixel fires even if parameters are added.
| Use Case | RegEx Pattern | Explanation |
| Fire pixel on all pages of a domain | ^https://(www\.)?example\.com |
^ anchors the match to the beginning of the URL (www\.)? makes the "www." optional example\.com matches your specific domain, ensuring it only fires on your site. |
| Fire only on the homepage | ^https://(www\.)?example\.com/?$ |
Builds on the previous pattern /?$ ensures the URL ends right after the domain, with or without a final slash |
| Fire on a specific subdomain (e.g., shop.example.com) | ^https://shop\.example\.com | ^ ensures match only with URLs that start with the exact subdomain specified |
| Fire for all blog content | ^https://(www\.)?example\.com/blog | ^ anchors the start of the URL and looks for any pages that begin with your domain followed by the /blog path |
Note: Google Tag Manager uses the RE2 regex engine, which does not support lookaheads/lookbehinds. Remember to replace example.com with your actual domain.
- In GTM, navigate to Triggers in the left menu.
- Click New.
- Name the Trigger (e.g., Page URL RegEx Match)
- Click into the Trigger Configuration box and select Page View as the Trigger Type.
- Change selection from All Page Views to Some Page Views.
- In the conditional settings that populate:
- Select the (+) image and choose Page URL
- Click the next drop-down menu (default shows contains) and select matches RegEx
- In the last blank field, paste your RegEx Pattern. See examples above for reference.
- Click Save in the top right corner.
- Follow the steps below to add/set the created trigger to your tag setup. For reference, example below shows use case #1.
Create a New Variable
- Navigate to Variables in the left menu
- Scroll to the User-Defined Variables section, click New
- Name the variable Timestamp
- Click into the Variable Configuration box
- Choose Custom JavaScript
- Copy and paste the below code snippet into the text box
function() {
return Date.now();
}
- Save
Implement the Variable into the Tag
- Navigate to Tags in the left menu
- Select the created tag you wish to connect (e.g., GroundTruth PageView)
- In the Tag Configuration box navigate to the Image URL field
- Move the cursor to the end of the pasted Image URL
- Click the (+) button at the end of the box to add
- Select the new variable (e.g., Timestamp)
- Save
Implement the Pixel as a New Tag
- Add the GTM container to your site. If Google Tag Manager (GTM) has not been installed, you can follow Google's setup guide.
-
Create a new tag in GTM.
- In GTM, go to Tags in the left menu.
- Click New.
- Click into the Tag Configuration box.
- Select Custom Image as the tag type.
- In the Image URL field, paste the pixel image tag provided in your pixel sheet (exported from Ads Manager).
-
Add Timestamp (Cache Busting).
- Replace {TIMESTAMP} in the pixel code with GTM’s built-in cache-busting macro.
- If {TIMESTAMP} variable doesn’t exist, then you'll need to create it and add it to the required tag. See instructions for Create a New Variable and Implement the Variable into the Tag below.
-
Set the Trigger.
- Click into the Triggering box.
- Select the RegEx trigger previously created.
-
Finalize the Tag
- Name your Tag (e.g., GroundTruth - PageView Pixel).
- Click Save.
- Publish your GTM container to make the changes live.
- Confirm that the pixel is firing on all site pages where you want tracking using the Validation Steps. Use Preview/Debug Mode to test and confirm the pixel fires correctly on target pages.
Add the Pixel to Your GroundTruth Campaign
The conversion pixel created is not yet linked to an ad group or campaign. To add it to an ad group or campaign, follow these steps:
- Navigate back to your campaign dashboard in Ads Manager.
- Click the eye icon to edit your ad group.
- Go to the Budget & Schedule section of the ad group.
- Scroll down to the Tracking Pixel section → Click the (+) Add tracking pixel from account button.
- Add the tracking pixel. The tracking pixel must be added to ALL ad groups of a campaign to track conversions comprehensively.
- Save the changes made in the ad group.
Reporting
Track and report on the actions of users who visit your page(s) after viewing or clicking on your ad
In Ads Manager
- In your campaign dashboard, click the Report Name drop-down menu and select Web Conversions. Note: this report is only available at the campaign and ad group levels.
- You have the option to view conversions for all of your tracking pixels or for individual pixels by using the Pixel drop-down on the left-hand side.
- The graph above the table will show one line tracking web conversions per day. You can change the start and end date of the report using the Duration feature.
- Option to export all pixel data using the export function within the dashboard, choosing Report Data. The report will include: ID: Pixel ID | Name: Pixel Name | Campaign Name: Shown at campaign level | Ad Group: Shown at Ad Group Level | Date: Only shows when row is expanded | Web Conversions: Total of both view and click conversions | View Conversions | Click Conversions
Difference between click-through conversion and view-through conversions
Click-Through Conversion: Often referred to as post-click conversion occurs when a user clicks on an ad and then takes a desired action on the advertiser's website or landing page. This action is typically a conversion goal, such as making a purchase, signing up for a newsletter, or filling out a contact form. Click-through conversions are directly attributed to the ad click, meaning that the user's action is directly tied to the initial click on the ad. Conversions are tracked with a 14-day look-back window.
View-Through Conversion: Also known as a post-impression conversion, occurs when a user is exposed to an ad (typically in the form of an impression or display ad) but does not click on it. Instead, the user later converts by taking the desired action on the advertiser's website. View-through conversions are attributed to the ad impression rather than the click. The time frame within which a view-through conversion is tracked on our ad platform is 14 days after the ad impression.
Frequently Asked Questions
-
My ad's clickthrough URL links to my site, but a 3rd-party site (like an ordering platform) handles the final conversion. What should I do? If your ad sends a user to
YourSite.comfirst, and then your site redirects them to3rdPartySite.comto complete the action, the tracking data will not get pass along. The 3rd-party site never receives the tracking code, so it has no way of knowing that user came from your ad. Our suggested solution is to direct traffic directly to the final conversion domain (e.g., the 3rd-party ordering page), which will skip the redirect and ensure the tracking codes are received and reporting more accurately. - Are conversion tracking pixels supported across all device types? Yes, our pixels are supported across Mobile, Desktop, and CTV/OTT.
- Can pixels be reused across multiple campaigns? Yes, pixels can be reused across campaigns and ad groups within the same account.
- How many pixels can I create? You can create as many pixels as you need and label them in such a manner that makes sense for your website.
- What is the look-back window for tracking conversions? The pixel uses a 14-day look-back window. This means a conversion can be attributed to your campaign if it occurs within 14 days of the ad impression.
- What is an image tag? It’s a simple, fast, and reliable method for triggering a server request (signal) when the page loads, thereby allowing the server to record the signal as a pageview or conversion.
Why do I need to use regex matching in when setting up pixels in a tag manager? Misconfigurations, especially around URL matching can cause dropped conversions and inaccurate reporting.
Why does exact matching fail when setting up pixels in a tag manager? By default, some advertisers set GTM triggers to fire pixels only on exact URL matches (e.g., https://www.example.com/thank-you). In our platform, we append query parameters to the landing page URL to track web engagements and provide detailed analytics for your campaigns (e.g., ?rid=123&capmaignId=456), the URL no longer matches exactly. This results in the pixel not firing and therefore lost conversions.
- What is a cachebusting macro? It’s a tool that prevents browser caching by automatically adding a unique name to a previously saved file to ensure that users are always receiving the most up-to-date version of the website without having to manually clear their cache.
- What is browser caching? When a user visits a website, the web browser downloads and saves files (e.g. logos, colors, fonts, etc.) to load the website faster when the user returns to the website in the future – loading files from the cache instead of re-downloading the files each time.
- What is a {TIMESTAMP} variable? This is a unique, dynamic value that represents the current time. It’s a short piece of code that generates a different number every time the page loads (i.e., a cachebusting macro). By adding a timestamp to the end of the pixel’s URL, you can make the URL unique for every visit, ensuring every pageview or conversion is recorded.
- I placed the pixel in the header section, but I’m experiencing load issues. The header is our standard placement, but if you notice any performance issues, try moving the pixel code to the very end of your page's HTML, right before the </body> tag. Placing it here ensures all of your page content loads before the pixel does, which typically solves any speed-related conflicts. For example:
<html>
<body>
<!-- Page Content -->
<!-- Conversion Pixel -->
document.write('<img src="https://bidagent.xad.com/conv/XXXXXX?ts=' + new Date().getTime() + "width="1" height="1" style="display:none;"/>');
</body>
</html>
Comments
Please sign in to leave a comment.