How to Set Up Meta Conversion Events: Purchases, Add to Cart and Leads

A conversion event in Meta advertising is a record that indicates someone has completed an action valuable to your business. Opening a product page and completing an order are different actions. Preserving that distinction in measurement makes reports more meaningful and clarifies the behavior your campaign is optimized for. Before setup, write down your business goal, where the action happens and how you will verify the event. Interface labels and available connection methods can vary by account and website platform.

Prepare an event map first

For an ecommerce website, viewing a product, adding it to a cart, starting checkout and completing a purchase are separate stages. For a service business, opening a form, submitting it and having the sales team evaluate the inquiry carry different meanings. Define each stage clearly. This ensures that developers, marketers and report readers count the same action.

This table is a starting template. With cash on delivery or bank transfers, placing an order and collecting payment may happen at different times. Agree on your Purchase definition alongside the business's order and revenue reporting approach. If you change it later, add the change date to your reporting notes.

Choose the right data source and connection

Open the relevant website data source in Events Manager. If a supported partner integration exists for your website platform, first review the events it provides. The Meta Pixel helps share events through the browser, while the Conversions API supports event sharing through servers or supported connections. Installing one does not mean the other automatically works correctly.

1. Check that you are in the correct business and data source.
2. List existing integrations and identify whether different plugins send the same event.
3. Follow your platform's setup steps and review event mapping.
4. For work that requires code, give your developer the event definitions and test scenarios.

Plan data sharing in line with your website's consent preferences and applicable data use conditions. Form text, health information, payment card details and freely entered personal explanations should not be sent as event parameters. Collecting unnecessary data is not a way to improve measurement.

Map parameters to business data

For purchase events, the amount and currency matter when interpreting revenue reports. For educational purposes only, consider an order worth TRY 1,250: its value can be mapped as 1250 and its currency as TRY. Define whether tax, discounts and shipping are included from the start. Do not send a fixed example value for actual orders.

If you share product IDs, check that they match the IDs in your catalog. When the website ID and catalog ID differ, matching may not work as expected. Do not add an arbitrary revenue amount to a Lead event to make an inquiry look like a sale. Assess the economic value of an action that has not yet generated revenue through a separate analysis.

Check for browser and server duplicates

If the same customer action is sent through both the Pixel and the Conversions API, you need to prevent it from appearing as two purchases. Check how your integration handles duplicate records using the event name and the event ID associated with the same action. IDs should match for the same order; different orders must not accidentally share one ID.

Duplicate counting has other causes too. Examples include sending an event again when someone refreshes a thank-you page, multiple tags running together or a form being processed twice. Do not diagnose the issue from report totals alone. Trace the points where your test action is sent.

Test the actual journey and interpret reports

Use the testing and diagnostic tools in Events Manager to run separate scenarios for adding a product, failed payment, completed orders and form submissions. An event appearing in the tool does not by itself mean it came from an ad. Event receipt, attribution to advertising and the business's order record are three different checks.

Compare an example test order with the record in your website administration system. Inspect its amount, time and duplicate count. Then verify that the campaign uses the appropriate conversion location, data source and optimization event. Instead of expecting ad reporting and accounting totals to match exactly, evaluate date ranges, attribution and cancellation processes within a consistent scope.

Common mistakes and final checklist

Common mistakes include treating a button click as a completed action, interpreting test data as actual results and stopping verification after installation. A theme change or new payment method can affect your event flow. Perform a short verification after every significant website update.

• Is the completion condition for every event written down and clear?
• Do the amount, currency and product ID come from the actual transaction?
• Are failed actions prevented from sending a success event?
• Does the setup handle page refreshes and duplicate integrations?
• Have consent preferences and data sharing been checked together?
• Is the campaign optimized for the correct event?