Netro Ads 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 from one settings screen and measures the conversions that matter on a service business site: phone calls, WhatsApp messages, form submissions and (optionally) WooCommerce purchases.<\/p>\n\n
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.<\/p>\n\n
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.<\/p>\n\n
Google Ads, Google Analytics 4 and Google Tag Manager<\/strong><\/p>\n\n Paste a GA4 measurement ID ( Google events are sent from the browser; the server-side channel covers Meta and OpenAI.<\/p>\n\n ChatGPT Ads (OpenAI)<\/strong><\/p>\n\n 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 ( What it measures without any setup per page<\/strong><\/p>\n\n Built for the things that fail silently<\/strong><\/p>\n\n Every failure mode of pixel measurement is silent \u2014 nothing errors, conversions just stop arriving. The status panel on the settings screen names each one:<\/p>\n\n Nothing is sent to the plugin author.<\/strong> This plugin has no servers of its own,\nno analytics of its own, no licence check and no usage reporting. The only\ndestinations it ever contacts are the advertising accounts the site owner\nconfigures: Meta (Facebook), OpenAI (ChatGPT Ads) and Google \u2014 each only if the\nsite owner enters an ID for it.<\/p>\n\n The consent gate is on by default.<\/strong> On a fresh install the consent mode is\n\"strict\": no measurement script is loaded and no event is sent until the visitor\nagrees. A built-in banner asks, unless one of the supported consent plugins is\ndetected, in which case that plugin's decision is used. Turning the gate off is\nan explicit choice the site owner has to make in the settings, and the settings\nscreen says what that means.<\/p>\n\n The visitor's browser decides, not the server.<\/strong> The consent state is read in\nthe browser, so a cached page cannot serve one visitor's decision to another.<\/p>\n\n The admin area is never measured.<\/strong> No event is sent from wp-admin, and by\ndefault logged-in administrators, editors and shop managers are not measured on\nthe front end either.<\/p>\n\n What leaves the site, once configured and consented to:<\/strong> the event name, the\npage URL, the visitor's IP address and user agent, Meta's own This plugin sends data to Meta (Facebook) and, if you configure them, to OpenAI and Google. Nothing is sent before you enter an ID.<\/p>\n\n Meta Conversions API<\/strong> ( Meta Pixel<\/strong> ( Meta pixel configuration<\/strong> ( The plugin also reads the site's own home page<\/strong> once every six hours from the\nadmin area, to detect measurement tags installed by the theme or another plugin.\nThat request stays on the site's own domain.<\/p>\n\n OpenAI Measurement Pixel<\/strong> ( OpenAI Conversions API<\/strong> ( Google<\/strong> ( No. Nothing is added to your theme, and no code is copied from the Meta or Google panels \u2014 paste the IDs (or the whole snippet) into this screen instead.<\/p><\/dd>\n Yes, and it is built for it: no per-visitor value is ever printed into the HTML, so cached pages stay correct. Measured with a full page cache serving byte-identical HTML to two visitors: the event IDs differ.<\/p><\/dd>\n Yes, and it is on by default: a new install starts in \"strict\" mode, where no measurement script loads until the visitor agrees. Complianz, CookieYes, Borlabs Cookie and Real Cookie Banner are detected and their decision is used; otherwise a simple built-in banner asks. Google Consent Mode v2 defaults are set before any Google tag loads. Meta has no cookieless mode, so the pixel is never loaded before marketing consent. You can switch the gate off if your audience is outside the EU\/UK, but that is a deliberate choice, not the default.<\/p><\/dd>\n Yes. The OpenAI tab takes the Pixel ID and the Conversions API key from ChatGPT Ads Manager (Tools \u2192 Conversions). Contact clicks and form submissions are sent as In its own option, never in the settings array and never in front-end output. For a stricter setup, define Open the status list. The usual causes are a missing access token, a test event code left in place, a Google Ads conversion label left empty, an event name Meta restricts on your pixel, or a REST API blocked by a security plugin \u2014 each one is reported there by name.<\/p><\/dd>\n\n<\/dl>\n\n\nG-\u2026<\/code>), a Tag Manager container (GTM-\u2026<\/code>) and a Google Ads conversion ID (AW-\u2026<\/code>) \u2014 or the whole snippet Google gives you; the IDs are read out of it. The same actions are then reported to Google:<\/p>\n\n\n
page_view<\/code>, generate_lead<\/code>, contact<\/code> (with the method: phone, WhatsApp, email\u2026) and, with WooCommerce, purchase<\/code> with value, currency and transaction ID.<\/li>\ntransaction_id<\/code>.<\/li>\ndataLayer<\/code> events you can trigger your own tags on: netroads_contact<\/code>, netroads_lead<\/code>, netroads_purchase<\/code>.<\/li>\nlead_created<\/code> by default), and with WooCommerce contents_viewed<\/code>, items_added<\/code>, checkout_started<\/code> and order_created<\/code>. 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<\/code> click identifier is carried from the landing page to later server events.<\/p>\n\n\n
data-netroads-conversion=\"lead\"<\/code> (or \"contact\"<\/code>) to a button or form.<\/li>\n<\/ul>\n\n\n
fbclid<\/code> is captured on the landing page and carried through the session, so events from inner pages still carry the click ID.<\/li>\nfbp<\/code>, fbc<\/code>, 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.<\/li>\nnavigator.sendBeacon<\/code> and survive the unload.<\/li>\nwp-config.php<\/code> instead of the database.<\/li>\n<\/ul>\n\nPrivacy<\/h3>\n\n
_fbp<\/code> \/ _fbc<\/code>\ncookies, and \u2014 for form and order conversions \u2014 the email address, phone number,\nname, city, postcode and country the visitor typed, SHA-256 hashed before they\nleave the server. The site owner is the data controller for all of it.<\/p>\n\nExternal services<\/h3>\n\n
graph.facebook.com<\/code>) \u2014 when you save a dataset ID and an access token, conversion events are sent from your server: event name, event time, page URL, the visitor's IP address and user agent, the _fbp<\/code> \/ _fbc<\/code> cookies, and \u2014 for form and order conversions \u2014 the email address, phone number, name, city, postcode and country hashed with SHA-256<\/strong> before they leave your site. Terms: https:\/\/www.facebook.com\/legal\/terms\/businesstools \u2014 Privacy: https:\/\/www.facebook.com\/privacy\/policy<\/p>\n\nconnect.facebook.net<\/code>) \u2014 the pixel script is loaded in the visitor's browser and reports the same events. Terms and privacy as above.<\/p>\n\nconnect.facebook.net\/signals\/config\/<id><\/code>) \u2014 read once every 12 hours in the admin area to detect event names Meta restricts on your pixel. No visitor data is sent.<\/p>\n\nbzrcdn.openai.com<\/code>, bzr.openai.com<\/code>) \u2014 loaded in the visitor's browser only if an OpenAI Pixel ID is saved, and only after marketing consent. It reports the same events and handles OpenAI's own click identifier. Terms: https:\/\/openai.com\/policies\/advertising-terms\/ \u2014 Privacy: https:\/\/openai.com\/policies\/<\/p>\n\nbzr.openai.com\/v1\/events<\/code>) \u2014 when an OpenAI Pixel ID and Conversions API key are saved, conversion events are sent from your server: event name, event time, page URL, the visitor's IP address and user agent, OpenAI's oppref<\/code> and obref<\/code> identifiers, and \u2014 for form and order conversions \u2014 the email address, phone number and name hashed with SHA-256<\/strong>, plus city, region, postcode and country as plain text, as OpenAI's documentation specifies. The \"Test server connection\" button sends one event with validate_only<\/code>, which OpenAI checks but does not save. Documentation: https:\/\/developers.openai.com\/ads\/conversions-api<\/p>\n\ngoogletagmanager.com<\/code>, google-analytics.com<\/code>, googleadservices.com<\/code>) \u2014 loaded in the visitor's browser only if you enter a GA4, Google Tag Manager or Google Ads ID, and in the default strict consent mode only after the visitor agrees. In the optional Consent Mode v2 \"advanced\" setting they load before consent without writing cookies. It reports the page view and the conversions listed above; no data is sent from your server. Terms: https:\/\/policies.google.com\/terms \u2014 Privacy: https:\/\/policies.google.com\/privacy<\/p>\n\n\n\n
\n
Do I have to paste code into my theme?<\/h3><\/dt>\n
Does it work with a caching plugin?<\/h3><\/dt>\n
Is consent supported?<\/h3><\/dt>\n
Does it support ads in ChatGPT?<\/h3><\/dt>\n
lead_created<\/code> by default \u2014 OpenAI has no separate contact event, and its documentation defines lead_created<\/code> as a lead form or a contact request. You can report contact clicks as a custom contact<\/code> event instead. Whatever you pick, create the same event in Ads Manager and attach it to your campaign.<\/p><\/dd>\nWhere does the access token live?<\/h3><\/dt>\n
NETROADS_CAPI_TOKEN<\/code> in wp-config.php<\/code> and the field is ignored.<\/p><\/dd>\nMy conversions do not arrive and there is no error.<\/h3><\/dt>\n
1.1.3<\/h4>\n\n
\n
transaction_id<\/code> so Google\nde-duplicates them, and are never sent under a form or contact label. The\nstatus list says when the label is missing.<\/li>\n1.1.2<\/h4>\n\n
\n
1.1.1<\/h4>\n\n
\n
measureSingle<\/code>).\nWith measure<\/code>, every event also reached any other OpenAI pixel already on\nthe page \u2014 for example one pasted into the theme by hand.<\/li>\n1.1.0<\/h4>\n\n
\n
oppref<\/code> carried from the landing page.<\/li>\n1.0.4<\/h4>\n\n
\n
1.0.3<\/h4>\n\n
\n
1.0.2<\/h4>\n\n
\n
1.0.1<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n