Sign Up

Updated: Jun 22, 2026

beehiiv pixel FAQ for advertisers

Article Contents

Notice: This guide is for advertisers on the beehiiv Ad Network. If you're a publisher using beehiiv but not placing ads as an advertiser, this doesn't apply. If you're looking to add tracking pixels to your publication site, refer to this article.

This article answers common questions about implementing, verifying, and troubleshooting the beehiiv tracking pixel for Ad Network campaigns. For step-by-step setup instructions, see Implementing the beehiiv Pixel for advertisers.

Setup and implementation

How do I get started with the beehiiv pixel?

The beehiiv pixel can be installed using one of two methods:

  • Google Tag Manager (GTM) (recommended). Follow the GTM setup steps in Implementing the beehiiv Pixel for advertisers. You will need your unique Pixel ID (a UUID, for example: fb187fb8-97ef-4f35-97f5-414dddd85c28), which your beehiiv Ad Network point of contact will provide when your campaign kicks off.
  • Manual JavaScript. Your web developer can embed the pixel script directly into your site's <head> section. Your beehiiv contact will provide your Pixel ID and a link to the manual implementation documentation once your campaign is active.

If you have not received your Pixel ID, reach out to your CSM or Network Performance representative.

What conversion events should I set up?

At a minimum, configure two event types:

  • PageView. Fires when a user lands on your campaign destination page.
  • Conversion event. The primary action you want to track, such as a sign-up, purchase, or trial start.

The event name you configure must match one of the beehiiv-supported conversion event names:

  • complete_registration
  • initiate_checkout
  • lead
  • purchase
  • start_trial
  • subscribe

For campaigns using beehiiv's Magic Link flow, or for booked demo calls through a third-party tool like Calendly, the recommended conversion trigger is a user reaching your post-action redirect page (such as a thank-you or welcome page) rather than a form submission event. See Why is my form submission trigger not tracking conversions? below for more detail.

Do I need to publish my GTM container before beehiiv can verify the pixel?

Yes. Preview Mode in GTM Tag Assistant only confirms your tags are configured correctly on your side. The beehiiv team cannot see or QA your pixel events until the GTM container has been published live.

Once you have published your container, notify your CSM or Network Performance representative so they can run through the flow and confirm events are firing correctly.

Tracking limitations and alternatives

Do you support server-to-server (S2S) tracking?

No. beehiiv does not currently support server-to-server tracking integration. The two supported tracking methods are:

  • beehiiv Pixel (heavily recommended). Installed via GTM or manual JavaScript. The pixel gives beehiiv direct visibility into on-site conversion events, enabling real-time optimization of publisher and creative selection. Campaigns without a pixel will have significantly limited optimization capability.
  • UTM parameters (required). UTMs must be present on all destination URLs before a campaign can go live. They allow performance to be tracked and segmented by publisher, placement, and creative in your own analytics platform.

If S2S is your standard tracking method, work with your engineering or analytics team to explore pixel implementation instead.

Can I use a third-party pixel (such as an affiliate network pixel) instead of the beehiiv pixel?

Third-party pixels are not supported at this time. For all pixel-based tracking, use the beehiiv pixel.

Using the beehiiv pixel gives the optimization models and your performance team direct visibility into conversion events, enabling better publisher placement decisions. Without this data, budget and rotation decisions are based on limited signal, which often reduces campaign performance.

Is there an API integration available for advertisers?

No. There is no API-based tracking integration available for advertisers on the beehiiv Ad Network.

Tech Note: beehiiv does offer API integrations for publishers (newsletter operators) on the platform, but these are unrelated to advertiser tracking. If you encountered API documentation while researching beehiiv, it is likely intended for the publisher side. For advertisers, tracking is handled via the beehiiv pixel or UTM parameters.

UTM tracking and parameters

Are UTM parameters required?

Only one UTM field is strictly required: the publisher ID merge tag {{publication_alphanumeric_id}} must be present on all destination URLs before your campaign can go live.

The beehiiv pixel is heavily recommended alongside UTMs but is not strictly required. The pixel tracks on-site conversion events and feeds data directly into beehiiv's optimization engine. Campaigns running the pixel give the beehiiv team significantly more signal to optimize publisher selection and pacing toward your conversion goals. Campaigns without a pixel are limited to click-level data only.

If your team needs additional lead time to implement either component, flag this with your CSM as early as possible.

Note: beehiiv's optimization systems are built around pixel data. With UTMs only, the beehiiv team is reliant on the conversion data you report back after the fact, which limits how quickly and accurately the campaign can be optimized. If you start with UTMs and later add the pixel, performance reporting will improve going forward.
How do I track performance by individual publisher?

beehiiv supports a dynamic UTM tag that automatically populates with each publisher's unique identifier when a reader clicks your ad:

{{publication_alphanumeric_id}}

Add this tag to your utm_content parameter, or a custom parameter of your choice. Example:

https://yoursite.com/page?utm_source=email&utm_medium=affiliate&utm_campaign=beehiiv&utm_content={{publication_alphanumeric_id}}

This allows your analytics platform to segment performance by each newsletter publication that served your ad.

How do I track performance by ad creative or placement type?

The {{publication_alphanumeric_id}} tag tracks by publisher. To break down performance by ad creative or placement type (such as Primary, Secondary, or Text-Only), add an additional custom UTM parameter. See Using URL dynamic parameters for Ad Network tracking for guidance on the available dynamic parameters.

Troubleshooting the pixel

I implemented the pixel in GTM, but beehiiv says no events are being received. What should I check?

Work through this checklist:

  1. Is your GTM container published live? Preview Mode does not make events visible to beehiiv. Publish the container and notify your performance contact.
  2. Is the correct GTM container placed on your site? Confirm that the container ID (for example, GTM-XXXXXXX) in your tag matches the one on your live website. Mismatches are a common cause of missing events.
  3. Is the beehiiv pixel script the one configured in GTM? Verify that the tag contains the beehiiv pixel code and not another platform's script, such as a Meta/Facebook Pixel.
  4. Is the trigger set correctly? See the question below about Magic Link flow issues. The trigger must fire on the correct page or event.
  5. Have you shared your implementation details with beehiiv? Sharing your GTM Container ID, trigger logic, and screenshots of your tag setup allows the beehiiv performance team to review and identify issues.

If you have worked through the checklist and are still experiencing issues, your CSM or Network Performance representative can schedule a screen-share session to troubleshoot live.

Why is my form submission trigger not tracking conversions?

This is the most common pixel misconfiguration for campaigns using beehiiv's Magic Link subscription flow.

When your campaign uses Magic Links, the opt-in form is hosted on beehiiv's platform, not on your website. Because GTM only has visibility into events that occur on your own domain, a Form Submission trigger on your site will not fire when a user subscribes through the beehiiv-hosted page.

The fix: Instead of triggering on form submission, update your conversion event to fire when a user reaches your post-subscription redirect page, typically a thank-you or welcome page on your domain (for example, yoursite.com/welcome).

In GTM, set the trigger to: Page View with the condition Page URL contains /your-redirect-path.

Once updated, publish the container live and notify your beehiiv contact so they can QA the flow.

How do I know when my pixel has been successfully verified by beehiiv?

Your CSM or Network Performance representative will confirm pixel verification directly by email once the team has completed the conversion flow and confirmed events are populating correctly.

To speed up the QA process:

  1. Publish your GTM container and notify your beehiiv contact that it is live.
  2. Share your GTM Container ID and the URL path of your redirect or conversion page.
  3. Your beehiiv contact will simulate the user journey to trigger and confirm the events.

Preview Mode confirmation alone is not sufficient. Pixel setup is not considered complete until beehiiv has confirmed events are visible on their end.

Was this article helpful?

Related Articles