diff --git a/_static/banners/marketing_automation.png b/_static/banners/marketing_automation.png new file mode 100644 index 000000000..7bd5d1f92 Binary files /dev/null and b/_static/banners/marketing_automation.png differ diff --git a/applications.rst b/applications.rst index 4390e9cf0..8543d52bb 100644 --- a/applications.rst +++ b/applications.rst @@ -24,6 +24,8 @@ Applications mobile/firebase social_marketing sms_marketing + marketing_automation fsm planning general + diff --git a/marketing_automation.rst b/marketing_automation.rst new file mode 100644 index 000000000..f977b9d4a --- /dev/null +++ b/marketing_automation.rst @@ -0,0 +1,11 @@ +:banner: banners/marketing_automation.png + +==================== +Marketing Automation +==================== + +.. toctree:: + :titlesonly: + + marketing_automation/overview + marketing_automation/advanced diff --git a/marketing_automation/advanced.rst b/marketing_automation/advanced.rst new file mode 100644 index 000000000..dc3804c22 --- /dev/null +++ b/marketing_automation/advanced.rst @@ -0,0 +1,8 @@ +======== +Advanced +======== + +.. toctree:: + :titlesonly: + + advanced/understanding_metrics \ No newline at end of file diff --git a/marketing_automation/advanced/media/metrics1.png b/marketing_automation/advanced/media/metrics1.png new file mode 100644 index 000000000..e1dbb6978 Binary files /dev/null and b/marketing_automation/advanced/media/metrics1.png differ diff --git a/marketing_automation/advanced/media/metrics2.png b/marketing_automation/advanced/media/metrics2.png new file mode 100644 index 000000000..1bb2e96e0 Binary files /dev/null and b/marketing_automation/advanced/media/metrics2.png differ diff --git a/marketing_automation/advanced/media/metrics3.png b/marketing_automation/advanced/media/metrics3.png new file mode 100644 index 000000000..5946a34a8 Binary files /dev/null and b/marketing_automation/advanced/media/metrics3.png differ diff --git a/marketing_automation/advanced/media/metrics4.png b/marketing_automation/advanced/media/metrics4.png new file mode 100644 index 000000000..cd7c38e89 Binary files /dev/null and b/marketing_automation/advanced/media/metrics4.png differ diff --git a/marketing_automation/advanced/media/metrics5.png b/marketing_automation/advanced/media/metrics5.png new file mode 100644 index 000000000..ee91bd8c5 Binary files /dev/null and b/marketing_automation/advanced/media/metrics5.png differ diff --git a/marketing_automation/advanced/understanding_metrics.rst b/marketing_automation/advanced/understanding_metrics.rst new file mode 100644 index 000000000..b6531e68d --- /dev/null +++ b/marketing_automation/advanced/understanding_metrics.rst @@ -0,0 +1,81 @@ +===================== +Understanding Metrics +===================== +Metrics are values that help you measure progress and can be a powerful way of linking your +employees to goals. + + +| When you create a workflow in Odoo, its visual content already shows metrics in a graph form and + in numbers. +| Let’s consider the example below: + + +.. image:: media/metrics1.png + :align: center + :alt: Metrics in Odoo Marketing Automation + + +| The *Target* - business object - is *Lead/Opportunity* and was narrowed down to the ones whose + *Tag Name* contain the description “Product”, and have an email address set. +| A total number of 20 records match the criteria. + + +.. image:: media/metrics2.png + :align: center + :alt: Metrics in Odoo Marketing Automation + + +Out of those 20 records, 25 have become participants, in other words, they have matched the criteria. + + +.. image:: media/metrics3.png + :align: center + :alt: Metrics in Odoo Marketing Automation + + +Every time the system runs, updating numbers and triggering actions, it will look at the *Target* +model and check if new records have been added or modified, keeping the flow up-to-date. + + +.. note:: + The filter here is applied to *all* activities. Leads that lose the tag in the meantime will be + excluded from later activities. + + +*Records* is a real-time number, therefore while the workflow is running, changes in opportunity +records can be made - delete, add, adjustment - updating the number of records, but not changing the +number of participants, as the metric *will not* exclude opportunities that have been set as +participants before. It will just add new ones. For this reason, the number of *Records* can be +different from the number of *Participants*. + + +.. tip:: + | You can also have filters applied to activities individually, under *Domain*. A useful feature + to specify an individual filter that will only be performed if the records satisfied both + filters, the activity and its domain one. + | Example: for an activity sending an SMS, you could make sure people a phone number is set to + avoid triggering a SMS that would never be sent and crash. + + .. image:: media/metrics4.png + :align: center + :alt: Metrics in Odoo Marketing Automation + +| *Success* is the number of times the searching for participants - that match the filter(s) of that + activity - was performed successfully in relation to the total number of participants. +| If a participant does not match the conditions, it will be added to *Rejected*. + +.. image:: media/metrics5.png + :align: center + :alt: Metrics in Odoo Marketing Automation + +Hovering over the graph, you can see the number of successful and rejected participants, per day, +for the last 15 days. + +.. note:: + Every time a new record is added to the *Target* model, it will be automatically added to the + workflow, and, it will start the workflow from the beginning (parent action). + +.. seealso:: + - :doc:`../overview/automate_actions` + - :doc:`../overview/segment` + - :doc:`../overview/test` diff --git a/marketing_automation/overview.rst b/marketing_automation/overview.rst new file mode 100644 index 000000000..66cb772a4 --- /dev/null +++ b/marketing_automation/overview.rst @@ -0,0 +1,10 @@ +======== +Overview +======== + +.. toctree:: + :titlesonly: + + overview/automate_actions + overview/segment + overview/test \ No newline at end of file diff --git a/marketing_automation/overview/automate_actions.rst b/marketing_automation/overview/automate_actions.rst new file mode 100644 index 000000000..d27374c36 --- /dev/null +++ b/marketing_automation/overview/automate_actions.rst @@ -0,0 +1,59 @@ +====================================== +Automate Actions and Create a Workflow +====================================== +Automated workflows are a sign that you are building intelligent, data-driven, multifaceted +campaigns to enable the delivery of the right message, to the right prospects, at the right time. +It also speeds up processes and creates a seamless experience for employees. + +Segment and create a campaign +============================= +Go to :menuselection:`Campaigns --> Create`. + +| In the example below, the *Marketing Automation* application is fully integrated with *Contacts*. +| But it can also be integrated with other apps like CRM, as long as they are installed in your + database. + + +.. image:: media/auto1.png + :align: center + :alt: Create workflows in Odoo Marketing Automation + + +| Depending on the criteria, the *target model updates itself* while the campaign is running. That + means that every new record that meets the criteria will be added to the workflow. +| Example: a campaign starts for leads that have no salesman assigned. If at some point, those leads + get to have a salesman assigned to it, the campaign will stop running. + + +Create a parent activity and start to build a workflow +====================================================== +Click on *Add new activity*. + + +.. image:: media/auto2.png + :align: center + :alt: Create workflows in Odoo Marketing Automation + +*Trigger* is the field to set for the activity to start to de deployed. + +Adopt an *Expiry Duration* if you would like to stop actions from being executed after a certain +amount of time and in subsequence to the trigger. + +Under *Domain* you can narrow down your target, even more, applying filters for this specific +activity. + + +Add Child Activities +-------------------- +| A *child activity* is an action that will take place based on a condition. +| You can either create or add a child activity if on the previous one: the email was opened or not, + the email was replied or not, the link was clicked or not, the email bounced back. + + +.. image:: media/auto3.png + :align: center + :height: 350 + :alt: Create workflows in Odoo Marketing Automation + +.. seealso:: + - :doc:`segment` \ No newline at end of file diff --git a/marketing_automation/overview/media/auto1.png b/marketing_automation/overview/media/auto1.png new file mode 100644 index 000000000..67b2ea3f4 Binary files /dev/null and b/marketing_automation/overview/media/auto1.png differ diff --git a/marketing_automation/overview/media/auto2.png b/marketing_automation/overview/media/auto2.png new file mode 100644 index 000000000..8cd6405a8 Binary files /dev/null and b/marketing_automation/overview/media/auto2.png differ diff --git a/marketing_automation/overview/media/auto3.png b/marketing_automation/overview/media/auto3.png new file mode 100644 index 000000000..2f73ebf08 Binary files /dev/null and b/marketing_automation/overview/media/auto3.png differ diff --git a/marketing_automation/overview/media/filters1.png b/marketing_automation/overview/media/filters1.png new file mode 100644 index 000000000..de928b029 Binary files /dev/null and b/marketing_automation/overview/media/filters1.png differ diff --git a/marketing_automation/overview/media/filters2.png b/marketing_automation/overview/media/filters2.png new file mode 100644 index 000000000..3f40fb98f Binary files /dev/null and b/marketing_automation/overview/media/filters2.png differ diff --git a/marketing_automation/overview/media/filters3.png b/marketing_automation/overview/media/filters3.png new file mode 100644 index 000000000..7039729ca Binary files /dev/null and b/marketing_automation/overview/media/filters3.png differ diff --git a/marketing_automation/overview/media/filters4.png b/marketing_automation/overview/media/filters4.png new file mode 100644 index 000000000..ca8e6f897 Binary files /dev/null and b/marketing_automation/overview/media/filters4.png differ diff --git a/marketing_automation/overview/media/filters5.png b/marketing_automation/overview/media/filters5.png new file mode 100644 index 000000000..722386bb6 Binary files /dev/null and b/marketing_automation/overview/media/filters5.png differ diff --git a/marketing_automation/overview/media/filters6.png b/marketing_automation/overview/media/filters6.png new file mode 100644 index 000000000..aaaf7e718 Binary files /dev/null and b/marketing_automation/overview/media/filters6.png differ diff --git a/marketing_automation/overview/media/filters7.png b/marketing_automation/overview/media/filters7.png new file mode 100644 index 000000000..656fcb41b Binary files /dev/null and b/marketing_automation/overview/media/filters7.png differ diff --git a/marketing_automation/overview/media/filters8.png b/marketing_automation/overview/media/filters8.png new file mode 100644 index 000000000..a9581c1d3 Binary files /dev/null and b/marketing_automation/overview/media/filters8.png differ diff --git a/marketing_automation/overview/media/test1.png b/marketing_automation/overview/media/test1.png new file mode 100644 index 000000000..0373f9bef Binary files /dev/null and b/marketing_automation/overview/media/test1.png differ diff --git a/marketing_automation/overview/media/test2.png b/marketing_automation/overview/media/test2.png new file mode 100644 index 000000000..0979ca51c Binary files /dev/null and b/marketing_automation/overview/media/test2.png differ diff --git a/marketing_automation/overview/media/test3.png b/marketing_automation/overview/media/test3.png new file mode 100644 index 000000000..f730398e7 Binary files /dev/null and b/marketing_automation/overview/media/test3.png differ diff --git a/marketing_automation/overview/segment.rst b/marketing_automation/overview/segment.rst new file mode 100644 index 000000000..d6060f58e --- /dev/null +++ b/marketing_automation/overview/segment.rst @@ -0,0 +1,66 @@ +================================= +Segment the Database with Filters +================================= +Filters let you reach a granular level of detail in your records. + +How to work with filters +======================== +When working with filters, you will see that some of the rules have an arrow button next to it, +informing you that the parameter has more variables within it. + + +.. image:: media/filters1.png + :align: center + :height: 350 + :alt: Filters in Odoo Marketing Automation + + +| More than one parameter line - *node* (+) - can be added under what is called a *branch* (...). +| To exclude a *node* or a *branch*, click on *Delete node* (x). + + +.. image:: media/filters2.png + :align: center + :alt: Filters in Odoo Marketing Automation + + +Every time a new branch is created, you can choose if you would like the records to match *all* +criteria of the upcoming rules, or *any*, meaning one rule or the other. + + +Use cases +========= + +- **Scenario**: narrow the target down to new opportunities in the pipeline. + + .. image:: media/filters3.png + :alt: Filters in Odoo Marketing Automation + +- **Scenario**: narrow the target down to suppliers. + + .. image:: media/filters4.png + :alt: Filters in Odoo Marketing Automation + +- **Scenario**: narrow the leads down to the ones that contain a certain tag name. + + .. image:: media/filters5.png + :alt: Filters in Odoo Marketing Automation + +- **Scenario**: narrow the target down to the attendees of a specific event that purchase a specific + category of ticket. + + .. image:: media/filters6.png + :alt: Filters in Odoo Marketing Automation + +- **Scenario**: narrow the target down to the employees who have kids. + + .. image:: media/filters7.png + :alt: Filters in Odoo Marketing Automation + +- **Scenario**: narrow the target down to records with a helpdesk ticket solved. + + .. image:: media/filters8.png + :alt: Filters in Odoo Marketing Automation + +.. seealso:: + - :doc:`automate_actions` \ No newline at end of file diff --git a/marketing_automation/overview/test.rst b/marketing_automation/overview/test.rst new file mode 100644 index 000000000..8bf5efaa5 --- /dev/null +++ b/marketing_automation/overview/test.rst @@ -0,0 +1,53 @@ +================================== +Launch a Test and Start a Campaign +================================== +Before starting a campaign, launching a test allows you to run the workflow on a test contact and +view the sequence of events in action, avoiding mistakes. + +Launch a test +============= +| Click on *Launch a test*. +| Once you have selected the test contact, *Run* the parent activity and the subsequent ones as + needed. + *Run* and *Stop* activities individually. To stop the whole workflow click on *Stop*. + + +.. image:: media/test1.png + :align: center + :height: 350 + :alt: Create workflows in Odoo Marketing Automation + + +.. note:: + Launching a test does not add data to your metrics with the purpose of not introducing wrong + inputs to reports. + + +Start and stop a workflow +========================= +Click on *Start* to run the workflow, and on *Stop* to interrupt it. The interruption and new start +can happen at any moment. The current status will be shown on the status bar. + + +.. image:: media/test2.png + :align: center + :alt: Create workflows in Odoo Marketing Automation + + +Participants and their specific workflow +======================================== +*Participants* are all the records that have ever been involved in the campaign. + + +.. image:: media/test3.png + :align: center + :alt: Create workflows in Odoo Marketing Automation + + +If you click on *Participants* and open a record, you will find the specific activities the record +went/are/will go through, as well as when the workflow was triggered to him. If you wish to cancel +an activity click on *Cancel*. + +.. seealso:: + - :doc:`automate_actions` + - :doc:`segment` \ No newline at end of file