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-6.6.0.tar.gz (48.4 kB view details)

Uploaded Source

Built Distribution

File details

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

File metadata

File hashes

Hashes for trytond_marketing_automation-6.6.0.tar.gz
Algorithm Hash digest
SHA256 a596fb47843938cd7313724f976465f07152f60e98d72088c3ecc25428575cb9
MD5 0d5d369780fc9ed1f236ebc3852b2779
BLAKE2b-256 1a70b0876a7ad492619fbc14bac6267593b8a1c07b03cad1d75de57262659d36

See more details on using hashes here.

File details

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

File metadata

File hashes

Hashes for trytond_marketing_automation-6.6.0-py3-none-any.whl
Algorithm Hash digest
SHA256 b2ba06220db89bddcfa56e46cfd7ed821aec6c70afec82400c80751074fb6b36
MD5 e1f53b888643c5db456f2ed22ff4ddac
BLAKE2b-256 284fddce299abee0822f4af019f366859309b46d628f9a08a76364167e24a615

See more details on using hashes here.

Supported by

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