Impressions can be served outside of a specified Geo area due to VPNs or Proxy Server. For instance, if someone is traveling and logging into their company’s VPN, the impression will be served in the user’s actual location even though it looks like they are in the city associated with the VPN. Geo targeting is based on databases that map IP addresses to geographic regions. As with any comparison of reports across systems discrepancies will exist due to the technological differences. Qunatcast works extensively to constantly maintain and update our databases to ensure accurate Geo targeting for our clients.

Absolutely. You can continue to access cookie data on the detailed Traffic Tab. Just select the “cookie” tab on the traffic chart to switch from people to cookie counts.

Prior to our cookie corrected model launch (June 23rd, 2008), Quantified sites had unique cookie data reported as their default traffic count. All Quantified sites now have people counts reported as their default traffic count, across all components of our service.

While cookies provide valuable learning related to traffic flow on a site, they do not provide the people-based insights that advertisers demand. We believe facilitating a view of both cookie and people-based intelligence is a critical advancement that will enable addressable advertising.

At Quantcast we have access to multiple complementary data sources. We have several clickstream data sources that allow us to calibrate our cookie correction models. Quantcast Measure captures billions of media consumption events every month. What’s more, many of our Quantified sites share anonymous identifiers with us that are independent of cookies. This mass of data – with different collection processes, biases and issues — allows us to effectively “triangulate” and develop dynamic, and accurate projections. For additional insights into how our model works see our Cookie Corrected Audience White Paper.

The impact of cookie deletion and multiple machine use/people use per machine is not uniform and differs significantly between sites. In some cases, though, it is not unusual to see an average of two (or more) cookies for every browser over the course of a month. A variety of factors must be taken into to account to properly adjust property level translations from cookies, to people. Quantcast has issued a Cookie Corrected Audience White Paper that discusses many of the considerations we factor into our model. At a high level, these include time period of evaluation, frequency of visit of user, cookie deletion rate and machine use behavior of a specific properties audience.

As text files, cookies may be deleted from time to time. If the cookie for a particular website is deleted between visits, a browser is issued a new cookie upon its return. In such cases, the website will have recorded two cookies for the same individual browser and the resulting cookie count is actually larger than the number of browsers that have visited the site.

Adding complexity to this problem, while many people may use the same browser to access a website, others may use multiple browsers or machines (at home and work, for example) to access the same website. This creates a more complicated environment and is why Quantcast has developed a sophisticated model to deal with cookie deletion and multiple machine usage to produce accurate estimates of the number of people that visit web destinations.

Quantcast is paid when Quantcast Advertise data is used to deliver an ad. Publishers can work together with their Quantcast representative to determine the best client-facing pricing methods that work for them. Quantcast Measure, is free of charge.

Cookie-Corrected Audience Data: Adjusting for Cookie Deletion and Machine Usage

No. Quantcast enables publishers (including many ad networks) to transact directly with marketers, working with them to define their specific audience targets. Marketers purchase inventory against these audiences directly from the publishers

We have the industry’s largest, real-time media consumption data set, enabling effective, real-time audience targeting at scale.

With over 100+ million web destinations measured by Quantcast, we’re able to ‘see’ all 245+ million people online in the U.S. — that’s everyone.

Our web-wide visibility means we can create nuanced audience models, find millions more customers that look like them, and effectively target those audiences at meaningful scale.

Because we process data in real time, our models are dynamically updated. This means we’re able to deliver precise targeting, even as online audiences change.

We start with a set of customer archetypes that best represent an audience segment. These archetypes can come from an advertiser’s first-party data, or online/offline transaction data from trusted providers. The customer archetypes act as ‘reference points’ for our targeting technology to find more consumers who look just like the archetypes.
Factoring in billions of observations, we identify the distinctive characteristics of the customer archetypes to build a unique audience model. The model is then compared to the entire online population, finding users who match those characteristics– this creates a unique audience segment that can be targeted across your inventory.

As a result, advertisers reach only the best customer prospects, even as online audiences change.

Quantcast Advertise enables marketers to:

• Reach specific demographic targets
• Find and target nuanced, unique audiences based on their own proprietary insights
• Target heavy-spending consumers across numerous product categories, leveraging anonymous online/offline purchase data
• Reach all of these target audiences at scale, using real-time data

Quantcast Advertise enables publishers to:

• Directly measure and understand their audience with detailed insights into traffic, demographics, geographies, lifestyle, and business data—completely free of charge
• Deliver effective, real-time audience targeting solutions to marketers
• Grow revenue by capturing more brand dollars from new and existing clients

Websites, publishers, networks, and advertisers—anyone interested in learning about web audiences and/or advertising online.

Yes. Quantcast supports PhoneGap. Learn more on our GitHub page.

No – it is not counted as an additional Visit. In this scenario, the visit would be attributed to the last Visit that occurred when the app was last active.

Please refer to the Integration Guide for iOS or the Integration Guide for Android.

No. Quantcast does not currently offer targeted advertising services for mobile apps.

The API Key is a long numerical code that must be pasted into the SDK – please consult the Quantcast Measure for Mobile Apps Implementation Guide for instructions.

Yes, when signing up for an app, you must choose a required “Network” field.

Traffic charts will be available in your Quantcast Measure profile, once the Quantcast iOS/Android SDK has been implemented and we receive data from your app.

Reports will be visible in your Quantcast profile page approximately 1-2 days after we begin receiving data. You will need to make sure that the SDK is properly implemented and the Terms of Service have been accepted.

An experienced app developer should be able to implement the iOS SDK and Android SDK within a few hours.

No. The Quantcast iOS SDK and Android SDK have been designed to have minimal impact on size, speed and device battery life.

Please see our Implementation Guide for instructions on how to implement Quantcast’s iOS and Android SDKs.

If you have any questions on the implementation process, please email us at A team member from Customer Support will respond as soon as possible.

You must operate a mobile application to receive measurement reports. You must also integrate the Quantcast SDK (software development kit) within your mobile app.

Once the tag has been placed on every page of your site, there is a 24-48 hour window where your profile will say “measurement in progress” (top right corner). After the tag has collected approximately 5 days worth of data, your site will be officially ‘Quantified’.

Yes. Our tag ultimately measures the number of times a browser loads Ajax, whether the load was triggered by a user or by an Ajax call. This is represented as “impressions” or “events” in our reports.

For sites that make heavy use of Ajax, there are considerations to be made in interpreting this number: It can understate user engagement if the site updates much of its content through Ajax without reloading our tag, or it can overstate engagement if the site reloads our tag when the user session is inactive.

We observe anonymous records of visits to Internet destinations. Quantcast does not collect any personally identifiable information (PII). All of the analysis conducted by the Quantcast system is done using anonymous Internet usage information. For further information please review our privacy policy.

We collect directly measured data from the millions of web destinations and mobile apps controlled by Quantified publishers. All the data we collect is anonymous and contains no personally identifiable information (PII).

No. The asynchronous tag is fully compatible with the previous version of the tag.

No. Assuming you simultaneously remove the old tag while adding the asynchronous tag, there will be no impact on your reporting.

By loading in the background, the number of direct calls is minimized and latency is improved, ensuring proper measurement with minimal impact on user experience.

For instructions, visit our Web Measurement Implementation Guide.

“Asynchronous” essentially means it does not disrupt page loading or user experience. The tag is backwards compatible with the previous Quantcast JavaScript tag (see below), and supports all existing Quantcast services.

No. Many websites also run a web analytics package in addition to Quantcast.

Yes. Sign into Quantcast and follow the instructions to Quantify your site. Be sure your Quantcast tag is placed on all pages of the site.

Quantcast can see these tags provided you follow the instructions in our advanced measurement guide.

No. To ensure proper functionality, the tag layout must remain completely unchanged in order to be quantified.

We recommend doing a realistic assessment of your organization, and consider implementing a third-party audit and monitoring tool.

No. quant.js must be dynamically generated from our specially configured servers in order to generate audience data for your site. It does not work properly from any other server.

After you have implemented the Quantcast tag on your website(s) and have submitted the URLs within the tag generator, sites will appear in your profile within 24-48 hours.

Yes: Take a look at our Best Practices for Tagging as well as the Web Measurement Implementation Guide.

Traffic reports will be available within 4 to 6 days. Demographics, geographies, lifestyle, and business reports are available in 4 to 6 weeks.

Quantcast is a member of the Digital Advertising Alliance (“DAA”) ( and is in compliance with the Self-Regulatory Principles for Online Behavioral Advertising.

Yes. While Quantcast’s most comprehensive dataset is in the U.S., we have global data as well.

Absolutely. You can continue to access cookie data on the detailed Traffic Tab. Just select the “cookie” tab on the traffic chart to switch from people to cookie counts.

No. Quantcast finds new audiences that match a marketer’s defined target, extending the reach of their messaging. Retargeting extends the frequency of messaging to consumers who have already interacted with the brand.

Quantcast Advertise is Quantcast’s targeted advertising solution for advertisers and publishers, addressing a full range of advertising objectives, from awareness to sales. Learn more about Quantcast Advertise.

Simply remove the Quantcast Measure pixels from your website to discontinue participation in the measurement program.

To understand your entire online audience, tag your website, display media campaigns, paid search campaigns and social media assets. The more channels measured by Quantcast, the more accurate and comprehensive the audience insights will be.

Data is available in 30-day windows up to the latest Saturday.

All data in Quantcast Measure can be hidden from public view, accessible only via login and password. Website owners have full control over the accessibility of their data.

You can:

• Define your audience at all stages of the consumer funnel

• Understand how those audiences are unique, in comparison to the general Internet population

• View categories of sites and specific sites your audience is likely to visit

• Identify the geographic regions of your audience

• Improve marketing programs by understanding ‘who’ is interacting with your assets and content

Quantcast Measure is available to marketers at no cost.

Quantcast takes enormous care to provide quality, accurate information. As a result, we will not display information until it passes our rigorous standards and tests. Some sites will not be large enough for us to generate demographics, but if we see at least 100 monthly uniques after your site has been Quantified you should start seeing demographic profiles within 1-2 weeks. For mobile apps, we require 1,000 monthly active users in order to generate demographic profiles.

When properly implemented, Quantcast data will line up closely with most web analytics packages—However, there are several common problems that account for the vast majority of issues with data alignment:

• Your tag is not placed on every page of your site. In order for us to accurately measure your site, it is essential that the tag be placed on all pages — consider placing it in a common footer file.

• You are recently Quantified. If we don’t have 30 days worth of data on your website or network, we attempt to project our metrics based on the data that we have seen. For instance, if you Quantified your site on a day with very low traffic, it’s likely that our 30-day projection will appear lower than your actual site traffic. These numbers will converge on your true traffic as we gather more data. An easy way to make sure we are seeing all of your traffic is to log into your Quantcast account, open your profile, and visit the Traffic tab. Click ‘Download traffic stats’ and ensure that the daily page views align fairly closely with your internal analytics.

• Your tag has been removed or malformed since Quantification. Oftentimes our tag is accidentally removed, or altered in a way that interferes with its correct operation, by accident. If you’re experiencing a sudden change in traffic, please ensure that the tag on your site is exactly as it appears in the ‘Network & Setting’ tab of your account, and ensure that it remains on all of the pages of your site.

• You’re using server log data that is counting unique IP addresses. This methodology tends to overstate the number of people visiting a site, as the same Internet user’s IP can change frequently for a large variety of reasons. Quantcast will also not count bots or spiders visiting your website, whereas the IP-based methodology will.

• Terminology varies slightly between different analytics packages. Typically, ‘Pageviews’ is counted fairly evenly across different analytics platforms (although they may appear higher when spider and crawler pageviews are being counted), so that is usually the best metric to use when comparing results. If there is a large difference between the pageviews Quantcast is reporting and the pageviews your analytics package is reporting, it’s most likely indicative of a faulty implementation.

If your site is not Quantified, then we’re only able to present estimates for your audience. These estimates are only as accurate as traditional panel-based measurement services, as we are relying solely on third-party data. Quantcast’s system is collaborative and sites can participate in our continuing effort to offer the most accurate data available by getting Quantified, free of charge. Quantcast Measure incorporates your real site traffic into the audience calculations, thus offering the highest degree of accuracy.

Quantcast provides Quantified sites with audience data based on directly measured census-level traffic. As a result, Quantcast audience data should align with a site’s internal reporting. Syndicated services typically report data based on panels, projecting a publishers’ total traffic off a small subset of their actual traffic.

The syndicated services may also be reporting different aggregations of domains, subdomains or even specific pages. As a result, traffic assignments may not line up between services. In such an environment, resulting data is not an exact apples-to-apples comparison.

Another possible difference – Quantcast audience data is based on visits, which may not be the case for other services that report traffic on basic audience composition.

After you’ve submitted your request, the website will receive a notification that you’d like access to this data. The notification will include the name and email address associated with the your Quantcast account. At that time, the website can choose to accept or deny your request for data. Additionally, the website may contact you directly.

If the website has granted your request to access hidden data, you will receive a notification in your Quantcast account. Once you’ve been granted access, viewing the reports is as easy as going to that publisher’s profile. The data that was previously hidden will now become visible (you must be logged into your Quantcast account). Note that the website may at anytime recall data access rights.

Quantcast will provide separate profiles on each of a site’s subdomains as long as the Quantcast tag is present. There is no need to add in each subdomain separately from the domain, as Quantcast will automatically generate them under the ‘Subdomains’ section of your profile.

As a Quantified site, you have complete control over which data is public, and which is kept private. Data visibility can be configured in the Home section by clicking “Edit settings” and selecting options in the “Public Access” section.

Access to data is on a site-by-site basis (also set in the ‘Home’ tab, select ‘Sites’ > ‘Settings’ > ‘User Privileges’). Please note that access can only be granted to individuals with a registered Quantcast account, available for free at

Affinity is best described as the tendency or likelihood of a user to perform a certain action. In this instance, Quantcast views a particular site’s entire audience, and gauges how likely they are to visit another specific site. The number is a representation of this group’s tendency to visit that other site compared to the rest of the Internet.

For example:Site A has a 14.0x affinity to site B

This means that a visitor from Site A is 14 times more likely to also visit site B, in comparison to the average Internet user.

A Network can be made up of both fully Quantified sites and distributed media (syndicated traffic), and we classify these differently to make analysis easier for publishers:

• Website traffic is what Quantcast sees from sites that are Quantified under your account.

• Syndicated traffic is what Quantcast sees coming from your tag, but not on a site you have listed as Quantified—for instance, if you distribute your widget to another site that isn’t yours.

• Network traffic is the sum of both Syndicated and Website traffic, indicating the full reach of all of your Quantcast-tagged assets.

Ensure that you have created a Network view. Log into your Quantcast account, and click the Home section. Click ‘Create Network’ which will prompt you to enter a name for your network. This will instantly create a network view that will include the reach of all of your distributed media.

Once the tag has been placed on every page of your site, there is a 24-48 hour window where your profile will say “measurement in progress” (top right corner). After the tag has collected approximately 5 days worth of data, your site will be officially ‘Quantified’.

Yes. Our tag ultimately measures the number of times a browser loads Ajax, whether the load was triggered by a user or by an Ajax call. This is represented as “impressions” or “events” in our reports.

For sites that make heavy use of Ajax, there are considerations to be made in interpreting this number: It can understate user engagement if the site updates much of its content through Ajax without reloading our tag, or it can overstate engagement if the site reloads our tag when the user session is inactive.

We rely on third-party data to measure properties that are not Quantified, derived from a variety of sample data sets collected from ISPs and Toolbar providers. Because these estimates are not based on actual census level traffic, they are subject to many of the same sample size and population biases that traditional panel-based audience measurement services encounter.

For Quantified sites, traffic numbers are updated daily and work on a rolling 30-day basis (traffic statistics shown are from the previous 30 days). For non-Quantified sites, data is updated monthly.

The People number aims to describe the actual number of human beings viewing a web property: One of the several issues with using the pure ‘cookie-counting’ methodology is that it does not account for the same person visiting the same site from multiple computers. The same person is visiting the site, but they are being counted as if they were two. You can read more on Quantcast’s methodology here.

Yes, you should compare Unique Visitors/Absolute Unique Visitors with the ‘Cookies’ statistic that we provide for Quantified Publishers.

JavaScript-based analytics packages calculate a site’s Unique Visitor number by counting the number of unique cookies seen over a specific period of time.

Quantcast uses an inference model to characterize audiences of nearly any size. Quantcast has NOT built its model on PII (personally identifiable information), but instead uses a large-scale mathematical model to infer demographics of visitors.

The inference approach is built on a foundation of direct measurement, using numerous data inputs that provide insight into demographic benchmarks. These benchmarks are the foundation for rich audience segments used across millions of digital media assets.

Quantcast automatically excludes robots and spiders from your traffic count as long as they identify themselves in the User-Agent request header. Traffic generated by Googlebot, monitoring services such as Gomez, and others known to the IAB’s Bot and Spider List will also be excluded from your traffic counts. If you’re using an automated, homegrown means of generating traffic to your site, you should make sure it identifies itself by putting “robot” in the User-Agent.

Internal traffic (visits from you or other employees/contributors to your own site) is a tiny part of a typical site’s audience—our studies have estimated internal traffic at less than 1% of the total. If you’re generating an unusual amount of internal traffic, we recommend adding server logic to your pages in order to exclude our measurement tag on requests from your own IP address. Alternatively, you may consider configuring your firewall to block requests to referred from your site.

If your staging environment is a subdomain of a site you’ve Quantified, such as, you may see reporting on this traffic rolling into your total. The best way to keep our measurement pixel from reporting traffic on these kinds of pages is to either include the pixel selectively when you generate these pages, or configure your firewall to block requests to referred from that domain.

You can download audience data for any of your properties or audience segments in CSV format. This includes all report information you see when you sign into Quantcast, including traffic, traffic frequency, demographics, geographies, lifestyle and business. To start, sign into Quantcast and click the Download button to select the data you want to use.

Getting Quantified will allow you to gather traffic information, as well as granular demographics, geographies, lifestyle and business data for all of your properties.

Quantcast Measure is completely free of charge.

We do not remove sites from our listing. We recommend getting Quantified in order to get more accurate traffic statistics as well as gain control over which data points you make visible to the public, and which you use for internal purposes only.