Meta pixel setup consists of creating a pixel in Meta Events Manager, adding its base code to every page of the website, defining important actions such as purchases and form submissions as standard events, and verifying the setup with the testing tool. To make measurement complete, the pixel is usually supplemented with the server-side Conversions API, and identical events arriving from the two sources are deduplicated.
This article covers what the pixel measures, installation options in WordPress and WooCommerce, which pages should trigger standard events, the Conversions API, domain verification, and consent management according to the Turkish Personal Data Protection Authority’s cookie guide. Interface names are written using their equivalents on the Turkish pages of the Meta Business Help Center.
What is the Meta pixel, and what does it measure?
The Meta pixel is a piece of code added to a website that reports visitors’ actions on the website to Meta as events. Meta’s help page about the pixelexplains that this data is used to measure conversions from ads, build audiences, and optimize ad delivery.
Without a pixel, Facebook and Instagram ads measure clicks but cannot know what happened after the click. Once the pixel is installed, reports show whether the person who saw the ad added a product to the cart, completed a form, or made a purchase. The advertising system also learns from these events whom to show ads to according to the targeted outcome.
Meta pixel data is also used to create audiences. Visitors who recently browsed a product page but did not buy can be shown ads again, while purchasers can be excluded from the campaign so they do not see the same product again. Since these audiences take time to populate, installing the pixel a few weeks before the advertising campaign begins allows richer data to be used from the very first campaign.
Meta requires that sensitive data, such as health status or financial information, not be sent through pixel events. Page addresses and event parameters are reviewed from this perspective during setup.
Before setup: business portfolio and permissions
The pixel should be created under the business’s own Meta business portfolio and associated with the ad account within that portfolio. A pixel opened in an agency’s or freelancer’s personal account makes it difficult for the business to access its historical data when the collaboration ends.
The person performing setup is granted the necessary permissions through the portfolio as a partner or user; the main account’s password is not shared. Opening multiple pixels for the same business splits reports and causes confusion. If an older pixel was previously installed, check which account it belongs to and whether it still receives data before creating another. If the old pixel works properly, keeping it is usually preferable; accumulated visitor data and audiences remain attached to the same identifier.
Meta pixel setup step by step
The basic setup consists of creating the pixel, adding the code to the website, and defining events. In practice, the sequence followed is as follows:
- Open Meta Events Manager, create a new pixel for the web from the data sources section, and give it a name appropriate for the business.
- Choose an installation method: partner integration, manually adding the base code, or Google Tag Manager.
- Add the base code to run once in the head section on every page of the website.
- Define standard events for actions such as purchasing, adding to cart, and submitting forms.
- Use the Test Events tool in Events Manager to check that each event arrives on the correct page with the correct parameters.
- Connect the Conversions API and configure deduplication for browser and server events.
- Verify the domain in the business portfolio and connect cookie consent management to the pixel.
Meta’s automatic events may also become active during event setup; this feature recognizes some button clicks as events without additional code. If automatically detected events overlap with manually defined ones, clarify which will be used for reporting.
Standard events: where should each event trigger?
Standard events are event names predefined by Meta that can be used directly in ad optimization. Triggering each event on the correct page and only once determines the reliability of reports.
| Event | Where it triggers | Point to watch |
|---|---|---|
| PageView | Every page load | Included with the base code; do not add it separately |
| ViewContent | Product or service detail page | The product identifier must match the identifier in the catalog |
| AddToCart | The action of adding to cart | It must also work for products added without a page refresh |
| InitiateCheckout | The step where the checkout process begins | It should not be confused with the cart page |
| Purchase | Order confirmation page | Send the amount and currency, and do not count it again on page refresh |
| Lead / Contact | Form submission, phone call, or WhatsApp click | It should trigger only after a successful submission |
For service businesses, form submissions, calls, and messages are the main conversions rather than purchases. Using a thank-you page for these businesses is the most reliable way to ensure the event triggers when the form has actually been submitted.
Page contents
Installation options in WordPress and WooCommerce
On WordPress websites, the pixel can be installed in three ways: Meta’s official WooCommerce plugin, Google Tag Manager, or code manually added to the theme file. The important point is to choose just one of these approaches; if two methods run together, events are counted twice.
In WooCommerce stores, the Meta for WooCommerce plugin, formerly called Facebook for WooCommerce, allows catalog synchronization and the Conversions API connection to be set up alongside the pixel from one place. For corporate websites, Tag Manager is a more flexible option for managing the pixel and other measurement codes from a single dashboard. If the store is being newly built, planning the measurement infrastructure within the e-commerce website development process produces fewer errors than adding it afterward.
Every third-party code added places some additional load on page loading. The effects of the pixel and other tags on page speed are evaluated alongside the measurements in the article on speed optimization and Core Web Vitals .
Let’s check your pixel setup together
If the pixel has never been installed, events are being counted twice, or purchases are missing from reports, a free preliminary assessment is offered when the website address is sent through WhatsApp. Measurement is set up under the business’s own Meta portfolio, and pricing is shared by message once the scope is clarified.
What is the Conversions API, and why is it added to the pixel?
The Conversions API is a connection that allows events to be sent directly to Meta from the business’s server, website platform, or customer management system instead of the visitor’s browser. Meta’s Conversions API pageexplains that events sent from the server are less affected by browser loading and connection issues or ad-blocking extensions than measurement through the pixel.
Meta’s recommendation is to use both methods together rather than remove the pixel. The browser side captures the visitor’s behavior on the page, while the server side reliably reports when the order is actually created. Offline sales or inquiries closed by phone can also be transferred in the same way through the customer management system.
Customer information such as email addresses or phone numbers can be included in events sent from the server; this information is hashed before being sent to Meta and helps match the event to the correct person. The website’s disclosure notice must clearly state which information is shared for this purpose. A software developer is not always required for installation. Partner integrations such as the WooCommerce plugin establish the connection from the dashboard; more specialized structures use methods in Meta’s developer documentation or server-side tagging.
Deduplicating browser and server events
When the pixel and Conversions API report the same purchase twice, both reports must use the same event name and the same event identifier for Meta to count them as a single event. According to Meta’s developer documentation, events are deduplicated when the pixel’s eventID value matches the server event’s event_id value.
In practice, this means generating a unique identifier for every order and placing the same value in both the browser code and server request. Unless there is a significant difference in content, Meta generally uses the event that arrives first. When deduplication is not configured, reports show more purchases than actually occurred, and the advertising system learns from incorrect signals.
Why is domain verification necessary?
Domain verification proves to Meta which business portfolio owns the website and gives the business control over permissions to edit links pointing to that domain. Meta’s domain verification pageexplains that the process is performed through Meta Business Suite. Under Meta’s current implementation, prioritizing eight events per domain and selecting a conversion domain are no longer required to measure website events; Meta states that it is rolling out this change to accounts gradually. Verification therefore concerns permissions for editing links and content rather than event measurement. The current situation regarding measurement is explained in detail in the Meta pixel not working guide.
Verification is completed through one of three methods: adding a meta tag to the home page’s head section, uploading the HTML file provided by Meta to the website’s root directory, or adding a TXT record to the domain’s DNS records. Since the DNS method is unaffected by theme or plugin changes, it is the most reliable long-term option. The person performing verification needs access to the domain dashboard or website files; having the domain registered in the business’s name makes this step easier.
If the same domain was previously verified in another portfolio, such as a former agency’s account, that record may need to be removed before moving it to the new portfolio. After verification is complete, note the meta tag, file, or DNS record used; add it to the checklist so this record is not lost during a theme change or hosting migration.
Cookie consent: how does the KVKK (Turkey’s Personal Data Protection Law) cookie guide affect pixel setup?
The Turkish Personal Data Protection Authority’s July 2025 Guide on Cookie Practicesstates that cookies used for behavioral advertising require explicit consent. The guide does not separately regulate the pixel itself; its scope section notes that it provides no guidance for pixels and similar technologies. However, because the pixel places advertising cookies in the browser, these rules directly concern installation in practice.
The main implications of the guide for pixel setup are as follows:
- Explicit consent must be obtained before cookies are placed; entering the website does not count as consent.
- Cookies subject to explicit consent must initially be inactive in the management panel.
- The guide cites designing the accept, reject, and preference buttons in the consent window so none is more prominent than the others as an example of good practice.
- Consent must be easy to withdraw, and the panel must be accessible again through a small icon in the corner of the page.
- Consent for advertising cookies cannot be obtained by attaching it to terms of use or a privacy notice.
On the technical side, Meta provides the commands fbq(‘consent’, ‘revoke’) to stop the pixel sending events until consent is given and fbq(‘consent’, ‘grant’) after consent. When Tag Manager is used, linking the pixel tag to the marketing preference in the cookie panel produces the same result.
Note: This section communicates the principles of the KVKK guide for general information and is not a legal opinion. Support from a KVKK consultant or attorney is recommended for the disclosure notice and consent arrangement.
Testing and verifying the setup
Setup is considered complete when each event is seen arriving on the correct page, once, and with the correct value, rather than merely when events appear in reports. The Test Events tool in Events Manager lists incoming browser and server events in real time as the website is browsed. The following items are checked during testing:
- The pixel sends no events when reject is selected in the cookie panel.
- After acceptance, PageView arrives once on every page.
- In a test order, the Purchase event is counted only once with the correct amount and currency.
- The same purchase arrives from both the browser and server, and deduplication can be observed.
- The Lead event does not trigger when form submission fails.
After Meta pixel setup is complete, test orders are canceled from the store dashboard. A few days later, event match quality and warnings in Events Manager are reviewed once again.
Common mistakes in Meta pixel setup
Most mistakes arise from setting things up once and never checking them again. A theme update, plugin change, or new cookie panel can silently break a working installation. Common situations are as follows:
- Adding the pixel both through a plugin and manually, causing events to be counted twice.
- Triggering the Purchase event again whenever the order confirmation page is refreshed.
- Running the pixel without waiting for cookie consent.
- Enabling the Conversions API without sending an event identifier.
- Leaving the pixel in the agency’s account, preventing the business from accessing its data.
Taking a brief test tour after every major website change is the easiest habit for catching these errors early. Reading the warnings in Events Manager once a month also helps identify problems before advertising budget is wasted.
Once measurement is correctly configured, the main task is to manage campaigns using this data; this part is explained on the Meta ads management page. If budget allocation between Meta and Google is being considered, the budget comparison of the two advertising platforms provides guidance.
Let’s give your advertising measurement a solid foundation
When pixel and Conversions API setup, event deduplication, or cookie panel integration is needed, leaving a message is sufficient; responses are provided every day until 21.00. The advertising budget is paid directly to Meta, and no results are guaranteed.
Related guides
Frequently asked questions
Does the Meta pixel cost money?
No, creating the pixel and adding it to the website are free. A fee is paid to Meta as an advertising budget only when ads are run.
Are the Facebook pixel and Meta pixel the same thing?
Yes, the Facebook pixel was renamed the Meta pixel after Meta’s rebranding. Its installation logic and management through Events Manager remain the same.
Is installing the Conversions API mandatory?
It is not mandatory, but Meta recommends using it together with the pixel. The server-side connection helps measure events that could be lost because of browser restrictions.
Can the pixel run without cookie consent?
According to the KVKK cookie guide, behavioral advertising cookies require explicit consent, and consent must be obtained before cookies are placed. Meta’s consent commands or a tag manager integrated with the cookie panel are used to keep the pixel waiting until consent is given.
Why are events being counted twice?
The most common reason is adding the pixel through two different methods or failing to use the same event identifier in pixel and server events. A purchase event triggered again when the order confirmation page is refreshed produces a similar result.
Which method should be used for domain verification?
Any of the meta tag, HTML file, or DNS TXT record methods can be used. Since the DNS record is unaffected by theme and plugin changes, it is more reliable over the long term.
Which plugin should be used for WooCommerce?
Meta’s official plugin is published as Meta for WooCommerce and sets up the pixel, catalog synchronization, and Conversions API connection together. Another pixel plugin should not run at the same time.
Call us
Call us for detailed information.
Let us call you!
Share your phone number and let us call you!
Our other services
- › Corporate web design
- › E-commerce website development
- › SEO optimization
- › WordPress website development
- › Google Ads management
- › WordPress speed optimization
Service areas
- › Web design in Sakarya
- › Web design in Tekirdağ
- › Web design in Bursa
- › Web design in Beşiktaş
- › Web design in Şişli
- › Web design in Tuzla
- › Web design in Ümraniye
- › Web design in Kadıköy
- › Web design in İstanbul
- › Web design in Ankara
- › Web design in Ataşehir
- › Web design in Üsküdar
- › Web design in Kartal
- › Web design in Maltepe
- › Web design in Pendik
- › Web design in Kocaeli
- › Web design in İzmir
- › Web design in Antalya
