Article sections

    The ‘User privacy settings (GDPR)’ feature from the Omniconvert platform is a feature available for the users who do not have a cookie pop-up consent and will address users from the European Union. You can find this feature after you have added your website to the platform.

    The possibilities you have are the following:

    GDPR Disabled

    Situations in which the GDPR feature should remain disabled:

    • You don’t address users (don’t have customers) from the European Union and you don’t need to worry about obtaining their consent for starting to track them and personalize their journey on your website.
    • You are using your own methods (your pop-up) to ask for the users’ consent and you do not need our pop up.

    How to do it:

    Click on Disabled:

    Click on ‘I understand and accept‘:

    Click on ‘Save and continue‘:

    [alert]Please, make sure you mention Omniconvert to your users as a 3rd party tool/partner that uses their data with the purpose of collecting information meant to deliver personalized content (to personalize and increase the user’s accessibility on the website).[/alert]

    GDPR Enabled

    • Enabled > Website: For websites that address users from the European Union and already have their own pop-up that requests the user their consent to be tracked. In this case, you use your own pop-up and methods to ask for your users’ consent and (need to!) send to Omniconvert their approval to be tracked by implementing in your source code these 2 snippets of code:
    _mktz.saveConsentChoice('yes', 'We value your privacy, so please confirm...', '3');

    _mktz.saveConsentChoice('no', 'We value your privacy, so please confirm...', '3');

    [alert]If, by mistake, you enabled the GDPR feature and did not implement the above-listed scripts (thus, you failed to send us your users’ consent or disapproval to be tracked), your experiments will not apply because the GDPR setting is enabled but we are not receiving the users’ consent.[/alert]

    • Enabled > Omniconvert: For websites that address users coming from the European Union and DO NOT have designed their own pop-up requesting the users’ consent to be tracked. for you use Omniconvert’s pop-up to ask for your users’ consent to be tracked and there is no need to make additional implementations. The banner on your website, implemented through our methods should look like this:

    [alert] It is not mandatory to use the GDPR functionality from Omniconvert. It is a functionality/possibility we offer for our users who don’t have the means to implement directly a GDPR pop-up. If you wish, you can disable it completely and through your own means inform your users about the fact you have a 3rd party tool (Omniconvert) that uses their data to customize and improve their experience. [/alert]

    Additional code options

    Accept the use of already existing data – The website’s user accepts the continued use of all the data that has been recorded up to this moment.

    _mktz.acceptDataUse(consentText, consentVersion)

    Delete already existing data – The website’s user refuses to allow the use of data that has been recorded up to this moment and all the data will be scheduled for removal, but data will continue to be collected in the future.

    _mktz.refuseDataUse(consentText, consentVersion);

    Revoke the consent and delete the recorded data – The user revokes a previously given consent. After this action, the data will not be used and will be scheduled for removal.
    ConsentText and ConsentVersion are optional.

    _mktz.revokeDataUse(consentText, consentVersion);

    Suppress the opt-in message – This should be used only when the website has another mechanism implemented for asking for the GDPR consent. This line has to be placed before the Omniconvert tracking code.

    _mktz.push(‘suppressOptin’);

    When using this option the website’s owner needs to implement its own widget/banner or another method to ask the users’ consent to allow us to use their data. When the user provides an answer the website’s code will need to trigger the _mktz.saveConsentChoice() function as described above to let us know about the user’s choice.
    This works in a similar way to the “Self Managed” option but is intended for a more fine-grained control use, such as on specific Landing Pages or website sections.

    Was this post helpful?