If you've installed the Pinterest pixel and still see zero conversions, random checkouts, or "No tag found" in Tag Helper, it's usually not Pinterest being flaky. It's almost always: the base tag isn't truly site-wide, your event code fires on page load instead of after the real action, or your Framer navigation isn't triggering events correctly.
This guide shows you the exact steps to install the Pinterest tag (what people call the "Pinterest pixel") across your Framer site, configure the minimum viable events for ad optimization, and verify everything works before you spend a dollar on campaigns.

Proper Pinterest tag implementation transforms guesswork into measurable campaign performance. With the right tracking setup in your Framer project, you gain visibility into which Pinterest ads actually drive conversions instead of just clicks.
Pinterest officially calls their tracking code the "Pinterest tag," though most marketers still refer to it as the "Pinterest pixel." Both terms mean the same thing, but Pinterest's interface, documentation, and troubleshooting tools all use "tag."
The base tag alone provides basic visitor data, but conversion events are what enable campaign optimization and ROI measurement.
Before installing any code, verify you have the necessary access and capabilities in both platforms. This preparation step prevents frustration midway through the Framer installation process.
You need a Pinterest business account with advertiser access to install the tag and view conversion data. Log in to your Pinterest business account and confirm you can access the Conversions section under the hamburger menu.
When setting up conversions in Pinterest, you may see a large "Google Tag Manager" option appear after entering your website URL. This is Pinterest offering a direct integration with GTM. Choose ONE install path—either GTM or manual code installation. Installing both causes duplicated events and broken optimization signals that will confuse Pinterest's algorithm.
Pinterest notes it can take up to 24 hours after install to reflect in Ads Manager, but dashboards often lag even longer. Rely on Tag Helper and Test events for immediate verification instead of waiting on dashboard updates.
Framer's path to add scripts is Project Settings → Custom Code → Add Script. You'll need to choose placement, apply to pages, and set whether scripts run Once or Run on every page visit.
If you don't see Custom Code available in your project, you're blocked by plan or permissions. You must resolve that first—upgrade or adjust access—or nothing in this tutorial will work.
The base tag contains your unique tag ID and must be copied directly from Pinterest—never use a generic sample snippet. This ensures your Framer site reports conversions to your account.
Follow this exact click-path to find your tag code in Pinterest:


Pinterest is explicit: don't copy sample code. You must copy the personalized snippet from Ads Manager so it includes your real tag ID.
If you see the GTM option and want to use that method, you don't need to copy code—proceed directly to Step 2A below.
You have two paths to install the Pinterest tag in Framer. Choose ONE method only—installing both will cause duplicate tracking.
Google Tag Manager provides a scalable way to manage the Pinterest tag alongside other marketing pixels, with centralized governance and easier event management as your tracking needs grow.
Prerequisites:
Confirm GTM is already installed and working on your published Framer domain. If you haven't set up GTM in Framer yet, follow our guide to install GTM in Framer first. If GTM isn't loading on your site, Pinterest won't load either.
Installing Pinterest tag via GTM:

Verification:
Test on your published Framer domain using Pinterest Tag Helper. The tag should now load site-wide. If Tag Helper shows "No tag found," confirm GTM is published and you're testing the correct domain where GTM is installed.

If you're not using GTM or prefer direct control for a simple setup, you can manually install the Pinterest tag via Framer's custom code feature.

Pinterest tells you to paste the base code inside the <head> section. In Framer, that means placing the script in Custom Code with a head location and applying it to all pages.

Adding the Pinterest tag code to Framer project settings for site-wide tracking:
Once you've copied the base code from Step 1:

For lead generation sites, the simplest and most reliable conversion tracking method uses a dedicated thank you page that visitors reach only after successful form submission. This Framer page becomes your conversion trigger point.
Create a page where visitors land after completing your desired action:
This page should not be linked anywhere publicly—visitors should only reach it via form redirect after successful submission.
To ensure the conversion event fires only after successful form submission, configure your Framer form to redirect to the thank-you page:
This way, the Lead event script you add in Step 4 fires only when someone reaches that page after a successful form submission, not just because they loaded a page.
We'll show one GTM example (thank-you page conversion). For other events, choose what matches your funnel or contact us for an advanced setup.
The most reliable conversion tracking approach uses a dedicated thank-you page that visitors reach only after completing your desired action. This page becomes your conversion trigger point.
Create and configure your thank-you page:
Configure the Lead event in GTM:


<script>
pintrk('track', 'lead');
</script>Verify the Lead event:
Beyond the thank-you page example above, you may want to track additional Pinterest events based on your conversion funnel:
Each event requires its own GTM trigger and tag configuration. Need help implementing the full event map? We can help—get in touch.
After installing the base tag and events, verify everything works before spending on campaigns. Use multiple verification methods because dashboards can lag for hours or days.

Install the Pinterest Tag Helper Chrome extension and visit your published Framer site:
If Tag Helper says "No tag found" and you're using the GTM method, confirm the GTM container is published (Submit/Publish in GTM) and you're testing the same domain where GTM is installed. If events appear in Tag Helper but not in dashboards, rely on Test events and allow for normal reporting delay.
Navigate to Business → Conversions → Test events in Pinterest. This real-time log shows events as they fire:
Test events is faster than waiting for dashboard updates and confirms Pinterest received the data.
Open Chrome DevTools (F12 or right-click → Inspect), then:
Each request should include query parameters like:
If you see requests, your code is firing. If Pinterest dashboards still show nothing, you're hitting normal reporting lag.
Choosing the right implementation method depends on your tracking complexity, existing infrastructure, and scale.
GTM is the recommended default approach for most Framer sites, especially those with multiple conversion events, complex triggers, or established marketing stacks. GTM provides centralized tag governance, easier event management, and the ability to update tracking without redeploying Framer custom code.
Use GTM when you need multi-event setups, want to manage Pinterest alongside other pixels (Meta, Google), or anticipate frequent tracking changes as campaigns evolve.
Manual installation via Framer Custom Code is the quick alternative for simple setups: base tag plus one or two straightforward events (like Lead on thank-you page). If your tracking needs are minimal and you want direct control without learning GTM, manual installation works perfectly.
Manual becomes harder to maintain as tracking complexity grows—adding new events, modifying parameters, or managing multiple conversion paths requires editing Framer custom code and republishing.
Conversions API sends conversion data directly from your server to Pinterest, bypassing browser-based tracking limitations. This is an advanced next step after browser tracking (GTM or manual) is stable.
Use Conversions API when browser tracking reliability becomes a concern (ad blockers, iOS restrictions), when conversions happen outside your Framer pages (backend systems, CRM), or when you need resilient tracking for high-spend campaigns.
Implement Conversions API only after your browser-based setup is stable and you understand deduplication requirements. This typically makes sense for high-volume advertisers or when browser tracking reliability becomes a concern.
When implementing Pinterest tag tracking on your Framer site, you may encounter several common issues. Here are the most frequent problems and their solutions:
Many Framer users have similar questions when implementing Pinterest tag tracking. Here are answers to the most common queries about Pinterest conversion tracking on Framer sites.
Pinterest's official term is the Pinterest tag, and their interface consistently uses that name even though marketers still say "pixel." Both terms refer to the same tracking code.
In Framer, it's a script you add site-wide to track actions after Pinterest ad clicks: the base tag loads on every page, and event codes track specific conversions. Copy the personalized base code from Pinterest Ads Manager, then add it in Framer via Project Settings → Custom Code applied to all pages, or install it via Google Tag Manager for more scalable management.
You have two options: GTM (recommended) or manual installation via Framer Custom Code.
For GTM, ensure GTM is already set up in Framer (install GTM in Framer), then use Pinterest's GTM integration option during Conversions setup. Publish the GTM container to activate the tag.
For manual installation, use Framer's Custom Code system so the base script loads across your entire site: create one script with a clear name, choose headStart or headEnd, and apply it to all pages. Set Run to Run on every page visit to reduce tracking gaps when navigating Framer pages.
If Tag Helper doesn't detect it, open DevTools and filter for ct.pinterest to confirm requests are being sent. Always publish after adding code—preview mode doesn't activate tracking.
Use three verification methods for complete confidence: Pinterest Tag Helper, Business → Conversions → Test events, and Chrome DevTools (Network filtered by ct.pinterest). Together, they confirm the tag loads, events fire, and requests contain the right data.
Test complete flows end-to-end: submit forms to confirm Lead fires only on the thank-you page, and test any other configured events on their respective trigger pages. If dashboards lag, DevTools is your fastest truth source.
The cleanest Framer-native approach is redirect-based conversion tracking: set a Redirect on your form so successful submission sends visitors to a thank-you page, then restrict an event script to run only on that page.
Create the thank-you page, add a page-scoped Lead (or Signup) event script via Project Settings → Custom Code (manual method) or configure a Lead event in GTM with a page URL trigger (GTM method), and Publish. Pinterest explicitly warns against firing conversion events just because a page loaded, so this redirect flow keeps timing aligned to real submissions.
Checkout tracking follows similar principles to the Lead event example in Step 4: configure your payment provider to redirect to a Framer success page (e.g., /purchase-success), then create a GTM trigger and tag for that page URL.
Pinterest documentation shows Checkout requires order_id and currency for conversion tracking. Many providers append identifiers like session_id to the success URL—you can configure GTM to parse these and pass them in the event payload. For help implementing Checkout or other advanced events, get in touch.
GTM is recommended as the default approach for most sites because it provides scalable event management, centralized governance, and easier updates without redeploying Framer code. Use GTM when you need multiple events, complex triggers, or when your marketing stack already lives in GTM.
Manual installation is the quick alternative for simple setups with just the base tag plus one or two straightforward events like Lead on a thank-you page. The overhead of learning GTM isn't justified for very simple Framer sites with straightforward conversion paths—but GTM becomes essential as tracking needs grow.
You need access to Framer's Custom Code feature to install the Pinterest tag manually. If you don't see Custom Code in Project Settings, check your plan or permissions.
Without Custom Code access, you can't add the base tag to your site's head section for manual installation. However, you can still use the GTM method if GTM is already installed on your Framer site by someone with Custom Code access.
Pinterest Tag Helper and Test events show results within seconds of completing conversion actions. However, Pinterest Ads Manager can take up to 24 hours to change tag status from "Unverified" to active and to surface conversion data in reports.
Don't wait on Ads Manager status updates—verify immediately with Tag Helper after you Publish. Many status delays are normal, so wait 24–48 hours before judging Ads Manager reporting.
For most lead-gen Framer sites, the tag (via GTM or manual) plus a Lead or Signup event is enough to start optimizing campaigns. Pinterest states you can use Conversions API in addition to the tag to maximize visibility into conversions, especially when browser tracking is imperfect or conversions happen outside your Framer pages.
Don't add server-side tracking unless you can handle deduplication properly—otherwise, you risk double-counting conversions. Start with the browser tag, verify it works, then consider Conversions API as a second phase if reliability issues justify the complexity. Most Framer sites don't need Conversions API unless spending $10,000+ monthly on Pinterest ads.
Use Chrome DevTools and inspect network requests to ct.pinterest.com. Filter the Network tab by typing ct.pinterest to see all Pinterest tracking requests and confirm the browser actually sent the event payload.
Pinterest documentation explains which parameters to check: tid (tag ID), event (event name), ed (event data), and cb (cache buster). If you see requests but Pinterest dashboards show nothing, you're likely hitting normal reporting delay. If you don't see requests, your code isn't installed correctly or the event never fired—always test on your published Framer URL, not in preview mode.
A working Pinterest tag setup in Framer is straightforward when you follow the right sequence: choose your installation method (GTM for scalable management or manual for simple setups), install the base tag site-wide, add meaningful conversion events that map to your actual Framer flows (starting with the thank-you page example), and verify with Tag Helper plus DevTools before spending money on campaigns.
The key is getting event timing right: fire events only after the intended action completes, not on page load. GTM provides the most scalable approach for ongoing event management and multi-pixel coordination, while manual installation works perfectly for straightforward tracking needs. As your campaigns mature, Conversions API offers resilient server-side tracking—especially when conversions happen outside Framer. For end-to-end implementation including additional events, our agency can help with the full setup—get in touch.
Install Pinterest tag in Webflow via GTM, verify with Tag Helper, and track conversions using a thank-you page.
Install TikTok Pixel in Framer, verify in Events Manager, and track ViewContent, SubmitForm, and Purchase.
Install TikTok Pixel in Webflow, verify in Events Manager, and track SubmitForm, AddToCart, and Purchase.