Deploying and Maintaining your Corvidae Pixel  

What is the Corvidae Pixel? 

Our pixel is a 1 pixel by 1 pixel transparent image, which is placed on our customers websites and, when the webpage loads, the pixel ‘fires’ which means it collects browser and session data (in the form of clickstream data), sending it to Corvidae’s secure data storage. 

Once the pixel is placed on the client’s website, we need to tell it information about the clickstream data it collects so that we can categorise each visit correctly.​ This tracks clicks the user makes, where they come from, what they do, and many more details taken about device, location, etc. 

The Corvidae pixel has two use functions depending on where it is deployed.​ 

We place the pixel on the client’s website using Google Tag Manager to collect clickstream data.​ We can also place it directly on their website if required. 

We embed the pixel in the creative used by partners to track impressions for activity such as Display and Native.​ 

The pixel is 1st party, meaning it is served from the customers domain. This provides a greater depth of data. 

Why do I need it? 

The Corvidae pixel has two use functions depending on where it is deployed. 

We place the pixel on the client’s website to collect clickstream data. 

We embed the pixel in the creative used by partners to track impressions for activity such as Display and Native. This means the same 1 pixel by 1 pixel image will be present, but can track if a user only sees the ad, without clicking on it. 

The clickstream click and impression data are both used to build the user journeys Corvidae attributes revenue towards. 

Pixel Deployment & Architecture​ 

To enable first party collection, we request the customer’s DNS is updated, following these instructions:​ 

Single Server Client DNS set up​   

Record TypeValuePoints to
Example: corvidae​ 
Provided by QueryClick

Dual Server Client DNS set up​ 

Record TypeValuePoints to
Example: pixel​ 
Provided by QueryClick
Example: pixel​ 
Provided by QueryClick
Example: corvidae ​ 

This would require an alteration to be made by whoever manages the website development of the customer, but that should be it on the client side. QueryClick would then handle adding the pixel servers, with SSL.​ 

Queryclick needs to be informed with the final subdomain set on the CNAME record (Example: corvidae.domainname). The rest can be internal first party domains. ​ 

 Example Pixel Deployment in GTM 

Google Tag Manager Setup for Clickstream Collection​ 


The client gives us access to Google Tag Manager​ (We do not require publish rights, but to allow progress to be made, someone on the customers side must be available to review and publish promptly and often during onboarding) 

The client gives access to test transaction codes or other ability to test pixel firing on transactions​. This may be an agreement to pass purchase IDs back to someone in the business who can cancel the orders before they are processed. 

This allows us to ensure the correct transaction value is recorded, in the correct currency, aligned against the right product details, etc. 

  1. Go to the GTM account and add our JavaScript snippet as which is used to specify what data is collected and where it goes.  
  2. Test changes in preview mode.  
  3. Ask customer to publish or if we have permissions publish the changes.​ 
  4. Once published wait until the changes are live and then access the domain and make sure there is a hit on the pixel when visiting the pages. 

Impression partners URL setup​ 


The client produces a list of partners from where they want impressions tracked.​ 

Important keys: AID needs to be client specific and created by the Corvidae team. This AID cannot be a subset or superset of another ID.​ 

Partner names used in pixel calls must be partner specific and also must NOT be a strict subset or superset of another partner’s name.​ 

Provide the URL for partners to fire the pixel on impressions and click throughs.​