Note
The labels of the fields offered here can be individualized. For marking the keywords associated with the stored documents, appropriate tags are inserted into the text. The preview here shows the standard texts used by contentbird Convert. |
Privacy policy
Export column: privacy
Export natively in export format as truth value, otherwise as text with values true|false.
Checkbox to confirm that the user is aware of the privacy policy ¹ ' ³.
Example:
Data processing by contentbird GmbH
Export column: dataprocessing
Export natively in export format as truth value, otherwise as text with values true|false.
Checkbox agreeing to data processing/storage of data by contentbird GmbH ¹.
Example:
Ordering newsletter
Export column: newsletter
Export natively in export format as truth value, otherwise as text with the values true|false.
If the double opt-in option is activated for your medium, there may be an additional column newsletterDoubleOptIn in the export. This is implicitly to be evaluated as false (boolean) if not present. If present, the field contains either the date on which the lead contact agreed to the newsletter via the double opt-in or false. Even if the value is set to NULL, this is to be interpreted as a lack of consent.
Checkbox with which an offered newsletter can be ordered ². Since a newsletter requires an email address, a corresponding field is added to the form if not already present.
If the double opt-in was activated in the medium, a corresponding process is triggered and the date of the executed double opt-in is also added to the export.
Example:
Conditions of participation
Export column: terms
Export natively in export format as truth value, otherwise as text with values true|false.
Checkbox to accept the provided terms of participation ¹.
Example:
Terms of participation and privacy policy
Export column: terms_privacy
Export natively in export format as truth value, otherwise as text with values true|false.
Checkbox accepting the provided terms of participation and confirming knowledge of the privacy policy ¹ ' ³
Example:
¹ is always configured as a mandatory field
² cannot be configured as a mandatory field
³ the confirmation of the acknowledgement of the privacy policy can be legally problematic and allows the end user to object if necessary. We will soon offer another field here that simply provides the privacy policy.