Download websites that use Pinterest Conversion Tag

About Pinterest Conversion Tag

An advertising pixel is the least ambiguous thing in a technology dataset. Nobody installs Pinterest Conversion Tag by accident, nobody inherits it from a theme, and nobody leaves it behind on a site that never ran a campaign. A detection means somebody opened an advertising account, built a campaign, and cared enough about attribution to put measurement code on their own pages.

The tag is a JavaScript snippet from Pinterest, Inc., part of a Proprietary advertising platform and available since 2014. The job of the tag is to close the loop between an impression on the network and an action on the advertiser's site, reporting page views, cart additions, checkouts and signups back to the campaign that produced them. Advertisers who install it are usually building retargeting audiences at the same time, which is why the code tends to sit across a whole site rather than on a single landing page.

What that implies about the business is unusually specific. The network is a visual discovery platform with a commerce heavy audience, so its advertisers cluster in home goods, fashion, food, weddings, crafts and interiors, and they lean towards direct to consumer sellers rather than service firms. A domain carrying the conversion tag is a retailer with a marketing budget, an attribution mindset, and at least one paid channel already running.

The country column puts United States at 150,128 sites, and the concentration follows the network's own audience rather than any technical factor. Channel adoption is geographic in a way that infrastructure is not. Advertising tools spread where the audience already is, so the country field on this entry can be read as a genuine market signal rather than a hosting artefact. The suffix column is concentrated in .com, consistent with a retail advertiser base selling across borders from generic domains.

Detection has a real limitation here. The tag is very often deployed through a tag manager, and when a container injects it after the page loads, the fingerprint is not present in the delivered markup we analyse. Sites run by professional agencies tend to work that way, so the measurable population is biased towards direct installations and the count is a floor rather than a total.

The commercial case for the list is easy to state. Competing ad networks want the advertisers, agencies want the accounts, ecommerce tooling vendors want businesses that already spend on acquisition, and analysts want to know which platforms merchants are genuinely funding. A per domain lookup serves none of those, because the question is never whether one named shop runs the pixel. The question is which shops run it, where they are, what else they run alongside it, and how the set changes between one release of the data and the next.