Package: tryton-modules-marketing-automation
Version: 7.0.4-1
Architecture: all
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Tryton Maintainers <team+tryton-team@tracker.debian.org>
Installed-Size: 347
Depends: python3-genshi, tryton-modules-party (>= 7.0), tryton-modules-marketing (>= 7.0), tryton-modules-web-shortener (>= 7.0), tryton-server (>= 7.0), tryton-server-api-7.0, python3:any, libjs-sphinxdoc (>= 9.0)
Section: python
Priority: optional
Homepage: https://www.tryton.org/
Description: Tryton application platform - marketing automation module
 Tryton is a high-level general purpose application platform. It is the base
 of a complete business solution as well as a comprehensive health and hospital
 information system (GNUHealth).
 .
 The marketing_automation module allows marketing actions to be automated. It is
 based on scenarios and activities that are executed on selected records.
 .
 Scenario
 ********
 .
 A scenario provides the entry point for records into an automated marketing
 campaign. Each record can only enter a scenario once.
 .
 A cron task runs periodically to find new records to apply the scenario to.
 .
 Activity
 ********
 .
 The activities form a scenario. They define which action should be triggered
 and when it should happen. The activities are organized as a tree.
 .
 Actions
 *******
 .
 Send E-Mail
 .
 The activity send an e-mail to the party defined on the record.
 The E-mail is composed using an HTML `Genshi <https://genshi.edgewall.org/>`_
 template with `record` in the evaluation context.
 All `<a>` elements have their `href` replaced by a shortened version used to
 trigger children activities. If the `href` value is `unsubscribe`, it is
 replaced by the URL which allows the recipient to block their record for the
 scenario.
 A empty image is automatically added at the end of the `<body>` to track when
 emails are opened.
 .
 Record
 ******
 .
 It stores a reference to the records included in each scenario. If the record
 is blocked, no activity will be triggered for the record.
 .
 Record Activity
 ***************
 .
 It stores the state of a record for an activity of the scenario.
 .
 A cron task runs periodically to execute any waiting record activity that is
 due.
 .
 Configuration
 *************
 .
 The marketing_automation module uses parameters from the section:
 .
 [marketing]:
  - `email_from`: The default `From` for the email.
  - `automation_base`: The base URL without a path for the unsubscribe URL
     and the empty image.
     The default value is created using the configuration `[web]` `hostname`.
