Pixel Code
Once you've registered a campaign, generate the tracking pixel code and embed it on your pages or creatives.
Generating the pixel tag
The pixel is a single <script> tag with your campaign ID:
<script src="https://l.csfy.me/je?c={campaign_id}"></script>
Replace {campaign_id} with the ID returned from pixel registration.
When loaded, the script resolves to a small payload that captures the page URL and reports it back to Classify:
window._turquoise = [
"s51dSW4gUyFfIzdHlB8AFnB4FWwHf3EDcwWZUPoyIA==",
];
document.head.appendChild(
Object.assign(document.createElement("script"), {
src: "https://t.csfy.net/p/latest.js",
async: true,
})
);
Macros
The pixel supports arbitrary key-value pairs appended as query parameters. This is especially powerful when combined with DSP macros, which expand into auction-time metadata.
Example: Google Ad Manager
Google Ad Manager's %%SITE%% macro expands into the auction domain. Pass it through to cross-reference the auction domain against the actual serving domain:
<script src="https://l.csfy.me/je?c={campaign_id}&google-site=%%SITE%%"></script>
In your reports, you'll see a google-site column with the expanded macro value. Comparing this to the actual serving URL is a powerful tool for catching inventory misrepresentation.
Common macros
These macros are available across most major DSPs:
| Macro | Description |
|---|---|
INVENTORY_DOMAIN | The domain of the inventory where the ad served |
INVENTORY_SOURCE | The inventory source (e.g. web, app, CTV) |
DEAL_ID | The deal ID associated with the impression |
PUBLISHER_ID | The publisher identifier |
PLACEMENT_ID | The ad placement identifier |
BID_URL | The URL associated with the bid request |
PubMatic macros
If you're running through PubMatic, these macros are commonly passed:
<script src="https://l.csfy.me/je?c={campaign_id}&deal_id=[DEAL_ID]&pub=[PUBLISHER_ID]&inv_domain=[INVENTORY_DOMAIN]&inv_source=[INVENTORY_SOURCE]"></script>
DSP macro documentation
Each DSP has its own macro syntax. Refer to your platform's documentation:
- The Trade Desk — "tracking tag"
- Google Ad Manager — "%%MACRO%%" format
- PubMatic — "[MACRO]" format
Embedding the pixel
For advertisers
Add the pixel as a custom impression tracker attached to your creatives in your DSP. While each platform uses slightly different terminology, they all support third-party impression tracking:
| DSP | Feature name | Documentation |
|---|---|---|
| The Trade Desk | Tracking Tag | Docs |
| PubMatic | Third Party Pixel | Docs |
| Google Ad Manager | Third Party Impression URL | Docs |
When configuring, select JavaScript as the format and enter either the full <script> tag or just the src URL. Include any macros you want to track.
For publishers
Embed the pixel tag directly in the <head> or <body> of your pages. The pixel fires on every page load, capturing both human and non-human traffic for analysis.
<head>
<!-- Classify Pixel -->
<script src="https://l.csfy.me/je?c={campaign_id}"></script>
</head>
For publisher use cases, macros are typically not needed — the pixel captures the full URL and visitor metadata automatically.