Skip to main content

Tracking with the Meta Pixel | Developer Documentation

Check what your website tracking measures around WhatsApp

Your website's tracking and your ChatArchitect message connection are separate parts of the customer journey. Connecting a WhatsApp number does not automatically install a Meta Pixel on your website or define the advertising events your site reports.

Name the action being measured

ObservationWhat it establishes
A visit to a pageThe website report recorded a visit under its own rules.
A click on a WhatsApp linkThe site recorded the click, if that event is configured. It does not by itself establish that a message was sent.
An incoming WhatsApp messageThe connected receiving system recorded the message; this is a separate observation from the website click.
A submitted website form or saleThe responsible site or business system recorded that action. Its relationship to a WhatsApp conversation requires supporting evidence.

Review the website configuration with its owner

  1. Identify the page, link or form you want to measure and the reporting tool configured for it.
  2. Ask the site's maintainer what event fires, which action triggers it and whether the report includes that page.
  3. Check an agreed example under the site's applicable tracking settings, then inspect the resulting event in its reporting tool.
  4. Check the receiving WhatsApp conversation separately when that is part of the test.

Record the time, event definition and available source reference for each observation. Compare them only when the data supports the connection; a nearby timestamp alone does not identify the same customer journey.

Keep signup tracking separate from customer messaging

The former provider example measured a developer's own Embedded Signup button. ChatArchitect supplies the ready-made customer connection. Adding a Meta SDK or signup button to your website is not required to complete that connection.

ChatArchitect does not provide Automatic Events API for inferred ad-driven leads or purchases. Ask the owners of any separately configured Pixel or Conversions API implementation what it actually sends. For a reporting disagreement, use the report comparison checklist; for work with an external analyst, prepare a measurement brief.

No comments to display