20 pages · Pixels and tags
What fires in the browser
A pixel is an HTTP request with a job: impression, click, page, or conversion. The 1x1 GIF is one transport. sendBeacon and fetch are the others. These pages are the failure modes you will actually hit.
- A pixel is an HTTP request with a job Pixels · PMs, marketers, engineers
- An image cannot hash an email Pixels · engineers, marketers
- Noscript is a different request Pixels · engineers, marketers
- Impression and click are not the same URL Pixels · marketers, PMs, engineers
- Thank-you page pixels miss the backend sale Pixels · PMs, marketers, engineers
- The vendor host cannot see your cookie jar Pixels · engineers, PMs
- A cached impression is a lie Pixels · engineers, marketers
- A 200 in a click chain is a dead end Pixels · engineers, marketers
- The URL changed. The pixel did not. Pixels · engineers, PMs
- The pixel ran in the wrong frame Pixels · engineers
- UTM is not a click id Pixels · marketers, PMs, engineers
- Purchase does not belong on the landing page Pixels · marketers, PMs, engineers
- Not every 200 was a person Pixels · engineers, PMs, marketers
- The tag ran. The request did not. Pixels · engineers, marketers, PMs
- no-referrer means the collector guesses Pixels · engineers
- buyer@example.com in the query is a finding Pixels · engineers, PMs
- The fired URL still says CACHEBUSTER Pixels · engineers, marketers
- Say whether it has fired Pixels · engineers, marketers
- A first-party hostname is still their collector Pixels · engineers, PMs
- PageView fired twice on one load Pixels · engineers, marketers