Website automations

The website runs two scheduled jobs and has no e-mail template of its own. The rest of what it does by itself happens when someone visits a page, opens a reporting menu or saves an option. The options are explained in Website settings.

The jobs are active once the app is installed, and off on a test copy of the database. An administrator stops or starts them in the scheduled actions of the technical menu (Developer mode and the technical menus).

Scheduled jobs

Disable unused snippets assets

• When: once a week.
• What it does: reads the content of the pages, posts and other texts of the database, switches off the style and script files of the blocks that nothing uses any more, and switches them back on for a block that is used again. Pages load fewer files; nothing on them changes.
• How to stop it: stop the job. The files of unused blocks then keep loading with every page.

Website Visitor: clean inactive visitors

• When: once a day.
• What it does: deletes, with their page views, the visitors who have not come back for 60 days and are not linked to a contact. Visitors who signed in are kept. The 60 days come from the system parameter website.visitor.live.days.
• How to stop it: stop the job. The lists under Reporting then keep every anonymous visitor.

Actions behind the reporting menus

Website: Analytics

• When: each time someone opens Website/Reporting/Analytics.
• What it does: opens the analytics screen of the website: the figures of the analytics account connected in Website settings, or a sample picture with a link to connect one. A button per website switches between them.
• How to stop it: nothing runs until the menu is opened.

Website: Dashboard

• When: from the eCommerce entry of Reporting, which this version keeps switched off.
• What it does: opens the same analytics screen, for administrators and the Editor and Designer access right; anyone else gets an access error.
• How to stop it: nothing runs while the entry is hidden.

On a visit

Visitor tracking

• When: a person, not a robot, opens a tracked page.
• What it does: creates or updates the visitor of that browser and records a page view; when the person signs in, links the visitor to their contact. How the website works explains what is kept.
• How to stop it: in the Pages list (Manage pages) show the hidden Track column from the column options at the end of the header, tick the page and clear it.

On a save

Cookie policy page

• When: Cookies Bar is saved on or off for a website.
• What it does: creates a published, not indexed cookie policy page at /cookie-policy, or deletes it.
• How to stop it: leave Cookies Bar off.

A new website

• When: a website is created.
• What it does: gives it an empty home page and a copy of the main menu; from the second website on, turns on the options that several websites need, such as the website switcher.
• How to stop it: nothing to stop; it happens once per website.