How do I check that my Chartable web pixel is properly installed?

After installing the Chartable web pixel on your website, the next thing you should do is verify that Chartable is receiving the expected data!

This tutorial will walk you through the process of checking your web pixel installation via the SmartAds Web Pixel report tool. This tool exports detailed reports containing the data that your web pixel is passing to Chartable.

Confirm Chartable is receiving event data

Once you have placed the web pixel on your site, you need to confirm whether Chartable is receiving any event data from your web pixel. To do this, log into your Chartable account, and navigate to the Pixel Integration page.

If you see the "Status: Pending" message at the top of the page, the pixel has not been placed properly and we haven't received any data. Depending on the traffic volume to your website, this may take an hour or two to update.

If you see the "Status: Active" message, then Chartable has received some data from your web pixel, which does not necessarily mean that the pixel is properly installed. 

Once you see the "Status: Active" message, you must also verify that Chartable is receiving the expected data, following the steps in the next section.

Confirm the Web Pixel Report contains expected data

Generating a SmartAds Web Pixel Report

First, log into your Chartable SmartAds account, and navigate to the Reports page. Go to the "Create" tab, and then click "Web Pixel Events."

You will see a variety of options to generate the report that looks as follows:

Each action shown in this list corresponds with an event action on your website that you may optionally pass through to us via the Chartable web pixel. If you want to verify all of the data the web pixel is sending to Chartable, you'll want to select all of the boxes. After you have made your selection, you can generate the report.

The actions are defined below:

  • "init" - this is basically a single page view event. It will be triggered each time the Chartable web pixel is called.

    The following actions are optional and may not appear in your report:
  • "pageview" - if you are sending Chartable the page type
  • "checkout" - if you are sending Chartable the start of a checkout event
  • "add_to_cart" - if you are sending Chartable add to cart events
  • "purchase" - if you are sending Chartable purchase events (orders)
  • "lead" - if you are sending Chartable lead events
  • "code" - if you are sending Chartable attribution codes
  • "identify" - if you are sending Chartable user registrations or unique user IDs

Downloading the report & extracting the spreadsheet

Once you've clicked "Generate Report" this will generate a CSV spreadsheet report that may take up to an hour to produce. When it's complete, you'll receive an email and see it available for download in the Reports page of your Chartable dashboard.

Once you've decompressed/unzipped the file, you'll have a .csv spreadsheet that can be opened in Microsoft Excel.

Viewing the SmartAds Web Pixel Report spreadsheet

After opening the .csv in Excel, you'll see the following columns:

  • request timestamp - this is the date/time of the request (in the UTC time zone)
  • action - these are the various actions that can be sent by the web pixel. Note that the 'init' action is a single request to the basic installation and can generally be considered a single pageview event. If you've selected this action for the report, you will see a lot of 'init' events. Tip: Use the Filter functionality in Excel (found under the "Data" tab) to see what "action" types are being sent to Chartable
  • properties - these are the additional optional properties that may be passed with each endpoint. For instance, an 'order' action may have an 'id', 'value', and 'currency' property. These are optional, and not every action will have associated properties. Properties are shown in a list format.
  • url - The url where the action was triggered
  • domain - The domain where the action was triggered

Note that the report will be for the date generated and will contain all of the events that Chartable has received during that time. The report is all of the raw event data from your site, not only events associated with podcast campaigns. This is the data that Chartable will ultimately use to compare to the data we received from the podcast in order to attribute events to your podcast campaigns.

Verifying the pixel events

Confirm that the data shown in this report is what you'd expect. Take the opportunity to Filter on the various "action" types included in the report (if more than "init" are showing) and verify that the volume of these events and their associated "properties" are correct.

If you only see "init" events, that means the basic implementation of the web pixel is in place and Chartable will be able to attribute visits and response rate (but not any other advanced funnel or conversion/purchase events). If you see other "action" types like "purchase" or "lead", that means you are also sending those events... be sure to verify that they look correct.

For instance, do the number of "purchase" events look correct for the time period? Do they include the correct "properties" like "id" and/or "value" (assuming you planned to pass them to us)?

If not, the pixel may not be properly installed and you'll want to examine the syntax and that it's on the proper pages.


  • Chartable can not provide technical support on pixel implementation or verify pixel placement. You must closely follow the directions outlined in the article in the section "Chartable Web Pixel Best Practices"
  • Note that though our web pixel is compatible with various third party software systems like Google Tag Manager, Google Floodlight, and Tealium, Chartable cannot provide technical support for third party software.
  • The "Advanced Endpoints" are optional. If you implement the basic implementation (in the "Installation" box) we can report on Household visit and response rate data. Integrating advanced endpoints gives more insight into attributed funnel activity including conversions.
  • If you are using an "Advanced Endpoint" like "purchase" or "lead", you must make sure that the basic Chartable pixel implementation (in the "Installation" box) is also implemented on the same page where you are triggering the advanced endpoint.  The basic implementation also must be called before you call the advanced endpoint. 
  • The parameters in the "Advanced Endpoints" are optional. For instance, you can trigger the "purchase" endpoint, and omit the order ID or order value (though it is recommended that you include that information).

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us