To verify your Pinterest Tag consent setup, start by reviewing your consent banner and CMP configuration. Then test browser-side Pinterest Tag requests, inspect server-side Conversions API transmissions, and confirm that both integrations respond appropriately when visitors accept, reject, or withdraw consent. Pay particular attention to situations where the Pinterest Tag is blocked but Conversions API events continue to be sent.
Tracking conversions is essential for understanding how your Pinterest advertising campaigns perform. However, you also need to ensure your tracking tools respect users' privacy choices and comply with applicable data privacy regulations.
If you use the Pinterest Tag and Conversions API, check your consent setup to confirm whether you have consent to track and share events. An incorrect configuration can result in unauthorized data collection, missing conversions, or inconsistencies between browser-side and server-side tracking. Pinterest consent management involves configuring and testing the Pinterest Tag for GDPR compliance.
In this guide, we'll explain how Pinterest's tracking tools work, why consent management matters, and how to verify that your setup respects visitors' preferences.
What are the Pinterest Tag and the Conversions API?
The Pinterest Tag and Pinterest Conversions API (CAPI) are tracking solutions that help advertisers measure user interactions and understand the effectiveness of their Pinterest campaigns.
Although both tools collect conversion information, they use different methods to send data to Pinterest.
Pinterest Tag
The Pinterest Tag is a browser script installed on your website that records page visits and conversions on your site. It records visitor interactions and sends event information from the user's browser to Pinterest.
The Pinterest Tag can record these events:
- PageVisit: The tracking event logs when someone visits a page on your website.
- AddToCart: This event records when a visitor adds a product to their shopping cart.
- Checkout: It records when a customer completes a purchase.
- Signup: It logs when someone registers for an account or service.
- Lead: The event signals when a visitor shows interest in your products or services.
This information helps advertisers evaluate campaign performance, optimize ads, and build audiences.
However, because the Pinterest Tag runs in the browser, browser privacy settings, ad blockers, and user consent preferences can affect its ability to log events.
Pinterest Conversions API
The Pinterest Conversions API sends conversion information directly from businesses’ server to Pinterest.
Unlike browser-based tracking, server-side tracking isn't affected by the visitor's browser when transmitting events to Pinterest. This can improve conversion measurement by reducing data loss due to certain browser restrictions or technical limitations.
The Conversions API can transmit information such as purchase events, transaction values, product details, and properly processed customer identifiers.
Many businesses use the Pinterest Tag and Conversions API together to improve event coverage and measurement accuracy. In this case, businesses should deduplicate events to prevent double counting.
Why Consent Setup Matters for Pinterest Tag and Conversions API
Proper consent setup is essential for complying with privacy laws, improving data reliability, and keeping browser and server tracking consistent.
Consent management determines whether customers allow the use of their Personal Information for advertising, measurement, and analytics purposes.
Privacy regulations, including the General Data Protection Regulation (GDPR) and the EU's eprivacy rules, establish requirements for processing personal data and using non-essential tracking technologies. Other laws may impose additional notice, opt-out, and data-use obligations. Thus, businesses often need to obtain consent before tracking users for advertising purposes.
Businesses need to configure Pinterest Tag consent setup properly for the following reasons:
- Reducing compliance risks
If consent is not configured properly, businesses may collect or share user data without an appropriate legal basis. This would violate data privacy requirements and could lead to non-compliance with privacy laws. - Improving data reliability
Consent settings also influence your conversion reporting. If consent signals are incorrectly configured, some events may be sent when they should be blocked, while other events may be unnecessarily restricted, leading to data loss. - Keeping browser and server tracking consistent
The Pinterest Tag and Conversions API operate independently. Disabling one would not automatically affect the other. Therefore, your consent management system must communicate relevant user preferences to both integrations.
Use CookieScript CMP to manage user consent. In 2025, CookieScript received its fourth consecutive badge in a row as the leader on G2, a peer review site, and became the best CMP on the market for a whole year!
How to Check Consent Settings for Your Pinterest Tag
Checking your Pinterest Tag consent configuration involves reviewing your Consent Management Platform (CMP), testing tag behavior, and confirming which information is transmitted to Pinterest.
Follow these steps to evaluate your setup.
Step 1: Review your consent banner
To test consent settings, open your website in a private or incognito browser window. A fresh browsing session helps ensure you review the current settings, not previously saved user consent preferences.
First, check whether your Cookie Banner clearly explains the use of advertising and tracking tools. Users should know that your site uses Pinterest tracking tools.
Visitors should be able to reject non-essential tracking scripts. Test the available options, including accepting, rejecting, and customizing cookie preferences.
Step 2: Check your Consent Management Platform
If your website uses a CMP, such as CookieScript, review how the Pinterest Tag is categorized.
A CMP should associate the tag with advertising or marketing purposes, although the appropriate classification depends on its actual functionality.
Verify that your CMP:
- Categorizes the Pinterest Tag as advertising or marketing technology.
- Blocks the tag before users give consent.
- Keeps the Pinterest Tag remains blocked after users reject it.
- Updates the tag's behavior after changing or withdrawing consent.
If you use Google Tag Manager (GTM), review your tag triggers and consent settings to confirm they align with your CMP configuration.
Step 3: Inspect the Pinterest Tag using browser developer tools
Browser developer tools can help determine whether Pinterest tracking requests are sent before or after consent.
To inspect the Pinterest Tag, perform these steps:
- Open your website in Google Chrome.
- Right-click the page and select Inspect.
- Open the Network tab.
- Enter ct.pinterest.com in the filter field.
- Do not accept advertising cookies and reload the page.
- Check whether tracking requests are transmitted to Pinterest.
- Accept the relevant consent category and repeat the test.
In jurisdictions where prior consent is required, conversion data should not be sent to Pinterest before visitors grant valid consent.
You should also inspect cookies and browser storage to identify tracking information created before consent.
Step 4: Verify Pinterest's consent signal
Pinterest provides a setconsent command that allows websites to explicitly communicate user consent choices to the Pinterest Tag.
For example:
pintrk('setconsent', false);
Indicates that the visitor has not consented to Pinterest tracking.
When valid consent is granted, you can use the corresponding command:
pintrk('setconsent', true);
According to Pinterest's documentation, setting consent to false prevents events from being sent for setting cookies and processing user conversion data before users grant consent.
Check that your implementation applies the appropriate consent state early enough to prevent unwanted event transmission and updates it when the user's choice changes.
Note: The setconsent command controls the Pinterest Tag. It does not automatically control server-side events sent through the Conversions API.
Step 5: Test events in Pinterest Ads Manager
Pinterest provides tools for verifying whether your Tag is sending events correctly.
- Open your Pinterest business account, navigate to Conversions, and select Test events.
- Enter your website URL, start the testing session, and perform actions like visiting a product page or adding an item to your cart.
- Review the events received by Pinterest.
- Repeat your tests under different consent states, when you accept all cookies, reject all cookies, or accept just some categories of cookies.
How to Verify Consent Handling in Pinterest Conversions API
Checking your Pinterest Conversions API consent configuration involves reviewing event transmission rules, inspecting API event parameters, and confirming which information reaches Pinterest.
A browser-based consent banner alone cannot guarantee that server-side tracking respects users' preferences. Instead, check Pinterest conversion tracking and which events your server sends, not what the visitor's browser sends.
Step 1: Identify how your Conversions API is implemented
First, determine how you integrated your Conversions API. Knowing the integration method helps you identify where consent decisions are processed and where you should change settings.
The Conversions API could be configured through:
- A direct server-to-server integration.
- A supported e-commerce platform or third-party partner.
- A server-side tag management solution, such as server-side Google Tag Manager.
Step 2: Check whether consent information reaches your server
Your backend must receive the user's relevant consent or opt-out status.
For example, if a visitor rejects advertising tracking, Pinterest should not generate Pinterest conversion events.
Review the data flow between your CMP, website, server-side tracking solution, and Pinterest API integration. Make sure the correct consent information reaches Pinterest.
Step 3: Review event transmission rules
Examine the rules for how your server sends conversion events to Pinterest.
Where consent is required for the processing, events should be transmitted only after obtaining valid consent.
Review how your integration handles:
- Visitors who accept advertising tracking.
- Visitors who reject advertising tracking.
- Visitors who have not interact with the Cookie Banner.
- Visitors who withdraw previously granted consent.
Pay particular attention to default settings. An unknown consent state should be treated as rejection of tracking by default.
Step 4: Inspect API event parameters
Pinterest's Conversions API supports an opt_out parameter that indicates whether a user has opted out of applicable conversion-event tracking.
For example, the parameter can appear as:
{
"opt_out": true
}
Pinterest documents opt_out as an optional Boolean event parameter. Verify that your integration uses opt-out information correctly where applicable. When there is no consent information, it should be treated as consent has been rejected.
Importantly, setting opt_out to true is not a universal substitute for withholding an event when consent is legally required. Your implementation should determine whether an event may be sent at all before preparing the API request.
Step 5: Test server-side events using different consent scenarios
Test server-side events to determine whether your server responds to the user's preferences.
Start with a fresh session and reject advertising tracking. Perform a test conversion, then inspect your server-side logs or outbound API requests. When Pinterest event transmission is not permitted, the request should remain blocked before reaching Pinterest.
Next, grant the relevant consent and repeat the conversion test. Confirm that permitted events are transmitted correctly and reach Pinterest.
Finally, withdraw consent and verify that future tracking behavior changes accordingly.
Pinterest Ads Manager can help confirm received events, but your own server-side request logs are particularly important when testing blocked transmissions.
Common Pinterest Consent Setup Issues and How to Fix Them
Even when the Pinterest Tag and Conversions API are installed correctly, consent configuration issues can still affect tracking behavior.
Here are some common issues and practical ways to resolve them.
1. Pinterest Tag fires before consent
Problem: Pinterest tracking requests are sent immediately when someone opens your website, before the visitor accepts advertising cookies.
Solution: Review your CMP configuration and tag-loading sequence. Use appropriate consent defaults and restrictions before Pinterest can transmit events.
If you use Google Tag Manager, check that the tag's firing conditions and consent configuration block tracking before consent.
2. Conversions API ignores consent preferences
Problem: Browser tracking stops when users reject advertising cookies, but your server continues sending conversion events to Pinterest.
Solution: Integrate consent information into your server-side tracking workflow.
Configure the server to evaluate the applicable consent or opt-out status before sending each event.
3. Consent changes are not reflected after withdrawal
Problem: A visitor withdraws advertising consent, but Pinterest events continue to be transmitted.
Solution: Ensure your CMP communicates updated preferences to both browser-side and server-side integrations.
Test whether changing consent immediately affects future event transmission and whether the tag receives the updated consent state.
4. Pinterest events are missing after consent
Problem: Visitors accept advertising tracking, but expected events are not sent to Pinterest.
Solution: Check whether consent updates are correctly passed to the Pinterest Tag and your server-side integration.
Use browser developer tools, Pinterest Tag Helper, and Ads Manager's Test events feature to investigate. Also inspect JavaScript errors, blocked requests, tag triggers, and API response messages.
Reporting delays and browser restrictions may also affect event after consent.
5. Duplicate conversions appear in reporting
Problem: A single purchase is recorded through both the Pinterest Tag and Conversions API, resulting in inaccurate conversion totals.
Solution: Implement proper event deduplication.
Although this is not strictly a consent issue, it is an important part of maintaining reliable tracking when both tracking tools are implemented.
Pinterest supports using matching event identifiers to recognize conversions sent through multiple tracking methods. Ensure both integrations use the appropriate shared event ID for the same conversion.
6. Consent works in the browser but fails during server-side testing
Problem: Pinterest Tag events are not transmitted without consent, but server-side logs shows outbound Conversions API requests.
Solution: Test both tracking channels independently.
Review server-side triggers, event queues, partner integrations, and consent validation logic.
7. Consent behavior differs between website pages
Problem: Tracking respects consent on the homepage but activates unexpectedly on product pages or other sections.
Solution: Audit consent behavior across your website.
Check whether different templates, embedded scripts, plugins, or third-party integrations load Pinterest tracking independently to make sure the same consent rules apply consistently throughout the user journey.
Frequently Asked Questions
How to check Pinterest Tag consent setup?
Testing your Pinterest Tag consent configuration involves reviewing your CMP, testing tag behavior, and confirming which information is transmitted to Pinterest. Open your website in incognito mode and use Chrome Developer Tools to check Pinterest tracking requests. Verify that the Pinterest Tag only fires after marketing consent is granted. Use Pinterest Tag Helper to test events and ensure tracking stops when users reject or withdraw consent.
How to verify Pinterest Conversions API consent?
To verify Pinterest Conversions API consent, check that your server-side tracking respects users' consent preferences. Test whether conversion events are blocked when marketing consent is denied and sent only when permitted. Review server-side logs and API requests to confirm consent settings are applied correctly.
How to configure Pinterest Tag Cookie Consent?
To configure Pinterest Tag Cookie Consent, connect the tag to your Consent Management Platform (CMP) and categorize it under marketing cookies. Ensure the tag only sends tracking events after users grant consent. Use Pinterest's setconsent command to manage consent preferences and test the setup using Pinterest Tag Helper.
How to prevent Pinterest Tag firing before consent?
To prevent Pinterest Tag from firing before consent, configure your Consent Management Platform (CMP) to block marketing tracking until users grant permission. Set the default consent state to denied using Pinterest's setconsent command and update it after consent is granted. Test the setup with Chrome Developer Tools or Pinterest Tag Helper.