Tracking Tag/Pixel Implementation and Pricing

Argyle can implement different levels of tracking tags/pixels from popular social media apps like Facebook, Pinterest, TikTok, etc.

There are generally 3 levels of implementation Argyle can perform to set up a tracking tag/pixel.

For ALL tracking implementation, Argyle must have access to the tracked domain and be able to change and implement the tracking code accordingly.

Base Code Implementation

This is the simplest tag implementation and only requires installing the base code for tracking tags/pixels. This will tell connected apps when a user from their platform has visited a page on the target website. Generally, it entails adding a string of code or an ID tag to the site, firing on all page views.

This implementation does not cover user behavior or conversion actions. Add to cart, viewed product, submitted lead form is not covered by base code implementation.

Time to implement: 30m – 1hr


  • Access to site code
  • Google Tag Manager installed on site
  • Access to Google Tag Manager container

Standard Event Tracking

Basic event tracking involves setting up the tracking tag/pixel to know if a user performs an action such as submitting a lead form, clicking a certain button on the site, or passing details on the type of post category being viewed. The key differentiator between basic event tracking and advanced event tracking is that advanced event tracking involves getting event details from a 3rd party software, typically an e-commerce software.

Example: with basic event tracking, we can build an audience from the pixel of users who like X post category (write about “Fashion”, build audience of “Fashion readers”).

The closest “conversion” data one can achieve with standard event tracking is lead generation, and will typically involve creating an audience of users who clicked a certain button to become a lead for the client.

Time to implement: 1.5hr – 2.5hr


  • Base code implementation (time included in estimate)

Advanced Event Tracking (E-commerce, 3rd Party Data)

This level of tracking is ideal for e-commerce funnel conversion monitoring and allows web apps to see cart conversion data, like add to cart and order completed. Argyle will need access to the web code of e-commerce platforms in order to install tracking tags with event code data in appropriate locations in the checkout funnel.

If checkout occurs on a domain or environment which Argyle cannot access, it will not be possible for Argyle to implement the advanced event tracking code.

Time to implement: 3.5hr – 5hr


  • Base code implementation (time included in estimate)
  • Access to E-commerce/3rd Party platform

Why do we not need standard event tracking?

Standard event tracking typically involves data that is generated by the site, whereas advanced event tracking looks at data generated by a 3rd party platform installed on the site. More often than not, setting up Advanced event tracking will not require standard event tracking to be set up since this data is sent via a 3rd party tool and not reliant on the client website.