Netro Ads – Pixel & Conversions API for Meta, Google Ads and ChatGPT

On a service business site the conversion is a phone call, a WhatsApp message or a form — not a checkout. Most measurement setups never record those, and nothing on the screen says so: the pixel loads, the campaign runs, and the conversion column stays empty. Netro Ads measures them. Paste your IDs into one screen and phone clicks, WhatsApp clicks and form submissions are reported to Meta, Google Ads, GA4, Tag Manager and ChatGPT Ads — no code in your theme, no tag manager to learn, nothing to mark up on each page. WooCommerce purchases are included when you have a shop. It installs the Meta Pixel, the Meta Conversions API, Google Ads conversion tracking, Google Analytics 4, Google Tag Manager and the ChatGPT Ads (OpenAI) Measurement Pixel and Conversions API. It is server-side tracking without a tag server: every conversion is sent from the browser and from your WordPress server (Meta CAPI and OpenAI Conversions API), so an ad blocker or an event name Meta restricts in the browser does not cost you the conversion. Call tracking and WhatsApp click tracking work on any theme, and the consent gate (GDPR, Google Consent Mode v2) is on by default. The browser event and the server event share a single event ID, so each platform de-duplicates them and counts one conversion instead of two. One user action gets one ID, used for every platform. Google Ads, Google Analytics 4 and Google Tag Manager Paste a GA4 measurement ID (G-…), a Tag Manager container (GTM-…) and a Google Ads conversion ID (AW-…) — or the whole snippet Google gives you; the IDs are read out of it. The same actions are then reported to Google:

• Google Ads conversions for form submissions, phone clicks, WhatsApp clicks and other contact links (email, Messenger, Telegram), each with its own conversion label or one shared contact label. A missing label is reported in the status list: Google ignores a conversion without one and shows no error.
• GA4 events: page_view, generate_lead, contact (with the method: phone, WhatsApp, email…) and, with WooCommerce, purchase with value, currency and transaction ID.
• With WooCommerce, purchases go to Google Ads under their own conversion label, with value, currency and the order number as transaction_id.
• Tag Manager dataLayer events you can trigger your own tags on: netroads_contact, netroads_lead, netroads_purchase.
• Google Consent Mode v2 defaults are set before any Google tag loads and updated when the visitor decides.

Google events are sent from the browser; the server-side channel covers Meta and OpenAI. ChatGPT Ads (OpenAI) Paste the Pixel ID and a Conversions API key from ChatGPT Ads Manager and the same actions are measured there too: page views, contact clicks and form submissions (lead_created by default), and with WooCommerce contents_viewed, items_added, checkout_started and order_created. OpenAI's own rules are applied, which differ from Meta's: names are normalised without spaces before hashing, amounts are sent as integers in the currency's minor unit (three decimals for KWD, none for JPY), and the oppref click identifier is carried from the landing page to later server events. What it measures without any setup per page

• PageView on every page.
• Contact on every phone, WhatsApp, Messenger, Telegram, SMS or email link — in any theme or page builder, including links added later or inserted by a page builder. One delegated listener covers the whole site; you never mark a link.
• Lead after a form submission actually succeeds: Contact Form 7, WPForms, Gravity Forms, Elementor Pro Forms, Fluent Forms. A failed or invalid submission produces nothing.
• ViewContent on the post types you choose.
• AddToCart, InitiateCheckout and Purchase when WooCommerce is active. Purchase is sent once per order even if the thank-you page is refreshed.
• Anything else: add data-netroads-conversion="lead" (or "contact") to a button or form.

Built for the things that fail silently Every failure mode of pixel measurement is silent — nothing errors, conversions just stop arriving. The status panel on the settings screen names each one:

• Meta restricts certain event names on individual pixels (common on health and aesthetics accounts). The browser drops such an event with no error at all. The plugin reads your pixel's own configuration, tells you when your contact event is restricted, and lets you pick another name — used on both channels so de-duplication still works.
• The event ID is generated in the browser, never printed into HTML, so a full page cache cannot hand one ID to every visitor.
• fbclid is captured on the landing page and carried through the session, so events from inner pages still carry the click ID.
• Phone numbers are normalised with a country code on both channels from one shared rule; a mismatch between browser and server hashing zeroes matching without any error.
• fbp, fbc, IP and user agent are never hashed; email and phone are hashed on the server and passed in plain text to the pixel, which hashes them itself.
• Contact clicks leave the page immediately, so server events are sent with navigator.sendBeacon and survive the unload.
• A filled-in test event code sends your live conversions to the Test Events stream instead of your dataset. The panel flags it in red.
• The access token is stored outside the settings array, is never printed on the front end, and can live in wp-config.php instead of the database.

1.1.4

• Fix: a Google Ads conversion label that Google never issued (a name typed by hand, such as "form", or an ID pasted into the label box) was accepted and sent as AW-XXXXXXXX/form. Google ignores an unknown label without any error, so those conversions were never recorded while the screen looked correctly set up. The label is now checked where you type it, the status list names every channel it affects, and an ID pasted into a label box is refused.
• Fix: a Google tag pasted into the Meta dataset field had its digits scraped into a pixel ID that does not exist. Google and Tag Manager tags are now recognised and refused in the Meta and OpenAI fields.
• The settings screen was rebuilt: a header bar with the live status, a side menu instead of the row of tabs, and the status list opens first when something needs attention. No extra requests — one stylesheet, one script, same as before.

1.1.3

• Fix: WooCommerce purchases were reported to Google Ads under the form (lead) conversion label. Purchases now have their own "WooCommerce purchase label" on the Google tab, carry the order number as transaction_id so Google de-duplicates them, and are never sent under a form or contact label. The status list says when the label is missing.
• Fix: on a store with only Google (GA4 / Google Ads) configured, the purchase was never sent, and the thank-you page could report it again on reload.
• Fix: when the visitor accepts cookies on the thank-you page itself, the purchase is now sent after the Google tags are configured, not before.
• The admin menu shows the Netrobit logo; plugin name and description now mention Google Ads, GA4 and Tag Manager.

1.1.2

• Security: the WooCommerce Purchase payload is now printed from the woocommerce_thankyou hook, which WooCommerce fires only after its own order-key, account and email checks. The plugin no longer reads the order ID from the request and never prints the order key.
• Inline JSON is encoded with JSON_HEX_TAG and related flags.
• The "Saved" notice no longer relies on a query argument.

1.1.1

• OpenAI events are sent only to this plugin's own Pixel ID (measureSingle). With measure, every event also reached any other OpenAI pixel already on the page — for example one pasted into the theme by hand.
• OpenAI server requests wait up to 10 seconds and are retried once on a network error, with the same event ID so OpenAI de-duplicates the retry.
• A network delay is now reported as a warning, not as a broken setup, and is re-checked after a minute.

1.1.0

• New: ChatGPT Ads (OpenAI) Measurement Pixel and Conversions API. Same actions, same consent gate, same event ID as Meta; OpenAI's own normalisation and minor-unit amounts; oppref carried from the landing page.
• The "Test server connection" button now tests every configured platform.
• The status list reports OpenAI setup and any other OpenAI pixel already on the page.

1.0.4

• The consent gate is now on by default: a new install starts in strict mode and loads nothing until the visitor agrees.
• The public reachability endpoint no longer reports whether an access token is configured; that answer now comes only from the administrator-only route.
• Removed a plugin header URL that did not resolve.

1.0.3

• New check: the plugin reads your own home page once (cached for six hours) and reports measurement tags that are not its own — a second Meta pixel, Google tags already loaded by the theme or another plugin, or a duplicate domain verification tag. Each of those makes conversions count twice or verification fail, and none of them produces an error anywhere.
• The domain verification field now warns when the value looks like a numeric ID rather than a verification code.

1.0.2

• The event name a successful form submission sends is now a setting, like the contact click name already was. Both channels always use the same name.
• The restriction check now compares every event name the site actually sends against the pixel's own restriction list, and says what it means for you: with a working server side a restricted name is a warning (the conversion still arrives), without one it is a failure (the conversion is lost).
• Fixed a stale diagnostic: the endpoint reachability result was cached for an hour, so a check that ran before the plugin was configured kept reporting a 409 long after the settings were saved. Saving now clears every diagnostic cache, failures are cached for five minutes, and the check no longer runs at all while the plugin is unconfigured.

1.0.1

• The "Test server connection" button now checks whether the token can actually send events, instead of reading the dataset's name. A Conversions API token can send events without being allowed to read the dataset object, so a working setup was reported as "(#100) Missing Permission".
• The status panel reports the same check, and each authentication failure now names its own cause: expired token, dataset not assigned to the token's user, or an ID that belongs to another business.

1.0.0

• First release.