Setting up tracking pixels for your website

Adding tracking pixels to your beehiiv website is a powerful way to better understand how visitors interact with your content. Pixels help you monitor performance, optimize ad campaigns, and gather deeper visibility into site activity beyond what's available in your built-in Posts, Clicks, and Subscribers reports.

Tracking pixels apply to your beehiiv website pages only and are not added to your email newsletters. In this article, you'll find an overview of what tracking pixels are, a list of supported platforms, step-by-step setup instructions, and troubleshooting guidance for pixels that aren't loading or firing.

Tracking pixels, also known as web beacons or pixel tags, are tiny, invisible snippets of code embedded in web pages or emails. They track user behavior, such as:

• Pageviews
• Clicks
• Conversions
• Email Opens

When a visitor lands on a page with a pixel, the pixel sends a request to the sender's server, providing information such as the time, date, recipient's IP address, and the pixel's source (e.g., Meta, Google, TikTok), helping you measure engagement and campaign success.

You can add tracking pixels from the following platforms:

• Meta (Facebook)
• X (Twitter)
• TikTok
• Google Analytics 4 (GA4) (Known as a Measurement ID in GA4)
• Google Tag Manager (GTM) (Known as a Container ID in GTM)
• Google Search Console (GSC)

1. Open the builder, go to Website > Builder. 
    
2. From the left panel, click on the Settings icon, then select on All Settings. 
   
   
   
3. Your General Site Settings will open. Click on Pixels in the left panel. 
   
   
   
4. Enter your pixel IDs or verification codes for each platform. Changes save automatically, no extra steps required.
   
   
   

If your pixel ID is saved correctly but your tracking platform isn't detecting events or pageviews, the most common causes are listed below.

If your publication has the Cookie Banner enabled under GDPR, CCPA, & Compliance in your website settings, tracking pixels will not load until a visitor clicks ‘Accept’ on the banner. This applies to all supported pixel types: Meta, GA4, GTM, TikTok, and X. If a visitor hasn't interacted with the banner yet, no pixel data will be collected for that session.

To test, visit your live website in a private or incognito browser window, click Accept on the cookie banner, then re-test your pixel using your platform's verification tool (e.g., Meta Pixel Helper, Google Tag Assistant).

Tech Note: Pixel scripts load on page load after consent is recorded. A visitor who accepts the banner mid-session will have their data collected from the next page load onward, not retroactively for the current page.

If your Meta pixel is firing correctly (confirmed via Meta Pixel Helper) but conversion events such as subscribe completions aren't appearing in Meta Events Manager, the most common cause is that a conversion event hasn't been configured in Meta. Pixels track pageviews by default, but conversion events require additional setup in Meta's Events Manager or through a GTM trigger mapped to a specific action.

To track subscribe conversions specifically, you'll need to configure a custom conversion in Meta Events Manager based on the thank-you or confirmation page URL that subscribers land on after signing up. If your publication uses double opt-in, note that the confirmation step adds an extra page load between signup and conversion. Confirm your conversion trigger accounts for the full confirmation flow.

Each platform uses a specific ID format. If your pixel ID doesn't match the expected format, it won't fire. 

Confirm you're using the correct format for each platform:

• Meta: Numeric ID only (e.g., 123456789012345).
• GA4: Starts with G- (e.g., G-XXXXXXXXXX).
• GTM: Starts with GTM- (e.g., GTM-XXXXXXX).
• TikTok: Alphanumeric code.
• Google Search Console: Verification meta tag content value only.

If you're using Google Tag Manager, changes made in GTM only take effect once the container is published, not just saved. If your GTM-based tags aren't firing, confirm your container has been submitted and published in GTM before testing.

If you have HTML blocks on the same page as your pixel, poorly scoped styles or scripts in those blocks could interfere with pixel loading. Test the page in Preview with your HTML blocks temporarily removed to isolate whether a conflict exists.

If your pixel still isn't firing after trying the steps above, have the following ready before contacting support: which pixel platform you're using, the pixel ID you entered, whether your Cookie Banner is enabled, and a screenshot of the error or non-detection message from your platform's verification tool. Visit the Help page in your account, or click the Chatbot Assistant on this page for immediate assistance.

Tracking pixels measure visitor behavior on your website pages. For other tracking and attribution tools in beehiiv, see:

• UTM-based subscriber attribution: The Subscribers Report lets you filter subscriber data by Channel, Source, Medium, and UTM Campaign to see which traffic sources are driving signups. You can also export filtered results from each tab.
• Double opt-in and Smart Nudge: If you want to confirm subscriber intent before counting a signup, see Double opt-in and Smart Nudge: How they work and why they matter.