Mercury Dokumentation

Google calendar

Integrates the external Google Calendar into a page with various options, e.g. to customise the appearance.

XSD documentation
Google calendar
Description of all editor fields

Part of the Mercury expansion pack

This feature is not included in the open source version of the Mercury template, but is part of the Mercury extension pack from Alkacon Software. Please contact us if you are interested in our Mercury extensions.
Further information

This element sets cookies in the “External content” group.

This element uses JavaScript from external servers.

The execution of Google Calendar is controlled by the cookie banner. Google Calendar will therefore NOT be displayed if the web user has not consented to external cookies.

Cookies are set when the Google Calendar is loaded. It can be assumed that these include tracking functions for the web user.

External JavaScript files are loaded from Google's servers for this element. These are executed in the context of the page. In theory, this enables extensive tracking of the web user's activities on the displayed page. The extent to which the external JavaScript is actually used for tracking is not known.

When a page with a Google Calendar is initially loaded, a preview image or text preview can optionally be displayed first. When the page is loaded, no data is initially transferred to Google's servers. Only when the web user clicks on the preview is the external code activated in this case.

Integrating a Google Calendar may be relevant in terms of data protection law. Google Calendar sets its own cookies. These are blocked by the cookie banner if the user has rejected external cookies. Google Calendar should only be used if all data protection questions have been clarified.

Click here to view the Google calendar
Click here to view the Google calendar
When clicked, code is loaded directly from Google's servers. This may be relevant for your data protection.

This element offers the option of only being executed after the user clicks on it. As long as the user has not clicked, a preview is displayed, which can be customized. This allows the user to be informed in advance about data protection aspects of the usage of external code, for example.