tryton-modules-marketing-automation 6.0.4-1 source package in Ubuntu
Changelog
tryton-modules-marketing-automation (6.0.4-1) unstable; urgency=medium * Merging upstream version 6.0.4. * Updating copyright file. -- Mathias Behrle <email address hidden> Tue, 27 Jun 2023 14:21:25 +0200
Upload details
- Uploaded by:
- Debian Tryton Maintainers
- Uploaded to:
- Sid
- Original maintainer:
- Debian Tryton Maintainers
- Architectures:
- all
- Section:
- misc
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Oracular | release | universe | misc | |
Noble | release | universe | misc | |
Mantic | release | universe | misc |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
tryton-modules-marketing-automation_6.0.4-1.dsc | 2.7 KiB | abb707fa8da808988ec30da0ab9d6ec383da6a93e6059a474439407a6c86cb0f |
tryton-modules-marketing-automation_6.0.4.orig.tar.gz | 43.8 KiB | 32acc932d6fa047aada7f8c03ebc73ede684bb79a434e9dac882b93ccff32ddb |
tryton-modules-marketing-automation_6.0.4.orig.tar.gz.asc | 506 bytes | a9f1a4be7b9f2bb975f6e9f91efb78c59d2f5dbf461d332bbc1fcc708b8d5751 |
tryton-modules-marketing-automation_6.0.4-1.debian.tar.xz | 12.3 KiB | 4c136daa8a5c9cf1894c4a1183ff8667706bfc7ffeb4131b1db455aee7ac1a1e |
Available diffs
- diff from 6.0.3-3 to 6.0.4-1 (4.1 KiB)
No changes file available.
Binary packages built by this source
- tryton-modules-marketing-automation: 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`.