| 开发者 | webaround |
|---|---|
| 更新时间 | 2026年9月29日 23:57 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
openai_ads_track( 'lead_created', [], [ 'event_id' => $lead_id, 'user' => [ 'email' => $email ] ] );
Also openai_ads_event_id(), openai_ads_pixel_event(), openai_ads_hash_user(),
openai_ads_image_tag() and openai_ads_is_configured(), plus filters and actions
for consent, event data, identity and integrations. Every event OpenAI documents
for the web is supported, plus custom.
Full documentation: https://github.com/webaroundlabs/openai-ads-toolkit
A purchase measured in the browser and again on the server is one purchase, but two reports. Both halves send one event id, so OpenAI counts one conversion.
The Pixel alone works, and needs only a Pixel ID. It is also the half an ad blocker or a failed script can remove. The API key adds the server-side half, which nothing in the browser can block - and because the two are deduplicated, adding it inflates nothing.
Everything is measured, and the settings screen tells you so in as many words. That default is deliberate: the alternative is a plugin that silently measures nothing while you hunt for the fault. Install a banner supporting the WP Consent API and it is used automatically.
Yes, and without a paid server-side container. Switch on the collection endpoint and point a tag at it; the API key never leaves your server.
No, and no. Conversions are never sent while the visitor is waiting, and WooCommerce is optional - where it is installed, the plugin reuses its queue.
No. If reporting fails the plugin logs it and moves on. The order, form submission or registration still completes.
No. It is used only server-side and is never printed into a page. The plugin's test suite asserts this.