The 5.7 branch of Magnolia reached End-of-Life on December 31, 2023, as specified in our End-of-life policy. This means the 5.7 branch is no longer maintained or supported. Please upgrade to the latest Magnolia release. By upgrading, you will get the latest release of Magnolia featuring significant improvements to the author and developer experience. For a successful upgrade, please consult our Magnolia 6.2 documentation. If you need help, please contact info@magnolia-cms.com.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

This page describes how to enable data privacy features offered by Magnolia with your third-party marketing automation system.

Magnolia provides a sample implementation showing how you can collect leads (such as email addresses) on a web form, ask for consent, and push those leads to IBM Watson.

The example on this page makes use of the Privacy moduleIBM Marketing cloud connector and External Forms IBM modules.

Note that External Forms is an EE std module and is not bundled. You should only use:

  • magnolia-external-forms – provides functionality to render external forms as Magnolia forms.
  • magnolia-external-forms-ibmprovides a sample implementation for the IBM Watson Campaign Automation tool.

Do not include the Infusionsoft and Eloqua submodules.


In the sample implementation, the magnolia-external-forms-ibm module (sub module of External Forms) provides a page called watsonFormSample (and a followup confrmation page) in the Pages app.

This page contains a simple email field form linked to IBM Watson. The form is processed using an out-of-the-box processor called XXX

The visitor consent tracking mechanism is provided using the default implementation of the magnolia‐privacy‐visitor‐manager module (sub module of Privacy module). A dedicated visitor references searcher called info.magnolia.extforms.consent.WatsonReferencesSearcher processes GDPR-sensitive data from the forms.

Magnolia provides a sample for IBM Watson Campaign Automation but you can connect to any external form provider by writing custom forms, custom form processors in Javascript/Nashorn and your own implementation of the VisitorManager.

DIAGRAM


Configuring the sample 

To enable the sample with your implementation of IMB Watson follow the steps in the sections below.

Connect to the external database

  1. If you do not already have one, create a Single Opt-In database in your Watson Campaign Automation account. Make sure that Email is one of the fields in your database. 
  2. Once created, open the additional details and copy the Database ID.
  3. In Magnolia, open the configuration of the magnolia-privacy-visitor-manager module: Configuration app >/modules/visitor-manager/config/visitorReferencesSearchers/watson/databasesIds
  4. Add a property node under databaseIds with the Database ID you copied previously as the value.
    The name of the property node is unimportant. You can add as many database ids as required. 
  5. In Magnolia, open the configuration of the magnolia-external-forms-ibm module: Configuration app >/modules/external-forms-ibm/config
  6. Add your IBM Watson credentials for the three property nodes:
    • clientId
    • clientSecret
    • refreshToken

XXXWhere would a customer get these credentials?

Create an external web form with a GDPR-aware email field

If you already have an IBM Watson Marketing Automation web form with an Email field, connect to it directly in the watsonFormSample page External Form component. XXX

The External Form component in the watsonFormSample page is preconfigured to:

  • Fetch data from IBM Watson once the site URL is provided.
  • Ask for visitor consent before submitting the form by displaying consent checkboxes.
  • Send the visitor an opt-in email. The XXX Opt-in Email tab configures the parts of the email which are sent to the user in the second phase of the opt-in procedure.


  1. In your IBM Watson Automation Campaign database, create a new standard web form.
  2. Keep the default fields in the new form and follow the instructions in the IBM wizard. 
  3. Publish the form.
  4. On the Publish Confirmation page, click Publish Site.
  5. In the Site Settings, copy the site URL. For example: http://www.pages03.net/trial-magnoliainternational/<sitename>/Form
  6. In Magnolia, go to the Pages app and open the watsonFormSample page: http://localhost:8080/magnoliaAuthor/.magnolia/admincentral#app:pages:detail;/watsonFormSample:edit
  7. Edit the External Form sample component to add the URL of the site you just published.

    The External Form component can now fetch data from IBM Watson Automation Campaign.

If you encounter problems, try refreshing the configuration of the magnolia-external-forms-ibm module. To do so, open a property in Configuration app >/modules/external-forms-ibm/config and close it again. This restarts the module.

Test the form and view consent in Magnolia and IBM Watson Campaign Automation

If you want to test this process yourself, you must configure your Mail settings in Magnolia first

Preview the watsonFormSample page. When a visitor submits their email address in the form, they are asked to give consent for their personal data to be processed.

Once they have checked the box, their email address appears in the Visitors app. However, no consent is recorded until the double opt-in process is complete. To complete the double opt-in process, in this sample the visitor must follow a link contained in an email that is sent to them and click Proceed to confirm their consent. 


Screen

Once the visitor confirms their consent you can see a record of it in the Visitors app:

Screen

In the Visitors app, click View dependencies to see the link to external sources, in this example IBM Watson Campaign Automation. The clickable link takes you to your Watson dashboard (contacts list), where you can see the an entry for the visitor along with the consent recorded.

Screen


Other gdpr features also interact with external source: send all data (export from JCR but also JSON from watson), forget me, delete all my data (request sent to watson). 


See GDPR and Forms for details about: configuring email options, consent duration








  1. On the Opt-in Email tab configure the parts of the email which will be sent to the user in the second phase of the opt-in procedure:

    The largest text area in the dialog is where you can define with FreeMarker variables how the main message of the confirmation email will look like. The body of this email message should contain hyperlinks to a consent confirmation/rejection page. The Travel Demo comes with a sample of such a page at /travel/contact/confirmation
  2. Copy and paste this path to the Confirmation page field of the dialog and save the changes.
  • No labels