chatgpt_ads 1.0.1

Bug fixes. Sites running the Conversions API sub-module with the consent gate on should update.

Bug fixes

• #3623579: with Load the pixel only after the visitor consents on, the Conversions API sent the hashed email, phone and names, the IP address and the user agent of a visitor who had not answered the consent notice yet, while the pixel held that visitor's events back. The server now follows the pixel's rule: with the gate on, personal identifiers go only for a visitor whose consent was recorded; with it off, for every visitor except one whose refusal was recorded.
• #3623581: on the Webform handler form, Event and Send from rendered below the Advanced matching and Value details. They now come first.

Behavior to note

• A consent manager wired through the JavaScript contract alone records no decision on the server, so with the gate on its server events now carry no personal identifiers, not even for visitors who accepted. To send them, override the chatgpt_ads.consent_reader service with a reader for that consent manager's cookie, as the README describes. The status report entry for this setup is now a warning that says so, instead of an error saying the pixel never loads.
• An order placed before the update and paid after it is sent under the old rule, because it was captured before the gate state was recorded.

Also in this release

• #3623580: a logo.png for Project Browser.
• The README says where each sub-module is configured, lists registration_completed among the server events, and describes every event the module measures, not only conversions.