Skip to main content

Tryton module to plan, coordinate and manage marketing campaigns

Project description

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 scenario is defined by:

  • Name

  • Model: the type of record for the scenario (by default Party and Sale)

  • Domain: used to filter records

  • State:

    • Draft

    • Running

    • Stopped

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 and defined by:

  • Name

  • Parent

  • Children

  • On: event from the parent that triggers the activity:

    • E-Mail Opened

    • E-Mail Not Opened

    • E-Mail Clicked

    • E-Mail Not Clicked

  • Condition: that the record must match to execute the activity

  • Delay: before the action is executed

  • Action: list of available actions

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 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.

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

trytond_marketing_automation-7.0.4.tar.gz (50.4 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

trytond_marketing_automation-7.0.4-py3-none-any.whl (94.7 kB view details)

Uploaded Python 3

File details

Details for the file trytond_marketing_automation-7.0.4.tar.gz.

File metadata

File hashes

Hashes for trytond_marketing_automation-7.0.4.tar.gz
Algorithm Hash digest
SHA256 bf66883374a1f67d3a08da2ab0907914a997dfc8d3f781a7ba0e4a57c631a530
MD5 9aea0f3ededb0ba9aea82eec5cdb2fc0
BLAKE2b-256 ebf23833e545a120dec76f7a7f08be59819c2efb6e9381f7ed5d841e540d7baa

See more details on using hashes here.

File details

Details for the file trytond_marketing_automation-7.0.4-py3-none-any.whl.

File metadata

File hashes

Hashes for trytond_marketing_automation-7.0.4-py3-none-any.whl
Algorithm Hash digest
SHA256 dbcf13c652d457a426a1de6f3efe80ae63e2fb1becebb18245a2681493611e4c
MD5 433b8d58407efc2b733a5dbc1e7f0a3b
BLAKE2b-256 023a4439b1b17c84b6e44d692567d55a47c813590aa59505927e77f65cdfdc39

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page