Conversion tracking and Pixel setup: Google, Meta, TikTok and Snap

1. Define the event before installing anything

Write down what has actually happened when an event fires. Purchase should represent the agreed confirmed purchase state; Lead should represent a successfully accepted inquiry, not merely a button click. Specify value, currency, event time and any transaction reference that the integration requires.

Choose one implementation owner and list existing plugins, tag managers and direct code. An ecommerce plugin and a second manual tag can send the same event twice. Do not add another installation until you understand the current one.

On a narrow screen, scroll the table sideways to compare.

2. Google Ads: distinguish the Google tag from the conversion

In Google Ads, create or select the website conversion action that represents your outcome. Follow its current setup instructions for the Google tag and the required conversion event, or the supported tag-manager or partner integration. Confirm the action’s account, identifiers, goal, counting setting and value treatment.

Install the base tag once through the chosen method and trigger the conversion only at the intended success state. Use the available tag diagnostics to test it. A tag detected on a page is not evidence that the right Google Ads action received a completed conversion. GA4 event collection alone is not proof of a configured Google Ads conversion.

3. Meta: connect the intended website event source

Use Meta Events Manager to select or create the website data source for the correct business. Follow the partner or manual installation workflow provided to that account. Record the source identifier and confirm that the ad account can use it before choosing it for a campaign.

Configure the events your business actually needs, then inspect Test Events and diagnostics for the completed action. Meta’s interface may use Pixel and dataset terminology; verify the identifier instead of relying only on a similar display name. If a partner also sends server events, check its deduplication configuration before adding a second integration.

4. TikTok: set up and verify the web connection

Open TikTok Ads Manager, then Tools and Events Manager. Start Connect Data Source, choose Web and follow the available partner or manual setup. Name and identify the Pixel for the intended website, then configure the required events.

Test the real success action with Test Events and inspect Diagnostics. Pixel Helper can help inspect browser firing, but it does not prove ad attribution. If Pixel and Events API send the same conversion, share the matching event and event_id through both paths so TikTok can deduplicate it.

5. Snapchat: install the Snap Pixel for your website

In Snapchat Ads Manager, locate the Pixel setup workflow for the correct ad account. Create or select the intended Pixel and follow the current manual or supported partner instructions. Configure the event for the business outcome and verify the destination before using it in a campaign.

Use the platform’s event diagnostics to verify receipt. When combining Snap Pixel with Conversions API, follow Snap’s field mapping: the browser client_dedup_id and server event_id must identify the same occurrence. Do not assume every platform uses the same browser field name.

6. Test failures, refreshes and duplicates as well as success

Test a successful action, a failed action and a reload of the success screen. Confirm that failures do not report a successful conversion and that a reload does not create an extra purchase. For server delivery, also test a retry of the same event and an invalid payload.

Separate a test-event receipt from live attributed reporting. Use documented test modes and permitted synthetic records, not real customer details or artificial ad clicks. Compare time zones, event names and reporting windows before concluding that a discrepancy is a tracking failure.

• Success: the intended event is received with the expected fields.
• Failure: no success event is sent for a rejected or incomplete action.
• Retry or refresh: the same occurrence is not counted as another conversion.

7. Review data sharing before production

Choose the minimum events and fields needed and review the platform requirements and privacy choices applicable to your business. Do not send passwords, full payment data or sensitive form content. Server-side delivery does not remove consent or privacy obligations.

This guide is informational: it does not install tracking on the AdsGorilla website or on your site. Additional measurement work and platform access must be agreed separately.