Access Sarbacane API keys for contact management.
Sarbacane's standard native connectors (Magento, PrestaShop, WordPress, Salesforce, MySQL) synchronize a predefined set of fields that does not include tracking pixel consent by default.
Transmitting this field via an external connector presents a compliance risk related to the one-way operation of synchronization (from the external source to Sarbacane):
A contact gives their consent to the pixel on the external source and is imported into Sarbacane.
The contact withdraws their tracking consent directly from a Sarbacane campaign.
This unsubscribe information is not sent back to the external source.
During the next synchronization cycle, the external source returns the initial "opt-in" value and overwrites the unsubscribe recorded in Sarbacane.
Important : synchronizing pixel consent via a one-way external connector risks silently re-subscribing contacts who had unsubscribed in Sarbacane to contact tracking.
Pixel consent (pixelOptin) is a system field attached directly to the contact (and not to a list).
The API allows you to record consent in the following situations:
Updating existing contacts: transmission of the parameter "pixelOptin" : "1" when updating the contact record.
New registrations: collecting consent during newsletter registration, for which neither external forms nor Sarbacane system forms allow direct writing to this system field.
The accepted values are identical to those for manual import:
- "True / Yes / 1 / yes" for contacts who accept tracking
- "False / No / 0 / no" for contacts who refuse tracking
Note: The exact field name is pixelOptin. Any field with a different name (for example optinPixel) will be ignored by the API: the request will succeed without error, but the information will not be recorded on the contact.
The pixelOptinAt field does not need to be filled in: the consent date is automatically populated as soon as pixelOptin is set.
Find all available fields on contacts in the developer documentation.
A standard list (non-synchronized) can also complement this approach. Unlike a synchronized list, a standard list has no external source that periodically pushes values: it only changes through actions taken directly in Sarbacane (one-time import, form, or API). By integrating the contacts affected by the tracking pixel into it and controlling their pixelOptin field only via the API, we eliminate by design the risk of overwriting, since nothing ever rewrites this value from outside.
