msgid "The Odoo *Email Marketing* app provides drag-and-drop design tools, pre-built templates, and other interactive features to create engaging email campaigns. The *Email Marketing* app also provides detailed reporting metrics to track the campaigns' overall effectiveness."
msgid "After installing the application, click the :menuselection:`Email Marketing` app icon from the main Odoo dashboard. Doing so reveals the main :guilabel:`Mailings` dashboard in the default list view."
msgid "In the search bar, the default filter of :guilabel:`My Mailings` is present to show all the mailings related to the current user. To remove that filter, click the :guilabel:`✖️ (remove)` icon next to the filter in the search bar. Doing so reveals all the mailings in the database."
msgid "The list view, represented by the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner, is the default view of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "While in list view, there are columns dedicated to different aspects of information related to the listed emails. Those columns are as follows:"
msgid "To add or remove columns, click the :guilabel:`Additional Options (two horizontal lines with dots)` icon, located to the far-right of the column titles in list view. Doing so reveals a drop-down menu of additional column options."
msgid "The Kanban view, represented by the :guilabel:`(inverted bar graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "In each stage, there are drag-and-drop cards representing the emails that have been created/sent, and the stage they are in represents the current status of that mailing."
msgid "When the cursor hovers over the upper-right corner of an email campaign card, a :guilabel:`⋮ (three vertical dots)` icon appears. When clicked, a mini drop-down menu reveals the option to color-code the email, :guilabel:`Delete` the email, or :guilabel:`Archive` the message for potential future use."
msgid "The calendar view, represented by a :guilabel:`📆 (calendar)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "To the right of the calendar, the options to filter the results by :guilabel:`Responsible` and/or :guilabel:`Status` are available, via checkboxes."
msgid "In the top-left corner, above the calendar, the option to change the time period being displayed is available via a drop-down menu, which shows :guilabel:`Month`, by default. When clicked, the drop-down menu that appears reveals the options: :guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month` (default), :guilabel:`Year`, and :guilabel:`Show weekends` (selected by default)."
msgid "Clicking either :guilabel:`⬅️ (left arrow)` icon or :guilabel:`➡️ (right arrow)` icon changes the calendar to a previous or future time, depending on what is clicked, based on the chosen amount of time being represented."
msgid "The graph view, represented by a :guilabel:`(line graph)` icon, can be accessed in the upper-right corner of the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "While in graph view, the status of the emails on the :guilabel:`Mailings` page is represented in a bar graph, but other graph view options can be implemented, if needed."
msgid "In the upper-left corner, above the graph, there is a :guilabel:`Measures` drop-down menu. When clicked, different filter options become available to further customize the graph views."
msgid "To the right of the :guilabel:`Measures` drop-down menu is an :guilabel:`Insert in Spreadsheet` button, if the *Documents* application is installed. When clicked, a pop-up window appears, in which the ability to add the graph to a spreadsheet or dashboard becomes available."
msgid "Beside the :guilabel:`Measures` drop-down menu and :guilabel:`Insert in Spreadsheet` button are different graph view options. From left-to-right, those graph view options are: :guilabel:`(bar chart)` (default), :guilabel:`(line chart)`, and :guilabel:`(pie chart)`."
msgid "Regardless of the view chosen for the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app, the :guilabel:`Filters`, :guilabel:`Group by`, and :guilabel:`Favorites` options are always available to further customize the information being displayed."
msgid "To access those options, click the :guilabel:`(downward arrow)` icon, located to the right of the search bar. Doing so reveals a drop-down mega menu featuring those filtering and grouping options."
msgid "This section of the drop-down mega menu provides different ways to filter email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "If :guilabel:`Add Custom Filter` is selected, Odoo reveals a pop-up window, with three customizable fields to fill in, in order to create custom filter rules for Odoo to use to retrieve results that fit more specific criteria."
msgid "This section of the drop-down mega menu provides different ways to group email results being shown on the :guilabel:`Mailings` dashboard in the :guilabel:`Email Marketing` app."
msgid "There is also the option to group the data by :guilabel:`Sent Period`, which has its own sub-menu of options to choose from. The :guilabel:`Sent Period` options are :guilabel:`Year`, :guilabel:`Quarter`, :guilabel:`Month`, :guilabel:`Week`, and :guilabel:`Day`."
msgid "If none of the above :guilabel:`Group By` options deliver the desired results, click :guilabel:`Add Custom Group` at the bottom of the :guilabel:`Group By` section. Doing so reveals a drop-down menu, wherein custom criteria can be selected and applied, thus delivering any grouping of data that may be desired."
msgid "This section provides the opportunity to save custom filters and/or groupings for future use. To utilize this section, click the :guilabel:`Save current search` field, which reveals additional fields."
msgid "Ticking the box for :guilabel:`Default filter` makes this favorited filter/grouping the default option. Ticking the box for :guilabel:`Shared` allows other users to see and use this favorited filter/grouping."
msgid "When all desired options are configured, click :guilabel:`Save` to save the filter/grouping in the :guilabel:`Favorites` section of the mega drop-down menu."
msgid ":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to blacklist themselves from future mailings during the unsubscribing process."
msgid ":guilabel:`Dedicated Server`: provides the option to utilize a separate, dedicated server for mailings. When enabled, Odoo reveals a new field (and link), in which the specific server configurations must be entered, in order for it to connect properly to Odoo."
msgid "To create an email, open the :menuselection:`Email Marketing` application, and click the :guilabel:`New` button in the upper-left corner of the :guilabel:`Mailings` dashboard page."
msgid "On the email form, there are fields for the :ref:`Subject <email_marketing/subject>` and :ref:`Recipients <email_marketing/recipients>` of the email."
msgid "Beneath that, there are three tabs: :ref:`Mail Body <email_marketing/mail_body>`, :ref:`A/B Tests <email_marketing/ab_tests>`, and :ref:`Settings <email_marketing/settings_tab>`."
msgid "First, enter a :guilabel:`Subject` to the email. The :guilabel:`Subject` is visible in the recipients' inbox, allowing them to quickly see what the message is about."
msgid "The :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field represents emojis that can be added to the :guilabel:`Subject` field. Clicking that icon reveals a pop-up menu of emojis that can be used."
msgid "Beside the :guilabel:`(smiley face with a plus sign)` icon at the end of the :guilabel:`Subject` field is an empty :guilabel:`(star)` icon. When clicked, the :guilabel:`(star)` icon turns gold, and the email is saved as a template in the :guilabel:`Mail Body` tab, which can be used again in the future."
msgid "Beneath the :guilabel:`Subject` field on the email form is the :guilabel:`Recipients` field. In this field, select the recipients of the email. By default, the :guilabel:`Mailing List` option is selected, but clicking the field reveals a drop-down menu of other recipient options."
msgid "With the default :guilabel:`Mailing List` option selected, a specific mailing list **must** be chosen from the adjacent :guilabel:`Select mailing lists` field drop-down menu."
msgid "When the :guilabel:`Recipients` field is clicked, a drop-down menu of other options is revealed. Each option provides different ways Odoo can create a target audience for the email."
msgid "Those options (excluding the default :guilabel:`Mailing List`) provide the option to create a more specified recipient filter, in an equation-like format, which appears beneath the :guilabel:`Recipients` field."
msgid ":guilabel:`Event Registration`: ties specifically to the *Events* app, and provides opportunities to interact with event registrants, in order to communicate important information about the event(s), or nurture other valuable actions, such as post-event surveys, purchases, etc."
msgid ":guilabel:`Lead/Opportunity`: ties specifically to records in the *CRM* application, which opens up a number of opportunities to influence sales or purchase decisions."
msgid ":guilabel:`Mailing Contact`: ties specifically to the *Email Marketing* app, and focuses on specific mailing contacts that have been entered in that specific application, and are related to a specific mailing list. These contacts are also unique because they do *not* have their own contact card in the *Contacts* application. This list can be accessed by navigating to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing List Contacts`."
msgid "To add a more specific recipient filter to any :guilabel:`Recipient` option, select any recipient option (other than :guilabel:`Mailing List`), and click the :guilabel:`Modify filter (right-facing arrow)` icon beneath the :guilabel:`Recipient` field to reveal three subsequent filter rule fields, formatted like an equation."
msgid "It is highly recommended that users implement detailed targeting criteria for the :guilabel:`Recipients` field. Typically, a single line of targeting logic is not sufficient enough for an email campaign."
msgid "While the :guilabel:`Mailing List` option is adequate for the :guilabel:`Recipients` field, the :guilabel:`Lead/Opportunity` and :guilabel:`Event Registration` options provide far more detailed targeting criteria, which can be added on top of those seed sources."
msgid "For example, with the :guilabel:`Lead/Opportunity` option chosen in the :guilabel:`Recipients` field, users can add various custom criteria related to :guilabel:`Created on` dates, :guilabel:`Stages`, :guilabel:`Tags`, :guilabel:`Lost Reasons`, :guilabel:`Sales Teams`, :guilabel:`Active` statuses, :guilabel:`Country`, and so much more."
msgid "To reveal the sub-menu options within the filter rule fields, click each field, and make the desired selections, until the preferred configuration has been achieved."
msgid "The number of :guilabel:`records` in the database that match the configured rule(s) are indicated beneath the configured filter rule(s), in green."
msgid "To the right of each rule, there are three additional options, represented by :guilabel:`➕ (plus sign)`, :guilabel:`(sitemap)`, and :guilabel:`🗑️ (trash)` icons."
msgid "The :guilabel:`(sitemap)` icon adds a branch to the node. A branch contains two additional, indented sub-nodes that are related to that specific rule, providing even more specificity to the parent line above it."
msgid "Select the desired template, and proceed to modify every element of its design details with Odoo's drag-and-drop building blocks, which appear on the right sidebar when a template is chosen."
msgid "The features on the sidebar used to create and customize emails are separated into three sections: :guilabel:`Blocks`, :guilabel:`Customize`, and :guilabel:`Design`."
msgid "Each building block provides unique features and professional design elements. To use a building block, drag-and-drop the desired block element onto the body of the email being built. Once dropped, various aspects of the building block can be customized."
msgid "To build an email from the ground up, without any building block elements, select the :guilabel:`Plain Text` template. When selected, Odoo provides a completely blank email canvas, which can be customized in a number of way using the front-end rich text editor that accepts forward slash `/` commands."
msgid "When `/` is typed into the blank body of the email, while using a :guilabel:`Plain Text` template, a drop-down menu of various design elements appears, which can be used to create the desired email design."
msgid "Initially, when the :guilabel:`A/B Tests` tab is opened on an email form, the only option available is :guilabel:`Allow A/B Testing`. This is **not** a required option."
msgid "This allows the user to send different versions of the same mailing to randomly selected recipients to gauge the effectiveness of various designs, formats, layouts, content, and so on -- without any duplicate messages being sent."
msgid "When the checkbox beside :guilabel:`Allow A/B Testing` is ticked, an :guilabel:`on (%)` field appears, in which the user determines the percentage of the pre-configured recipients that are going to be sent this current version of the mailing as part of the test."
msgid "The :guilabel:`Winner Selection` field provides a drop-down menu of options, wherein the user decides what criteria should be used to determine the \"winning\" version of the email tests that are sent."
msgid ":guilabel:`Manual`: allows the user to determine the \"winning\" version of the mailing. This option removes the :guilabel:`Send Final On` field."
msgid "The :guilabel:`Send Final On` field allows users to choose a date that is used to know *when* Odoo should determine the \"winning\" email, and subsequently, send that version of the email to the remaining recipients."
msgid "To the right of those fields is a :guilabel:`Create an Alternative Version` button. When clicked, Odoo presents a new :guilabel:`Mail Body` tab for the user to create an alternate version of the email to test."
msgid "The options present in the :guilabel:`Settings` tab of the mail form are divided into two sections: :guilabel:`Email Content` and :guilabel:`Tracking`."
msgid "The options available in the :guilabel:`Settings` tab vary depending on if the *Mailing Campaigns* feature is activated in :menuselection:`Email Marketing --> Configuration --> Settings`. See :ref:`email_marketing/mailing-campaigns` for more information."
msgid "Without the *Mailing Campaigns* feature activated, the :guilabel:`Settings` tab on the email form only contains the :guilabel:`Preview Text`, :guilabel:`Send From`, :guilabel:`Reply To`, :guilabel:`Attachments`, and :guilabel:`Responsible` fields."
msgid ":guilabel:`Preview Text`: allows the user to enter a preview sentence to encourage recipients to open the email. In most inboxes, this is displayed next to the subject. If left empty, the first characters of the email content appear, instead. The ability to add an emoji in this field is available, as well, via the :guilabel:`(smiley face with a plus sign)` icon."
msgid ":guilabel:`Attach a file`: if any specific files are required (or helpful) for this email, click the :guilabel:`Attachments` button, and upload the desired file(s) to the email."
msgid "If the *Mailing Campaign* feature *is* activated, an additional :guilabel:`Campaign` field appears in the :guilabel:`Tracking` section of the :guilabel:`Settings` tab."
msgid "If the desired campaign is not available in the initial drop-down menu, select :guilabel:`Search More` to reveal a complete list of all mailing campaigns in the database."
msgid "Or, type the name of the desired mailing campaign in the :guilabel:`Campaign` field, until Odoo reveals the desired campaign in the drop-down menu. Then, select the desired campaign."
msgid "Once the mailing is finalized, the following options can be utilized, via buttons located in the upper-left corner of the email form: :ref:`Send <email_marketing/send>`, :ref:`Schedule <email_marketing/schedule>`, and :ref:`Test <email_marketing/test>`."
msgid "When the :guilabel:`Send to all` button is clicked, Odoo sends the email to the desired recipients. Once Odoo has sent the mailing, the status changes to :guilabel:`Sent`."
msgid "From the calendar pop-up window, select the future date and time for Odoo to send this email. Then, click :guilabel:`✔️ Apply`. When a date and time are chosen, click the :guilabel:`Schedule` button, and the status of the mailing changes to :guilabel:`In Queue`."
msgid "From this pop-up window, enter the email addresses of the contacts to whom Odoo should send this test email in the :guilabel:`Recipients` field. Multiple contacts can be added in this field, if desired."
msgid "By default, there's a daily limit applied for **all emails** sent throughout **all applications**. So, if there are remaining emails to be sent after a limit has been reached, those mailings are **not** sent automatically the next day. The sending needs to be forced, by opening the email and clicking :guilabel:`Retry`."
msgid "In order to create and customize mailing campaigns, the *Mailing Campaigns* feature **must** be activated in the *Settings* page of the *Email Marketing* application. To do that, navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, tick the box beside :guilabel:`Mailing Campaigns`, and click the :guilabel:`Save` button."
msgid "When that is clicked, Odoo reveals a separate :guilabel:`Campaigns` page, displaying all the mailing campaigns in the database, and the current stage they are in, showcased in a default Kanban view."
msgid "There are two different ways to create and customize campaigns in the *Email Marketing* application, either directly from the :ref:`Campaigns page <email_marketing/campaign-page>` or through the :ref:`Settings tab <email_marketing/campaign-settings>` on an email form."
msgid "When the *Mailing Campaigns* feature is activated, a new *Campaigns* option appears in the header of the *Email Marketing* application. Campaigns can be created directly on the *Campaigns* page in the *Email Marketing* app."
msgid "When the :guilabel:`New` button is clicked in the default Kanban view on the :guilabel:`Campaigns` page, a Kanban card appears in the :guilabel:`New` stage."
msgid "New campaign cards can also be made by clicking the :guilabel:`➕ (plus sign)` at the top of any Kanban stage on the :guilabel:`Campaigns` page."
msgid "When the new campaign Kanban card appears, the options to enter a :guilabel:`Campaign Name`, a :guilabel:`Responsible`, and :guilabel:`Tags` become readily available."
msgid "A :guilabel:`Campaign Name` **must** be entered in the Kanban card, in order for the :guilabel:`Edit` button to reveal the campaign form for further modifications."
msgid "To enter the list view on the :guilabel:`Campaigns` page, click the :guilabel:`☰ (horizontal lines)` icon in the upper-right corner. Doing so reveals all campaign information in a list format."
msgid "To create a campaign from the :guilabel:`Campaigns` page while in list view, click the :guilabel:`New` button. Doing so reveals a blank campaign form."
msgid "At the top of the form, various metric-related smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`."
msgid "On the campaign form (after clicking :guilabel:`Edit` from the Kanban card, or selecting an existing campaign from the :guilabel:`Campaigns` page) there are additional options and metrics available."
msgid "At the top of the form, various smart buttons can be seen that showcase specific analytics related to the campaign. Those smart buttons are: :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Opportunities`, and :guilabel:`Clicks`."
msgid "If the :guilabel:`Send Mailing` and :guilabel:`Send SMS` buttons are not readily available, enter a :guilabel:`Campaign Name`, then save (either manually or automatically). Doing so reveals those buttons."
msgid "To create a new campaign from the :guilabel:`Settings` tab of a mailing form, click the :guilabel:`Campaign` field, and start typing the name of the new campaign. Then, select either :guilabel:`Create \"[Campaign Name]\"` or :guilabel:`Create and edit...` from the drop-down menu that appears."
msgid "Select :guilabel:`Create and Edit...` to add this new mailing campaign to the database, and reveal a :guilabel:`Create Campaign` pop-up window."
msgid "Here, the new mailing campaign can be further customized. Users can adjust the :guilabel:`Campaign Name`, assign a :guilabel:`Responsible`, and add :guilabel:`Tags`."
msgid "In order to properly understand the success or failure of an email marketing campaign, it is necessary to monitor several key metrics. The insights gained from these metrics can then be used to optimize future campaigns. Odoo's **Email Marketing** application tracks several :ref:`key metrics <email-marketing/view-metrics>`, that can be interpreted through :ref:`reports <email_marketing/create_reports>` to improve future campaigns."
msgid "To access the metrics for an individual mailing, navigate to :menuselection:`Email Marketing app --> Mailings`. Locate the specific mailing in the list view, and use the column headings to view the results for that mailing. Click on one of the mailings in the list to open the record."
msgid "In cases where a reply is expected, such as cold outreach emails, high open rate may indicate the subject line was timely, compelling, and successfully prompted the recipients to view the message."
msgid "In cases where a reply is not expected, such as promotional emails, it may indicate an issue with the email, such as incorrect product links or coupon codes."
msgid "In cases where a reply is expected, a low open rate may indicate the subject line failed to capture the recipients' interest or the message ended up in a spam or junk folder. It could also indicate the email ended up in a spam or junk folder."
msgid "Emails that consistently land in recipient spam folders could be due to having a poor sender reputation (i.e. high unsubscribe rate, high percentage of past emails marked as spam, etc.), or failing to :doc:`configure the proper DNS records <../../general/email_communication/email_domain>`."
msgid "This represents the *Clicked through rate (CTR)*, which measures the percentage of recipients who clicked on a link within the email, against the total number of sent emails."
msgid "A high |CTR| may indicate the email content was relevant and appropriately targeted. Recipients were motivated to click the links provided, and likely found the content engaging."
msgid "A low |CTR| may indicate issues with either the targeting, or the content itself. Recipients may have been unmotivated by the calls-to-action, if there were any, or the message itself may have been directed toward the wrong audience."
msgid "A low received rate may indicate issues, either with the mailing list used for the mailing, or with the sender authentication. View the :ref:`email-marketing/deliverability-issues` section for more information."
msgid "This rate measures the percentage of emails that were **unsuccessfully** delivered, and did not enter a recipient's inbox, against the total number of sent emails."
msgid "A low bounce rate may indicate that the mailing list used is up-to-date, and the sender authentication is trusted by email providers. View the :ref:`email-marketing/deliverability-issues` section for more information."
msgid "Click on the respective smart buttons to see all the corresponding recipient records that are attributed to each metric. When these filtered records are in view, multiple types of reports can be run for further analysis."
msgid "Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar to see a drop-down menu of filtering and grouping parameters."
msgid ":guilabel:`Filters`, located in the left column of the search options, can be used to keep only the results that fit the filter. For example, selecting the *Bounced* filter only shows emails that could not be delivered."
msgid "Setting multiple :guilabel:`Group By` options creates nested groups, according to which option is selected first. For example, selecting :guilabel:`Sent Period`, followed by :guilabel:`Add Custom Group --> Responsible`, in the :guilabel:`Group By` column, sorts all results *first* by the sent period, *then* by the team member responsible. This is a useful metric for analyzing who on the team is sending in volume or quantity over a set time period."
msgid "This can be verified by looking at the direction, and order, of the selections in the group tile that appears in the search bar after the selections are made."
msgid "To see what these bounced recipients have in common, the records are grouped using a custom group targeting :guilabel:`Mailing Lists`, which groups all records by the mailing lists they are on. The records are then filtered using a custom filter with the rule `Created on >= 07/01/2024 00:00:00`, to filter by when the mailing list was last checked. This filter only includes recipients that have been created on, or after, July 1st, 2024, in the report."
msgid "Using these configurations, it is evident that all the recipients with bounced emails were added after the list was last checked. Looking closer at the domains, it is evident that each recipient has a malformed email domain (i.e: @yaoo.com instead of @yahoo.com), likely due to a manual entry error while updating the database."
msgid "It is also possible to analyze the success between mailing campaigns by creating a *Mass Mailing Analysis* report. To begin, navigate to :menuselection:`Email Marketing app --> Reporting --> Mass Mailing Analysis`."
msgid "A dashboard appears displaying a bar chart containing each mailing campaign. By default, :guilabel:`Sent` is selected, displaying the number of sent records on the y-axis. To change the measure, click the :guilabel:`Measures` button, and select the desired measure from the drop-down menu."
msgid "In this view, it can be seen that the first mass mailing led to a higher opened rate than the second. Because a lower opened rate can sometimes be attributed to a subject line that failed to capture readers' attention, the subject line of each mass mailing can be a good place to begin looking."
msgid "Comparing the two subject lines, it is clear the newsletter's subject line was less engaging, which may have led to the lower opened rate, when compared to the other mass mailing."
msgid "Using a mailing list that contains outdated contact information, or malformed email addresses are likely to result in a high bounce rate and/or a low received rate."
msgid "Mailings sent using a *From* email address that differs from the sender's domain are likely to bounce with certain email providers due to failing :ref:`DMARC authentication <email-domain-dmarc>`."
msgid "In Odoo, lost leads are removed from the active *CRM* pipeline, but can still be targeted with the *Email Marketing* application for strategic campaign purposes, such as lost leads reactivation."
msgid "A lost leads reactivation email looks at the leads that were lost during a specific period of time, and uses custom filters and lost reasons to exclude undesirable leads from the mailing list."
msgid "Once a lost leads reactivation email is complete, it can be sent as is, modified and sent to different groups for A/B testing, or saved as a template for later."
msgid "A warehouse has leftover merchandise from a limited run of items from last year. To help clear out the excess inventory, the warehouse manager creates a lost leads email to reach out to old opportunities that were lost, and inform them that the limited merchandise is back in stock."
msgid "As filters are added and removed, pay attention to the :guilabel:`# record(s)` value below the filtering section. This value indicates the total number of records that match the current criteria."
msgid "In order to create and deliver a lost leads reactivation email campaign, the *CRM* and *Email Marketing* applications **must** be :ref:`installed <general/install>` and configured."
msgid ":ref:`Stage <email_marketing/stage_filter>` filter(s) to exclude leads that were already won, or are still active in new stages of the sales pipeline (i.e. *New*, *Qualified*, etc.). These values will be different per organization; however, it's minimally viable to exclude all the leads in the *Won* stage."
msgid "One or more :ref:`Lost Reason <email_marketing/lost_reason_filter>` filters to exclude undesired leads, such as duplicate, spam, or irrelevant records."
msgid "First, navigate to the :menuselection:`Email Marketing` app, and on the :guilabel:`Mailings` page, click the :guilabel:`New` button in the top-left corner."
msgid "On the new :guilabel:`Mailings` form, enter an appropriate :guilabel:`Subject` line for the email in the corresponding field. Then, in the :guilabel:`Recipients` field, choose the :guilabel:`Lead/Opportunity` model from the drop-down menu."
msgid "In the rules section, located beneath the :guilabel:`Recipients` field, click the modify filter (:guilabel:`▶ (triangle pointing right)`) icon to expand the filter rules. Leave the default :guilabel:`Blacklist` rule in place."
msgid "Begin by clicking :guilabel:`New Rule` beneath the default :guilabel:`Blacklist` rule. Then, click the first field of the new rule that appears, and select the :guilabel:`Created on` parameter from the drop-down menu. With that in place, a specific time period during which the targeted leads were lost can be designated (e.g. 30 days prior, 90 days prior, previous year, etc.)."
msgid "Then, in the second field, select :guilabel:`<= (less than or equal to)`, :guilabel:`>= (greater than or equal to)`, or :guilabel:`is between` as a date operator, in order to frame the time selection chosen in the third field."
msgid "When there is more than one rule applied, make sure the statement at the top of the :guilabel:`Recipients` filter list reads: :guilabel:`Match all of the following rules`. If it does not, click on the statement, and select :guilabel:`all` from the drop-down menu (as opposed to :guilabel:`any`)."
msgid "This step assumes that the *New*, *Qualified*, and *Won* stages exist in the CRM pipeline; however, stage names may differ from business to business. Refer to the database's actual stage names in the *CRM* app's pipeline to complete this step, accordingly."
msgid "Begin again by clicking :guilabel:`New Rule` and select :guilabel:`Stage` from the first field's drop-down menu. In the second field, select the :guilabel:`is not in` operator, and in the third field, select the :guilabel:`New`, :guilabel:`Qualified` and :guilabel:`Won` stages to define the rule's parameters."
msgid "Another way to add *Stage* rules, is to do so on a one-rule-per-row basis using the :guilabel:`contains` or :guilabel:`does not contain` operators, and manually typing out the defining characters in each stage name. This method, however, only allows for one selection at a time, which can be useful for quickly turning on/off filters in the :guilabel:`Search...` bar."
msgid "Next, add one or more :guilabel:`Lost Reason` rules to exclude leads that should **not** be targeted for specific :doc:`lost reasons <../../sales/crm/pipeline/lost_opportunities>`."
msgid "To do that, create another :guilabel:`New Rule`, once again. Then, in the rule's first field, select :guilabel:`Lost Reason` from the drop-down menu. For the operator, choose either :guilabel:`is not in` or :guilabel:`does not contain` from the drop-down menu. With either selection, use the third field to enter a lost reason (or multiple lost reasons, depending on your operator choice) to include in the rule."
msgid "If choosing the :guilabel:`does not contain` operator, then repeat the preceding steps to add more lost reasons, as needed, where each lost reason occupies one rule row at a time."
msgid "For more information, refer to the section below outlining how to :ref:`select appropriate lost reasons <email_marketing/select_lost_reasons>`."
msgid "Adding both active *and* inactive lead records is necessary to capture the full scope of lost leads in the database. Doing one without the other greatly impacts the number of targetable records for the email campaign, and does **not** include a complete or accurate lost leads audience."
msgid "First, click the :guilabel:`(Add Branch)` icon on the most recently created rule (e.g. :guilabel:`Lost Reason`), which is the middle of three icons located to the right of the rule row. Doing so adds a pair of :guilabel:`any of` rules. Then, in the top rule's first field of the newly-created branch, select the :guilabel:`Active` parameter from the drop-down menu. The rule then automatically fills out to read: :guilabel:`Active` *is* `set`."
msgid "For the first field of the bottom rule of the branch, select :guilabel:`Active` from the drop-down menu again. However, this time, select :guilabel:`is not` from the operator drop-down menu in the second field. The rule should then read: :guilabel:`Active` *is not* `set`."
msgid "Now, with the domain section of the email campaign complete, create the body content of the email using any of the premade stylized templates, or choose between the :guilabel:`Plain Text` or :guilabel:`Start From Scratch` options for more granular control. For more information, refer to the *Email Marketing* :ref:`documentation on how to create an email <email_marketing/create_email>`."
msgid "To save the set of filters for later use, click :guilabel:`Save as Favorite Filter 💾 (floppy disk)`, enter a name (such as `Lost Leads`), and click :guilabel:`Add`."
msgid "Consider using *A/B Testing* to send an alternate version of the email to a percentage of the target leads. This can help determine what subject lines and body content produce the best click-through rates, before sending a final version to the remaining leads."
msgid "To do so, open the :guilabel:`A/B Tests` tab on the mailing form and check the box next to :guilabel:`Allow A/B Testing`. Then, adjust the parameters as needed, and click :guilabel:`Create an Alternative Version`."
msgid "When a lead is marked as lost, Odoo recommends selecting a *Lost Reason* to indicate why the opportunity did not result in a sale. Doing so keeps the pipeline organized and reporting data accurate, and generates potential to follow up with the lead in the future."
msgid "If an existing *Lost Reason* is not applicable, users with the necessary permissions can create new ones, which means the lost reasons in a database can vary from organization to organization, and from pipeline to pipeline."
msgid "When determining which reasons to include in a lost leads reactivation email, consider what the email is advertising, in order pinpoint one or more relevant lost reasons. Then, add a rule stating, :guilabel:`Lost Reason` *does not contain* `_____` for every reason in the database, **except** for the relevant one(s)."
msgid "If the email advertises a selection of previously-limited merchandise that is now back in stock, it makes sense to target leads with the lost reason: *not enough stock*."
msgid "After sending a lost leads reactivation email, marketing teams can use the smart buttons along the top of the email to analyze the results, and determine follow-up actions."
msgid ":guilabel:`Leads/Opportunities`: number of leads (or opportunities) that have been created in the *CRM* pipeline, as a result of the email campaign."
msgid ":guilabel:`Invoiced`: total revenues generated, as a result of the email campaign, via invoices sent to, and paid by, customers. These values are recorded in either the *Invoicing* or *Accounting* application, depending on which app is installed in the database."
msgid ":guilabel:`Ignored`: the number of recipients that received the email, but have not interacted with it in a meaningful way (i.e. opened, clicked, etc.)."
msgid "*Email nurturing* (sometimes referred to as *lead nurturing*) is the process of sending a series of timely and relevant \"nudge\" emails to connect with a lead, build a deeper relationship, and ultimately convert the lead into a sale."
msgid "Continuously adjusting the approach to remain \"visible\" at the top of the lead's inbox, and hopefully, get a meaningful response from the lead."
msgid "A marketing team wants to advertise a restocking of limited-run merchandise to all leads with a lost reason of *not enough stock*. They develop the following three-week long lead nurturing campaign."
msgid "**Week 3:** the marketing team sends a final email to all leads who have not been converted stating: *“20% off, don't miss your last chance to get these items before they're gone!”*"
msgid "Throughout the campaign, the marketing team continuously refers to the smart buttons along the top of the mailing page to see what percentages of leads are opening, clicking on, or ignoring the emails. They also regularly analyze reports on how many opportunities, quotations, and invoices have been generated by the campaign."
msgid "Mailing lists in Odoo are used for both pre and post sales communications in the *Email Marketing* application. They provide sales teams with qualified lead lists, focus group participants, or current customers that fulfill specific criteria."
msgid "Mailing lists can be generated in Odoo, and exported as a downloadable file, or into the *Knowledge*, *Dashboards*, or *Spreadsheets* applications, or imported via copy/paste or file upload."
msgid "To create a mailing list in the *Email Marketing* application, navigate to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists --> New`."
msgid "If the mailing list should be accessible by recipients from the subscription management page, allowing them to update their preferences, tick the box next to :guilabel:`Show In Preferences`."
msgid "Clicking :guilabel:`Send Mailing` reveals a separate page with a blank email template form, which can be filled out by following steps explained in the :doc:`Email Marketing doc <../email_marketing>`."
msgid "Clicking :guilabel:`Send SMS` reveals a separate page with a blank SMS template form, which can be filled out by following steps explained in the :doc:`SMS Marketing doc <../sms_marketing>`."
msgid "At the top of the mailing list form is a series of smart buttons that display a variety of metrics related to the specific mailing list. When any of the smart buttons are clicked, a separate page is revealed, showcasing detailed analytics related to that particular statistic."
msgid "Once all the configurations on the mailing list form are complete, Odoo automatically adds the new mailing list to the :guilabel:`Mailing List` page in the *Email Marketing* app (:menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists`)."
msgid "From the :guilabel:`Mailing Lists` page (:menuselection:`Email Marketing --> Mailing Lists --> Mailing Lists`), click the :guilabel:`Total Contacts` link on the line of the desired mailing list to which contacts should be added."
msgid "Doing so reveals a separate :guilabel:`Mailing List Contacts` page for that specific mailing list, where contacts can be created or imported, and then added to the specific mailing list."
msgid "This same page can also be accessed by clicking the desired mailing list from the :guilabel:`Mailing Lists` page, and then clicking the :guilabel:`Recipients` smart button on the mailing list form."
msgid "Doing so *also* reveals a separate :guilabel:`Mailing List Contacts` page for that specific mailing list, where contacts can be created or imported, and then added to the specific mailing list."
msgid "Contacts can also be directly imported to a specific mailing list from the :guilabel:`Mailing Lists` page, by clicking :guilabel:`Import Contacts` to the far-right of the desired mailing list."
msgid "Here, the desired mailing list is auto-populated in the :guilabel:`Import contacts in` field. Beneath that, write or paste email addresses in the :guilabel:`Contact List` field."
msgid "To add contacts to a specific mailing list from a master list of all mailing list contacts in the database, navigate to :menuselection:`Email Marketing app --> Mailing Lists --> Mailing List Contacts`. Doing so reveals the :guilabel:`Mailing List Contacts` page, featuring a list of all contacts associated with every mailing list."
msgid "To add an existing contact to a mailing list, select the desired contact from the list on the :guilabel:`Mailing List Contacts` page to reveal their contact form."
msgid "At the bottom of their contact form, click :guilabel:`Add a line` under the :guilabel:`Mailing List` column, locate the desired mailing list from the drop-down menu, and select it."
msgid "A mailing list can be created directly from a contact form, by typing the name of the new mailing list in the :guilabel:`Mailing List` field. Then, after a new mailing list name has been entered, two options appear on the drop-down menu beneath the new mailing list name."
msgid "From this drop-down menu, select :guilabel:`Create` to create the mailing list and edit it later, or select :guilabel:`Create and edit...` to create and edit the new mailing list right away."
msgid "To remove a contact from a mailing list that the contact has been added to, enable the :guilabel:`Opt Out` checkbox. If the :guilabel:`Opt Out` checkbox is ticked, the ability to add a :guilabel:`Reason` why the contact opted-out is also available."
msgid "When/if a contact *has* opted-out of a mailing list, the date they activated their opt-out appears in the :guilabel:`Unsubscription Date` column on their contact form."
msgid "Lastly, the initial :guilabel:`Subscription Date` can be seen, as well. This field is auto-populated with the date and time their subscription to the mailing list has been saved."
msgid "When a mailing list is created in the database, Odoo provides the option to directly link the mailing list to the Odoo-built website (created via the Odoo *Website* application)."
msgid "To link a mailing list to a website, navigate to the front-end of the website, which can be accomplished in a variety of ways throughout the database. The most direct way to get to the front-end of the website is to simply open the :menuselection:`Website` application from the main Odoo dashboard."
msgid "From the front-end of the website, click the :guilabel:`Edit` button in the upper-right corner. When clicked, Odoo reveals a right-sidebar, filled with drag-and-drop *building blocks*, packed with various features, options, and design elements."
msgid "Next, in the search bar of the right-sidebar, search for `Newsletter`. The :guilabel:`Newsletter` selection of building blocks is used to add subscription fields for any mailing list onto the website."
msgid "Doing so reveals the following building block options: :guilabel:`Newsletter Block`, :guilabel:`Newsletter Popup`, and :guilabel:`Newsletter`. Any of these options can be used to add subscription fields for a mailing list onto the website."
msgid "The :guilabel:`Newsletter Block` option places a customizable block onto the body of the website where a visitor to enter their email and click a button to subscribe to a designated mailing list."
msgid "The :guilabel:`Newsletter Popup` option reveals a customizable pop-up window that appears when a visitor scrolls to the specific section of the webpage on which the building block is placed. When the visitor reaches the designated section, a pop-up window appears, in which a visitor can enter their email address, click a button, and subscribe to that predetermined mailing list."
msgid "The :guilabel:`Newsletter` option provides the same functionality as the other options. However, it only consists of a field for the visitor to enter their email address, and a button to subscribe to the mailing list."
msgid "Once the desired newsletter building block is chosen, drag-and-drop it onto the body of the website. Then, select the newly-placed newsletter building block to reveal its configuration options on the right-sidebar."
msgid "Now, when a visitor enters their email address, and clicks the button to subscribe, they are instantly subscribed to that pre-configured mailing list. They are also added as a contact for that mailing list in Odoo *Email Marketing*."
msgid "Providing recipients with the power to unsubscribe from mailing lists is not only a smart business practice, it's often a legal requirement. Allowing recipients to unsubscribe from a mailing list establishes a sense of trust and control with an audience. It also helps companies appear more genuine, and less *spammy*."
msgid "In addition to having the option to unsubscribe from specific mailing lists, the recipient can also *blacklist* themselves during the unsubscription process, meaning they will not receive *any* more marketing emails from the Odoo database."
msgid "In order to provide recipients with the ability to blacklist themselves, a specific feature **must** be enabled in the *Email Marketing* application."
msgid "Navigate to :menuselection:`Email Marketing app --> Configuration --> Settings`, and tick the checkbox next to the :guilabel:`Blacklist Option when Unsubscribing` feature. Then, click :guilabel:`Save` in the upper-left corner of the :guilabel:`Settings` page."
msgid "The *Unsubscribe* link does **not** appear by default if the *Start From Scratch* template is used to create a mailing. The user **must** manually add the specific unsubscribe link `/unsubscribe_from_list` in the body of the email, or use a block from the *Footers* section of the email builder, which includes the unsubscribe link."
msgid "If a recipient clicks the *Unsubscribe* link in a mailing, Odoo instantly unsubscribes them from the mailing list, presents them with a :guilabel:`Mailing Subscriptions` page where they can directly manage their subscriptions, and informs them that they've been :guilabel:`Successfully Unsubscribed`."
msgid "Beneath that, Odoo asks the former subscriber to :guilabel:`Please let us know why you updated your subscription`, and the user can proceed to choose the appropriate opt-out reason from a series of options presented to them."
msgid "The opt-out answer options can be created and modified by navigating to :menuselection:`Email Marketing app --> Configuration --> Optout Reasons`."
msgid "Once they've chosen the appropriate opt-out reason from the options presented to them, they can click the :guilabel:`Send` button. Odoo then logs their reasoning for unsubscribing in the *Email Marketing* app for future analysis."
msgid "For a recipient to remove (i.e. blacklist) themselves from **all** marketing emails during the unsubscription process, on the :guilabel:`Mailing Subscriptions` page, they must click :guilabel:`Exclude Me`."
msgid "Upon clicking :guilabel:`Exclude Me`, Odoo informs the recipient they have been successfully blacklisted, with a message reading: :guilabel:`✔️ Email added to our blocklist`."
msgid "Beneath that, Odoo asks the former subscriber to :guilabel:`Please let us know why you want to be added to our blocklist`, and the user can proceed to choose the appropriate reason from a series of options presented to them."
msgid "Once they've chosen the appropriate reason from the options presented to them, they can click the :guilabel:`Send` button. Odoo then logs their reasoning for blacklisting themselves in the *Email Marketing* app for future analysis."
msgid "To view a complete list of all blacklisted email addresses, navigate to :menuselection:`Email Marketing app --> Configuration --> Blacklisted Email Addresses`."
msgid "When a blacklisted record is selected from this list, Odoo reveals a separate page with the recipient's contact information, along with the provided :guilabel:`Reason` why they chose to blacklist themselves."
msgid "In the *chatter* of the blacklisted record page, there's a time-stamped message, informing the user when the recipient blacklisted themselves (via a :guilabel:`Mail Blacklist created` log note)."
msgid "Blacklisted emails are excluded from all marketing mailings, however, these emails can still receive transactional emails, such as order confirmations, shipping notifications, etc."
msgid "To *Unblacklist* contacts, click the :guilabel:`Unblacklist` button in the upper-left corner of a blacklisted record's page to remove the contact from the blacklist, allowing them to receive mailings once again."
msgid "In this pop-up window, the email address of the selected blacklisted record is shown, and there's a :guilabel:`Reason` field, in which a reason can be entered, explaining why this particular contact was removed from the blacklist."
msgid "Explore the various aspects of the Odoo **Events** detailed dashboard, and useful settings, that can be utilized to generate and gather valuable data about events (and their attendees), which can then be used to improve decision-making and event-planning."
msgid "When the **Events** application is opened, Odoo reveals the main :guilabel:`Events` dashboard, which can be viewed in a number of different ways. Those different view options are accessible from the :guilabel:`Events` dashboard in the upper-right corner, via a series of view-related icon buttons."
msgid "By default, the :guilabel:`Events` dashboard is displayed in the :icon:`oi-view-kanban` :guilabel:`Kanban` view, which is populated with a variety of pipeline stages."
msgid "This view showcases all the events in the database in their respective stages. By default, the stages are: :guilabel:`New`, :guilabel:`Booked`, :guilabel:`Announced`, :guilabel:`Ended`, and :guilabel:`Cancelled`."
msgid "On each event card, find the scheduled date of the event, the name of the event, the location, the number of expected :guilabel:`Attendees`, any scheduled activities related to the event, the status of the event, and the person responsible for the event."
msgid "To quickly add a new event to a pipeline, click the :icon:`fa-plus` :guilabel:`(plus)` icon at the top of the stage to which the event should be added to reveal a blank Kanban card to fill out."
msgid "Then, either click :guilabel:`Add` to add it to the stage and edit it later, or click :guilabel:`Edit` to add the event to stage and edit its configurations on a separate page."
msgid "To access the event settings and feature options in Odoo **Events**, navigate to :menuselection:`Events app --> Configuration --> Settings`. From here, tick the checkboxes beside the desired settings and/or features, and click :guilabel:`Save` to activate them."
msgid "In the :guilabel:`Events` section of the :guilabel:`Settings` page, there are selectable features that can be enabled to add various elements to events created with the Odoo **Events** application."
msgid "The :guilabel:`Schedule & Tracks` feature allows users to manage and publish a schedule with tracks for events. *Tracks* is a catch-all term that refers to talks, lectures, demonstrations, presentations, and other similar elements that users may choose to include as part of an event."
msgid "When the :guilabel:`Schedule & Tracks` feature is enabled, two additional fields appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`."
msgid "The :guilabel:`Event Gamification` feature lets users share a quiz after any event track, in order for attendees to gauge how much they learned from the track they just saw/heard. Companies can also benefit from this feature, in that the subsequent responses and results of the quizzes can help determine where a company's strengths and weaknesses are, when it comes to their presentations."
msgid "Next, is the :guilabel:`Online Exhibitors` feature. This feature allows users to display sponsors and exhibitors on event pages, which can serve as a valuable incentive to encourage partners and businesses to participate in the event."
msgid "The :guilabel:`Jitsi Server Domain` field represents an external conferencing service that is integrated with Odoo. It is what is used to create and host virtual conferences, community rooms, and other similar elements for events."
msgid "The :guilabel:`Community Chat Rooms` feature allows users to create virtual conference rooms for event attendees, providing them with a centralized place to meet and discuss anything related to the event."
msgid "Lastly, there is the :guilabel:`Booth Management` feature. This feature provides users with the ability to create and manage event booths and booth reservations. When enabled, users can create different booth tiers, with individual price points, and sell them to interested parties."
msgid "The :guilabel:`Registration` section of the :guilabel:`Settings` page provides selectable settings that are directly related to event registration."
msgid "The :guilabel:`Online Ticketing` setting creates a selectable *Event Ticket* product type on product forms, which provides users with the ability to sell event tickets online, via their website/eCommerce store."
msgid "In the :guilabel:`Attendance` section of the :guilabel:`Settings` page, there is a selectable setting that is directly related to how attendees can attend/enter the event."
msgid "The :guilabel:`Use Event Barcode` setting, when activated, enables barcode (and QR code) scanning for attendees to enter the event. This provides attendees with quick access, and helps Odoo users easily track, manage, and analyze all event attendees."
msgid "The :guilabel:`Barcode Nomenclature` field, beneath the :guilabel:`Use Event Barcode` setting, is set to :guilabel:`Default Nomenclature`, by default, but can be changed at any time."
msgid "Once launched, the **Events** application then integrates with the **Website** app for the front-end promotion and registration of the event for attendees, the **Sales** app for the purchasing ability of paid tickets, and the **CRM** application through customizable lead generation rules."
msgid "Create custom ticket tiers (with various price points) for potential event attendees to choose from, directly on the event template form, under the *Tickets* tab."
msgid "Discover how to access various event tracks (talks, presentations, etc.), view entire agendas, and learn how attendees can propose talks for the event."
msgid "With the *Events* application, event organizers can create and configure in-person or online-only events in Odoo. Each new event contains a number of customizable options that are geared around specific event logistics, as needed per event, such as ticket sales and registration desk, booths, tracks, sponsors, rooms, and more."
msgid "Events can be manually created from scratch or built off of pre-made templates. Once launched, the *Events* application then integrates with the *Website* app for the front-end promotion and registration of the event for attendees, the *Sales* app for the purchasing ability of paid tickets, as well the *CRM* application through customizable lead generation rules."
msgid "To create a new event, begin by navigating to the :menuselection:`Events app` to land on the default :guilabel:`Events` dashboard, in the :icon:`oi-view-kanban` :guilabel:`Kanban` view. From there, or alternatively from the :icon:`oi-view-list` :guilabel:`List` or :icon:`fa-tasks` :guilabel:`Gantt` views, click the :guilabel:`New` button in the upper-left corner of the dashboard to open up a new event form."
msgid "If certain fields do not readily appear on the event form, that means an additional application needs to be installed, or the database is not operating in a multi-company environment."
msgid "For example, the :guilabel:`Twitter Wall` field **only** appears if the *Social Marketing* app is installed, and the :guilabel:`Company` field **only** appears if the database is working in a multi-company environment."
msgid "These are just *additional* elements that can be used for an event. They are **not** required to create, host, and manage an event with Odoo *Events*."
msgid "At the top of the event form are a series of smart buttons related to various event metrics, which will autopopulate with pertinent data once attendees begin to register, booths and sponsors sign on for the event, the event takes place, and so on."
msgid "Primarily, these smart buttons are used as logistical portals to perform specific actions for the event. The numeric displays are primarily for quick reference points."
msgid "While those visual metrics are useful, they can still be clicked, and used to navigate to specific event-related pages to modify and/or perform any desired actions."
msgid "Beneath the smart buttons is the event form, which contains various fields and clickable tabs that serve to configure the initial, necessary details of the event."
msgid "To the right of the entered :guilabel:`Event Name`, there is a language tooltip, represented by an abbreviated language indicator (e.g. `EN`). When clicked, a :guilabel:`Translate: name` pop-up window appears, displaying various pre-configured language translation options available in the database."
msgid ":guilabel:`Date`: when the event is scheduled to take place (expressed in your local timezone). This field is auto-populated, but modifiable, and is **required**."
msgid ":guilabel:`Display Timezone`: the timezone in which the event dates/times will be displayed on the website. This field is auto-populated, but modifiable, and is **required**."
msgid ":guilabel:`Language`: designate a specific language for all event communications to be translated into, if necessary. This field is blank, by default, so if event-related communications are being sent to recipients who speak a different language, be sure to configure this field properly."
msgid ":guilabel:`Twitter Wall`: creates a separate page on the event website to feature specific social posts on X (formerly Twitter) that contain pre-determined desired elements."
msgid "To create and customize a :guilabel:`Twitter Wall`, type the name of the desired wall into the field, and select :guilabel:`Create and edit...` from the resulting drop-down menu."
msgid "From this window, enter a :guilabel:`Wall Name`. Then, select a certain word or hashtag for Odoo to search for on X, like `#WoodWorkingExpo24`, for example."
msgid "Next, determine the :guilabel:`Type of tweets` Odoo should showcase with that predetermined criteria. The choices in this field are: :guilabel:`Recent`, :guilabel:`Popular`, or :guilabel:`Mixed`."
msgid "Lastly, the greyed-out, non-modifiable :guilabel:`Website URL` field will autopopulate with the full URL needed to access the document through the event website."
msgid "An image can also be added to the wall by clicking the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :guilabel:`(camera)` placeholder image in the upper-right corner of the pop-up window."
msgid "This :guilabel:`Twitter Wall` field **only** appears on the event form if the *Social Marketing* app is installed, and an X account has been added as a stream on the application. To learn more, check out the :doc:`Social Marketing <../social_marketing>` documentation."
msgid ":guilabel:`Tags`: add any corresponding tags to briefly describe the event (e.g. `Online`, `Conference`, etc.). Multiple tags can be added per event."
msgid "Tags can be displayed on events that are listed on the website by enabling the *Show on Website* checkbox from :menuselection:`Events app --> Configuration --> Event Tag Categories`."
msgid ":guilabel:`Company`: designate which company in the database to which this event is related. This field **only** appears if working in a multi-company environment. This field is auto-populated, but modifiable, and is **required**."
msgid ":guilabel:`Website`: choose to restrict the publishing of this event to a specific website created in Odoo. If this field is left blank, the event can be published on *all* websites in the database. To learn more, refer to the :doc:`Multiple websites <../../websites/website/configuration/multi_website>` documentation."
msgid ":guilabel:`Venue`: enter event venue details. This field pulls pertinent information from the *Contacts* application. Alternatively, :guilabel:`Venue` information can be manually added in this field, as well. At the very least, there **must** be a venue name, address, city, zip code/region, and country entered."
msgid ":guilabel:`Limit Registrations`: if this checkbox is ticked, a limit to the amount of registrations is added to the event, and that desired limit amount **must** be entered in the blank field before :guilabel:`Attendees`."
msgid ":guilabel:`Badge Dimension`: select a desired paper format dimension for event badges. The options are: :guilabel:`A4 foldable`, :guilabel:`A6`, or :guilabel:`4 per sheet`."
msgid "When the above fields in the event form have been adequately filled in, move on to the four tabs at the bottom of the event form for further customization."
msgid "To create a ticket, click :guilabel:`Add a line` in the :guilabel:`Tickets` tab. Then, enter a name for the ticket (e.g. `Basic Ticket` or `VIP`) in the :guilabel:`Name` field."
msgid "In the :guilabel:`Product` field, either select the pre-configured :guilabel:`Event Registration` product, or create a new one by typing in the name of the new event registration product, and then select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu."
msgid "Upon installing Odoo *Events*, a new product type, *Event Ticket*, becomes available on product forms (:menuselection:`Sales --> Products --> Products`). In order for an event registration product to be selectable in the *Tickets* tab, the event registration :guilabel:`Product Type` **must** be set to :guilabel:`Event Ticket`."
msgid "Existing event registration products can be modified directly from this field, as well, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon, located beside the event registration product. Doing so reveals that product's form. If the *Inventory* application is installed, additional choices are available to customize for the product."
msgid "The *Sales Price* defined on the event registration product's product form sets the default cost of a ticket. Modifying the :guilabel:`Price` of a ticket in the :guilabel:`Tickets` tab, sets a new registration cost of the ticket for that event."
msgid "Next, determine a :guilabel:`Sales Start` and :guilabel:`Sales End` date in their respective fields. To do that, click into the blank field to reveal a calendar popover. From there, select the desired date and time, then click :icon:`fa-check` :guilabel:`Apply`."
msgid "Optionally, in the :guilabel:`Color` column, add a custom color to differentiate ticket badges. The selected color displays on ticket badges when printed."
msgid "To delete any tickets from the :guilabel:`Tickets` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding line for the ticket that should be deleted."
msgid "To add an optional :guilabel:`Description` column to the :guilabel:`Tickets` tab, click the :icon:`oi-settings-adjust` :guilabel:`(additional options)` drop-down menu, located to the far-right of the column titles."
msgid "When added, the option to add brief descriptions for each event ticket appears, which can be used to inform attendees of any perks or amenities that may coincide with specific ticket purchases."
msgid "In the :guilabel:`Communication` tab of an event form, create various marketing communications that can be scheduled to be sent at specific intervals leading up to, and following, the event."
msgid "By default, Odoo provides three separate pre-configured communications on every new event form. One is an email sent after each registration to confirm the purchase with the attendee. The other two are email event reminders that are scheduled to be sent at different time intervals leading up to the event to remind the recipient of the upcoming event."
msgid "To add a communication in the :guilabel:`Communication` tab, click :guilabel:`Add a line`. Then, select the desired type of communication in the :guilabel:`Send` field. The options are: :guilabel:`Mail`, :guilabel:`SMS`, :guilabel:`Social Post`, or :guilabel:`WhatsApp`."
msgid "To delete a communication from the :guilabel:`Communication` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding communication line. Doing so removes the communication from the event entirely."
msgid "The :guilabel:`Social Post` option **only** appears if the *Social Marketing* application is installed. The :guilabel:`WhatsApp` option **only** appears if the *WhatsApp Integration* module is installed."
msgid ":doc:`WhatsApp <../../productivity/whatsapp>` templates **cannot** be edited during active configuration. A separate approval from *Meta* is required."
msgid "Next, define the :guilabel:`Interval`, :guilabel:`Unit`, and :guilabel:`Trigger` from their respective drop-down fields, letting Odoo know when the communication should be sent."
msgid "Then, select an option from the :guilabel:`Trigger` drop-down menu. The options are: :guilabel:`After each registration`, :guilabel:`Before the event`, and :guilabel:`After the event`."
msgid "The :guilabel:`Sent` column populates with the number of sent communications. And, beside the number are different icons that appear, depending on the status of that particular communication."
msgid "The status of *Running* is represented by a :icon:`fa-cogs` :guilabel:`(three gears)` icon. The status of *Sent* is represented by a :icon:`fa-check` :guilabel:`(checkmark)` icon. And, the status of *Scheduled* is represented by an :icon:`fa-hourglass-half` :guilabel:`(hourglass)` icon."
msgid "Existing email templates can be modified directly from the :guilabel:`Template` drop-down menu, if necessary, by clicking the :icon:`oi-arrow-right` :guilabel:`(right arrow)` icon next to the template name. Doing so reveals a separate page where users can edit the :guilabel:`Content`, :guilabel:`Email Configuration`, and :guilabel:`Settings` of that particular email template."
msgid "To view and manage all email templates, activate :ref:`developer-mode` and navigate to :menuselection:`Settings --> Technical --> Email: Email Templates`. Modify with caution as email templates effect all communications where the template is used."
msgid "In the :guilabel:`Questions` tab of an event form, users can create brief questionnaires for registrants to interact with, and respond to, after they register for the event."
msgid "These questions can be focused on gathering basic information about the attendee, learning about their preferences, expectations, and other things of that nature. This information can also be used to create more detailed reporting metrics, in addition to being utilized to create specific lead generation rules."
msgid "By default, Odoo provides three questions in the :guilabel:`Questions` tab for every event form. The default questions require the registrant(s) to provide their :guilabel:`Name` and :guilabel:`Email`, and make it optional to include their :guilabel:`Phone` number, as well."
msgid "The information gathered from the :guilabel:`Questions` tab can be found on the :guilabel:`Attendees` dashboard, accessible via the :icon:`fa-users` :guilabel:`Attendees` smart button. Odoo populates individual records that contain basic information about the registrant(s), as well as their preferences."
msgid "To add a question in the :guilabel:`Questions` tab, click :guilabel:`Add a line`. Doing so reveals a :guilabel:`Create Question` pop-up window. From here, users can create and configure their question."
msgid "First, enter the question in the field at the top of the form. Then, decide if the question should require a :guilabel:`Mandatory Answer` and/or if Odoo should :guilabel:`Ask once per order`, by ticking their respective boxes, if desired."
msgid "If the :guilabel:`Ask once per order` checkbox is ticked, the question will only be asked once, and its value is propogated to every attendee in the order (if multiple tickets are purchased at once). If the checkbox is *not* ticked for this setting, Odoo will present the question for every attendee that is connected to that registration."
msgid ":guilabel:`Selection`: provide answer options to the question for registrants to choose from. Selectable answer options can be managed in the :guilabel:`Answers` column at the bottom of the pop-up window."
msgid "Once all the desired configurations have been entered, either click :guilabel:`Save & Close` to save the question, and return to the :guilabel:`Questions` tab on the event form, or click :guilabel:`Save & New` to save the question and immediately create a new question on a new :guilabel:`Create Question` pop-up window."
msgid "For :guilabel:`Selection` and :guilabel:`Text Input` types, a :icon:`fa-bar-chart` :guilabel:`Stats` button appears on the right side of the question line. When clicked, Odoo reveals a separate page, showcasing the response metrics to that specific question."
msgid "To delete any question from the :guilabel:`Questions` tab, click the :icon:`fa-trash-o` :guilabel:`(trash can)` icon on the corresponding question line."
msgid "In the :guilabel:`Notes` tab of an event form, users can leave detailed internal notes and/or event-related instructions/information for attendees."
msgid "In the :guilabel:`Note` field of the :guilabel:`Notes` tab, users can leave internal notes for other event employees, like \"to-do\" lists, contact information, instructions, and so on."
msgid "In the :guilabel:`Ticket Instructions` field of the :guilabel:`Notes` tab, users can leave specific instructions for people attending the event that appear on the attendees ticket."
msgid "Once all configurations and modifications are complete on the event form, it is time to publish the event on the website. Doing so makes the event visible to website visitors, and makes it possible for people to register for the event."
msgid "To publish an event after all the customizations are complete, click the :icon:`fa-globe` :guilabel:`Go to Website` smart button at the top of the event form. Doing so reveals the event's web page, which can be customized like any other web page on the site, via the :guilabel:`Edit` button."
msgid "To learn more about website design functionality and options, consult the :doc:`Building block <../../websites/website/web_design/building_blocks>` documentation."
msgid "Once the event website is ready to be shared, click the red :guilabel:`Unpublished` toggle switch in the header menu, changing it to a green :guilabel:`Published` switch. At this point, the event web page is published, and viewable/accessible by all website visitors."
msgid "To send event invites to potential attendees, navigate to the desired event form, via :menuselection:`Events app --> Events`, and click into the desired event. Following this, click the :guilabel:`Invite` button in the upper-left corner of the event form."
msgid "Doing so reveals a blank email form to fill out, as desired. To learn more about how to create and customize emails like this, refer to the :ref:`Create an email <email_marketing/create_email>` documentation."
msgid "Proceed to create and customize an email message to send as an invite to potential attendees. Remember to include a link to the registration page on the event website, allowing interested recipients to quickly register."
msgid "Sending emails from Odoo is subject to a daily limit, which, by default, is 200. To learn more about daily limits, visit the :ref:`email-issues-outgoing-delivery-failure-messages-limit` documentation."
msgid "When the :guilabel:`Booth Management` setting is activated, a new :doc:`Product Type <../../inventory_and_mrp/inventory/product_management/configure/type>` becomes available on all product forms: *Event Booth*."
msgid "This is important because every created booth **must** be assigned a *Booth Category* on their respective booth form, and every booth category **must** have an *Event Booth* product assigned to it."
msgid "With the *Booth Management* setting activated in the *Events* app, the *Booth Categories* option appears in the :guilabel:`Configuration` menu."
msgid "To access the :guilabel:`Booth Category` dashboard, go to :menuselection:`Events app --> Configuration --> Booth Categories`, which reveals a list of all created booth categories."
msgid "When the :icon:`oi-settings-adjust` :guilabel:`(settings)` icon, located to the far-right of the column titles, is clicked, a drop-down menu of additional column options appears. From the resulting drop-down menu, tick the checkbox beside :guilabel:`Sponsor Level` and/or :guilabel:`Sponsor Type` to reveal those columns on the :guilabel:`Booth Category` page."
msgid "To create a booth category from the :guilabel:`Booth Category` page, click the :guilabel:`New` button in the upper-left corner to reveal a blank booth category form."
msgid "To add a corresponding image to the booth category (e.g. a sample photo of how the booth looks), click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the camera placeholder in the upper-right corner of the booth category form. When clicked, proceed to upload the desired image to the booth category form, if needed."
msgid "In the :guilabel:`Booth Details` section, users **must** assign a :guilabel:`Product` to the category, and it **must** have *Event Booth* set as the *Product Type* on the product form."
msgid "And, regardless of the listed price on the *Event Booth* product chosen, the user can input a custom :guilabel:`Price` to be applied for this booth category in the field below."
msgid "In the :guilabel:`Sponsorship` section, there is a :guilabel:`Create Sponsor` checkbox option. With that checkbox ticked, whenever a booth belonging to this category is booked, the user is created as an official *Sponsor* of the event."
msgid "When the :guilabel:`Create Sponsor` checkbox is ticked, two additional fields appear beneath it: :guilabel:`Sponsor Level` and :guilabel:`Sponsor Type`."
msgid ":guilabel:`Sponsor Level` and :guilabel:`Sponsor Type` are purely to distinguish different distinctions of sponsors. For example, if a sponsor has been attached to a company for multiple years, they would be granted a higher level (e.g. *Gold* level), which provides them with immediate credability and status. Whereas, conversely, a relatively new sponsor would be granted a lower level (e.g. *Bronze* level), which coincides with its own credability and status."
msgid "To modify any existing :guilabel:`Sponsor Level`, select it from the drop-down field, then click the :icon:`fa-arrow-right` :guilabel:`(right arrow)` that appears at the end of the line. Doing so opens a separate page, wherein the :guilabel:`Sponsor Level` name and :guilabel:`Ribbon Style` can be changed, if necessary."
msgid "Users can also create a new :guilabel:`Sponsor Level`, by typing in the name of the new level, and clicking :guilabel:`Create and edit...` from the resulting drop-down menu."
msgid "Clicking :guilabel:`Create` from the resulting drop-down menu in this instance creates the sponsor level, but doesn't immediately prompt the user to further configure it, via a :guilabel:`Create Sponsor Level` pop-up window."
msgid "From this pop-up window, confirm the newly-created :guilabel:`Sponsor Level`, and decide what kind of :guilabel:`Ribbon Style` should be applied, if any. The :guilabel:`Ribbon Style` options available in that drop-down field are: :guilabel:`No Ribbon`, :guilabel:`Gold`, :guilabel:`Silver`, and :guilabel:`Bronze`."
msgid "On the booth category form, beneath those sections (:guilabel:`Booth Details` and :guilabel:`Sponsorship`), there is the :guilabel:`Description` tab. In this tab, proceed to enter any vital information related to the booth category that would be important for any potential booth-buyer to know about (e.g., the square footage, any amenities, size of display screen, etc.)."
msgid "In order to add a booth to an event, navigate to an existing event form, via :menuselection:`Events app --> Events`, and select the desired event from the :guilabel:`Events` dashboard. Or, click :guilabel:`New` to open a blank event form."
msgid "The :guilabel:`Booths` page is displayed in a Kanban view, by default, with two different stages: :guilabel:`Available` and :guilabel:`Unavailable`."
msgid "The :guilabel:`Booths` page of an event is also viewable in a :icon:`oi-view-list` :guilabel:`List` view, :icon:`fa-area-chart` :guilabel:`Graph` view, and :icon:`oi-view-pivot` :guilabel:`Pivot` view. All of which are accessible, via their icons, in the upper-right corner of the :guilabel:`Booths` page."
msgid "The booths present in the :guilabel:`Available` stage are still available for people to purchase for the event. The booths present in the :guilabel:`Unavailable` stage have already been purchased, and are no longer available."
msgid "To modify any existing booth, simply click the desired booth from the :guilabel:`Booths` page, and proceed to make any necessary changes from the booth form. Or, create a new one, by clicking the :guilabel:`New` button in the upper-left corner to reveal a blank booth form."
msgid "A new :guilabel:`Booth Category` can be created from this field, by typing in the name of the new category, and clicking :guilabel:`Create and edit...` from the resulting drop-down menu. Doing so reveals a :guilabel:`Create Booth Category` pop-up window, with all the standard fields found on a common booth category form."
msgid "Simply clicking :guilabel:`Create` from the resulting drop-down menu creates the category, but does not reveal the :guilabel:`Create Booth Category` pop-up window. The category would have to be modified later, via the *Booth Categories* page (:menuselection:`Events app --> Configuration --> Booth Categories`)."
msgid "Upon selecting a pre-existing :guilabel:`Booth Category`, two additional, non-modifiable fields appear: :guilabel:`Product` and :guilabel:`Price`. Both fields represent their respective selections for that specific booth category."
msgid "When a person purchases a booth rental through the event website, the subsequent renter-related fields on the form auto-populate, based on the information provided by the purchaser during the online transaction. The booth also automatically changes its status from *Available* to *Unavailable*."
msgid "However, if the rental of a booth is conducted in any other way (e.g., in person, via sales order, etc.), the :guilabel:`Renter`, :guilabel:`Renter Name`, :guilabel:`Renter Email`, and :guilabel:`Renter Phone` fields can be entered in manually."
msgid "The status of the booth (:guilabel:`Available` or :guilabel:`Unavailable`) can also be changed manually, either by clicking the appropriate status from the status bar present on the booth form, or by dragging-and-dropping the desired booth into the appropriate stage, via the *Booths* page Kanban view."
msgid "With event booths configured on the event form, via the event-specific *Booths* pages, Odoo presents them on the event website, via the *Get A Booth* event subheader link."
msgid "To access the *Get A Booth* page on the event website, open the :menuselection:`Events app`, and select the desired event from the :guilabel:`Events` dashboard. From the event form, click the :guilabel:`Go to Website` smart button to be taken to the Odoo-built event website."
msgid "If the event subheader menu (with the :guilabel:`Get A Booth` option) is *not* showing up on the event website, there are two ways to make it appear."
msgid "While on the event website, enter the edit mode by clicking the :guilabel:`Edit` button in the upper-right corner. Then, click into the :guilabel:`Customize` tab of the resulting sidebar of web design tools."
msgid "In the :guilabel:`Customize` tab, click the toggle switch for :guilabel:`Sub-Menu (Specific)`, and click :guilabel:`Save`. Doing so reveals the event subheader menu with various options."
msgid "On the event form, with *Debug mode* on, an array of subheader menu options appears. Tick the checkbox for :guilabel:`Website Submenu`, in order for the submenu to appear on the event website. Doing so also ticks every other submenu-related checkbox automatically."
msgid "At this point, proceed to choose which options to keep on the event subheader menu. In this case, make sure the :guilabel:`Booth Register` checkbox is ticked."
msgid "From there, click the :guilabel:`Get A Booth` event subheader menu option. Doing so reveals the :guilabel:`Get A Booth` page, showcasing all the configured event booths that were created on the event form."
msgid "From here, the visitor can select their desired booth option, then :guilabel:`Location`. Next, they would click the :guilabel:`Book my Booth(s)` button, located at the bottom of the :guilabel:`Get A Booth` page."
msgid "Doing so reveals a :guilabel:`Contact Details` page, wherein they fill out either *Contact Details* or *Sponsor Details*, depending on how the booth was configured on the event form. The fields present on this form vary, depending on whether its meant for a basic contact or an event sponsor."
msgid "The information provided on this details page is used to auto-populate the renter-related information on the booth form on the event form in the *Events* application."
msgid "Once the necessary information has been entered, the visitor then clicks the :guilabel:`Go to Payment` at the bottom of the page, and proceeds to complete the typical checkout process."
msgid "Upon a successful payment confirmation, that selected booth automatically moves to the *Unavailable* stage on the event-specific *Booths* page in the *Events* application (accessible via the *Booths* smart button on the event form)."
msgid "Also, the provided *Sponsor* information (if applicable) and *Sales Order* information are accessible from the specific event form, via their respective smart buttons that appear at the top of the form."
msgid "The Odoo *Events* application provides the ability to customize and configure event templates, which can be used to expedite the event-creation process."
msgid "These templates can be created and personalized in the application, and then selected from an event form, in order to quickly apply a series of settings and elements to the new event, all of which can be further modified, if needed."
msgid "To begin, navigate to :menuselection:`Events app --> Configuration --> Event Templates`. Doing so reveals the :guilabel:`Event Templates` page. Here, find all the existing event templates in the database."
msgid "By default, Odoo provides three pre-configured event templates: :guilabel:`Exhibition`, :guilabel:`Training`, and :guilabel:`Sport`, which all have their own unique customizations applied to them."
msgid "To change how these event templates appear on the *Template* drop-down field on an event form, drag-and-drop them into any desired order, using the :icon:`oi-draggable` :guilabel:`(draggable)` icon, located to the left of each event template line on the :guilabel:`Event Templates` page."
msgid "**On the dashboard**, by navigating to :menuselection:`Events app --> Configuration --> Event Templates` and clicking the :guilabel:`New` button in the upper-left corner. Doing so reveals a blank event template form that can be customized in a number of different ways."
msgid "**On an event form itself**. Start by typing the name of a new event template in the *Template* field, and click :guilabel:`Create and edit...` from the resulting drop-down menu. Doing so reveals a *Create Template* pop-up window, featuring all the same configurable fields and elements found on a standard event template form."
msgid "Clicking :guilabel:`Create \"[template name]\"` from the resulting drop-down menu, via the *Template* field on an event form creates the event template in the database, but does **not** present the user with the *Create Template* pop-up window."
msgid "The event template would have to be modified, by selecting it on the *Event Templates* page (:menuselection:`Events app --> Configuration --> Event Templates`)."
msgid "All the fields on a standard :guilabel:`Event Template` form are *also* on the *Create Template* pop-up window, accessible via the *Template* field on an event form."
msgid "Beneath that field, there is a series of selectable checkboxes, all of which are related to how the event menu will be displayed on the event web page."
msgid ":guilabel:`Website Submenu`: enables a submenu on the event's website. When this checkbox is ticked, every other checkbox in this series is automatically ticked, as well. Then, choose to untick (deselect) any of the checkbox options, as desired."
msgid ":guilabel:`Track Proposals Menu Item`: adds a submenu item to navigate to a page, in which visitors can fill out a form to propose a track (talk, lecture, presentation, etc.) to happen during the event."
msgid ":guilabel:`Booth Menu Item`: adds a submenu item that takes visitors to a separate page, where an event booth can be purchased. Event booths can be customized and configured in the :guilabel:`Booths` tab of the event template form, from the *Booth Categories* page (:menuselection:`Events app --> Configuration --> Booth Categories`)."
msgid ":guilabel:`Exhibitors Menu Item`: adds a submenu item that takes visitors to a separate page, showcasing all the exhibitors related to that specific event. Icons representing those exhibitors are also found on the footer of every event-specific web page, as well."
msgid ":guilabel:`Community`: adds a submenu item allowing attendees to access pre-configured virtual community rooms to meet with other attendees, and discuss various topics related to the event. When this checkbox is ticked, the :guilabel:`Allow Room Creation` feature becomes available."
msgid ":guilabel:`Register Button`: adds a button at the end of the event submenu that takes visitors to the event-specific registration page when clicked."
msgid "There is also the option to :guilabel:`Limit Registrations` to this specific event template by ticking that checkbox. If ticked, proceed to enter the number of :guilabel:`Attendees` this template should be limited to."
msgid "The :guilabel:`Booths` tab on an event template form is the only tab that differentiates itself from a standard event form, where the other tabs (:guilabel:`Tickets`, :guilabel:`Communication`, :guilabel:`Questions`, and :guilabel:`Notes`) are present and configured using the same process. For more information about those tabs, refer to the :doc:`create_events` documentation."
msgid "To create a booth or booth category, an event booth product **must** be created in the database first, with the *Product Type* set to *Event Booth*. **Only** products with that specific configuration can be selected in the required *Product* field of a booth or booth category form."
msgid "Event booths can be created and customized in two ways in the Odoo *Events* application. Either in the :guilabel:`Booths` tab of an event template form, or by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`, and click :guilabel:`New`."
msgid "To add a booth from the :guilabel:`Booths` tab of an event template form, click :guilabel:`Add a line`. Doing so reveals a blank :guilabel:`Create Booths` pop-up window."
msgid "Then, select an appropriate :guilabel:`Booth Category` from the drop-down field below. Booth categories can be created and modified from the *Booth Categories* page in the *Events* application, which is accessible by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`."
msgid "A :guilabel:`Booth Category` can be created directly from this field on the :guilabel:`Create Booths` pop-up window. To accomplish that, type the name of the new booth category in the :guilabel:`Booth Category` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...` from the resulting drop-down menu."
msgid "Clicking :guilabel:`Create` merely creates the category, which can (and should be) customized at a later date. Clicking :guilabel:`Create and edit...` reveals a new :guilabel:`Create Booth Category` pop-up window, from which the category can be configured in a number of different ways."
msgid "From this pop-up window, proceed to name the :guilabel:`Booth Category`, modify its :guilabel:`Booth Details` settings, configure its :guilabel:`Sponsorship` options (if applicable), and leave an optional :guilabel:`Description` to explain any pertinent details related to this specific category of booths."
msgid "There is also the option to add a photo/visual representation of the booth category, via the :guilabel:`(camera)` icon in the upper-right corner."
msgid "The same configurations and options are available by navigating to :menuselection:`Events app --> Configuration --> Booth Categories`, and clicking :guilabel:`New`."
msgid "Once the desired :guilabel:`Booth Category` is selected, the remaining fields on the :guilabel:`Create Booths` pop-up window (:guilabel:`Currency`, :guilabel:`Product`, and :guilabel:`Price`) autopopulate, based on information configured for that selected :guilabel:`Booth Category`."
msgid "These fields **cannot** be modified from the :guilabel:`Create Booths` pop-up window. They can only be modified from the specific booth category form page."
msgid "When all desired configurations are complete, click :guilabel:`Save & Close` to save the booth, and return to the event template form. Or, click :guilabel:`Save & New` to save the booth, and start creating another booth on a fresh :guilabel:`Create Booths` pop-up window. Click :guilabel:`Discard` to remove all changes, and return to the event template form."
msgid "From the event form, click the :guilabel:`Template` field to reveal all the existing event templates in the database. They appear in the same order as they are listed in on the *Event Templates* page (:menuselection:`Events app --> Configuration --> Event Templates`)."
msgid "Select the desired event template from the :guilabel:`Template` drop-down field on the event form. Pre-configured settings automatically populate the event form, saving time during the event creation process."
msgid "Any of these pre-configured settings related to the selected event template chosen in the :guilabel:`Template` field on an event form can be modified, as desired."
msgid "Odoo *Events* provides the ability to create, schedule, and manage talks, lectures, demonstrations, presentations, etc., which known as *Tracks* in Odoo."
msgid "The Odoo *Events* application also has an option to allow event attendees to propose talks (tracks) for an event, which can then be approved (or disapproved)."
msgid "To do that, navigate to :menuselection:`Events app --> Configuration --> Settings`, and tick the checkbox beside the :guilabel:`Schedule & Tracks` setting. Doing so provides the ability to manage and publish an event schedule with various tracks."
msgid "Also, when that setting checkbox is ticked, two additional setting options appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event Gamification`."
msgid "The :guilabel:`Event Gamification` options provides the ability to share a quiz with track attendees once the track is over, in order to test how much they learned."
msgid "With the :guilabel:`Event Gamification` setting enabled, an :guilabel:`Add Quiz` button appears on track forms, providing the ability to :ref:`quickly create a quiz <events/track-add-quiz>` specific to the topic related to that particular track."
msgid "Once all desired settings have been enabled, be sure to click the :guilabel:`Save` button in the upper-left corner of the :guilabel:`Settings` page."
msgid "To access, modify, and/or create tracks for an event, first navigate to a preconfigured event, or :doc:`create a new one <create_events>` from the *Events* application."
msgid "To do that, navigate to :menuselection:`Events app`, and either select a pre-existing event from the :guilabel:`Events` dashboard, or create a new one by clicking :guilabel:`New`."
msgid "If the :guilabel:`Tracks` smart button is not readily available, click the :guilabel:`More` :icon:`fa-sort-desc` drop-down menu to reveal hidden smart buttons. Then, click :guilabel:`Tracks` from the resulting drop-down menu."
msgid "Clicking the :guilabel:`Tracks` smart button reveals the :guilabel:`Event Tracks` page for that particular event, which presents all the tracks (both scheduled and proposed) for the event, if there are any."
msgid "The tracks are presented in a default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, but there is also the option to view these tracks in a :icon:`oi-view-list` :guilabel:`(List)`, :icon:`oi-view-cohort` :guilabel:`(Gantt)` chart, :icon:`fa-calendar-check-o` :guilabel:`(Calendar)`, :icon:`fa-area-chart` :guilabel:`(Graph)`, or :icon:`fa-clock-o` :guilabel:`(Activity)` view. All of which are accessible in the upper-right corner of the :guilabel:`Tracks` page."
msgid "In the default :icon:`oi-view-kanban` :guilabel:`(Kanban)` view, the tracks are categorized into different stages. The default stages are: :guilabel:`Proposal`, :guilabel:`Confirmed`, :guilabel:`Announced`, :guilabel:`Published`, :guilabel:`Refused` (collapsed stage), and :guilabel:`Cancelled` (collapsed stage). All of which can be edited, if needed."
msgid "To edit a stage, hover over the stage name, click the :icon:`fa-cog` :guilabel:`(Settings)` icon, and select :guilabel:`Edit` from the resulting drop-down menu."
msgid "From the :guilabel:`Event Tracks` page, click :guilabel:`New` in the upper-left corner to reveal a blank event track form to create an event track."
msgid "Then, if desired, add an accompanying image to the track via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon in the upper-right corner of the form. When clicked, proceed to upload the desired image for the track. This image appears on the front-end of the event website, on this specific tracks webpage."
msgid "To access a complete list of locations for event tracks, which can be modified (and added to) at any time, navigate to :menuselection:`Events app --> Configuration --> Track Locations`."
msgid "If the *Live Broadcast* setting has been enabled in the *Events* app settings, the option to add a corresponding link in the :guilabel:`YouTube Video Link` field is available."
msgid "Assign someone to be in charge of managing this track in the :guilabel:`Responsible` field. By default, the person who initially created the track is assigned."
msgid "Then, ensure the track is applied to the correct event in the :guilabel:`Event` field. By default, this field is auto-populated with the event related to the *Event Tracks* page the track was originally created from."
msgid "Next, choose to add existing tags, or create new ones, to further organize the track. These tags, and their corresponding tag categories are utilized on the event specific website - mainly on the *Talks* web page on the event website, via the drop-down filter menus."
msgid "Beneath that general information section, there are three tabs: :ref:`Speaker <events/track-speaker-tab>`, :ref:`Description <events/track-description-tab>`, and :ref:`Interactivity <events/track-interactivity-tab>`."
msgid "The :guilabel:`Speaker` tab on an event track form is filled with various fields related to the specific speaker who is planning to conduct/host the track."
msgid "In the :guilabel:`Contact Details` section, proceed to use the :guilabel:`Contact` drop-down field to select an existing contact from the database as the main point of contact for the talk."
msgid "If this contact is not yet in the database, type in the name of the contact, and click :guilabel:`Create` to create and edit the contact form later, or click :guilabel:`Create and edit...` to be taken to that new contact's contact form, where the rest of their pertinent information can be entered."
msgid "The :guilabel:`Contact Email` and :guilabel:`Contact Phone` fields are greyed-out and populated with the information found on that chosen contact's contact form. These fields are not modifiable once the :guilabel:`Contact` field is selected."
msgid "In the :guilabel:`Speaker Bio` section, proceed to enter information related to the specific speaker scheduled to conduct/host the track. This section may auto-populate based on the :guilabel:`Contact` selected in the :guilabel:`Contact Details` section. If not, enter information in the necessary fields."
msgid "This information appears on the front-end of the event website, on the specific track webpage, providing more information about the speaker to the track attendees."
msgid "Next, if desired, add an image to appear alongside the speaker biogrpahy on the event website, via the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears when the cursor hovers over the :icon:`fa-camera` :guilabel:`(camera)` icon. When clicked, proceed to upload the desired image for the speaker."
msgid "The :guilabel:`Description` tab of an event track form is a blank text field, in which a description of the track can be entered. The information entered here appears on the specific track page on the event website."
msgid "When the checkbox beside :guilabel:`Magic Button` is ticked, Odoo displays a *call to action* button to attendees on the track sidebar, while the track is taking place."
msgid "The :guilabel:`Add Quiz` button **only** appears on event track forms if the *Event Gamification* setting is enabled in the Odoo *Events* settings."
msgid "To add a quiz to the event track, click the :guilabel:`Add Quiz` button. Doing so reveals a separate page where an event track quiz can be created and configured."
msgid "Start by entering a title for the quiz in the blank field at the top of the page. Then, if participants should be allowed to try the quiz multiple times, tick the checkbox beside :guilabel:`Allow multiple tries`."
msgid "The :guilabel:`Event` and :guilabel:`Event Track` fields are non-modifiable, and show the corresponding event and track this quiz is associated with."
msgid "To add questions to the quiz, click :guilabel:`Add a line` beneath the :guilabel:`Question` column. Doing so reveals a :guilabel:`Create Questions` pop-up window."
msgid "From the pop-up window, enter the question in the blank field at the top. Then, click :guilabel:`Add a line` to add answer options. Upon clicking :guilabel:`Add a line`, a new line appears, in which an answer option can be entered."
msgid "Once an answer option has been entered, proceed to designate whether it is the :guilabel:`Correct` response, by ticking the checkbox in the :guilabel:`Correct` column."
msgid "Once all desired answer options (and their configurations) are complete, click :guilabel:`Save & Close` to save the question, close the pop-up window, and return to the track quiz form. Or, click :guilabel:`Save & New` to save this question, and instantly start creating another question on a new :guilabel:`Create Questions` pop-up form."
msgid "Once all the desired configurations are complete on an event track form, click the desired stage it should be in from the status bar in the upper-right corner (e.g. :guilabel:`Confirmed`, :guilabel:`Announced`, etc.)."
msgid "The stage of a track can also be changed from the :guilabel:`Event Tracks` page, where the desired track card can be dragged-and-dropped into the appropriate Kanban stage."
msgid "If an event track has *not* been published yet, and it is moved to the :guilabel:`Published` stage, Odoo automatically publishes the track on the event website."
msgid "An event track can *also* be published by opening the desired event track form, and clicking the :guilabel:`Go to Website` smart button. Then, in order for the track page to be viewable (and accessible) for event attendees, toggle the :icon:`fa-toggle-off` :guilabel:`Unpublished` switch at the top of the page to :icon:`fa-toggle-on` :guilabel:`Published`; thus turning it from red to green, and making it accessible for attendees."
msgid "Use the *Registration Desk* feature in Odoo **Events** to grant access to registered event attendees as they arrive, and store attendee-related data in the reporting metrics."
msgid "On a mobile device (on the Odoo app or in a browser), open the :menuselection:`Events app`, and click the :guilabel:`Registration Desk` to view the :guilabel:`Registration Desk` page."
msgid "Scan the codes present on event attendee badges, by navigating to :menuselection:`Events app --> Registration Desk`, and selecting the :guilabel:`Scan a badge` option."
msgid "Once Odoo has access to the camera, a :guilabel:`Barcode Scanner` pop-up window appears, showing the camera's point-of-view. There is also a specified view finder box present, whose size can be manually modified, accordingly, using the :icon:`fa-crop` :guilabel:`(crop)` icon."
msgid "When the badge code is in the middle of the view finder box, the code is scanned, the :guilabel:`Barcode Scanner` pop-up window disappears, and the attendee is granted access to the event. Once the code is scanned, their attendance is logged in the Odoo **Events** app."
msgid "Manually grant access to event attendees, by navigating to :menuselection:`Events app --> Registration Desk`, and selecting the :guilabel:`Select Attendee` option."
msgid "Odoo reveals an :guilabel:`Attendees` page, with all the attendees for every event in the database, in a default :icon:`oi-view-kanban` :guilabel:`Kanban` view."
msgid "On the :guilabel:`Attendees` page, each attendee card displays that person's name, which event they are registered to attend, their associated company (if applicable), what ticket tier they purchased (if applicable), along with two buttons: a :icon:`fa-check` :guilabel:`(checkmark)` and :icon:`fa-undo` :guilabel:`(counter-clockwise arrow)`."
msgid "To do that, click the :icon:`fa-sort-desc` :guilabel:`(down arrow)` beside the seach bar to reveal a drop-down menu with :guilabel:`Filters`, :guilabel:`Group By`, and :guilabel:`Favorites` options."
msgid "For example, click the :guilabel:`Event` option, in the :guilabel:`Group By` column. Then, click away to remove the drop-down menu. Odoo reveals the :guilabel:`Attendees` page with event-specific columns, allowing users to locate specific event attendees."
msgid "The Odoo **Events** application creates custom reports, based on event-related data and analytics. These reports can either be focused on *Attendees* or *Revenues*."
msgid "By default, the :guilabel:`Revenues` reporting page appears as a graph (a :icon:`fa-line-chart` :guilabel:`(Line Chart)` with :icon:`fa-database` :guilabel:`(Stacked)` data). The default filters, :guilabel:`Non-free tickets` and :guilabel:`Event Start Date: (current year)`, are present in the search bar."
msgid "The :guilabel:`Revenues` reporting page can also be viewed as a :ref:`pivot table <reporting/views/pivot>`, by clicking the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner."
msgid "Regardless of the chosen view, the measures on the :guilabel:`Revenues` reporting page are as follows: :guilabel:`Revenues`, :guilabel:`Untaxed Revenues`, and :guilabel:`Count`."
msgid "In the default graph view of the :guilabel:`Revenues` reporting page, only the :guilabel:`Revenues` option is set in the :guilabel:`Measures` drop-down menu."
msgid "To reveal a drop-down menu of filter and grouping options to create custom reports, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar."
msgid "Doing so opens a drop-down mega menu of options organized into columns: :ref:`Filters <search/preconfigured-filters>`, :ref:`Group By <search/group>`, and :ref:`Favorites <search/favorites>`."
msgid "If a time-related option has been selected from the :guilabel:`Filters` column (e.g. the default :guilabel:`Event Start Date: (year)` filter), a :guilabel:`Comparison` column appears, with comparison options for the corresponding time-related filter option selected."
msgid "In the :guilabel:`Filters` column of the drop-down mega menu, there are various event-related options that can be utilized to create custom reports, based on a number of specific criteria."
msgid ":guilabel:`Registration Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to view a specific periods of time and see how many registrations happened during that time."
msgid ":guilabel:`Upcoming/Running`: include revenue-related information for events that are either currently running or are going to happen in the future."
msgid ":guilabel:`Event Start Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to designate event start dates to use as filters for revenue-related event data."
msgid ":guilabel:`Event End Date`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a list of month, quarter, and year options. Select any number of these options to designate event end dates to use as filters for revenue-related event data."
msgid ":guilabel:`Add Custom Filter`: Create a custom filter to analyze event-related revenue data. To learn more, refer to the documentation on :ref:`custom filters <search/custom-filters>`."
msgid ":guilabel:`Add Custom Group`: Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon to reveal a drop-down of grouping options. To select one, click on the desired option, and Odoo adds it to the :guilabel:`Group By` column. Multiple selections can be made."
msgid "The following is an example of how various filters and grouping options can create a useful analytic graph report related to event revenues. In this case, the configurations present data about sold or free tickets to published events, with the metrics separated by ticket type and event."
msgid "To create such a report, navigate to :menuselection:`Events app --> Reporting --> Revenues`. Stay in the default graph view, but remove the default filters from the search bar."
msgid "Then, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` to the right of the search bar, to reveal the drop-down mega menu of filter and grouping options."
msgid "Then, since it is desired to **only** view data related to already published events, select the :guilabel:`Published Events` option in the :guilabel:`Filters` column, as well."
msgid "Next, in the :guilabel:`Group By` column, select the :guilabel:`Event` and :guilabel:`Ticket` options, **in that sequential order**. Doing so first groups the data by event, *then* by ticket type, which provides a more useful array of data to analyze."
msgid "If no additional filters or groupings are added, Odoo presents a graphical representation of data related to all *free* or *sold* tickets for *published events*, grouped by *event*, and organized by *ticket* type."
msgid "The following is an example of how various filters and grouping options can create a useful analytic pivot table report related to event revenues. In this case, the configurations present data about how much revenue different event types have generated, in order to gauge which events are the most profitable."
msgid "First, navigate to :menuselection:`Events app --> Reporting --> Revenues`, and switch to the pivot table view, by clicking the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right corner."
msgid "Next, open the :guilabel:`Measures` drop-down menu, and deselect the option for :guilabel:`Count`, because this report is only going to focus on revenues."
msgid "Then, click :icon:`fa-plus-square` :guilabel:`Total` above the column titles, and select :guilabel:`Event Type` from the resulting drop-down menu."
msgid "With these configurations in place, all the revenues generated from the events (and their corresponding registrations) are displayed, organized by the event type (presented as expandable columns)."
msgid "First, navigate to :menuselection:`Events app --> Configuration --> Settings`. In the :guilabel:`Registration` section, there are two different settings: :guilabel:`Tickets` and :guilabel:`Online Ticketing`."
msgid "If these options are *not* enabled, a default :guilabel:`Register` button becomes available for visitors to interact with and procure free registrations to the event."
msgid "With those settings enabled, Odoo automatically creates a new *Product Type* called, *Event Ticket*, which is accessible on every product form. Odoo also creates three event registration products (with the *Product Type* set to *Event Ticket*) that can be used or modified for event tickets."
msgid "When creating a new event registration product, the *Product Type* **must** be set to *Event Ticket* on the product form, in order for it to be selected in the *Product* column under the *Tickets* tab on an event form."
msgid "Any event with paid tickets sold, features a :icon:`fa-dollar` :guilabel:`Sales` smart button at the top of the event form, where the respective sales orders attributed to those ticket sales become available."
msgid "Clicking the :icon:`fa-dollar` :guilabel:`Sales` smart button reveals a separate page, showcasing all the sales orders (standard and/or online) related to tickets that have been sold for that specific event."
msgid "To sell event tickets with sales orders, start by navigating to the :menuselection:`Sales` app. Then, click :guilabel:`New` to open a new quotation form."
msgid "After filling out the top portion of the form with the appropriate customer information, click :guilabel:`Add a product` in the :guilabel:`Order Lines` tab. Then, in the :guilabel:`Product` column, select (or create) an event registration product configured with its :guilabel:`Product Type` set to :guilabel:`Event Ticket` on its product form."
msgid "From the :guilabel:`Configure an event` pop-up window, select to which event this ticket purchase is related to in the :guilabel:`Event` field drop-down menu. Then, in the :guilabel:`Event Ticket` drop-down menu, select which ticket tier the customer wishes to purchase, if there are multiple tiers configured for that event."
msgid "When all the desired configurations are complete, click :guilabel:`Ok`. Doing so returns the user to the sales order, with the event registration ticket product now present in the :guilabel:`Order Lines` tab. The user can proceed to confirm and close the sale, per the usual process."
msgid "To re-open the *Configure an event* pop-up window, hover over the event registration product name in the :guilabel:`Order Lines` tab, and click on the :icon:`fa-pencil` :guilabel:`(pencil)` icon."
msgid "When a visitor arrives on the register page of the event website, they can click the :guilabel:`Register` button to purchase a ticket to the event."
msgid "If the visitor is *not* already on the register page of the event website, clicking :guilabel:`Register` on the event website's submenu redirects them to the proper register page. From there, they can click the :guilabel:`Register` button to begin the ticket purchasing process."
msgid "From here, visitors select which ticket tier they would like to purchase, along with a quantity, using the numerical drop-down menu available to the right of their desired ticket. Once the desired selections have been entered, the visitor then clicks the :guilabel:`Register` button."
msgid "Then, an :guilabel:`Attendees` pop-up window appears, containing all the questions that have been configured in the *Questions* tab of the event form for this particular event."
msgid "If multiple tickets are being purchased at once, there are numbered sections for each individual ticket registrant, each containing the same questions. However, if any question has been configured with the *Ask once per order* setting, that question is only asked once -- and **not** for every attendee making the reservation in the order."
msgid "With all necessary information entered, the visitor can then click the :guilabel:`Go to Payment` button. Doing so first takes the visitor to a :guilabel:`Billing` confirmation page, followed by a :guilabel:`Payment` confirmation page, where they can utilize any configured payment method set up in the database to complete the order."
msgid "Then, once the purchase is complete on the front-end of the website, the subsequent sales order is instantly accessible in the back-end of the database."
msgid "With Odoo *Events*, users can utilize a fully-integrated event website, where attendees can quickly access various tracks (talks, presentations, etc.), view entire agendas, and propose talks for the event."
msgid "To access an event website, navigate to the specific event form in the Odoo *Events* app, and click the :guilabel:`Go to Website` smart button. Or, while on the Odoo-built website for the company, click the :guilabel:`Events` header option, and select the desired event to view that event's website."
msgid "With the *Schedule & Tracks* setting enabled in the Odoo *Events* app, the following links are automatically added to the subheader menu, located on the event website: :guilabel:`Talks`, :guilabel:`Talk Proposals`, and :guilabel:`Agenda`."
msgid "The first drop-down filter menu (with the starting title: :guilabel:`Favorites`) is the only drop-down filter menu that appears by default. When clicked, the resulting menu presents two options: :guilabel:`Favorites` and :guilabel:`All Talks`."
msgid "The other drop-down filter menus that appear on this page are related to any configured tags (and tag categories) created for event tracks in the backend."
msgid "To add tags and tag categories to track forms, open a desired event track form, and start typing a new tag in the :guilabel:`Tags` field. Then, click :guilabel:`Create and edit...` from the resulting drop-down menu."
msgid "From here, users see the recently added tag in the :guilabel:`Tag Name` field. Beneath that, there is an option to add a specific :guilabel:`Color Index` to the tag for added organization."
msgid "All options in the :guilabel:`Category` field for tags appear as their own drop-down filter menu on the :guilabel:`Talks` page, located on the event website."
msgid "Beneath the drop-down filter menus at the top of the :guilabel:`Talks` page, there is a list of planned tracks for the specific event, organized by day."
msgid "If an attendee wishes to favorite a track, they can click the :icon:`fa-bell-o` :guilabel:`(empty bell)` icon, located to the right of the track title. Attendees will know a track has been favorited when they notice the icon has been changed to :icon:`fa-bell` :guilabel:`(filled bell)` icon."
msgid "Favoriting a track this way places it on the list of :guilabel:`Favorites`, which is accessible from the default drop-down filter menu, located at the top of the :guilabel:`Talks` page."
msgid "The :guilabel:`Talk Proposals` link takes attendees to a page on the event website, wherein they can formerly submit a proposal for a talk (:dfn:`track`) for the event, via a custom online form."
msgid "In addition to the form, an introduction to the page, along with any other pertinent information related to the types of talks the event will feature can be added, if needed."
msgid "The talk proposal form can be modified in a number of different ways, via the web builder tools, accessible by clicking :guilabel:`Edit` while on the specific page."
msgid "Then, proceed to edit any of the default fields, or add new forms with the :guilabel:`Form` building block (located in the :guilabel:`Blocks` section of the web builder tools sidebar)."
msgid "Then, that talk, and all the information entered on the form, can be accessed on the :guilabel:`Event Tracks` page for that specific event in the :guilabel:`Proposal` stage, which is accessible via the :guilabel:`Tracks` smart button on the event form."
msgid "If accepted, the internal user can then move the track to the next appropriate stage in the Kanban pipeline on the :guilabel:`Event Tracks` page for the event. Then, they can open that track form, and click the :guilabel:`Go to Website` smart button to reveal that track's page on the event website."
msgid "From there, they can toggle the :guilabel:`Unpublished` switch in the header to :guilabel:`Published`, which allows all event attendees to view and access the talk."
msgid "The :guilabel:`Agenda` link takes attendees to a page on the event website, showcasing an event calendar, depicting when (and where) events are taking place for that specific event."
msgid "Use the Odoo **Marketing Automation** application to create dynamic campaigns with actions that automatically occur within a defined duration, such as sending a series of timed mass emails or engaging with leads based on their interactions with marketing campaigns."
msgid "While the application is designed to be user-friendly for creating, launching, and reviewing marketing campaigns, it also provides advanced features to automate repetitive tasks throughout the database."
msgid "Get started by creating a :ref:`new campaign from scratch <marketing_automation/campaigns>` or start with a :ref:`campaign template <marketing_automation/campaign-templates>`."
msgid "Installing the **Marketing Automation** application also installs the :doc:`Email Marketing <email_marketing>` app, as most features of Odoo **Marketing Automation** are dependent on that specific application."
msgid "Additionally, install the :doc:`CRM <../sales/crm>` and :doc:`SMS Marketing <sms_marketing>` applications to access *all* of the features available in **Marketing Automation**."
msgid "A *campaign* refers to a workflow of activities that are automatically executed to a target audience, based on predefined filters, triggers, and durations of activities."
msgid "To create a campaign, navigate to the :menuselection:`Marketing Automation` application and click the :guilabel:`New` button to reveal a new campaign form."
msgid "Odoo provides six campaign templates to help users get started. The campaign template cards **only** display when there are no existing campaigns in the database. Once a campaign has been created, the template cards on the *Campaigns* dashboard are replaced with a Kanban view of the existing campaigns."
msgid "To get started with a template, navigate to the :menuselection:`Marketing Automation` application, from the main Odoo dashboard, to open the :guilabel:`Campaigns` dashboard, which displays six :doc:`campaign template <marketing_automation/campaign_templates>` cards:"
msgid "These templates are designed to be used as starting points for creating new campaigns. Click one of the template cards to open the campaign form."
msgid "To display the campaign template cards again after a campaign has been created, type the name of a campaign that does **not** exist in the database into the search bar, then press :kbd:`Enter`."
msgid "For example, searching for `empty` displays the campaign template cards again, as long as there is not a campaign with the name \"empty\" in the database."
msgid "On the campaign form, the :guilabel:`Target` and :guilabel:`Filter` section, also referred to as the domain, contains the fields used to define the target audience for the campaign's reach (i.e., the unique contact records in the database)."
msgid "The target audience specifies the type of records available for use in the campaign, such as *Lead/Opportunity*, *Event Registration*, *Contact*, and more."
msgid "The number of records that are displayed next to the campaign :guilabel:`Filter` represent the total number of records the campaign is targeting."
msgid "The number of participants engaged in a test run are shown in the *Tests* smart button, which displays on the top of the campaign form after a test has been run."
msgid "The number of participants engaged in a running, or stopped, campaign are shown in the *Participants* smart button at the top of the campaign form."
msgid "A *workflow* consists of an activity, many activities, or a sequence of activities organized in a campaign. A campaign's workflow is defined in the :guilabel:`Workflow` section of the campaign form."
msgid "*Activities* are the methods of communication or server actions, organized in a workflow, that are executed within a campaign. Once running, each activity displays the number of participants that are engaged by the activity as *Success* and *Rejected* counts."
msgid "Once a campaign has been created, it can be tested to ensure the workflow is functioning as expected, to check for errors, and correct any mistakes before it reaches its target audience."
msgid "After testing, the campaign can be launched to start engaging the target audience. The campaign can also be launched *without* testing, if the user is confident in the workflow."
msgid "A range of reporting metrics are available to measure the success of each campaign. Navigate to :menuselection:`Marketing Automation app --> Reporting` to access the following menu options:"
msgid "A *double opt-in*, also referred to as a *confirmed opt-in*, may be required in some countries for marketing communications, due to anti-SPAM laws. Confirming consent has several other benefits, as well: it validates email addresses, avoids spam/robo subscribers, keeps mailing lists clean, and only includes engaged contacts in the mailing list."
msgid "When the *Double Opt-in* campaign template is used, a new mailing list titled, *Confirmed contacts* is created in the *Email Marketing* app, and any new mailing list contacts that are added to the default *Newsletter* mailing list are sent a confirmation email to double opt-in. The contacts that click on the confirmation link in the email are automatically added to the *Confirmed contacts* mailing list in Odoo."
msgid "When using the *Double Opt-in* campaign template, only the contacts in the *Confirmed contacts mailing* list are considered to have confirmed their consent."
msgid "Open the :menuselection:`Marketing Automation` app, and select the :guilabel:`Double Opt-in` campaign template to create a new campaign for confirming consent."
msgid "The campaign templates do **not** display, by default, when there are existing *Marketing Automation* campaigns. To display the campaign templates, type the name of a campaign (that does not exist in the database) into the :guilabel:`Search...` bar, then press :kbd:`Enter`."
msgid "The :guilabel:`Target` model of the campaign should **not** be modified. Changing the :guilabel:`Target` model with activities in the :guilabel:`Workflow` invalidates the existing activities in the :guilabel:`Workflow`."
msgid "The campaign loads two activities in the :guilabel:`Workflow` section of the campaign: an email activity, with a child server action activity that triggers *on click*."
msgid "By default, the `Confirmation` email activity is set to trigger :guilabel:`1 Hours` after the beginning of the workflow. In other words, the email is sent 1 hour after a new contact is added to the *Newsletter* mailing list."
msgid "The email activity uses the preconfigured *Confirmation* email template, which contains a button for the contact to click to confirm their consent."
msgid "To modify the email template, select the :icon:`fa-envelope-o` :guilabel:`Templates` smart button at the top of the campaign form. Then, in the list of templates, select the `Confirmation` email template."
msgid "Be sure to personalize the contents of the email template; however, it is recommended to keep the contents of double opt-in confirmation emails short and to-the-point."
msgid "The default confirmation button, in the body of the template, links directly to the database's website homepage. Click on the button to edit the button text and URL."
msgid "To provide a streamlined experience for the contact, consider :doc:`creating a page on the website <../../../websites/website/pages>` that expresses gratitude to the contact for confirming their subscription to the mailing list. Add the link to that page in the URL of the confirmation button."
msgid "The child activity *Add to list* server action's *On click* trigger cannot differentiate between multiple URLs in an email, besides the `/unsubscribe_from_list` unsubscribe button that is included in any one of the footer blocks."
msgid "When triggered, the `Add to list` activity executes the *Add To Confirmed List* server action, automatically adding the contact to the *Confirmed contacts* mailing list, if they are not already in the mailing list."
msgid "To modify the server action, select the title of the activity to open the :guilabel:`Open: Activities` pop-up window and edit the server action activities configuration."
msgid "It is not recommended to modify the preconfigured Python code in the :guilabel:`Add To Confirmed List` server action, as doing so may trigger a change in the database's pricing plan."
msgid "Once the campaign configuration is complete, consider :doc:`launching a test <../testing_running>` to verify the campaign executes as expected. If the campaign testing is successful, :guilabel:`Start` the campaign to begin sending double opt-in confirmation emails to *Newsletter* mailing list contacts, and fill the *Confirmed contacts* mailing list with engaged contacts."
msgid "To prepare for sending newsletter marketing emails on an Odoo database, a mailing contact list must be procured. One way of collecting subscribers is through a sign-up form on the website that adds contacts to the *Newsletter* mailing list on the form submission."
msgid "Before sending any marketing emails, :ref:`use the Double Opt-in campaign template <marketing_automation/template/using-double-optin>` in the *Marketing Automation* app to confirm marketing email consent from the contacts in the *Newsletter* mailing list."
msgid "After launching the *Double Opt-in* campaign, view the contacts that have double opt-in in the *Confirmed contacts* mailing list (:menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists`)."
msgid "The :guilabel:`Target` and :guilabel:`Filter` fields on the campaign form, also referred to as the *domain*, contain the parameters used to define the target audience for the campaign's reach (i.e., the unique contact records in the database, and imported list, etc.)."
msgid ":guilabel:`Target`: specifies the type of records available for use in the campaign, such as :guilabel:`Lead/Opportunity`, :guilabel:`Event Registration`, :guilabel:`Contact`, The assigned records model determines the fields that are available throughout the campaign, including the fields available in the :guilabel:`Filter` section, and in dynamic placeholders."
msgid ":guilabel:`Save as Favorite Filter`: saves the current :guilabel:`Filter` for future use with the current :guilabel:`Target` model, and can be managed from the :menuselection:`Marketing Automation app --> Configuration --> Favorite Filters` menu."
msgid ":guilabel:`Unicity based on`: specifies the :guilabel:`Target` model field where duplicates should be avoided. Traditionally, the :guilabel:`Email` field is used, but any available field can be used."
msgid ":guilabel:`Filter`: contains an interactive form with configurable logic to further refine the targeting parameters under the chosen :guilabel:`Target` model. See more details in the :ref:`marketing_automation/defining-filters` section."
msgid "Each activity in a campaign's workflow can target a subset of the target audience; see the :doc:`workflow_activities` documentation for more information."
msgid "The default campaign :guilabel:`Filter` configuration is set to :guilabel:`Match all records`, indicating that the campaign is targeting **all** records of the :guilabel:`Target` model."
msgid "To refine the :guilabel:`Filter` rules of a campaign, click the :guilabel:`➕ Add condition` button to reveal a new row with configurable rule parameters. See the :ref:`Search, filter, and group records <search/custom-filters>` documentation for more information on how to create filter rules."
msgid "At the bottom of the filter rules is a :guilabel:`# record(s)` button, which indicates the total number of records targeted by this domain. Select the :guilabel:`# record(s)` button to open a :guilabel:`Selected records` pop-up window, in which the targeted records can be viewed."
msgid "Activate :ref:`developer-mode` to reveal each field's technical name and data type, as well as the :guilabel:`# Code editor` text area below the filter rules, to view and edit the domain manually."
msgid "To target all leads and opportunities from the *CRM* app that are in the *New* stage, and have an expected revenue greater than $1,000, the following should be entered:"
msgid "The Odoo *Marketing Automation* app allows users to test marketing campaigns (and mailings) before officially running them to check for errors and correct any mistakes before it reaches its target audience."
msgid "To test a marketing campaign, open the :menuselection:`Marketing Automation app`, and select the desired campaign to test, which reveals the campaign's detail form."
msgid "On the campaign detail form, make sure the campaign already has activities configured in the workflow (or build a campaign by following the directions on :doc:`workflow_activities` documentation)."
msgid "Testing marketing automation campaigns is meant to be performed in the production version of the database. Duplicate (or trial) databases have limited email sending capabilities."
msgid "In the :guilabel:`Launch a test` pop-up window, click the :guilabel:`Pick or create a/an Contact to generate a Test Participant` field to reveal a drop-down menu of contacts. From this drop-down menu, select an existing contact (or create a new one) to run the test on."
msgid "To create a new contact directly from the :guilabel:`Launch a test` pop-up window, start typing the name of the new contact in the blank field, and click :guilabel:`Create and edit...`."
msgid "Doing so reveals a blank :guilabel:`Create Record` pop-up form, in which the necessary contact information (:guilabel:`Email`, :guilabel:`Mobile`, etc.) *must* be entered, in order for the test to work. When the necessary information is entered, click :guilabel:`Save & Close`."
msgid "On the campaign test page, the name of the :guilabel:`Record` being tested is visible, along with the precise time this test workflow was started in the :guilabel:`Workflow Started On` field. Beneath that, in the :guilabel:`Workflow` section is the first activity (or activities) in the workflow that's being tested."
msgid "To start a test, click the :guilabel:`Run` button, represented by a :guilabel:`▶️ (play button)` icon beside the first activity in the workflow. When clicked, the page reloads, and Odoo shows the various results (and analytics) connected to that specific activity as they occur, in real-time."
msgid "If a child activity is scheduled beneath a parent activity, that child activity will be revealed slightly indented in the workflow, once that parent activity has been run, via the :guilabel:`▶️ (play button)` icon."
msgid "Once all the workflow activities are completed, the test ends, and the status bar (in the upper-right corner) moves to the :guilabel:`Completed` stage."
msgid "To stop a test before all the workflow activities are completed, click the :guilabel:`Stop` button in the upper-left corner of the campaign test page."
msgid "On the campaign detail form, with all the desired activities ready in the :guilabel:`Workflow` section, click :guilabel:`Start` in the upper-left corner to officially run the campaign to the configured target audience specified on the campaign detail form."
msgid "Clicking :guilabel:`Start` launches the campaign, and the status bar of the campaign switches to :guilabel:`Running`, which is located in the upper-right corner of the campaign detail form."
msgid "If some participants are already running on a campaign, and was stopped for any reason, clicking the :guilabel:`Start` button again prompts a pop-up warning. This warning advises the user to click an :guilabel:`Update` button to apply any modifications made to the campaign."
msgid "Be aware that participants that had already gone through an entire campaign in its original state **can** be reintroduced into the newly-modified campaign, and new traces could be created for them."
msgid "Then, as the mailings and actions are triggered in the :guilabel:`Workflow`, the various stats and data related to each activity appear in each activity block. There is also a series of stat-related smart buttons that appear at the top of the campaign detail form, as well."
msgid "These analytical smart buttons will *also* populate with real-time data as the campaign progresses: :guilabel:`Templates`, :guilabel:`Clicks`, :guilabel:`Tests`, :guilabel:`Participants`."
msgid "To stop a campaign that's currently running, navigate to the :menuselection:`Marketing Automation app`, and select the desired campaign to stop. On the campaign detail form, click the :guilabel:`Stop` button in the upper-left corner."
msgid "When clicked, the campaign is officially stopped, and the status changes to :guilabel:`Stopped` in the upper-right corner of the campaign detail form."
msgid "*Campaign metrics* are detailed statistics and analytics within a marketing campaign, measuring its success and effectiveness. Triggered marketing activities populate relevant activity blocks with real-time metrics, in the campaign detail form."
msgid "In the :guilabel:`Workflow` section of a campaign detail form in the *Marketing Automation* app, where the various campaign activities are located, a collection of useful data can be found on every individual activity block, like number of communications :guilabel:`Sent`, percentage of messages that have been :guilabel:`Clicked`, and more."
msgid "To the left of the activity block, the configured :doc:`trigger time <workflow_activities>` is displayed as a duration (either :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, or :guilabel:`Months`) if it corresponds to period after the workflow begins."
msgid "If the trigger time is dependent on another activity or triggering action (e.g. :guilabel:`Mail: Replied`, etc.) the time is displayed, along with the necessary action for that activity to be activated (e.g. `Replied after 2 Hours`)."
msgid "In the activity block, an icon represents each activity type. An :guilabel:`✉️ (envelope)` icon means the activity is an email. Three tiny, interlocking :guilabel:`⚙️ (gear)` icons means the activity is an internal action. And, a small, basic :guilabel:`📱 (mobile)` icon means the activity is an SMS."
msgid "Beside the activity icon, at the top of the activity block, is the title of the activity. To the right of the activity title, there are :guilabel:`Edit` and :guilabel:`Delete` buttons."
msgid "Click :guilabel:`Edit` to open the :guilabel:`Open: Activities` pop-up form for that specific activity, in which that activity can be modified. Click the :guilabel:`Delete` button to completely delete that specific activity from the workflow."
msgid "In every activity block, the :guilabel:`Graph (pie chart icon)` tab is open by default, displaying related metrics as a simple line graph. The success metrics are represented in `green` and the rejected metrics are represented in `red`."
msgid "Beneath the graph in the activity block, for *Email* or *SMS* activity types, a line of accessible data figures provide a bird's eye view of the campaign activity, including: :guilabel:`Sent` (numerical), :guilabel:`Clicked` (percentage), :guilabel:`Replied` (percentage), and :guilabel:`Bounced` (percentage)."
msgid "Clicking any of those stats on the :guilabel:`DETAILS` line, beneath the line graph, reveals a separate page containing every specific record for that particular data point."
msgid "Next to the :guilabel:`Graph` tab on the activity block, there's the option to open a :guilabel:`Filter` tab (represented by a :guilabel:`filter/funnel` icon)."
msgid "Clicking the :guilabel:`Filter` tab on an activity block, reveals what the specific filters are for that particular campaign activity, and how many records in the database match that specific criteria."
msgid "Clicking the :guilabel:`records` link beneath the displayed filter reveals a separate pop-up window containing a list of all the records that match that specific campaign activity rule(s)."
msgid "Odoo tracks all URLs used in marketing campaigns. To access and analyze those URLs, navigate to :menuselection:`Marketing Automation app --> Reporting --> Link Tracker`. Doing so reveals a :guilabel:`Link Statistics` page, wherein all campaign-related URLs can be analyzed."
msgid "The default view on the :guilabel:`Link Statistics` page is the :guilabel:`Bar Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Pie Chart`."
msgid "Beside that, there is also the option to view the statistics as :guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or :guilabel:`Ascending` order."
msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Number of Clicks` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button."
msgid "Also, in the upper-right corner of the :guilabel:`Link Statistics` page, to the far-right of the search bar, there are additional view options to choose from: the default :guilabel:`Graph` view, the :guilabel:`Pivot` table view, and the :guilabel:`List` view."
msgid "Odoo tracks all activities used in every marketing campaign. The data related to these activities can be accessed and analyzed in the :guilabel:`Traces` page, which can be found by navigating to :menuselection:`Marketing Automation app --> Reporting --> Traces`."
msgid "The default view on the :guilabel:`Traces` page is the :guilabel:`Bar Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Pie Chart`."
msgid "At the top of the graph, there's a color key, informing the user which activities have been :guilabel:`Processed`, :guilabel:`Scheduled`, and :guilabel:`Rejected`. There's also an outline indicator to inform users of the :guilabel:`Sum` of certain activities, as well."
msgid "Beside the various view option in the upper-left corner of the :guilabel:`Traces` page, there is also the option to view the statistics as :guilabel:`Stacked`, and the data can be put into :guilabel:`Descending` or :guilabel:`Ascending` order."
msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Document ID` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button."
msgid "Odoo tracks all participants related to every marketing campaign. The data related to these participants can be accessed and analyzed in the :guilabel:`Participants` page, which can be found by navigating to :menuselection:`Marketing Automation app --> Reporting --> Participants`."
msgid "The default view on the :guilabel:`Participants` page is the :guilabel:`Pie Chart` view, but there are different view options available in the upper-left corner. There is the option to view the statistics as a :guilabel:`Line Chart` or :guilabel:`Bar Chart`."
msgid "To the far-left of the view options, there is the :guilabel:`Measures` drop-down menu. When clicked, the options to view the :guilabel:`Record ID` or total :guilabel:`Count` are available. And, to the right of the :guilabel:`Measures` drop-down menu, there's the ability to add any data to a spreadsheet by clicking the :guilabel:`Insert in Spreadsheet` button."
msgid "A *workflow* is the overall *activity* structure of a marketing automation campaign. There can only be a single workflow in each campaign. However, a workflow can be made up of any number of :ref:`activities <marketing_automation/activities>` to meet the needs of the campaign."
msgid "Workflow sequence of three activities; the last child activity has a :ref:`trigger type <marketing_automation/trigger-type>` of **Mail: not opened**."
msgid "Activities are the methods of communication or server actions, organized in a workflow, that are executed within a campaign; they are the building blocks of the campaign's workflow."
msgid "A new activity can be added to the workflow on a campaign form by selecting an existing campaign or :ref:`creating a new campaign <marketing_automation/campaigns>` from the :menuselection:`Marketing Automation app --> Campaigns` dashboard, then clicking the :guilabel:`Add new activity` button in the :guilabel:`Workflow` section. Doing so opens the :guilabel:`Create Activities` pop-up window."
msgid "First, define the name of the activity in the :guilabel:`Activity Name` field, and select the :ref:`type of activity <marketing_automation/activity-types>` to be executed from the :guilabel:`Activity Type` field."
msgid "Then, configure the activity's :ref:`Trigger <marketing_automation/trigger>`, and optionally, the :ref:`Expiry Duration <marketing_automation/expiry-duration>` and the :ref:`DOMAIN <marketing_automation/activity-domain>` of the activity."
msgid "Once the activity is fully configured, click :guilabel:`Save & Close` to add it to the campaign's workflow, or click :guilabel:`Save & New` to add the activity to the workflow and open a new :guilabel:`Create Activities` pop-up window to add another activity. Clicking :guilabel:`Discard` closes the pop-up window without saving the activity."
msgid "If :guilabel:`Email` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Template` in the :guilabel:`Mail Template` field is available."
msgid "To create a new template directly from the :guilabel:`Mail Template` field, start typing the title of the new template, then select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window. Proceed to create and configure the new email template."
msgid "Once the email template is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to continue to configure the :ref:`trigger <marketing_automation/trigger>`."
msgid "The title used for the :guilabel:`Mail Template` **must** be unique from any other mail template titles in the campaign, and it also serves as the subject of the email."
msgid "If :guilabel:`Server Action` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Server Action` in the :guilabel:`Server Action` field is available. This field is a drop-down menu containing all the pre-configured server actions for the campaign's :guilabel:`Target` model. Optionally, :ref:`create a new server action <marketing_automation/create-sa>`."
msgid "After selecting a pre-configured server action, no other activity type configuration is needed. Click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger <marketing_automation/trigger>`."
msgid "To view all server actions in the database, activate :ref:`developer-mode`, and navigate to :menuselection:`Settings app --> Technical --> Actions --> Server Actions` dashboard."
msgid "The option to create a new server action is also available. To do so, type in the :guilabel:`Server Action` field a title for the new action, then click :guilabel:`Create and edit...`. Doing so reveals a blank :guilabel:`Create Server Action` pop-up window, wherein a custom server action can be created and configured."
msgid "On the :guilabel:`Create Server Action` pop-up window, select the :guilabel:`Type` of server action. The configuration fields change, depending on the selected :guilabel:`Type`:"
msgid "Once the server action is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger <marketing_automation/trigger>`."
msgid "Some of the server action types have advanced configurations available when :ref:`developer-mode` is activated, such as specifying the :guilabel:`Allowed Groups` that can execute this server action."
msgid "If :guilabel:`SMS` is selected as the :guilabel:`Activity Type`, the option to :guilabel:`Pick a Template` in the :guilabel:`SMS Template` field is available."
msgid "To create a new template directly from the :guilabel:`SMS Template` field, start typing the title of the new template, and select :guilabel:`Create and edit...` to reveal a :guilabel:`Create Marketing Template` pop-up window. Proceed to create and configure the new SMS template."
msgid "Once the SMS template is configured, click :guilabel:`Save & Close` to save the activity, and return to the :guilabel:`Create Activities` pop-up window, in order to configure the :ref:`trigger <marketing_automation/trigger>`."
msgid "Once an :ref:`activity type <marketing_automation/activity-types>` is configured, the next step in the :guilabel:`Create Activities` pop-up window is to define when the activity should be executed. This is done in the :guilabel:`Trigger` field group."
msgid "To set an execution delay for the activity from when the :ref:`trigger type <marketing_automation/trigger-type>` occurs, type a whole number in the *interval number* input (e.g. `2` is valid, `0` is also valid, and `1.5` is not)."
msgid "Next, select the unit of time for the interval number in the *interval type* drop-down menu, the options are: :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`."
msgid "If the interval number is set to `0` and the interval type is set to :guilabel:`Hours`, the activity will be executed immediately after the trigger type occurs (at the next scheduled run of the :ref:`Mail: Email Queue Manager cron <email-issues-outgoing-execution-time>`)."
msgid "All other trigger types reveal a drop-down menu :guilabel:`Activity` field containing all of the other activities in the campaign. Selecting one of these types converts this activity into a :ref:`child activity <marketing_automation/child-activities>` to be executed directly after the selected :guilabel:`Activity`:"
msgid "If the trigger type is set to :guilabel:`Mail: clicked`, this activity is converted to a :ref:`child activity <marketing_automation/child-activities>` and will execute **after** a participant clicks on a link from the parent activity defined in the :guilabel:`Activity` field."
msgid "Optionally, an :guilabel:`Expiry Duration` can be defined in the :guilabel:`Create Activities` pop-up window to cancel the execution of this activity after a specific amount of time. Selecting this checkbox reveals the :guilabel:`Cancel after` field with *interval* and *interval type* inputs."
msgid "Type a whole number in the interval number input (e.g. `2` is valid, `0` is also valid, and `1.5` is not). Then, select the unit of time for the interval number in the interval type drop-down menu, the options are: :guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and :guilabel:`Months`."
msgid "If the interval number is set to `2` and the interval type is set to :guilabel:`Days`, the activity will be cancelled if it has not been executed within 2 days of the trigger type."
msgid "The :guilabel:`DOMAIN` section of the :guilabel:`Create Activities` pop-up window contains fields to further filter the target audience of the activity."
msgid "The :guilabel:`Activity Filter` field focuses this activity, **and** its :ref:`child activities <marketing_automation/child-activities>`, even further on a specific group of the campaign's filter. The process is the same as :ref:`defining filters <marketing_automation/defining-filters>` for the campaign, and the fields that are available to filter are also specific to the :guilabel:`Target` of the campaign."
msgid "The :guilabel:`# record(s)` beside the :guilabel:`Activity Filter` field indicates how many records are currently being targeted by this :guilabel:`Activity Filter`."
msgid "The :guilabel:`Applied Filter` displays the combined filters from the :guilabel:`Activity Filter` and the inherited campaign :doc:`Filter <target_audience>`. This field is read-only."
msgid "The :guilabel:`# record(s)` beside the :guilabel:`Applied Filter` field indicates how many records, in total, are currently being targeted by the activity."
msgid "A child activity can be added to a campaign's workflow by hovering over the :guilabel:`➕ Add child activity` button, located beneath the desired parent activity."
msgid "The child activity's :ref:`trigger types <marketing_automation/trigger-type>` are specific to the parent :ref:`activity type <marketing_automation/activity-types>` (*Email*, *SMS*, or *Server Action*), and are as follows:"
msgid "Once a trigger type is selected, the :guilabel:`Create Activities` pop-up window opens to configure the child activity. The process is the same as :ref:`creating a new activity <marketing_automation/activities>`, with the exception that the :guilabel:`Trigger` field is pre-filled with the selected trigger type, and the :guilabel:`Activity` field has the parent activity selected."
msgid "Utilizing :abbr:`SMS (Short Message Service)` outreach in communication strategies can help companies expand their market reach, especially in some countries, where emails might not be very common, or even used at all."
msgid "Odoo's *SMS Marketing* application can also help boost conversion rates around valuable actions, such as event registrations, free trials, purchases, etc., since text and mobile-based marketing channels typically yield higher :abbr:`CTOR (click-to-open rate)` and :abbr:`CTR (click-through rate)` outcomes."
msgid "When the application is opened, Odoo displays the main :guilabel:`SMS Marketing` dashboard, which showcases the various SMS mailings that have been created, along with pertinent information and data related to that specific message."
msgid "The :icon:`oi-view-kanban` :guilabel:`Kanban` view is the default Odoo uses when the application is opened, which provides an organized display of the SMS mailings that have been created, and what their current status is at the moment."
msgid "An :abbr:`SMS (Short Message Service)` mailing can have one of the following statuses: :guilabel:`Draft`, :guilabel:`In Queue`, :guilabel:`Sending`, or :guilabel:`Sent`."
msgid "In the upper right corner of the main :guilabel:`SMS Marketing` dashboard, there are a few different view options to choose from. Each one provides a unique take on the same SMS information."
msgid "The :icon:`fa-calendar` :guilabel:`Calendar` view shows when SMS mailings are scheduled or have been sent. Clicking a future date opens a blank SMS template to be scheduled for that date."
msgid "Lastly, the :icon:`fa-area-chart` :guilabel:`Graph` view visualizes that same SMS-related data in series of graphs and charts. Odoo also provides various ways to sort and group the data for more detailed analysis."
msgid "To start, click :guilabel:`Create` on the main :guilabel:`SMS Marketing` dashboard, and Odoo reveals a blank SMS template form, which can be configured in a number of different ways."
msgid "Next, in the :guilabel:`Recipients` field, choose to whom this :abbr:`SMS (Short Message Service)` will be sent. By default, Odoo has :guilabel:`Mailing List` selected. If this is the desired :guilabel:`Recipients` field option, specify which mailing list Odoo should send this :abbr:`SMS (Short Message Service)` to in the :guilabel:`Select Mailing List` field."
msgid "To create (or edit) a mailing list, go to :menuselection:`Mailing Lists --> Mailing List`. There, Odoo displays all previously created mailing lists, along with various types of data related to that specific list (e.g. number of contacts, mailings, recipients, etc.)."
msgid "When another field (other than :guilabel:`Mailing List`) is selected, the option to specify that chosen field even further becomes available — either with a default recipient filter equation that appears automatically (which can be customized to fit any business need), or, if no default recipient filter equation is present, an :guilabel:`Add Filter` button will appear."
msgid "Clicking the :guilabel:`Add Filter` button, reveals fully customizable domain rule fields, which can be configured similar to an equation. You can create multiple recipient rules, if necessary."
msgid "Then, Odoo will only send the :abbr:`SMS (Short Message Service)` to recipients who fit into whatever criteria is configured in those fields. Multiple rules can be added."
msgid "If :guilabel:`Contact` is chosen, all of the *Contacts* records in the Odoo database (vendors, customers, etc.) will receive the :abbr:`SMS (Short Message Service)`, by default — unless more specific recipient rules are entered."
msgid "For instance, the message below will only be sent to contacts in the database that are located in the United States (e.g. `Country` > `Country Name` equals `United States`), and they haven't blacklisted themselves from any mailings (e.g. `Blacklist` > `is` > `not set`)."
msgid "Enter the content of the :abbr:`SMS (Short Message Service)` in the text field, found in the :guilabel:`SMS Content` tab. Links and emojis can also be included. Beneath the text field, Odoo displays how many characters are used in the message, along with how many :abbr:`SMS (Short Message Service)` mailings it will take to deliver the complete message."
msgid "Credits must be purchased from Odoo in order to take advantage of the *SMS Marketing* app; :abbr:`SMS (Short Message Service)` messages will not be sent without credits."
msgid "When links are used in :abbr:`SMS (Short Message Service)` messages, Odoo automatically generates link trackers to gather analytical data and metrics related to those specific links, which can be found by going to :menuselection:`Configuration --> Link Tracker`."
msgid "Under the :guilabel:`Settings` tab of the SMS template, there is an option to :guilabel:`Include opt-out link`. If activated, the recipient is able to unsubscribe from the mailing list, thus avoiding all future mailings."
msgid ":guilabel:`Send`: sends the message immediately. Consider using this option if the recipient list is highly refined, or in cases that involve fast approaching deadlines, such as a \"flash sale.\""
msgid ":guilabel:`Schedule`: choose a day (and time) for Odoo to send the mailing. This is typically the best option for mailings related to a specific event. Such a method can also be used to promote a limited-time offer, or to help plan a company's content strategy in advance."
msgid ":guilabel:`Test`: allows for an :abbr:`SMS (Short Message Service)` to be sent to one or multiple numbers for test purposes. Remember to use a comma between phone numbers if multiple numbers are used as recipients."
msgid "Creating or importing mailing lists in Odoo is very useful when curating content to specific groups of people that already share similar demographics or interests. Mailing lists are also a great way to get started if a company is migrating from another system, and already has a established audience."
msgid "Moreover, providing an audience with the option to 'unsubscribe' from mailings, helps businesses maintain good customer relations, by giving recipients the power to control what they are (and aren't) sent."
msgid "In the :guilabel:`SMS Marketing` app, there's an option on the header menu called :guilabel:`Mailing Lists`. When clicked, a sub-menu is revealed with options for :guilabel:`Mailing Lists` and :guilabel:`Mailing List Contacts`."
msgid "To create a new mailing list, click :guilabel:`Create` in the upper left corner of the :guilabel:`Mailing Lists` page. Doing so, will reveal a blank mailing list template form."
msgid "First, choose a name for the :guilabel:`Mailing List`, and activate the option :guilabel:`Is Public`, to make the mailing list accessible to recipients on the :guilabel:`Subscription Management page`. Doing so allows users to update their subscription preferences at any time."
msgid "When those fields are filled in, click :guilabel:`Create` to finalize the form. Then on the main :guilabel:`Mailing Lists` dashboard, the new mailing list that was just created will be accessible."
msgid "To edit or customize the mailing list further, select the mailing list from the main :guilabel:`Mailing Lists` page to reveal the mailing list detail form."
msgid "Along the top of the mailing list detail form, there are various analytical smart buttons displaying statistics for different metrics related to the mailing list (e.g. :guilabel:`Recipients`, :guilabel:`Mailings`, etc.)."
msgid "To review or edit any of those elements, click the desired smart button to reveal a separate page with in-depth data associated with the mailing list."
msgid "Access contacts information from one or more mailing lists navigate to :menuselection:`Mailing Lists --> Mailing List Contacts` to reveal a dashboard with with all the contacts associated with one or more of the configured mailing lists in the database."
msgid "By default, Odoo reveals the :guilabel:`Mailing List Contacts` page with the :guilabel:`Exclude Blacklisted Phone` filter in the search bar. Therefore only showing contact information for recipients who still want to receive communications and mailings."
msgid "An accessible record of every sent mailing(s) is kept on each recipient's *chatter* section, located beneath a recipient's contact form (in the *Contacts* application)."
msgid "Database users can reference the chatter to easily keep track of communications, and see a history of interactions with contacts and prospects."
msgid "For example, sales representatives can use the chatter to quickly find out which :abbr:`SMS (Short Message Service)` mailing promotions a certain customer has received (or not received)."
msgid "Odoo *SMS Marketing* has a :guilabel:`Blacklist` feature that provides recipients with the power to add their phone number to a list of people who no longer want to receieve communications or mailings."
msgid "This is also known as the unsubscribe process: customers will automatically be added onto a *blacklist*, if they click :guilabel:`Unsubscribe`, via their :guilabel:`Subscription Management` page. Customers can also be added manually to the blacklist, if necessary."
msgid "To see a complete collection of blacklisted numbers, navigate to the :menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone Numbers` to reveal a dashboard containing every blacklisted phone number in the database."
msgid "To manually add a number to a blacklist, click the :guilabel:`Create` button in the upper-left corner of the dashboard and enter the phone number on the next page's form. There's also a checkbox to indicate whether that particular phone numnber is :guilabel:`Active` (or not)."
msgid "Once the form is completed, click :guilabel:`Save` to add it to the :guilabel:`Blacklisted Phone Numbers` list. To remove any number from the blacklist, select the desired number on the dashboard, and then, on the phone number's form, click :guilabel:`Unblacklist`."
msgid "During a software/platform migration, it is possible to import an already existing blacklist of contacts. This would include customers, who have already asked to be blacklisted` on :abbr:`SMS (Short Message Service)` mailings."
msgid "To do that, navigate to :menuselection:`SMS Marketing app --> Configuration --> Blacklisted Phone Numbers`, and then select the :guilabel:`Favorites` drop-down menu (beneath the search bar), and click :guilabel:`Import records`."
msgid "Utilizing :abbr:`SMS (Short Message Service)` campaigns with Odoo *SMS Marketing* isn't just an effective advertisement strategy, it's also a great way to remind people about upcoming events, issued invoices, and so much more."
msgid "But, before :abbr:`SMS (Short Message Service)` campaigns can be created (and sent), a few specific settings and features must be enabled first."
msgid "To enable :abbr:`SMS (Short Message Service)` campaigns in Odoo, make sure the *Mailing Campaigns* feature is activated by going to :menuselection:`Email Marketing --> Configuration --> Settings`, and then enable :guilabel:`Mailing Campaigns` and :guilabel:`Save` the changes."
msgid "Once the setting is enabled, navigate back to the :menuselection:`SMS Marketing` app, and notice the :guilabel:`Campaigns` header menu is now available for use. Similarly, the :guilabel:`A/B Test` tab is now also available on every :abbr:`SMS (Short Message Service)` template form."
msgid ":guilabel:`A/B Tests` allows any :abbr:`SMS (Short Message Service)` mailings to be tested against other versions within the same campaign, in order to compare which version is the most successful in producing engagement and/or conversion outcomes."
msgid "On an :abbr:`SMS (Short Message Service)` template form, under the :guilabel:`A/B Tests` tab, initially, there's only a single checkbox labeled: :guilabel:`Allow A/B Testing.`"
msgid "Beneath the percentage field is the :guilabel:`Winner Selection` field. This is what Odoo will use to determine the successful result of an A/B Test. In other words, this tells Odoo how to pick a winning A/B test."
msgid "The following sections are available: :guilabel:`Manual`, :guilabel:`Highest Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or :guilabel:`Revenues`."
msgid "Finally, the :guilabel:`Send Final On` field is listed. This represents the date-time that Odoo uses as a deadline to determine the winning mailing variation. Then, Odoo sends that winning mailing variation to the remaining recipients, who weren't involved in the test, at that prior date and time."
msgid "To create, edit, or analyze any campaign, click :menuselection:`Campaigns` in the header menu of the :guilabel:`SMS Marketing` app. On the :guilabel:`Campaigns` page, each campaign displays various information related to the mailings associated with that campaign (e.g. number of emails, social posts, SMSs, and push notifications)."
msgid "Click :guilabel:`Create` to create a new campaign, and Odoo reveals a blank campaign template form to fill out. Alternatively, select any previously-made campaign in order to duplicate, review, or edit its campaign template form."
msgid "With each campaign, the options to :guilabel:`Send New Mailing`, :guilabel:`Send SMS`, :guilabel:`Send Social Post`, and :guilabel:`Push Notifications` are available above the template form."
msgid "Whenever one of those communication options is added to the campaign, Odoo will create a new corresponding tab on the template form, where those types of messages can be reviewed or edited, along with various data sets related to each specific mailing."
msgid "At the top of the template, there are various analytical smart buttons. When clicked, Odoo reveals in-depth metrics related to that specific topic (e.g. :guilabel:`Engagement`, :guilabel:`Opportunities`, etc.) on a separate page."
msgid "Beneath the smart buttons, are fields for :guilabel:`Campaign Name` and :guilabel:`Responsible`. Odoo also allows for various :guilabel:`Tags` to be added, as well (if necessary)."
msgid "In order to send an :abbr:`SMS (Short Message Service)` in this fashion, navigate to the :menuselection:`Contacts` app, select the desired contact in the database, and click on the :guilabel:`SMS` icon on the contact form (next to the :guilabel:`Phone Number` field)."
msgid "To send a message to multiple contacts at once, navigate to the main :menuselection:`Contacts` app main dashboard, choose the :guilabel:`List View`, and select all the desired contacts to whom the message should be sent. Then, under :guilabel:`Action`, select :guilabel:`Send SMS`."
msgid "In order to set up :guilabel:`SMS Templates` for future use, activate :ref:`developer mode <developer-mode>`, by navigating to the main Odoo dashboard that is full of apps, and select the :menuselection:`Settings app`. Then, scroll down to the :guilabel:`Developer Tools` section, and click :guilabel:`Activate the Developer Mode`."
msgid "Once *developer mode* is activated, the main Odoo dashboard appears once more, with a now-visible bug icon, which is located at the top-right corner of the dashboard; this bug icon indicates that developer mode is currently active."
msgid "Next return to the :menuselection:`Settings app` and, in the now-visible header menus at the top, choose :menuselection:`Technical --> SMS Templates` to begin setting up :abbr:`SMS (Short Message Service)` templates for future marketing campaigns."
msgid "Inside of the :guilabel:`SMS Templates` dashboard, Odoo reveals an entire page of :abbr:`SMS (Short Message Service)` templates. The default :guilabel:`List` view showcases each template's name, and to which recipients it applies."
msgid "For GSM7 SMS the size limit is 160 characters, and for Unicode is 70. *Above these limits, the content is divided into a multi-part message* and the limit of characters is lowered to 153 for GSM7 and to 67 for Unicode. Then, in real-time, the system displays the number of SMS mailings the message represents."
msgid "The price of an SMS depends on the destination and the length (number of characters) of the message. To see the **price per country, please consult**: `Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing#sms_faq_01>`_."
msgid "Multiple SMS communications at once at are counted as a single transaction, so no SMSs will be sent until there are enough credits to send them all."
msgid "A history of sent SMSs, along with all pertinent information related to its sent contacts (and the message itself), can be found in the :guilabel:`Sent` column of the main :guilabel:`SMS Marketing` dashboard (while in :guilabel:`Kanban` view)."
msgid "For more detailed information, select a desired SMS from the main dashboard (in :guilabel:`Kanban` view), and click on either link in the blue banner above the SMS detail form to learn more."
msgid "No, not if the phone number is incorrectly formatted (e.g. too many digits). However, if the SMS is sent to the wrong person (or to a fake number), the credit for that SMS will be lost."
msgid "Yes, but it is not possible out-of-the-box. Odoo experts can help customize a database to allow for the use of a personal SMS provider. Please check our success packs `here <https://www.odoo.com/pricing-packs>`_."
msgid "On the :guilabel:`Reporting` page (accessible via the :menuselection:`Reporting` option in the header menu), there are options to apply different combinations of :guilabel:`Filters` and :guilabel:`Measures` to view metrics in a number of different layouts (e.g. :guilabel:`Graph`, :guilabel:`List`, and :guilabel:`Cohort` views.)"
msgid "For example, while in the default :guilabel:`Graph` view, :abbr:`SMS (Short Message Service)` data is visualized as different graphs and charts, which can be sorted and grouped in various ways (e.g. :guilabel:`Measures` drop down menu)."
msgid "Adding the *Studio* application upgrades the subscription status to *Custom*, which increases the cost. Consult `support <https://www.odoo.com/contactus>`_, or reach out to the database's customer success manager, with any questions on making the change."
msgid "To use automation rules, navigate in :ref:`developer mode <developer-mode>`, to :menuselection:`Settings app --> Technical menu --> Automation section --> Automation Rules`. Then, click :guilabel:`New` to create a new rule."
msgid "Based on the selection for the :guilabel:`Trigger`, additional fields will populate below. Set the :guilabel:`Trigger` to one of the following options:"
msgid "Other options may appear based on the :guilabel:`Model` selected. For example if the :guilabel:`Calendar Event` model is selected, then the following options appear in addition to those above:"
msgid "Under the :guilabel:`Before Update Domain` field, set a condition to be met before updating the record. Click :guilabel:`Edit Domain` to set record parameters."
msgid "Under the :guilabel:`Actions To Do` tab, select :guilabel:`Add an action`. Next, in the resulting :guilabel:`Create Actions` pop-up window, select :guilabel:`Send SMS`, and set the :guilabel:`Allowed Groups`. :guilabel:`Allowed Groups` are the access rights groups that are allowed to execute this rule. Leave the field empty to allow all groups. See this documentation: :ref:`access-rights/groups`."
msgid "Next, set the :guilabel:`SMS Template` and choose whether the SMS message should be logged as a note, by making a selection in the drop-down menu: :guilabel:`Send SMS as`. Click :guilabel:`Save and Close` to save the changes to this new action."
msgid "Add any necessary notes under the :guilabel:`Notes` tab. Finally, navigate away from the completed automation rule, or manually save (by clicking the :guilabel:`☁️ (cloud)` icon), to implement the change."
msgid "Odoo's *Social Marketing* application helps content marketers create and schedule posts, manage various social media accounts, analyze content effectiveness, and engage directly with social media followers in one, centralized location."
msgid "In order to create social posts and analyze content with Odoo *Social Marketing*, social media accounts **must** be added as a *stream* on the application's main dashboard."
msgid "Be aware that personal profiles **cannot** be added as a stream. The main use of Odoo *Social Marketing* is to manage and analyze business accounts on social media platforms."
msgid "Odoo *Social Marketing* has some limitations in regards to social media accounts. For example, Odoo **cannot** handle a large quantity of various pages (e.g. ~40 pages) under the same company. The same limitations are present in a multi-company environment because of how the API is constructed."
msgid "For example, if Company 1 is the only company selected from the main Odoo dashboard, and activates *Facebook Page 1* and *Facebook Page 2*, then those pages will be accesible on the *Social Marketing* dashboard."
msgid "However, if on that same database, the user adds Company 2 from the company drop-down menu in the header, and attempts to add those same streams, it results in a permission error."
msgid "To add a social media business account as a stream, navigate to :menuselection:`Social Marketing app` and select the :guilabel:`Add A Stream` button located in the upper-left corner. Doing so reveals an :guilabel:`Add a Stream` pop-up window."
msgid "In the :guilabel:`Add a Stream` pop-up window, choose to :guilabel:`Link a new account` for a business from any of the following popular social media platforms: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, and :guilabel:`YouTube`."
msgid "After clicking the desired social media outlet from the :guilabel:`Add a Stream` pop-up window, Odoo navigates directly to that specific social media outlet's authorization page, where permission must be granted, in order for Odoo to add that particular social media account as a stream to the *Social Marketing* application."
msgid "Once permission is granted, Odoo navigates back to the :guilabel:`Feed` on the main :guilabel:`Social Marketing` dashboard, and a new column, with that account's posts, is added. Accounts/streams can be added at any time."
msgid "A :guilabel:`Facebook` page can be added as long as the :guilabel:`Facebook` account that grants permission is the administrator for the page. It should also be noted that different pages can be added for different streams."
msgid ":guilabel:`Instagram` accounts are added through a :guilabel:`Facebook` login because it uses the same API. This means, an :guilabel:`Instagram` account needs to be linked to a :guilabel:`Facebook` account in order for it to show up as a stream in Odoo."
msgid "Another way to quickly link social media accounts to Odoo *Social Marketing* can be done on the :guilabel:`Social Media` page. To access the :guilabel:`Social Media` page, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Media`."
msgid "On the :guilabel:`Social Media` page there is a collection of all social media options, each complete with a :guilabel:`Link account` button: :guilabel:`Facebook`, :guilabel:`Instagram`, :guilabel:`LinkedIn`, :guilabel:`Twitter`, :guilabel:`YouTube`, and :guilabel:`Push Notifications`."
msgid "To see a list of all social accounts and websites linked to the database, go to :menuselection:`Social Marketing app --> Configuration --> Social Accounts`. This :guilabel:`Social Accounts` display the :guilabel:`Name`, the :guilabel:`Handle/Short Name`, the :guilabel:`Social Media` platform, who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated."
msgid "To edit/modify any of the social accounts on this page, simply select the desired account from the list on this page, and proceed to make any adjustments necessary."
msgid "To view a separate page with all the social media streams that have been added to the main *Social Marketing* dashboard, navigate to :menuselection:`Social Marketing app --> Configuration --> Social Streams`."
msgid "Here, the social stream information is organized in a list with the :guilabel:`Social Media`, the :guilabel:`Title` of the stream, the :guilabel:`Type` of the stream (e.g. :guilabel:`Posts`, :guilabel:`Keyword`, etc.), who it was :guilabel:`Created by`, and the :guilabel:`Company` to which it is associated."
msgid "To see a complete overview of all the people who have visited the website(s) connected to the database, navigate to :menuselection:`Social Marketing app --> Visitors`."
msgid "Here, Odoo provides a detailed layout of all the visitors' pertinent information in a default kanban view. If visitors already have contact information in the database, the option to send them an :guilabel:`Email` and/or an :guilabel:`SMS` is available."
msgid "This same visitor data can also be viewed as a list or a graph. Those view options are located in the upper-right corner of the :guilabel:`Visitors` page."
msgid "Social marketing campaigns help companies connect directly with the marketplace. These campaigns are helpful when introducing a new product to customers, explaining the value of a product or service, or when advertising an upcoming event or product release."
msgid "The most effective social marketing campaigns typically involve multiple channels to maximize content distribution, and Odoo's *Social Marketing* application acts as a singular control center to monitor, plan, post, track, and analyze all of the various content and content channels within a single dashboard."
msgid "To access a complete overview of all social marketing campaigns, open the :menuselection:`Social Marketing` application, and click :menuselection:`Campaigns` from the header menu. Doing so reveals a separate page with every campaign in a default kanban view."
msgid "Each *stage* in the kanban view can be edited, by clicking the :guilabel:`gear icon` to the left of the :guilabel:`+ (plus sign)` - located to the right of the stage title."
msgid "The **gear icon** *only* appears when the cursor hovers to the left of the **+ (plus sign)**. When the gear icon is clicked, a drop-down menu reveals the options: :guilabel:`Fold`, :guilabel:`Edit Stage`, and :guilabel:`Delete`."
msgid "Clicking :guilabel:`Fold` minimizes that specific stage's column. The stage column can be restored by clicking the folded version of it on the main :guilabel:`Campaigns` dashboard in the default kanban view."
msgid "Selecting :guilabel:`Edit Stage` reveals a pop-up window, in which the name and the sequence of the stage can be modified. If changes are made, be sure to click :guilabel:`Save`."
msgid "To add a new stage to the pipeline, side-scroll to the right on the :guilabel:`Campaigns` dashboard, click :guilabel:`Add a Column`, enter in the desired information, and click :guilabel:`Add`."
msgid "The same social marketing campaign information on the :guilabel:`Campaigns` dashboard can also be viewed as a list, by selecting the :guilabel:`List` option, located under the search bar, in the upper-right corner."
msgid "On the :guilabel:`Campaigns` dashboard, a new campaign can be created by clicking the quick add :guilabel:`+ (plus sign)` located in the top-right corner of each stage in the pipeline, visible in the kanban view. Campaigns can also be created by clicking :guilabel:`Create` in the upper-left corner of the :guilabel:`Campaigns` dashboard."
msgid "Here, the :guilabel:`Campaign Name`, :guilabel:`Responsible`, and :guilabel:`Tags` can be entered. When all modifications are complete, click :guilabel:`Add` to add the campaign to the database."
msgid "In order to edit a campaign in greater detail, and create/send various forms of communications related to it, the template page for that campaign must be accessed and modified, accordingly. There are multiple ways to access a template page for a campaign."
msgid "On the :guilabel:`Campaigns` dashboard in the kanban view, select the :guilabel:`⋮ (three dots)` drop-down menu on the desired campaign, and select :guilabel:`Edit`."
msgid "On a *Campaign Template* page, numerous elements can be customized/modified, and various forms of communications can be created, modified, and sent or scheduled. Below is a sample of a completed campaign template."
msgid "In order for the :guilabel:`Send New Mailing` option to appear on campaign templates, make sure the *Mailing Campaigns* feature is enabled in the *Email Marketing* app. To do that, navigate to :menuselection:`Email Marketing --> Configuration --> Settings`, activate :guilabel:`Mailing Campaigns`, and click :guilabel:`Save`."
msgid "If the proper settings and applications are installed (as instructed above), there are four forms of communication/content options that can be added to campaigns. Each of these options are displayed as buttons in the upper-left corner of the campaign template page."
msgid ":guilabel:`Send New Mailing`: reveals a blank email template on a separate page, in which the message can be fully customized in a variety of ways."
msgid ":guilabel:`Send Social Post`: reveals a blank social post template on a separate page, in which a post can be created, and applied to social media accounts that are already connected to the database."
msgid ":guilabel:`Push Notification`: reveals a similar blank social post template on a separate page, however, the :guilabel:`Push Notification` options are already pre-selected in the :guilabel:`Post on` field."
msgid "Whichever form of communication is created, once it's completed, Odoo returns to the :guilabel:`Campaign Template` page, showcasing that new content in its corresponding tab (e.g. :guilabel:`Mailings`, :guilabel:`SMS`, :guilabel:`Social Media`, and/or :guilabel:`Push Notifications`)."
msgid "As content and communications are added to a campaign, tabs for those specific mediums appear, along with a variety of analytical smart buttons (e.g. :guilabel:`Revenues`, :guilabel:`Quotations`, :guilabel:`Leads`, etc.)."
msgid "These smart buttons, located at the top of the template, display different metrics related to the campaign, and its various communications and content. Clicking any smart button reveals a separate page dedicated to that particular element of the campaign, allowing for quicker, more organized analysis."
msgid "To see a complete overview of posts, go to Odoo :menuselection:`Social Marketing app --> Posts`. Here, on the :guilabel:`Social Posts` page, every post that has been created and posted with Odoo can be seen and accessed."
msgid "By default, Odoo displays the posts in a kanban view. The information on this page can be sorted even further, via the left sidebar, where all connected social accounts and posts can be quickly seen, accessed, and analyzed."
msgid "The calendar view option displays a visual representation of posts in a calendar format of when posts were published, or are scheduled to be published. This option provides a clear overview of any planned day, week, or month, and Odoo displays all drafted, scheduled, and published posts."
msgid "Clicking on a date reveals a blank social media post detail form, in which a social media post can be created, and Odoo will post it on that specific date/time."
msgid "The list view option is similar to the kanban option, but instead of individual blocks, all post information is displayed in a clear, list layout. Each line of the list displays the :guilabel:`Social Accounts`, :guilabel:`Message`, and :guilabel:`Status` of every post."
msgid "There is also a helpful left sidebar that organizes all posts by :guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as well."
msgid "While in the pivot view, the option to :guilabel:`Insert in Spreadsheet` is available, located to the right of the :guilabel:`Measures` drop-down menu, in the upper-left corner of the :guilabel:`Social Posts` page."
msgid "Clicking on a post from a social media stream reveals a pop-up window, showcasing the content of that specific post, along with all the engagement data related to it (e.g. likes, comments, etc.)."
msgid "If desired, the user can leave a new comment of the post from the post's pop-up window, by typing one in the :guilabel:`Write a comment...` field, and clicking :guilabel:`Enter` to post that comment."
msgid "To create a lead from a comment left on a social media post, click on the desired post from the dashboard to reveal that post's specific pop-up window. Then, scroll to the desired comment, and click the :guilabel:`three vertical dots` icon to the right of that comment."
msgid "In this pop-up window, select to either: :guilabel:`Create a new customer`, :guilabel:`Link to an existing customer`, or :guilabel:`Do not link to a customer`."
msgid "If :guilabel:`Link to an existing customer` is selected, a new :guilabel:`Customer` field appears beneath those options, wherein a customer can be chosen to be linked to this lead."
msgid "Once the desired selection has been made, click the :guilabel:`Convert` button at the bottom of the :guilabel:`Convert Post to Lead` pop-up window. Doing so reveals a fresh lead detail form, where the necessary information can be entered and processed."
msgid "When a social media account stream is added to the *Social Marketing* dashboard, each stream also displays and links that specific social media platform's KPIs (if the platform has them)."
msgid "To get redirected to the statistics and metrics related to any social media account's KPIs, click on the :guilabel:`Insights` link, located at the top of each stream."
msgid "For example, if the companies have 3 *Facebook* pages, but only grant access to 1, and try to grant access to another at a later date, they will be de-authenticated, and access to the initial page's insights/analytics will be lost."
msgid "So, be sure to add *all* pages for *all* companies in a multi-company environment to avoid this issue. If a page gets de-autenticated, simply remove the stream, and re-establish it."
msgid "To create content for social media accounts, navigated to the :menuselection:`Social Marketing app`, and click :guilabel:`New Post` located in the upper-right corner of the *Social Marketing* dashboard."
msgid "If working in a multi-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Company`. In this field, select the company that should be connected to this specific social media post."
msgid "If working in a single-company environment, the first field in the :guilabel:`Your Post` section of the social media post detail form is :guilabel:`Post on`. In this field, determine which social media outlets (streams) this post is intended to be posted on, and/or which website's visitors this post should be sent to, via push notification, by checking the box beside the desired option(s)."
msgid "Odoo automatically provides every available social media account that's been linked to the database as an option in this section. If a social media account hasn't been added as a stream to the *Social Marketing* application, it will **not** appear as an option on the post template."
msgid "Multiple social media outlets (streams) and websites can be selected in the :guilabel:`Post on` field. At least **one** option in the :guilabel:`Post on` field *must* be selected."
msgid "In order for the :guilabel:`Push Notification` option to appear on the social media post detail form in Odoo *Social Marketing*, make sure the *Enable Web Push Notifications* feature is enabled in the *Website* app."
msgid "To do that, navigate to :menuselection:`Website app --> Configuration --> Settings`, activate :guilabel:`Enable Web Push Notifications`, fill out the corresponding fields, and click :guilabel:`Save`."
msgid "In the :guilabel:`Message` field, type in the desired message for the social post. After typing, click away from the :guilabel:`Message` field to reveal visual samples of how the post will look on all the previously selected social media accounts (and/or websites, as push notifications)."
msgid "Emojis can also be added directly to the text in the :guilabel:`Message` field. Just click the :guilabel:`🙂 (smiley face)` icon, located on the line of the :guilabel:`Message` field to the far right. Clicking this icon reveals a drop-down menu containing numerous emojis to choose from."
msgid "If images are to be used in the post, click the :guilabel:`Attach Images` button, in the :guilabel:`Attach Images` field, located beneath the :guilabel:`Message` field. When clicked, Odoo reveals a pop-up window. In this pop-up window, select the desired image from the hard drive, and upload it."
msgid "After successfully uploading and attaching the desired image, Odoo reveals a new preview of the social media post, complete with the newly-added image, on the right side of the detail form."
msgid "Next, there is the :guilabel:`Campaign` field. This non-required field provides the options to attach this post to a specific marketing campaign."
msgid "To add this post to a pre-existing campaign, click the empty :guilabel:`Campaign` field to reveal a drop-down menu, containing all the existing campaigns in the database. Select the desired campaign from this drop-down menu to add this post to that campaign."
msgid "To create a new campaign directly from the social media post detail form, start typing the name of the new campaign in the blank :guilabel:`Campaign` field, and select either :guilabel:`Create` or :guilabel:`Create and edit...`."
msgid "Clicking :guilabel:`Create and edit...` creates the campaign, and reveals a :guilabel:`Create Campaign` pop-up form, wherein the :guilabel:`Campaign Identifier`, :guilabel:`Responsible`, and :guilabel:`Tags` can be instantly configured."
msgid "When all the desired settings have been entered, click :guilabel:`Save & Close` to save the campaign and return to the social media post detail form."
msgid "Then, in the :guilabel:`When` field, choose either :guilabel:`Send Now` to have Odoo publish the post immediately, or :guilabel:`Schedule later` to have Odoo publish the post at a later date and time."
msgid "If :guilabel:`Schedule later` is selected, a new :guilabel:`Scheduled Date` field appears. Clicking the empty field reveals a pop-up calendar, in which a future date and time can be designated."
msgid "After selecting a desired date and time, click :guilabel:`Apply`. Then, Odoo will promptly publish the post at that specific date and time on the pre-detemined social media account(s)."
msgid "If scheduling a post, the :guilabel:`Post` button at the top of the social media post detail form changes to :guilabel:`Schedule`. Be sure to click :guilabel:`Schedule` after completing the social media post detail form."
msgid "If one (or multiple) :guilabel:`[Push Notification]` options are chosen in the :guilabel:`Post on` field, a specific :guilabel:`Push Notification Options` section appears at the bottom of the social media post detail form."
msgid "The first field in this section is :guilabel:`Notification Title`. In this field, there is the option to add a custom title to the push notification that will be sent."
msgid "To designate a specific page on the website that should trigger this push notification, enter that page's URL in the :guilabel:`Target URL` field. Then, once a visitor reaches that specific page, Odoo will display the push notification."
msgid "Below that field is the option to add a custom :guilabel:`Icon Image` to the push notification. This is an icon that appears beside the push notification."
msgid "To upload a new image, click the :guilabel:`✏️ (pencil) icon` when hovering over the :guilabel:`Icon Image` camera icon. Doing so reveals a pop-up window, in which the desired icon image can be located on the hard drive, and subsequently uploaded."
msgid "Next, if the post is scheduled to be posted later, there is the option to ensure the post is sent in the visitor's timezone, by enabling the :guilabel:`Local Time` option. If enabled, Odoo will send it at the appropriate, pre-determined time, taking the visitor's location into consideration."
msgid "Then, there is the :guilabel:`Match all records` field. This field provides the ability to target a specific group of recipients in the database, based on certain criteria, and can be applied to match :guilabel:`all` or :guilabel:`any` of the rules."
msgid "In this equation-like rule field, specifiy the specific criteria Odoo should take into account when sending this post to a particular target audience."
msgid "To add a branch (series of additional rules based on the previous rule, to further specify a target audience), click the unique :guilabel:`branch icon`, located to the right of the :guilabel:`➕ (plus sign) icon`."
msgid "With Odoo *Surveys*, users create various surveys, questionnaires, certifications, assessments, and so much more. These can be used to collect feedback, evaluate the success of a recent event, and measure the satisfaction of customers and/or employees. This process yields valuable insights into shifting market trends."
msgid "Upon opening the *Surveys* application, Odoo presents the main dashboard of the *Surveys* application, otherwise known as the :guilabel:`Surveys` page."
msgid "In the upper-left corner, there is a :guilabel:`New` button. When clicked, Odoo presents a blank survey form that can be used to create a survey."
msgid "From left-to-right, after the survey name, the user who is responsible for it, and the month it was created, each line on the *Surveys* dashboard shows the following:"
msgid "The :guilabel:`Certified` percentage and bar **only** appears if that particular survey has the *Is a Certification* option enabled on the survey form."
msgid "If neither :guilabel:`Passed` nor :guilabel:`Certified` appear on the line, that indicates the survey is without a *Required Score* and was not enabled with the *Is a Certification* option."
msgid "Number of :guilabel:`Courses` related to that survey, which **only** appears if more than one course has been created and attached to a single survey"
msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey - complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch."
msgid "When the :guilabel:`Send by Email` toggle is active (green switch), additional fields appear, in which :guilabel:`Recipients`, :guilabel:`Additional Emails`, and a :guilabel:`Subject` can be added to the email."
msgid "Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can be modified, as well, if needed."
msgid "Once modifications are complete, click :guilabel:`Send` to send that email invite to all the email addresses/contacts listed in the :guilabel:`Recipients` field."
msgid "The default :guilabel:`Mail Template` for survey invites can be edited by navigating to :menuselection:`Settings --> Technical --> Email Templates` and searching for `Survey: Invite`."
msgid ":guilabel:`Test`: click to take a test version of the survey in a new tab, from the point-of-view of a survey participant, in order to check for any errors or inconsistencies."
msgid ":guilabel:`See results`: click to reveal a new tab showcasing detailed metrics and graphical representations of all survey participants, questions, and responses for deeper analysis."
msgid ":guilabel:`Start Live Session`: click to initiate a *Live session* survey, and reveal a session manager window in a new tab. This button is **not** present for surveys that have enabled the *Is a Certification* option on the survey form."
msgid ":guilabel:`End Live Session`: click to end a *Live session* survey that has been officially started. This button option **only** appears on survey lines that have previously initiated a live session."
msgid "Above the buttons that are located to the far-right of the survey lines, a :guilabel:`⋮ (three dots)` icon appears when the cursor hovers over that particular line. When the :guilabel:`⋮ (three dots)` icon is clicked, a drop-down menu with some configuration-related options appear:"
msgid ":guilabel:`Edit Survey`: when clicked, Odoo reveals the survey form for that particular survey, which can then be modified in a number of different ways."
msgid ":guilabel:`Share`: when clicked, Odoo reveals the :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey."
msgid ":guilabel:`Delete`: when clicked, Odoo presents a pop-up window, wherein the user **must** confirm they want to delete the survey entirely, which they can do by clicking the :guilabel:`Delete` button at the bottom of the pop-up window."
msgid "Beneath the buttons that are located to the far-right of the survey lines, there is an *Activities* button, represented by a :guilabel:`🕘 (clock)` icon. When clicked, a mini pop-up window appears, from which activities related to that particular survey can be scheduled and customized."
msgid "The *Surveys* dashboard is shown in the Kanban view, by default, but there is also a list view option available in the upper-right corner, represented by a :guilabel:`≣ (bars)` icon."
msgid "Additional columns can be added to the *Surveys* application dashboard, while in list view, by clicking the *additional options* drop-down menu, located to the far-right of the column titles, represented by a :guilabel:`(slider with two dots)` icon."
msgid "To have the *Surveys* application dashboard display nothing but the activities associated to the surveys in the database, click the :guilabel:`🕘 (clock)` icon to the far-right of the other view options, located in the upper-right corner."
msgid "Doing so reveals a table with rows and columns. The rows show the different surveys in the database, and the columns depict the various activity types."
msgid "Discover how to measure a survey participant's performance, or overall satisfaction, with Odoo's detailed (and fully customizable) survey scoring options."
msgid "With Odoo *Surveys*, there are many question types and options to choose from, providing the ability to create any kind of unique survey, questionnarire, and/or certification."
msgid "The *Live Session* survey option available in Odoo can enhance in-person demonstrations and presentations, where participants' real-time responses can be used to dictate where the conversation goes next."
msgid "Once the surveys start to come in, it is time to analyze the responses from your participants. Fortuantely, the in-depth reporting pages and options available in Odoo *Surveys* provide countless ways to examine everything related to surveys, and their submitted responses."
msgid "After surveys have been created and sent to participants, it is only a matter of time before the responses start to come in. When they do, it is important to know where and how to analyze them in the Odoo *Surveys* application."
msgid "Fortunately, Odoo provides numerous ways to view survey responses, allowing users to access and analyze survey responses as they are submitted."
msgid "Upon opening the :menuselection:`Surveys` application, the main dashboard reveals a list of all the surveys in the database, along with pertinent information related to each one."
msgid "By default, every survey line showcases its number of :guilabel:`Questions`, :guilabel:`Average Duration`, and how many participants have :guilabel:`Registered` or :guilabel:`Completed` the survey."
msgid "There are also elements showing the percentage of how many participants :guilabel:`Passed` (if a *Required Score (%)* was configured), or how many participants became :guilabel:`Certified` (if the *Is a Certification* option was configured)."
msgid "To learn more about the different analytical elements found on the :guilabel:`Surveys` dashboard, check out the :doc:`Survey Essentials <../surveys/create>` documentation."
msgid "On the :guilabel:`Surveys` dashboard, to the far-right of each survey line displayed in the default list view, there is a :guilabel:`See results` button."
msgid "When the :guilabel:`See results` button is clicked, a new browser tab opens, revealing a separate page filled with all of that particular survey's results and responses, with an informative :guilabel:`Results Overview` and some filtering drop-down menus at the top."
msgid "At the top of the page, there is an :guilabel:`Edit Survey` link, in the middle of a blue header banner. When clicked, Odoo returns the user to the survey form for that particular survey."
msgid "To the right of the survey title, there are two drop-down menus with various filtering options, which can be used to personalize and segment the survey results in a number of different ways."
msgid "The first filter drop-down menu is set on the default :guilabel:`All Surveys` option, meaning the results below are showing results and responses from all the submitted surveys, regardless if they have been fully completed or not."
msgid "To the right of that drop-down menu of filter options, is another drop-down menu of filter options that can be used to further customize the results showcased on this page."
msgid "That drop-down menu is set to the :guilabel:`Passed and Failed` option, by default. This option shows the results and responses from all participants who have passed or failed this particular survey."
msgid "This second drop-down menu of filter options **only** appears if the survey being analyzed has a *Scoring* option configured, or if the *Is a Certification* feature has been enabled."
msgid "When that second drop-down menu of filter options is clicked open, two additional options appear: :guilabel:`Passed only` and :guilabel:`Failed only`."
msgid "Each option would filter the results below to only show responses from participants who have passed the survey, or who have failed the survey, respectively."
msgid "The various sections of the survey, if there were any, appear at the top of their corresponding questions on the results page, as well, for added organization."
msgid "Every question that was a part of the survey is shown, along with an in-depth breakdown, and visual representation, of how it was answered by participants, beneath the :guilabel:`Results Overview` section."
msgid "Each question is displayed above its corresponding results. To the left of the question is an :guilabel:`👁️ (eye)` icon. When clicked, Odoo hides the visual and data-related results and responses. When clicked again, that question's visual and data-related results re-appear."
msgid "To the far-right of the question, there are indicators to see how many participants :guilabel:`Responded` and how many :guilabel:`Skipped` the question."
msgid "If the question required the participant to enter in their own answer, without any options to choose from, like entering a specific number or date, for example, there is also an indicator to showcase how many users answered the question :guilabel:`Correct`."
msgid "Even if there is no configured *correct* response for question of this nature, the :guilabel:`Correct` indicator still appears, although, it displays a `0`."
msgid "If there is only one correct response to a multiple choice question, those results and responses are represented by a :guilabel:`Pie Graph`. The correct answer is indicated by a :guilabel:`✔️ (checkmark)` icon next to the correct answer option, in the legend above the graph."
msgid "If there are multiple correct answer options (or no correct answers at all) for a multiple choice question, those results and responses are represented by a :guilabel:`Bar Graph`."
msgid "The :guilabel:`Data` tab shows all the provided :guilabel:`Answer` options for the question. The :guilabel:`User Choice` (with percentages and votes) along with the :guilabel:`Score` of each option."
msgid "Other question types, wherein there were no answer options for the participant to choose from, there is a :guilabel:`Most Common` tab and an :guilabel:`All Data` tab."
msgid "If a question is looking for participants to enter a numerical value as a response, :guilabel:`Maximum`, :guilabel:`Minimum`, and :guilabel:`Average` indicators appear to the far-right of the results tabs."
msgid "A :guilabel:`filter` icon is also present either to the right of the :guilabel:`User Choice` column in a :guilabel:`Data` tab, or to the far-right of a :guilabel:`User Response` line in an :guilabel:`All Data` tab."
msgid "When that :guilabel:`filter` icon is clicked, Odoo returns the user to the top of the results page, with that chosen filter applied, showing the results of each question for participants who submitted that particular answer for that specific question."
msgid "Therefore, showcasing the remaining results for participants who answered that specific question in the same way. To remove that filter, and reveal all the results once again, click :guilabel:`Remove all filters` or click the :guilabel:`✖️ (X)` icon in the filter box at the top of the results page."
msgid "To view a consolidated list of participation results for a specific survey, navigate to :menuselection:`Surveys app`, select the desired survey from the list, and click the :guilabel:`Participations` smart button at the top of the survey form."
msgid "Doing so reveals a separate :guilabel:`Participations` page, showcasing the participants for that specific survey, along with a collection of pertinent information related to each one."
msgid "Here, users can view information related to individual participants who took that specific survey. If they desire to see a more detailed breakdown of their various answers and responses, they can click on any participant, and Odoo reveals a separate page showing that participant's survey details, along with their submitted answers."
msgid "To view a consolidated list of all participants of every survey in the database, navigate to :menuselection:`Surveys app --> Participations`. Here, every survey in the database is shown in a default nested list. Beside each survey title has the number of participants in parenthesis."
msgid "When a survey is un-nested from this list, by clicking the survey title, the corresponding participants, along with their response-related data for that survey, appear on the page."
msgid "These options are here to streamline the survey-making process, by providing users with automated settings and options that are ideally specific to those types of surveys. Each of those survey type options comes equipped with its own specific selection of options."
msgid "The :guilabel:`Custom` option, selected by default, offers all the options from every potential survey type (located in the :guilabel:`Options` tab)."
msgid "Below the survey name field, is the :guilabel:`Responsible` field. Choose a user from the drop-down menu to be in charge of the survey. By default, the user who initially created the survey is selected as the default :guilabel:`Responsible`."
msgid "To the right of those fields, and above the tabs, is the option to add a background image, represented by a :guilabel:`📷 (camera)` icon. When clicked, the option to upload an image becomes available. This image would be used as the background image for the entire survey. This is **not** a required option."
msgid "Below those fields and options are four tabs: :guilabel:`Questions`, :guilabel:`Options`, :guilabel:`Description`, and :guilabel:`End Message`."
msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, a column titled, :guilabel:`# Questions Randomly Picked` appears in the :guilabel:`Questions` tab."
msgid "Indicate whether questions require a mandatory answer by clicking the :guilabel:`(optional columns)` icon to the far-right of the column titles. Then, select :guilabel:`Mandatory Answer` from the drop-down menu to reveal the :guilabel:`Mandatory Answer` column in the :guilabel:`Questions` tab."
msgid "To add a question to a survey, click :guilabel:`Add a question` in the :guilabel:`Questions` tab, and proceed to fill out the :guilabel:`Create Sections and Questions` pop-up window that appears."
msgid "There **must** be a survey title entered in order for the :guilabel:`Create Sections and Questions` pop-up window to appear. If no title is entered for the survey, an error pop-up message appears in the upper-right corner, instructing the user to enter a survey title."
msgid "A *section* divides the survey into organized parts, in order to visually group similar questions together. To make a section, click :guilabel:`Add a section` at the bottom of the :guilabel:`Questions` tab, proceed to type in a desired name for the section, then either press :kbd:`Enter` or click away."
msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey. Doing so populates the section with questions that align with its theme."
msgid "If the :guilabel:`Randomized per Section` option is enabled in the :guilabel:`Options` tab of the survey form, the number `1` appears, by default, on the section line, beneath the :guilabel:`# Questions Randomly Picked` column."
msgid "This indicates that `1` question from that section will be picked at random for each participant taking the survey, bypassing every other, non-chosen question from that section. To change that number, select that figure, and type in the desired number in its place. Then, either press :kbd:`Enter`, or click away."
msgid "In the :guilabel:`Options` tab of the survey form, there are many options to choose from, separated in four different sections: :guilabel:`Questions`, :guilabel:`Time & Scoring`, :guilabel:`Participants`, and :guilabel:`Live Session`."
msgid "The options available in this tab vary on the survey type chosen, via the radio buttons at the top of the survey form: :guilabel:`Survey`, :guilabel:`Live Session`, :guilabel:`Assessment`, or :guilabel:`Custom`."
msgid "The :guilabel:`Custom` survey type showcases all the possible options in the :guilabel:`Options` tab. So, if any of the following options do **not** appear in the :guilabel:`Options` tab, it is likely because the selected survey type does not offer it."
msgid "Choose between :guilabel:`One page per question`, :guilabel:`One page per section`, or :guilabel:`One page with all the questions` in the :guilabel:`Pagination` field."
msgid "If :guilabel:`One page with all the questions` is selected, all the remaining options in the :guilabel:`Questions` field, apart from :guilabel:`Question Selection` is removed, as they are no longer needed."
msgid "In the :guilabel:`Question Selection` field choose to have the survey show :guilabel:`All questions` or :guilabel:`Randomized per Section`. If :guilabel:`Randomized per Section` a new column appears in the :guilabel:`Questions` tab, titled: :guilabel:`# Questions Randomly Picked`."
msgid "In the :guilabel:`# Questions Randomly Picked` column, designate how many questions, in that particular section, should be chosen at random to the participant."
msgid "The first option in the :guilabel:`Time & Scoring` section is the :guilabel:`Survey Time Limit` option. If enabled, proceed to enter in an amount of time (in :guilabel:`minutes`) to be set as the time limit for the survey."
msgid "Next, in the :guilabel:`Scoring` section, determine whether there should be: :guilabel:`No scoring`, :guilabel:`Scoring with answers after each page`, :guilabel:`Scoring with answers at the end`, or :guilabel:`Scoring without answers`."
msgid "If the :guilabel:`No scoring` option is selected, no other options are available in this section. However, if any *other* :guilabel:`Scoring` option is selected, two additional fields appear: :guilabel:`Required Score (%)` and :guilabel:`Is a Certification`."
msgid "In the :guilabel:`Required Score (%)` field, enter the minimum percentage participants **must** earn in order to pass the survey. Scores below this threshold are considered fails. This figure is also used to determine if a participant is 'certified' or not, if the :guilabel:`Is a Certification` option is enabled."
msgid "If the :guilabel:`Is a Certification` option is enabled, that makes the survey a *Certification*, which is represented on the main *Surveys* app dashboard via a half-tropy image behind the survey title, while in the default Kanban view. Or, via a full-trophy icon, while in list view."
msgid "Beneath that, in the :guilabel:`Certified Email Template` field, users can select a preconfigured email template, or create one on-the-fly, to be sent to certified participants of the survey upon completion."
msgid "Lastly, if the :guilabel:`Give Badge` field is enabled, a preconfigured badge is then displayed on the contact page for that certified survey participant."
msgid "The first available option in the :guilabel:`Participants` section is the :guilabel:`Access Mode` field. This is where users can determine who has access to the survey. Users can select either: :guilabel:`Anyone with the link` or :guilabel:`Invited people only`."
msgid "Next, there is the option to :guilabel:`Require Login`. Enabling this feature means users **must** login before being able to take the survey, even if they have a valid token."
msgid "Lastly, in there is the :guilabel:`Limit Attempts` field. If enabled, an additional field appears beside it, in which users can determine how many times users can attempt this survey."
msgid "The first option in the :guilabel:`Live Session` section is the :guilabel:`Session Code` field. In this field, enter a custom code, consisting of letters, numbers, and/or symbols, to be used by participants in order to access the live session survey."
msgid "If a :guilabel:`Session Code` has been entered, the URL in the :guilabel:`Session Link` field ends with that specific :guilabel:`Session Code`."
msgid "If that complete :guilabel:`Session Link` (ending in the custom :guilabel:`Session Code`) is used by participants to access the live session survey, that link would *already* be entered for them. At that point, they'd simply have to wait until the host of the live session begins the survey, and then they'd be able to enter."
msgid "If the :guilabel:`Session Link` (ending in the custom :guilabel:`Session Code`) is sent **without** including the :guilabel:`Session Code` ending, participants trying to access the live session, via that link, will need to enter the custom :guilabel:`Session Code` to gain access."
msgid "If the :guilabel:`Session Code` field is empty, a slightly longer, more complicated URL populates the :guilabel:`Session Link` field. When participants attempt to access the live session via that link (without a configured :guilabel:`Session Code`), all they have to do is wait for the host of the live session to begin the survey, and they'd be able to participate."
msgid "Lastly, in the :guilabel:`Live Session` section, there is the option to :guilabel:`Reward quick answers`. If that option is enabled, participants who submit their answer quickly receive more points."
msgid "In this non-required tab, users can enter a custom description about the survey, along with any explanations or guidance that a survey participant may need in order to properly participate (and complete) the survey."
msgid "Once the survey has been configured properly, and questions have been added, the user can utilize any of the available buttons in the upper-left corner of the survey form."
msgid ":guilabel:`Share`: click to reveal a :guilabel:`Share a Survey` pop-up form that can be used to invite potential participants to the survey — complete with a :guilabel:`Survey Link` that can be copied and sent to potential participants, and a :guilabel:`Send by Email` toggle switch."
msgid "When the :guilabel:`Send by Email` toggle is in the 'on' position, indicated by a green switch, additional fields appear, in which :guilabel:`Recipients` and a :guilabel:`Subject` can be added to the email. Below that, a dynamic email template, complete with a :guilabel:`Start Certification` button appears, which can also be modified."
msgid ":guilabel:`See results`: this button **only** appears if there has been at least one participant who has completed the survey. Clicking :guilabel:`See results` reveals a separate tab containing a visual analysis of the survey questions and responses. For more information, check out the :doc:`scoring surveys <scoring>` documentation."
msgid ":guilabel:`Create Live Session`: clicking this button opens the *Session Manager* in a separate tab. It also allows participants to access the live session, but the actual survey does **not** begin until the user hosting the live session survey clicks the :guilabel:`Start` button on the *Session Manager* window."
msgid "Additionally, when :guilabel:`Create Live Session` has been clicked, and the *Session Manager* tab has been opened, the :guilabel:`Create Live Session` button on the survey form is replaced with two new buttons: :guilabel:`Open Session Manager` and :guilabel:`Close Live Session`."
msgid "Clicking :guilabel:`Open Session Manager` opens another separate tab to the *Session Manager*, and clicking :guilabel:`Close Live Session` closes, and subsequently ends, the live session."
msgid ":guilabel:`Test`: clicking this button opens a new tab to a test version of the survey, in order for the user to check for errors or inconsistencies, from the point-of-view of a participant. Users can tell if they are in a test version of the survey if there is a blue banner at the top of the screen, reading: `This is a Test Survey --> Edit Survey`."
msgid ":guilabel:`Print`: clicking this button opens a new tab to a printable version of the survey that the user can proceed to print for their records."
msgid ":guilabel:`Close`: clicking this button closes the survey (i.e. archives it), which is represented by a red :guilabel:`Archived` banner across the top-right corner of the survey form."
msgid "When this button is clicked, and the survey is closed, a single button appears in the upper-right corner of the survey form, titled: :guilabel:`Reopen`. When :guilabel:`Reopen` is clicked the survey is reopened (i.e. unarchived), and the :guilabel:`Archived` banner is removed from the survey form."
msgid "*Live Session* surveys function the same way as a normal survey, but with a host or moderator, who presents the questions to participants, reveals their responses in real-time, and controls the tempo of the survey."
msgid "In *Live Session* surveys, participants access the survey experience via a custom URL, and sign in with an optional access code. When the survey has begun, the host presents one question at a time."
msgid "Then, the audience of participants submit their answer, either via their computer or mobile device, and once the responses have been gathered, the host reveals all the participant's responses, in real time, with each answer's results displayed as a bar graph."
msgid "To create a *Live Session* survey, begin by opening the *Surveys* application. From the :guilabel:`Surveys` dashboard, click the :guilabel:`New` button to reveal a blank survey form."
msgid "Any of the survey type options (:guilabel:`Survey`, :guilabel:`Live Session`, :guilabel:`Assessment`, or :guilabel:`Custom`), presented as radio buttons at the top of the survey, can be used to create a *Live Session*."
msgid "However, selecting the :guilabel:`Live Session` survey type radio button streamlines the process because Odoo auto-selects the optimal settings and options for a *Live Session* survey when that option is selected."
msgid "If the :guilabel:`Is a Certification` option is enabled in the :guilabel:`Options` tab, the survey **cannot** be used as a *Live Session* survey."
msgid "With the desired survey radio button option selected, proceed to :doc:`create a survey <../surveys/create>` with :doc:`questions and sections <../surveys/questions>`."
msgid "While creating questions for the *Live Session* survey, open the :guilabel:`Options` tab on the :guilabel:`Create Sections and Questions` pop-up form, in order to reveal the :guilabel:`Live Sessions` section, which only has one available feature: :guilabel:`Question Time Limit`."
msgid "When the :guilabel:`Question Time Limit` option is enabled, a new field appears beside it, wherein the user **must** enter the desired amount of time (in seconds) the participant gets to answer the question."
msgid "After the questions have been created for the *Live Session* survey, open the :guilabel:`Options` tab of the survey form to further configure the survey."
msgid "The :guilabel:`Options` tab is organized into four sections: :guilabel:`Questions`, :guilabel:`Time & Scoring`, :guilabel:`Participants`, and :guilabel:`Live Session`."
msgid "Regardless of the option selected for the :guilabel:`Pagination` field, the *Live Session* survey *only* shows :guilabel:`One page per question`, and will default to that option when the :guilabel:`Create Live Session` button is clicked, and a *Live Session* survey officially begins."
msgid "The :guilabel:`One page per question` option in the :guilabel:`Pagination` field is selected by default, and no other options appear in the :guilabel:`Questions` section, when the :guilabel:`Live Session` survey type radio button is selected."
msgid "The :guilabel:`Display Progress as` and :guilabel:`Question Selection` options are still viable and active options for *Live Session* surveys, if desired, but they are **not** required."
msgid "However, the :guilabel:`Allow Roaming` feature is **not** available during *Live Session* surveys whatsoever, as the host/moderator controls the survey, and participants have no control over what question they see, or when they see it."
msgid "The :guilabel:`Survey Time Limit` option is **not** applicable for *Live Session* surveys. This option does not even appear in the :guilabel:`Time & Scoring` section of the :guilabel:`Options` tab if the :guilabel:`Live Session` survey type radio button option is selected."
msgid "While the :guilabel:`Survey Time Limit` option is not applicable for *Live Session* surveys, each question *can* be affixed with its own *Question Time Limit*, via the *Options* tab of the question pop-up form. Those question-specific time limits *do* work with *Live Session* surveys."
msgid "If desired, any :guilabel:`Scoring` option, and subsequent :guilabel:`Required Score (%)` option are available to use with *Live Session* surveys."
msgid "However, if the :guilabel:`Is a Certification` option is enabled, the survey **cannot** be used as a *Live Session* survey. The :guilabel:`Is a Certification` option does **not** appear in the :guilabel:`Time & Scoring` section of the :guilabel:`Options` tab if the :guilabel:`Live Session` survey type radio button option is selected."
msgid "The :guilabel:`Access Mode` field is set to the :guilabel:`Anyone with the link` option when the survey is used as a *Live Session*. The :guilabel:`Anyone with the link` option **cannot** be modified if the :guilabel:`Live Session` survey type radio button option is selected."
msgid "The :guilabel:`Require Login` option is available for *Live Session* surveys. However, if the :guilabel:`Live Session` survey type radio button option is selected, the usual :guilabel:`Limit Attempts` field that appears when :guilabel:`Require Login` is enabled does **not** appear, as live session participants only get to attempt the survey once, as the host leads them through it."
msgid "The :guilabel:`Session Code` field allows users to create unique codes for participants to use, in order to gain access to the *Live Session* survey. This code can consist of any combination of letters, numbers, and/or symbols."
msgid "The :guilabel:`Session Code` field is **not** required, however, it is encouraged because it adds a level of exclusivity to the survey and, without a :guilabel:`Session Code`, the URL that appears in the following :guilabel:`Session Link` field becomes far more complex."
msgid "If a :guilabel:`Session Code` is **not** entered, participants can access the survey, via the :guilabel:`Session Link` without needing a host, and the fundamental elements of the *Live Session* are lost, as the survey is then just a normal questionnaire, without any real-time results."
msgid "With a :guilabel:`Session Code`, the URL in the non-modifiable :guilabel:`Session Link` field is simplified, and ends with the :guilabel:`Session Code`, preceded by `/s/`."
msgid "If `1212` has been entered as the :guilabel:`Session Code`, the URL in the :guilabel:`Session Link` field begins with the basic URL of the database (e.g. `sample-database.odoo.com`), followed by: `/s/1212`."
msgid "If a user sends out the :guilabel:`Session Link` URL in its complete form - :guilabel:`Session Code` and all - participants would *not* need to enter in a code, as it would already be entered for them. That complete link places the participant in a virtual waiting room, where they simply need to wait for the host to officially start the *Live Session* survey."
msgid "If a user sends out the :guilabel:`Session Link` URL - *except* for the :guilabel:`Session Code` at the end (i.e. the entire URL *through* `.../s/`) - participants would be taken to a page, wherein they would need to enter the specific :guilabel:`Session Code` in order to access the *Live Session*."
msgid "If any :guilabel:`Scoring` option has been enabled, the opportunity to :guilabel:`Reward quick answers` is also available with *Live Session* surveys."
msgid "Once all the questions and configurations are complete, users can click the :guilabel:`Create Live Session` button at the top of the survey form. Doing so opens a new browser tab to the *Session Manager*."
msgid "When the :guilabel:`Create Live Session` button has been clicked, and the *Live Session* has begun, a new :guilabel:`Open Session Manager` button appears on the survey form, which opens a new browser tab to the *Session Manager*. If the *Live Session* has already begun, that button leads the user to the question or section the *Live Session* is currently on."
msgid "Additionally, a :guilabel:`Close Live Session` button appears on the survey form. When that button is clicked, the *Live Session* survey closes."
msgid "The *Session Manager* is controlled by the host/moderator of the *Live Session* survey, and is typically shown on a projection or screen, so the participants can collectively view the questions and real-time responses, as the host/moderator guides them through the *Live Session*."
msgid "The participant can see and answer the questions from their computer or mobile device, but the results and real-time responses can **only** be seen on the *Session Manager*."
msgid "Initially, the *Session Manager* shows the title of the *Live Session* survey, the link needed to access it, and a :guilabel:`Waiting for attendees...` counter, which populates as participants enter the *Live Session* survey."
msgid "Once the desired amount of participants have entered the *Live Session* survey, the host/moderator can click the :guilabel:`Start` button on the right side of the *Session Manager* window to begin the *Live Session*."
msgid "If the survey begins with a section title on the survey form, that section title appears in the *Session Manager*, and the participant's view of the survey informs them to `Pay attention to the host screen until the next question`. This message appears whenever a section title appears during a *Live Session*."
msgid "When the first question appears on the survey, the *Session Manager* shows the question above an empty bar graph, showing the potential answer options on the x-axis. The participants see the question and selectable answer options on their computer or mobile device."
msgid "As participants submit their answers, a progress bar, in the upper-left corner of the *Session Manager*, fills in. This is how *Live Session* hosts/moderators know when every participant has submitted their responses."
msgid "Then, when the desired amount of participants have submitted their responses, the host/moderator clicks the :guilabel:`Show Results` button on the right side of the *Session Manager* to reveal the collective real-time responses on the bar graph."
msgid "Once the host/moderator feels like the participants have had enough time to view the real-time results, via the populated bar graph, they can click the :guilabel:`Show Correct Answer(s)` button on the right side of the *Session Manager* window. Doing so highlights the correct response, if one has been designated, in green. All incorrect responses are highlighted in red."
msgid "When the host/moderator feels the participants have had enough time to take in the correct and incorrect responses, via the bar graph on the *Session Manager*, they can click the :guilabel:`Next` button to move on to the next portion of the survey."
msgid "To access a list of *all* the questions that have been created in the database, navigate to :menuselection:`Surveys app --> Questions & Answers --> Questions`. There, users can view and modify any question from any survey."
msgid "However, there is only one place in the Odoo *Surveys* application where survey questions can be created. To do that, navigate to a survey form, by going to :menuselection:`Surveys app --> New`, or by selecting any pre-existing survey from the :guilabel:`Surveys` page (:menuselection:`Surveys app --> Surveys`)."
msgid "To reveal the :guilabel:`Mandatory Answer` column on the :guilabel:`Questions` tab, which indicates if questions require a mandatory answer or not, click the :guilabel:`(optional columns)` icon located to the far-right of the column titles."
msgid "Then, drag-and-drop desired questions beneath a section, or drag-and-drop a section title on top of (i.e. *before*) the desired question(s) in the survey, in order to populate the section with specific questions that fit the theme of the section."
msgid "Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and Questions` pop-up window, in which a survey question can be created."
msgid "When all desired configurations are complete click either :guilabel:`Save & Close` to save the question and return to the survey form, or :guilabel:`Save & New` to save the question and create a new one right away in a fresh :guilabel:`Create Sections and Questions` pop-up window."
msgid "In the :guilabel:`Create Sections and Questions` pop-up window, start by typing the question into the :guilabel:`Question` field, located at the top of the pop-up window."
msgid "Then, choose the desired :guilabel:`Question Type`. A preview of each :guilabel:`Question Type` is to the right of the :guilabel:`Question Type` field, when a :guilabel:`Question Type` is selected."
msgid ":guilabel:`Datetime`: a date-based question, where participants must enter a date *and* time (year-month-day, hour-minute-second) as a response."
msgid ":guilabel:`Matrix`: a multiple-choice, multiple question, in a table/chart layout, where participants are presented with different questions on each row, and different answer options on each column."
msgid "Once a :guilabel:`Question Type` has been selected, there are three possible tabs where information can be customized for the question. These include the :guilabel:`Answers` tab (if applicable for the chosen :guilabel:`Question Type`), the :guilabel:`Description` tab, and the :guilabel:`Options` tab."
msgid "However, if a custom response is required to answer the selected :guilabel:`Question Type`, like a :guilabel:`Multiple Lines Text Box`, for example. Or, if the answer to the :guilabel:`Question Type` is a number, date, or datetime, the :guilabel:`Answers` tab disappears completely."
msgid "If the :guilabel:`Single Line Text Box` is selected as the :guilabel:`Question Type`, the :guilabel:`Answers` tab remains, although it only provides two checkbox options: :guilabel:`Input must be an email` and :guilabel:`Save as user nickname`."
msgid "If the :guilabel:`Input must be an email` option is enabled, a new field, :guilabel:`Save as user email` appears. If that box is ticked, Odoo saves the participant's answer to that specific question as their email address."
msgid "For all other applicable :guilabel:`Question Type` options that provide answer options to the participant, the :guilabel:`Answers` tab appears the same."
msgid "From here, users can add answer options by clicking :guilabel:`Add a line`, and typing in the various answer options for that question. Then, either press :kbd:`Enter` to lock in that answer option and immediately add another one. Or, click away to simply lock in that answer option."
msgid "If any *Scoring* option is enabled in the :guilabel:`Options` tab of the survey form, the :guilabel:`Correct` and :guilabel:`Score` columns appear to the right of the :guilabel:`Choices` column."
msgid "To mark an answer option as correct, tick the box beneath the :guilabel:`Correct` column for the respective question. If :guilabel:`Multiple choice: multiple answers allowed` is set as the :guilabel:`Question Type`, multiple answers in the :guilabel:`Choices` column can be marked as :guilabel:`Correct`."
msgid "In the :guilabel:`Score` column, designate how many points (if any) should be rewarded to the participant for entering that specific answer. It is possible to enter a negative amount as the :guilabel:`Score` to take points away for an incorrect response."
msgid "The option to upload a corresponding image to accompany the answer options is available on the question line, beneath the :guilabel:`Image` column, by clicking :guilabel:`Upload your file`, and uploading the desired image."
msgid "An exception to that is if the :guilabel:`Matrix` option is selected as the :guilabel:`Question Type`. If that's chosen, the :guilabel:`Answers` tab remains, but below the typical :guilabel:`Choices` section, there is a :guilabel:`Rows` section. That's because the :guilabel:`Matrix` option provides an answer table for participants to fill out."
msgid "In the :guilabel:`Description` tab of the :guilabel:`Create Sections and Questions` pop-up window is used to provide any kind of guidelines, instructions, or any other type of supplemental material deemed necessary to help participants answer/understand the question."
msgid "In the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window, there are four available sections: :guilabel:`Answers`, :guilabel:`Constraints`, :guilabel:`Conditional Display`, and :guilabel:`Live Sessions`."
msgid "Fields in the :guilabel:`Answers` section in the :guilabel:`Options` tab of the :guilabel:`Create Sections and Questions` pop-up window vary, depending on the selected :guilabel:`Question Type` and overall :guilabel:`Options` configured on the survey form."
msgid "If the selected :guilabel:`Question Type` is either :guilabel:`Multiple choice: only one answer` or :guilabel:`Multiple choice: multiple answers allowed`, there is a :guilabel:`Show Comments Field` present in the :guilabel:`Answers` section."
msgid "In the :guilabel:`Comment Message` field, type in a guiding message to help participants know what is expected of them (e.g. `If other, please specify`)."
msgid "If the :guilabel:`Comment is an answer` option is enabled, Odoo takes the participant's commented response as an answer, and not just commentary on the question. This is best utilized in surveys where there is no scoring option enabled."
msgid "If the selected :guilabel:`Question Type` is :guilabel:`Multiple Lines Text Box`, a :guilabel:`Placeholder` field appears in the :guilabel:`Answers` section of the :guilabel:`Options` tab."
msgid "In the :guilabel:`Placeholder` field, enter a guiding direction to help participants know what they should write in the :guilabel:`Multiple Lines Text Box` presented to them."
msgid "If the selected :guilabel:`Question Type` is :guilabel:`Single Line Text Box`, :guilabel:`Numerical Value`, :guilabel:`Date`, or :guilabel:`Datetime`, two options appear in the :guilabel:`Answers` section of the :guilabel:`Options` tab: :guilabel:`Validate Entry` and :guilabel:`Placeholder`."
msgid "If the :guilabel:`Validate Entry` option is enabled, two additional fields appear beneath: :guilabel:`Min/Max Limits` and :guilabel:`Validation Error`."
msgid "When :guilabel:`Mandatory Answer` is enabled, that means that specific question requires an answer from the participant before they can move on. Also, when :guilabel:`Mandatory Answer` is enabled, that reveals an additional field: :guilabel:`Error Message`."
msgid ":guilabel:`Conditional Display` means the question is **only** displayed if a specified conditional answer(s) (i.e. :guilabel:`Triggering Answers`) has been selected in a previous question(s)."
msgid "In the :guilabel:`Triggering Answers` field, select specific responses from previous questions that would trigger this question. More than one answer can be selected. Leave the field empty if the question should always be displayed."
msgid "When the :guilabel:`Question Time Limit` option is enabled, designate how much time (in :guilabel:`seconds`) participants have to answer the question during a *Live Session* survey."
msgid "To measure a survey participant's performance, knowledge, or overall satisfaction, Odoo ascribes points to survey answers. At the end of the survey, these points are summed up, resulting in the participant's final score."
msgid "To add points to questions, open the :guilabel:`Surveys` application, choose the desired survey form, and then click on the :guilabel:`Options` tab. Under the :guilabel;`Scoring` section, choose between :guilabel:`Scoring with answers at the end` or :guilabel:`Scoring without answers at the end`."
msgid ":guilabel:`Scoring with answers at the end` shows the survey participant their answers after completing the survey, and displays which questions they got right or wrong. On questions where there was an incorrect answer, the correct answer will be highlighted."
msgid ":guilabel:`Scoring without answers at the end` does not show the survey participant their answer choices after completing the survey, only their final score."
msgid "To indicate correct answers, click on the :guilabel:`Questions tab` and choose a question. In the question form, check the :guilabel:`Is a correct answer` box for the choice that is the correct answer and attach a score value."
msgid "Back on the :guilabel:`Options` tab of the survey, set the :guilabel:`Success %`. The percentage entered determines what percentage of correct answers is needed to pass the survey."
msgid "Further on the :guilabel:`Options` tab of the survey, survey administrators can also choose to make the survey a certification. A certification indicates that the survey asks questions to test the participants' knowledge level on a subject."
msgid "When enabling the :guilabel:`Is a certification` option, choose a :guilabel:`Certification email template`. The certification will automatically be emailed using this email template to users who pass the survey with a final score that is greater than or equal to the set :guilabel:`Success %`."
msgid "In the :guilabel:`Candidates` section, participants can be required to log in to take the survey. If the :guilabel:`Login Required` setting is enabled, two new options appear: the :guilabel:`Attempts Limit` checkbox, which limits the number of times a participant can attempt the survey, and the option to :guilabel:`Give Badge`, located beneath the :guilabel:`Certification` options in the :guilabel:`Scoring` section."
msgid "Badges are displayed on the eLearning portion of a given user's portal, and are a way to set milestones and reward participants for passing surveys or gaining points. Besides the awardee, website visitors who access the :guilabel:`Courses` page will also be able to see the granted badges."
