NextERP/documentation
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
18.0
documentation/locale/fi/LC_MESSAGES/marketing.po
Odoo Translation Bot 19cb93e6b5 [I18N] *: fetch 18.0 translations
2025-02-23 08:02:15 +00:00

13925 lines
533 KiB
Plaintext
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# SOME DESCRIPTIVE TITLE.
# Copyright (C) Odoo S.A.
# This file is distributed under the same license as the Odoo package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
# Translators:
# Tuomas Vihinen, 2025
# Jessica Jakara, 2025
# Ossi Mantylahti <ossi.mantylahti@obs-solutions.fi>, 2025
# Martti Valto, 2025
# Wil Odoo, 2025
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Odoo 18.0\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-20 16:01+0000\n"
"PO-Revision-Date: 2024-10-08 06:34+0000\n"
"Last-Translator: Wil Odoo, 2025\n"
"Language-Team: Finnish (https://app.transifex.com/odoo/teams/41243/fi/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: fi\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
#: ../../content/applications/marketing.rst:5
msgid "Marketing"
msgstr "Markkinointi"
#: ../../content/applications/marketing/email_marketing.rst:5
msgid "Email Marketing"
msgstr "Sähköpostimarkkinointi"
#: ../../content/applications/marketing/email_marketing.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:12
msgid ""
"`Odoo Tutorial: Email Marketing <https://www.odoo.com/slides/slide/email-"
"marketing-essentials-989?fullscreen=1>`_"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:38
msgid "Email marketing dashboard"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:40
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the main dashboard of the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:47
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:51
msgid ""
"The information on the :guilabel:`Mailings` dashboard has four different "
"view options, located in the upper-right corner as individual icons."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:54
msgid "The view options, from left-to-right, are:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:56
msgid ":ref:`List <email_marketing/list-view>` (default view)"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:57
msgid ":ref:`Kanban <email_marketing/kanban-view>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:58
msgid ":ref:`Calendar <email_marketing/calendar-view>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:59
msgid ":ref:`Graph <email_marketing/graph-view>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:64
#: ../../content/applications/marketing/email_marketing.rst:736
#: ../../content/applications/marketing/social_marketing/social_posts.rst:52
#: ../../content/applications/marketing/surveys.rst:172
msgid "List view"
msgstr "Listanäkymä"
#: ../../content/applications/marketing/email_marketing.rst:66
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:69
msgid ""
"While in list view, there are columns dedicated to different aspects of "
"information related to the listed emails. Those columns are as follows:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:72
msgid ":guilabel:`Date`: the date the email was sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:73
msgid ":guilabel:`Subject`: the subject of the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:74
msgid ""
":guilabel:`Responsible`: the user who created the email, or the user who has"
" been assigned to the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:76
msgid ":guilabel:`Sent`: how many times the email has been sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:77
msgid ""
":guilabel:`Delivered (%)`: percentage of sent emails that have been "
"successfully delivered."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:78
msgid ""
":guilabel:`Opened (%)`: percentage of sent emails that have been opened by "
"the recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:79
msgid ""
":guilabel:`Clicked (%)`: percentage of sent emails that have been clicked by"
" the recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:80
msgid ""
":guilabel:`Replied (%)`: percentage of sent emails that have been replied to"
" by the recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:81
msgid ""
":guilabel:`Status`: the status of the email (:guilabel:`Draft`, "
":guilabel:`In Queue`, or :guilabel:`Sent`)."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:84
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:91
#: ../../content/applications/marketing/email_marketing.rst:709
#: ../../content/applications/marketing/social_marketing/social_posts.rst:23
msgid "Kanban view"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:93
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"Kanban view of the main dashboard of the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:100
msgid ""
"While in Kanban view, the email information is displayed in the various "
"stages."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:102
msgid ""
"The stages are: :guilabel:`Draft`, :guilabel:`In Queue`, "
":guilabel:`Sending`, and :guilabel:`Sent`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:104
msgid ":guilabel:`Draft`: the email is still being written/created."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:105
msgid ""
":guilabel:`In Queue`: the email is scheduled to be sent at a later date."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:106
msgid ""
":guilabel:`Sending`: the email is currently being sent to its recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:107
msgid ":guilabel:`Sent`: the email has already been sent to its recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:109
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:112
msgid ""
"Each card on the :guilabel:`Mailings` dashboard provides key information "
"related to that specific email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the three-dot drop-down menu on the Odoo Email Marketing dashboard."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:127
#: ../../content/applications/marketing/social_marketing/social_posts.rst:36
msgid "Calendar view"
msgstr "Kalenterinäkymä"
#: ../../content/applications/marketing/email_marketing.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:132
msgid ""
"While in calendar view, a monthly calendar (by default), shows when the "
"mailings have been sent or are scheduled to be sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"Calendar view of the mailings dashboard in the Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:139
msgid ""
"The current date is represented by a :guilabel:`🔴 (red circle)` icon over "
"the date on the calendar."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:141
msgid ""
"To the right of the calendar, the options to filter the results by "
":guilabel:`Responsible` and/or :guilabel:`Status` are available, via "
"checkboxes."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:145
msgid ""
"To hide the right sidebar, click the :guilabel:`(panel-right)` icon, located"
" above the sidebar."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:147
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)."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:152
msgid ""
"Clicking any of those options changes the calendar display to reflect that "
"desired amount of time."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:154
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:158
msgid "To jump back to the current date, click the :guilabel:`Today` button."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:163
msgid "Graph view"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:165
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:168
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "How the Graph view appears in the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:175
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:178
msgid ""
"Those :guilabel:`Measures` options are: :guilabel:`A/B Testing percentage` "
"and :guilabel:`Count` (default)."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:181
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:185
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)`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:190
msgid ""
"Each graph view option provides its own series of additional view options, "
"which appear to the right of the selected graph view option."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:194
msgid "Search options"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:196
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:200
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"The drop-down mega menu of search options the Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:207
msgid ""
"These options provide various ways to specify and organize the information "
"seen on the :guilabel:`Mailings` dashboard."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:212
msgid "Filters"
msgstr "Suodattimet"
#: ../../content/applications/marketing/email_marketing.rst:214
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:0
msgid ""
"View of filters drop-down menu options on the Odoo Email Marketing "
"dashboard."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:221
msgid ""
"The options are: :guilabel:`My Mailings`, :guilabel:`Sent Date`, "
":guilabel:`A/B Tests`, :guilabel:`A/B Tests to review`, "
":guilabel:`Archived`, and :guilabel:`Add Custom Filter`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:224
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:0
msgid ""
"Add custom filter pop-up window that appears in Odoo Email Marketing app."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:232
msgid "Group By"
msgstr "Ryhmittely"
#: ../../content/applications/marketing/email_marketing.rst:234
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:0
msgid ""
"View of the Group By drop-down menu on the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:241
msgid ""
"Using this section, the data can be grouped by the messages' "
":guilabel:`Status`, or who it was :guilabel:`Sent By`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:244
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:248
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:253
msgid "Favorites"
msgstr "Suosikit"
#: ../../content/applications/marketing/email_marketing.rst:255
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:0
msgid ""
"View of the Favorites drop-down menu on the Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:263
msgid ""
"Give the favorited filter/grouping a title on the blank line above the "
"checkboxes for :guilabel:`Default filter` and :guilabel:`Shared`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:266
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:270
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:274
#: ../../content/applications/marketing/events.rst:99
msgid "Settings"
msgstr "Asetukset"
#: ../../content/applications/marketing/email_marketing.rst:276
msgid ""
"To view and modify the *Email Marketing* settings, navigate to "
":menuselection:`Email Marketing app --> Configuration --> Settings`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the Configuration menu with Settings page in the Odoo Email "
"Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:283
msgid "On the :guilabel:`Settings` page, there are four features available."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the Settings page in the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:289
msgid "The features are:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:291
msgid ""
":guilabel:`Mailing Campaigns`: enables the option to manage mass mailing "
"campaigns."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:292
msgid ""
":guilabel:`Blacklist Option when Unsubscribing`: allows recipients to "
"blacklist themselves from future mailings during the unsubscribing process."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:294
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:297
msgid ""
":guilabel:`24H Stat Mailing Reports`: allows users to check how well "
"mailings have performed a day after it has been sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:303
msgid "Create an email"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:305
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:308
msgid "Clicking :guilabel:`New` reveals a blank email form."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of a blank email detail form in Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:314
msgid ""
"On the email form, there are fields for the :ref:`Subject "
"<email_marketing/subject>` and :ref:`Recipients "
"<email_marketing/recipients>` of the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:317
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:323
msgid "Subject"
msgstr "Aihe"
#: ../../content/applications/marketing/email_marketing.rst:325
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:329
msgid ""
"The :guilabel:`Subject` field is mandatory. An email can **not** be sent "
"without a :guilabel:`Subject`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:332
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:336
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:344
msgid "Recipients"
msgstr "Vastaanottajat"
#: ../../content/applications/marketing/email_marketing.rst:346
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:350
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:354
msgid ""
"More than one mailing list can be chosen from the :guilabel:`Select mailing "
"lists` field."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:356
msgid ""
"Odoo then sends the email to contacts on that specific mailing list(s)."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:359
#: ../../content/applications/marketing/email_marketing.rst:825
msgid ":doc:`email_marketing/mailing_lists`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:361
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of recipients drop-down menu in the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:368
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:372
msgid ""
"The :guilabel:`Recipients` field options, other than the default "
":guilabel:`Mailing List` option, are as follows:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:375
msgid ""
":guilabel:`Contact`: ties specifically to the *Contacts* app, and includes "
"all the contacts entered in the database."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:377
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:380
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:382
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:387
msgid ""
":guilabel:`Sales Order`: ties specifically to the *Sales* app, and focuses "
"on a specific sales orders in the database."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:391
msgid "Add recipient filter"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:393
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:398
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:402
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:407
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:0
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of how recipient filters can be customized in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:416
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:419
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:427
msgid ""
"Some sub-menu options in the first rule field allow for a second choice to "
"provide even more specificity."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:430
msgid ""
"To the right of each rule, there are three additional options, represented "
"by :guilabel:`➕ (plus sign)`, :guilabel:`(sitemap)`, and :guilabel:`🗑️ "
"(trash)` icons."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:433
msgid ""
"The :guilabel:`➕ (plus sign)` icon adds a new node (line) to the overall "
"targeting logic."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:434
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:437
msgid ""
"The :guilabel:`🗑️ (trash)` icon deletes a specific node (line) in the array "
"of logic."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:442
msgid "Mail Body tab"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:444
msgid ""
"In the :guilabel:`Mail Body` tab, there are a number of pre-configured "
"message templates to choose from."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the templates in the Mail Body tab in Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:451
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the building blocks in the Mail Body tab in Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:458
msgid ""
"The features on the sidebar used to create and customize emails are "
"separated into three sections: :guilabel:`Blocks`, :guilabel:`Customize`, "
"and :guilabel:`Design`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:461
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:466
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."
msgstr ""
"Jos haluat rakentaa sähköpostin alusta alkaen ilman "
"rakennuspalikkaelementtejä, valitse :guilabel:\"Plain Text\" -malli. Kun "
"valittuna, Odoo tarjoaa täysin tyhjän sähköpostipohjan, jota voidaan "
"mukauttaa useilla tavoilla käyttämällä käyttöliittymän rich text editoria, "
"joka hyväksyy vinoviivan `/`-komennot."
#: ../../content/applications/marketing/email_marketing.rst:471
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."
msgstr ""
"Kun `/` kirjoitetaan sähköpostin tyhjään runkoon, kun käytät "
":guilabel:`Plain Text` -mallia, näkyviin tulee erilaisten "
"suunnitteluelementtien pudotusvalikko, jota voidaan käyttää halutun "
"sähköpostimallin luomiseen."
#: ../../content/applications/marketing/email_marketing.rst:0
msgid ""
"View of the rich text editor drop-down in the Odoo Email Marketing "
"application."
msgstr ""
"Näkymä Odoo Email Marketing -sovelluksen avattavasta Rich Text Editor "
"-valikosta."
#: ../../content/applications/marketing/email_marketing.rst:482
msgid "A/B Tests tab"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:484
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."
msgstr ""
"Aluksi, kun :guilabel:`A/B-testit`-välilehti avataan sähköpostilomakkeella, "
"ainoa käytettävissä oleva vaihtoehto on :guilabel:`Salli A/B-testit`. Tämä "
"**ei** ole pakollinen vaihtoehto."
#: ../../content/applications/marketing/email_marketing.rst:487
msgid ""
"If this option is enabled, recipients are only mailed *once* for the "
"entirety of the campaign."
msgstr ""
"Jos tämä vaihtoehto on käytössä, vastaanottajille lähetetään postia vain "
"*kerran* koko kampanjan ajan."
#: ../../content/applications/marketing/email_marketing.rst:489
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."
msgstr ""
"Näin käyttäjä voi lähettää saman postituksen eri versioita satunnaisesti "
"valituille vastaanottajille arvioidakseen eri mallien, formaattien, "
"ulkoasujen, sisällön ja niin edelleen tehokkuutta - ilman, että lähetetään "
"päällekkäisiä viestejä."
#: ../../content/applications/marketing/email_marketing.rst:493
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:498
msgid ""
"The default figure in the :guilabel:`on (%)` field is `10`, but that figure "
"can be changed at any time."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:501
msgid "Beneath that, two additional fields appear:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:503
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:507
msgid "The options in the :guilabel:`Winner Selection` field are as follows:"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:509
msgid ""
":guilabel:`Manual`: allows the user to determine the \"winning\" version of "
"the mailing. This option removes the :guilabel:`Send Final On` field."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:511
msgid ""
":guilabel:`Highest Open Rate` (default): the mailing with the highest open "
"rate is determined to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:513
msgid ""
":guilabel:`Highest Click Rate`: the mailing with the highest click rate is "
"determined to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:515
msgid ""
":guilabel:`Highest Reply Rate`: the mailing with the highest reply rate is "
"determined to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:517
msgid ""
":guilabel:`Leads`: the mailing with the most leads generated is determined "
"to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:519
msgid ""
":guilabel:`Quotations`: the mailing with the most quotations generated is "
"determined to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:521
msgid ""
":guilabel:`Revenues`: the mailing with the most revenue generated is "
"determined to be the \"winning\" version."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:524
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the A/B Tests tab in Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:532
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:539
msgid "Settings tab"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:541
msgid ""
"The options present in the :guilabel:`Settings` tab of the mail form are "
"divided into two sections: :guilabel:`Email Content` and "
":guilabel:`Tracking`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:545
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:549
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of settings tab in Odoo Email Marketing app, without campaign setting "
"activated."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:558
msgid "Email content"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:560
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:564
msgid ""
":guilabel:`Send From`: designate an email alias that displays as the sender "
"of this particular email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:566
msgid ""
":guilabel:`Reply To`: designate an email alias to whom all the replies of "
"this particular email are sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:568
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:572
msgid "Tracking"
msgstr "Seuranta"
#: ../../content/applications/marketing/email_marketing.rst:574
msgid ""
":guilabel:`Responsible`: designate a user in the database to be responsible "
"for this particular email."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:578
msgid ""
"If the *Mailing Campaign* feature *is* activated, an additional "
":guilabel:`Campaign` field appears in the :guilabel:`Tracking` section of "
"the :guilabel:`Settings` tab."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of settings tab in Odoo Email Marketing when campaign setting is "
"activated."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:585
msgid ""
"The additional :guilabel:`Campaign` field allows users to attach this "
"particular email to a mailing campaign, if desired."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:588
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:591
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:595
msgid "Send, schedule, test"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:597
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:604
msgid "Send"
msgstr "Lähetä"
#: ../../content/applications/marketing/email_marketing.rst:606
msgid ""
"The :guilabel:`Send` button reveals a :guilabel:`Ready to unleash emails?` "
"pop-up window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of pop-up window that appears when the send button on an email form is "
"clicked."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:612
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:618
msgid "Schedule"
msgstr "Aikatauluta"
#: ../../content/applications/marketing/email_marketing.rst:620
msgid ""
"The :guilabel:`Schedule` button reveals a :guilabel:`When do you want to "
"send your mailing?` pop-up window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of pop-up window that appears when the schedule button on an email form"
" is clicked."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:627
msgid ""
"In this pop-up window, click the :guilabel:`Send on` field to reveal a "
"calendar pop-up window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:633
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:640
msgid "Test"
msgstr "Testi"
#: ../../content/applications/marketing/email_marketing.rst:642
msgid ""
"The :guilabel:`Test` button reveals a :guilabel:`Test Mailing` pop-up "
"window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of pop-up window that appears when the test button on an email form is "
"clicked."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:648
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:652
msgid ""
"Once all the desired email addresses have been entered in the "
":guilabel:`Recipients` field, click the :guilabel:`Send Test` button."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:656
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:664
msgid "Mailing campaigns"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:666
msgid ""
"The *Email Marketing* application provides users with the ability to build "
"mailing campaigns."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:668
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the campaign feature setting in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:677
msgid ""
"Once the :guilabel:`Mailing Campaigns` feature is activated, a new "
":guilabel:`Campaigns` menu option appears in the header."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:680
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the campaign page in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:688
msgid ""
"This information can also be viewed in a list, by clicking the :guilabel:`☰ "
"(horizontal lines)` icon in the upper-right corner."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:691
msgid ""
"Clicking any campaign from the :guilabel:`Campaigns` page reveals that "
"campaign's form."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:693
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:700
msgid "Create mailing campaign (from campaigns page)"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:702
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:706
msgid ""
"To do that, navigate to :menuselection:`Email Marketing app --> Campaigns "
"--> New`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:711
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the campaign pop-up kanban in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:718
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:721
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:724
msgid ""
"To add the campaign to the Kanban stage, click the :guilabel:`Add` button."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:726
msgid "To delete the campaign, click the :guilabel:`🗑️ (trash can)` icon."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:728
msgid ""
"To further customize the campaign, click the :guilabel:`Edit` button, which "
"reveals the campaign form for additional modifications."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:732
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:738
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the campaign page in list view in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:745
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the blank campaign form in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:752
msgid ""
"From this campaign form, a :guilabel:`Campaign Name`, a "
":guilabel:`Responsible`, and :guilabel:`Tags` can be added."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:755
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:760
msgid ""
"Once a :guilabel:`Campaign Name` is entered and saved, additional buttons "
"appear at the top of the campaign form."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:763
msgid ""
"Those additional buttons are: :guilabel:`Send Mailing` and :guilabel:`Send "
"SMS`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:766
msgid "Campaign form"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:768
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid "View of the campaign form in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:775
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:779
msgid ""
"There are also buttons to :guilabel:`Send Mailing`, :guilabel:`Send SMS`, "
":guilabel:`Add Post`, and :guilabel:`Add Push` (push notification)."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:783
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:787
msgid ""
"The status of the campaign can be viewed in the upper-right corner of the "
"campaign form, as well."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:792
msgid "Create mailing campaign (from settings tab)"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:794
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the mailing campaign creation in the Settings tab of an email form."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:803
msgid ""
"Select :guilabel:`Create` to add this new mailing campaign to the database, "
"and modify its settings in the future."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:806
msgid ""
"Select :guilabel:`Create and Edit...` to add this new mailing campaign to "
"the database, and reveal a :guilabel:`Create Campaign` pop-up window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst-1
msgid ""
"View of the email mailing campaign pop-up window in Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:813
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:816
msgid ""
"Buttons to :guilabel:`Add Post` or :guilabel:`Send Push` (push "
"notifications) are also available."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:818
msgid ""
"There is also a status located in the upper-right corner of the "
":guilabel:`Create Campaign` pop-up window."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:821
msgid ""
"When all modifications are ready to be finalized, click :guilabel:`Save & "
"Close`. To delete the entire campaign, click :guilabel:`Discard`."
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:826
msgid ":doc:`email_marketing/unsubscriptions`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:827
msgid ":doc:`email_marketing/lost_leads_email`"
msgstr ""
#: ../../content/applications/marketing/email_marketing.rst:828
msgid ":doc:`email_marketing/analyze_metrics`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:3
msgid "Analyze metrics"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:16
msgid "View metrics"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:18
msgid ""
"After a mass mail has been sent, the results for that particular mailing are"
" displayed in multiple locations."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:21
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:25
msgid ""
"At the top of the record, detailed metrics are displayed as smart buttons."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst-1
msgid ""
"The smart buttons on a mass mailing, displaying the results of the message."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:32
msgid "Opened rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:34
msgid ""
"The percentage of emails opened by recipients, against the total number of "
"sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:36
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:39
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:42
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:47
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:53
msgid "Replied rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:55
msgid ""
"The percentage of recipients who responded to the email, against the total "
"number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:57
msgid ""
"A high replied rate may indicate the email resonated with recipients, "
"prompting them to take action or provide feedback."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:60
msgid ""
"A low replied rate may suggest the message lacked relevance or did not "
"contain a clear call-to-action."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:64
msgid "Clicked rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:66
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:70
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:78
msgid "Received rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:80
msgid ""
"This rate measures the percentage of emails that were **successfully** "
"delivered, against the total number of sent emails."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:83
msgid ""
"A high received rate can indicate the mailing list used is up-to-date, and "
"the sender authentication is trusted by email providers."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:86
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:91
msgid "Bounced rate"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:93
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:96
msgid ""
"A high bounce rate could indicate issues, either with the mailing list used "
"for the mailing, or with the sender authentication."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:99
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:104
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:111
msgid "Create metrics reports"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:113
msgid ""
"Individual metrics can be analyzed by creating a report. To begin, click on "
"the smart button of the desired metric."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:116
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:119
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:123
msgid ""
":guilabel:`Group By`, found in the middle column, is used to organize the "
"results into groups, and can be used with or without filters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:127
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:133
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:137
msgid ""
"A monthly newsletter has been sent out, and 6.9% of the sent emails were "
"bounced."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "The metrics smart buttons of the newsletter."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:143
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "The custom filter creation form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:153
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "A list of bounced email addresses with malformed email domains."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:163
msgid ""
"View :doc:`../../essentials/search` for more information about making custom"
" groups and filters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:169
msgid "Mass mailing analysis"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:171
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:175
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:181
msgid ""
"The following chart displays the number of opened emails from two different "
"mass mailings."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:183
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid ""
"A bar chart displaying the different opened rate between two mass mailing "
"campaigns."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:192
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:0
msgid "alt text"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:200
msgid "Deliverability issues"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:202
msgid ""
"The following define possible reasons for a high bounce rate or low received"
" rate:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:204
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:206
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:209
msgid ""
"Failing to :doc:`configure the proper DNS records "
"<../../general/email_communication/email_domain>` can also result in a high "
"bounce rate."
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:213
msgid ":ref:`Mailing campaigns <email_marketing/mailing-campaigns>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/analyze_metrics.rst:214
msgid ":doc:`Manage unsubscriptions <unsubscriptions>`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:3
msgid "Lost leads reactivation email"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:8
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:11
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:15
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:19
msgid ""
"The warehouse manager uses the following filters for a lost leads email:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:21
msgid ":guilabel:`Blacklist` *is* `not set`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:22
msgid ":guilabel:`Created on` *>=* `01/01/2024 00:00:01`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:23
msgid ":guilabel:`Stage` *is not in* `New`, `Qualified`, or `Won`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:24
msgid ":guilabel:`Lost Reason` *is in* `Not enough stock`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:25
msgid "and either :guilabel:`Active` *is* `set` or `not set`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"A lost leads reactivation filter list excluding lost reasons like Too "
"Expensive."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:32
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:36
msgid ""
"To view a list of all matching records, click the :guilabel:`# record(s)` "
"text."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid "The # record(s) text is located below the list of Recipient filters."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:43
msgid "Minimum requirements"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:45
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:48
msgid ""
"Here are the minimum necessary filters that pertain to a lost leads "
"reactivation mailing campaign:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:50
msgid ""
"The :ref:`Recipients <email_marketing/recipients_field>` field **must** be "
"set to the *Lead/Opportunity* model."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:52
msgid ""
"A :ref:`Blacklist <email_marketing/blacklist_filter>` filter to exclude "
"unsubscribed recipients."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:53
msgid ""
"A :ref:`Created on <email_marketing/created_on_filter>` to target leads that"
" were lost during a specific period of time."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:55
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:59
msgid ""
"One or more :ref:`Lost Reason <email_marketing/lost_reason_filter>` filters "
"to exclude undesired leads, such as duplicate, spam, or irrelevant records."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:61
msgid ""
"A pair of :ref:`Active <email_marketing/active_filter>` filters to target "
"*both* active and inactive leads."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:65
msgid "Add the necessary filters"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:67
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:85
msgid "Created on"
msgstr "Luotu"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:87
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.)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:96
msgid ""
"In the third field, use the calendar popover window to select dates, and "
"click :guilabel:`Apply` to lock in the time range."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst-1
msgid ""
"A custom filter rule setting the time period to be anything before today's "
"date."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:104
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`)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"The statement at the top of the filters list, with the drop-down menu open."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:116
msgid "Stage"
msgstr "Vaihe"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:118
msgid ""
"Now, add the :guilabel:`Stage` filter to exclude leads that are in the "
"*New*, *Qualified*, and *Won* stages of the sales pipeline."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:122
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."
msgstr ""
"Tässä vaiheessa oletetaan, että *New*-, *Qualified*- ja *Won*-vaiheet ovat "
"CRM-liukuhihnassa; taiteilijanimet voivat kuitenkin vaihdella "
"yrityskohtaisesti. Katso tietokannan todelliset näyttämönimet "
"*CRM*-sovelluksen prosessissa suorittaaksesi tämän vaiheen vastaavasti"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:126
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."
msgstr ""
"Aloita uudelleen napsauttamalla :guilabel:`Uusi sääntö` ja valitse "
":guilabel:`Vaihe` ensimmäisen kentän avattavasta valikosta. Valitse toisessa"
" kentässä operaattori :guilabel:`is not in` ja kolmannesta kentästä "
":guilabel:`New`, :guilabel:`Qualified` ja :guilabel:`Voitti`-vaiheet "
"määrittääksesi säännön. parametrit."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:131
msgid ""
"When the rule is added in this way, the logic in the third field renders as "
":code:`OR` (`|`) statements."
msgstr ""
"Kun sääntö lisätään tällä tavalla, kolmannen kentän logiikka esitetään "
":code:`OR` (`|`) -lausekkeina."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst-1
msgid ""
"Include multiple Stages in the filtering rule, using the \"is in\" operator."
msgstr ""
"Sisällytä useita vaiheita suodatussääntöön ”is in” operaattorin avulla."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:139
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."
msgstr ""
"Toinen tapa lisätä Stage sääntöjä on tehdä se yksi sääntö per rivi "
"-periaatteella käyttäen :guilabel:contains tai :guilabel:does not contain "
"operaattoreita ja kirjoittamalla määrittävät merkit jokaisen stage-nimen "
"kohdalle käsin. Tämä menetelmä kuitenkin sallii vain yhden valinnan "
"kerrallaan, mikä voi olla hyödyllistä suodattimien nopeassa päälle/pois "
"kytkemisessä :guilabel:Search... palkissa."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"Three filter rules requiring that the Stage does not contain New, Qualified,"
" or Won."
msgstr ""
"Kolme suodatussääntöä, jotka edellyttävät, että Vaihe ei sisällä Uusia, "
"Hyväksytty- tai Voitettuja."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:151
msgid "Lost Reason"
msgstr "Häviämisen syy"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:153
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>`."
msgstr ""
"Lisää seuraavaksi yksi tai useampi :guilabel:\"Lost Reason\" -sääntö "
"sulkeaksesi pois liidejä, joita **ei** pitäisi kohdistaa tiettyihin "
":doc:`lost reasons <../../sales/crm/pipeline/lost_opportunities>`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:156
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."
msgstr ""
"Tätä varten luo jälleen uusi :guilabel:`New Rule`. Valitse sitten säännön "
"ensimmäiseen kenttään :guilabel:`Lost Reason` pudotusvalikosta. Valitse "
"operaattoriksi joko :guilabel:`is not in` tai :guilabel:`does not contain` "
"pudotusvalikosta. Jos valitset kumman tahansa, kirjoita kolmanteen kenttään "
"sääntöön sisällytettävä kadonneen syy (tai useita kadonneen syitä "
"operaattorin valinnasta riippuen)."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:162
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."
msgstr ""
"Jos valitset :guilabel:`does not contain`-operaattorin, toista edelliset "
"vaiheet lisätäksesi lisää kadonneita syitä tarpeen mukaan, jolloin jokainen "
"kadonnut syy vie yhden sääntörivin kerrallaan."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:165
msgid ""
"For more information, refer to the section below outlining how to "
":ref:`select appropriate lost reasons "
"<email_marketing/select_lost_reasons>`."
msgstr ""
"Lisätietoja saat alla olevasta osiosta, jossa kerrotaan, miten "
":ref:`valitaan sopivat kadonneet syyt "
"<email_marketing/select_lost_reasons>`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst-1
msgid ""
"A list of filter rules that exclude all lost reasons other than the desired "
"reason."
msgstr ""
"Luettelo suodatinsäännöistä, jotka sulkevat pois kaikki muut menetetyt syyt "
"kuin haluttu syy."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:175
msgid "Active"
msgstr "Aktiivinen"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:177
msgid ""
"Finally, add a pair of :guilabel:`Active` filters to include both active and"
" inactive leads for the campaign."
msgstr ""
"Lisää lopuksi pari :guilabel:`Active`-suodatinta, jotta kampanjaan voidaan "
"sisällyttää sekä aktiiviset että inaktiiviset liidit."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:181
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."
msgstr ""
"Sekä aktiivisten * että* ei-aktiivisten liiditietueiden lisääminen on "
"välttämätöntä, jotta tietokantaan voidaan tallentaa kaikki kadonneet liidit."
" Toisen tekeminen ilman toista vaikuttaa suuresti sähköpostikampanjan "
"kohdistettavien tietueiden määrään, eikä se **ei** sisällä täydellistä tai "
"tarkkaa menetettyjen liidien yleisöä."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:186
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`."
msgstr ""
"Napsauta ensin :guilabel:`(Add Branch)` -kuvaketta viimeksi luodussa "
"säännössä (esim. :guilabel:`Lost Reason`), joka on sääntörivin oikealla "
"puolella olevien kolmen kuvakkeen keskellä. Tämä lisää parin "
":guilabel:\"joka tahansa\" sääntöä. Valitse sitten juuri luodun haaran "
"ylimmän säännön ensimmäisessä kentässä avattavasta valikosta parametri "
":guilabel:`Active. Sääntö täyttyy sitten automaattisesti lukemaan: "
":guilabel:`Active` *is* `set`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:192
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`."
msgstr ""
"Valitse haaran alimman säännön ensimmäiseksi kenttään avattavasta valikosta "
"uudelleen :guilabel:`Active`. Tällä kertaa valitse kuitenkin toisen kentän "
"avattavasta operaattorivalikosta :guilabel:`is not`. Säännön pitäisi sitten "
"olla seuraava: :guilabel:`Active` *is not* `set`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst-1
msgid ""
"A pair of Match Any Of filter rules that include both active and inactive "
"leads."
msgstr ""
"Pari Match Any Of -suodatussääntöä, jotka sisältävät sekä aktiiviset että "
"inaktiiviset liidit."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:201
msgid "Add body content"
msgstr "Lisää vartalosisältöä"
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:203
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>`."
msgstr ""
"Nyt kanssa sähköpostikampanjan verkkotunnusosio on valmis, luo sähköpostin "
"runkosisältö millä tahansa valmiiksi tehty tyylitellyistä malleista tai "
"valitse :guilabel:`Pelateksti` tai :guilabel:`Aloita tyhjästä` "
"-vaihtoehdoista saadaksesi lisää. rakeinen ohjaus. Katso lisätietoja "
"*Sähköpostimarkkinointi* :ref:`dokumentaatiosta sähköpostin luomiseen "
"<email_marketing/create_email>`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:209
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`."
msgstr ""
"Tallenna suodatinsarja myöhempää käyttöä varten napsauttamalla "
":guilabel:`Tallenna suosikkisuodattimeksi 💾 (levyke)`, kirjoita nimi (kuten "
"`Lost Leads`) ja napsauta :guilabel:`Lisää`."
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"The Save as Favorite Filter pop-up can save the lost leads criteria for "
"later."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:217
msgid "Send or schedule"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:219
msgid "Once all the components of the email campaign are complete, either:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:221
msgid ""
"click the purple :guilabel:`Send` button at the top-left of the form to "
"immediately send the email; or"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:223
msgid ""
"click the gray :guilabel:`Schedule` button, located to the right of the "
":guilabel:`Send` button, to send the email at a future date and time."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:227
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:231
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"The A/B Tests tab with the Allow A/B Testing box checked to create an "
"alternate version."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:242
msgid "Select appropriate lost reasons"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:244
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:248
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:252
msgid ""
"For more information on *Lost Reasons*, including the creation of them, "
"refer to :doc:`../../sales/crm/pipeline/lost_opportunities`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:255
msgid "By default, Odoo includes a few common *Lost Reasons*, such as:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:257
msgid "*Too expensive*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:258
msgid "*We don't have people/skills*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:259
msgid "*Not enough stock*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:261
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)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:267
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*."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"A list of filter rules that exclude all lost reasons except for Out of "
"Stock."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:274
msgid ""
"If the email advertises a price reduction, it makes sense to target leads "
"with the lost reason: *too expensive*."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:0
msgid ""
"A list of filter rules that exclude all lost reasons except for Too "
"Expensive."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:282
msgid "Analyze the results"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:284
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:287
msgid ""
"Clicking on any of the smart buttons opens a list of records matching that "
"button's specific criteria."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst-1
msgid ""
"The Mailing page of a sent email showing the smart buttons along the top of "
"the page."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:294
msgid "The smart buttons include:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:296
msgid ":guilabel:`Sent`: total number of emails sent."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:297
msgid ":guilabel:`Opened`: percentage of recipients that opened the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:298
msgid ""
":guilabel:`Replied`: percentage of recipients that replied to the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:299
msgid ""
":guilabel:`Clicked`: click-through rate (%) of recipients that clicked on a "
"link in the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:300
msgid ""
":guilabel:`Leads/Opportunities`: number of leads (or opportunities) that "
"have been created in the *CRM* pipeline, as a result of the email campaign."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:302
msgid ""
":guilabel:`Quotations`: number of quotations that have been created in the "
"*Sales* application, as a result of the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:304
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:307
msgid ""
":guilabel:`Received`: percentage of recipients that received the email."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:308
msgid ""
":guilabel:`Bounced`: percentage of emails that bounced (:dfn:`not "
"delivered`)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:309
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.)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:313
msgid "Email nurturing"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:315
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:319
msgid ""
"The point of nurturing is to keep the email campaign \"visible\" or at the "
"top of a lead's inbox, until they are ready to buy."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:322
msgid ""
"There are many approaches to effective lead nurturing, but they often "
"involve:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:324
msgid "Sending an initial email (such as, a lost leads reactivation email)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:325
msgid ""
"Sending a follow-up email each week (or according to specific triggers) for "
"the duration of the campaign."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:327
msgid ""
"Continuously analyzing results to learn what approaches have resulted in "
"sales."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:328
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:331
msgid ""
"As a campaign progresses, a marketing team may send different follow-up "
"emails depending on how a lead responded the previous week."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:335
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:339
msgid ""
"**Week 1:** the marketing team sends an initial email, with the subject "
"line: *“Limited run merchandise is back in stock! Act now!”*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:341
msgid ""
"**Week 2:** the marketing team sends two different emails, depending on how "
"a lead responded."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:343
msgid ""
"If a lead ignored the Week 1 email: *“Stock is almost out, did you get "
"yours?”*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:344
msgid ""
"If a lead clicked on the Week 1 email: *\"You still have time to add this to"
" your collection\"*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:346
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!”*"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:349
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:355
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:223
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:129
msgid ":doc:`../email_marketing`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:356
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:224
msgid ":doc:`unsubscriptions`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/lost_leads_email.rst:357
msgid ":doc:`../marketing_automation`"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:3
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:15
msgid "Mailing lists"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:9
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:14
msgid "Create mailing lists"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:16
msgid ""
"To create a mailing list in the *Email Marketing* application, navigate to "
":menuselection:`Email Marketing app --> Mailing Lists --> Mailing Lists --> "
"New`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:19
msgid "Clicking :guilabel:`New` reveals a blank mailing list form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid "View of the mailing list form in the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:25
msgid ""
"On the form, type a name in the :guilabel:`Mailing List` field at the top."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:27
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:30
msgid ""
"In the upper-left corner of the mailing list form, there are two buttons: "
":guilabel:`Send Mailing` and :guilabel:`Send SMS`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:34
msgid ""
"The :guilabel:`Send SMS` button **only** appears if the *SMS Marketing* "
"application is installed."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:36
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:40
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>`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:44
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:48
msgid "The smart buttons available on a mailing list form are:"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:50
msgid ""
":guilabel:`Recipients`: how many people are subscribed to the mailing list"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:51
msgid ""
":guilabel:`Mailings`: how many mailings have been sent using this mailing "
"list"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:52
msgid ""
":guilabel:`% Bounce`: percentage of mailings related to this mailing list "
"that have been bounced back"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:54
msgid ""
":guilabel:`% Opt-out`: percentage of recipients that have opted-out of "
"mailings from this mailing list"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:56
msgid ""
":guilabel:`% Blacklist`: percentage of recipients that have blacklisted "
"themselves from the mailing list altogether"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:59
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`)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:64
msgid "Add contacts to mailing list"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:66
msgid ""
"In Odoo *Email Marketing*, there are a few different ways to add contacts to"
" a mailing list."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:68
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:75
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:81
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
"The import contacts button of a mailing list line in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:88
msgid "Doing so reveals an :guilabel:`Import Mailing Contacts` pop-up form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
"The import mailing contacts pop-up form that appears in Odoo Email "
"Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:94
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:97
msgid ""
"The option to import a country, company name, and more is available, via the"
" :guilabel:`Upload a file` link at the bottom of the pop-up form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:100
msgid ""
"When all contacts and configurations are complete, click :guilabel:`Import`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:102
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid "The Mailing List page in the Odoo Email Marketing application."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:111
msgid ""
"The default :guilabel:`Exclude Blacklisted Emails` filter appears in the "
"search bar."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:113
msgid ""
"From the :guilabel:`Mailing List Contacts` page, contacts can be created "
"and/or imported, and then added to a mailing list."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:116
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:119
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
"The Add a line for mailing lists on a standard contact form in Odoo Email "
"Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:127
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:131
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:134
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:138
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:144
msgid "Multiple mailing lists can be added to a single contact form."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:146
msgid ""
"To delete any mailing list from a contact form, simply click the "
":guilabel:`🗑️ (trash can)` icon."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:149
msgid "Link mailing list to website"
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:151
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)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:154
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:159
msgid ""
"Doing so reveals the designated homepage of the Odoo-built website for the "
"database."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:161
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:165
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
"View of how to quickly search for Newsletter blocks in the Odoo Website "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:173
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:177
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid "Sample of how a newsletter block appears on an Odoo Website."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:184
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid "Sample of how a newsletter popup block appears on an Odoo Website."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:193
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:197
msgid ""
"It is covertly designed in this fashion to be cleanly implemented into the "
"content of the webpage and/or footer."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:204
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:208
msgid ""
"From there, open the :guilabel:`Newsletter` drop-down menu, and select the "
"specific mailing list that should be applied to the block."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst-1
msgid ""
"The newsletter drop-down menu in the customize sidebar that appears in Odoo "
"Website."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:215
msgid ""
"Once the desired configurations and customizations are complete, be sure to "
"click the :guilabel:`Save` button in the upper-right corner."
msgstr ""
#: ../../content/applications/marketing/email_marketing/mailing_lists.rst:218
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*."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:3
msgid "Manage unsubscriptions (blacklist)"
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:5
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*."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:11
msgid "Unsubscribe and blacklist"
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:13
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:17
msgid ""
"In order to provide recipients with the ability to blacklist themselves, a "
"specific feature **must** be enabled in the *Email Marketing* application."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:20
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"View of the blacklist feature in the Settings page of the Odoo Email "
"Marketing app."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:29
msgid "Unsubscribe"
msgstr "Lopeta kanavan tilaus"
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:31
msgid ""
"By default, an *Unsubscribe* link appears at the bottom of all mailing "
"templates."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:34
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:39
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"The Mailng Subscriptions page that appears when 'Unsubscribe' link in "
"mailing is clicked."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:48
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:53
msgid ""
"The opt-out answer options can be created and modified by navigating to "
":menuselection:`Email Marketing app --> Configuration --> Optout Reasons`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:56
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:61
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:102
msgid "Blacklist"
msgstr "Markkinointikielto"
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:63
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:67
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`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"The blocklist question on the Mailing Subscriptions page that recipients "
"see."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:74
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:83
msgid "Blacklisted email addresses"
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:85
msgid ""
"To view a complete list of all blacklisted email addresses, navigate to "
":menuselection:`Email Marketing app --> Configuration --> Blacklisted Email "
"Addresses`."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid "View of the blacklisted email addresses page in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid "View of a blacklisted contact detail form in Odoo Email Marketing."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:100
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)."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:104
msgid ""
"Blacklisted emails are excluded from all marketing mailings, however, these "
"emails can still receive transactional emails, such as order confirmations, "
"shipping notifications, etc."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:108
msgid "Unblacklist contacts"
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:110
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:114
msgid ""
"When :guilabel:`Unblacklist` is clicked, an :guilabel:`Are you sure you want"
" to unblacklist this Email Address?` pop-up window appears."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:117
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."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst-1
msgid ""
"View of the unblacklist pop-up window in the Odoo Email Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:125
msgid ""
"After filling in the fields, click :guilabel:`Confirm` to officially remove "
"that particular contact from the blacklist."
msgstr ""
#: ../../content/applications/marketing/email_marketing/unsubscriptions.rst:130
msgid ":doc:`mailing_lists`"
msgstr ""
#: ../../content/applications/marketing/events.rst:5
msgid "Events"
msgstr "Tapahtumat"
#: ../../content/applications/marketing/events.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:12
msgid "`Odoo Tutorials: Events <https://www.odoo.com/slides/surveys-63>`_"
msgstr ""
#: ../../content/applications/marketing/events.rst:57
msgid "Events dashboard"
msgstr ""
#: ../../content/applications/marketing/events.rst:59
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:63
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."
msgstr ""
#: ../../content/applications/marketing/events.rst-1
msgid "Overview of events setting with the kanban view in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events.rst:70
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`."
msgstr ""
#: ../../content/applications/marketing/events.rst:75
msgid ""
"The :guilabel:`Ended` and :guilabel:`Cancelled` stages are folded, by "
"default, and located to the right of the other stages."
msgstr ""
#: ../../content/applications/marketing/events.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:82
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."
msgstr ""
#: ../../content/applications/marketing/events.rst-1
msgid "Typical blank kanban card to fill out in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events.rst:89
msgid ""
"In this blank Kanban card, enter the name of :guilabel:`Event`, along with "
"the start and end :guilabel:`Date` and time."
msgstr ""
#: ../../content/applications/marketing/events.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:95
msgid ""
"Each event card can be dragged-and-dropped into any stage on the Kanban "
"pipeline, providing easy organizational access."
msgstr ""
#: ../../content/applications/marketing/events.rst:101
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:106
msgid "Events section"
msgstr ""
#: ../../content/applications/marketing/events.rst:108
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."
msgstr ""
#: ../../content/applications/marketing/events.rst-1
msgid ""
"The Events section on the Odoo Events settings page in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:119
msgid ""
"When the :guilabel:`Schedule & Tracks` feature is enabled, two additional "
"fields appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event "
"Gamification`."
msgstr ""
#: ../../content/applications/marketing/events.rst:122
msgid ""
"The :guilabel:`Live Broadcast` feature lets users air tracks online, via a "
"*YouTube* integration."
msgstr ""
#: ../../content/applications/marketing/events.rst:124
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:133
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:137
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:146
msgid "Registration section"
msgstr ""
#: ../../content/applications/marketing/events.rst:148
msgid ""
"The :guilabel:`Registration` section of the :guilabel:`Settings` page "
"provides selectable settings that are directly related to event "
"registration."
msgstr ""
#: ../../content/applications/marketing/events.rst-1
msgid ""
"The Registration section in the Odoo Events settings page in the Odoo Events"
" application."
msgstr ""
#: ../../content/applications/marketing/events.rst:155
msgid ""
"The :guilabel:`Tickets` setting allows users to sell event tickets, via "
"standard sales orders."
msgstr ""
#: ../../content/applications/marketing/events.rst:157
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:162
msgid "Attendance section"
msgstr ""
#: ../../content/applications/marketing/events.rst:164
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."
msgstr ""
#: ../../content/applications/marketing/events.rst-1
msgid ""
"The Attendance section in the Odoo Events Settings page in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events.rst:171
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:175
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:179
#: ../../content/applications/marketing/events/create_events.rst:3
msgid "Create events"
msgstr ""
#: ../../content/applications/marketing/events.rst:181
msgid ""
"With Odoo **Events**, events can be manually created from scratch or built "
"off of pre-made templates."
msgstr ""
#: ../../content/applications/marketing/events.rst:184
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:189
msgid ":doc:`events/create_events`"
msgstr ""
#: ../../content/applications/marketing/events.rst:192
#: ../../content/applications/marketing/events/sell_tickets.rst:3
msgid "Sell event tickets"
msgstr ""
#: ../../content/applications/marketing/events.rst:194
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."
msgstr ""
#: ../../content/applications/marketing/events.rst:197
msgid ""
"Odoo simplifies the ticket-purchasing process by providing plenty of payment"
" method options, as well."
msgstr ""
#: ../../content/applications/marketing/events.rst:201
msgid ":doc:`events/sell_tickets`"
msgstr ""
#: ../../content/applications/marketing/events.rst:204
msgid "Track and manage talks"
msgstr ""
#: ../../content/applications/marketing/events.rst:206
msgid ""
"Discover how to access various event tracks (talks, presentations, etc.), "
"view entire agendas, and learn how attendees can propose talks for the "
"event."
msgstr ""
#: ../../content/applications/marketing/events.rst:210
msgid ":doc:`events/track_manage_talks`"
msgstr ""
#: ../../content/applications/marketing/events.rst:213
#: ../../content/applications/marketing/events/event_templates.rst:3
msgid "Event templates"
msgstr ""
#: ../../content/applications/marketing/events.rst:215
msgid ""
"Learn the process to customize and configure event templates, which can be "
"used to expedite the event-creation process."
msgstr ""
#: ../../content/applications/marketing/events.rst:219
msgid ":doc:`events/event_templates`"
msgstr ""
#: ../../content/applications/marketing/events.rst:222
#: ../../content/applications/marketing/events/event_booths.rst:3
msgid "Event booths"
msgstr ""
#: ../../content/applications/marketing/events.rst:224
msgid ""
"Explore the various ways to create, manage, and sell event booths with the "
"Odoo **Events** application."
msgstr ""
#: ../../content/applications/marketing/events.rst:228
msgid ":doc:`events/event_booths`"
msgstr ""
#: ../../content/applications/marketing/events.rst:231
#: ../../content/applications/marketing/events/event_tracks.rst:3
msgid "Event tracks"
msgstr ""
#: ../../content/applications/marketing/events.rst:233
msgid ""
"Find out how to create, manage, and schedule different experiences (aka "
"*Tracks*) for events with Odoo."
msgstr ""
#: ../../content/applications/marketing/events.rst:237
msgid ":doc:`events/event_tracks`"
msgstr ""
#: ../../content/applications/marketing/events.rst:240
msgid "Registration desk"
msgstr ""
#: ../../content/applications/marketing/events.rst:242
msgid ""
"Grant access to event attendees quickly and easily with the Odoo **Events** "
"*Registration Desk* feature."
msgstr ""
#: ../../content/applications/marketing/events.rst:246
msgid ":doc:`events/registration_desk`"
msgstr ""
#: ../../content/applications/marketing/events.rst:249
#: ../../content/applications/marketing/events/revenues_report.rst:3
msgid "Revenues report"
msgstr ""
#: ../../content/applications/marketing/events.rst:251
msgid ""
"Gain invaluable insight into event-related revenues with customizable "
"reports and metrics."
msgstr ""
#: ../../content/applications/marketing/events.rst:254
msgid ":doc:`events/revenues_report`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:10
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:16
msgid "New event"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:18
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid "Typical event template in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:29
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:32
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:36
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*."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:40
msgid "Event form"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:42
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:46
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:49
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:52
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:55
msgid "The following are fields found on an event form:"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:57
msgid ""
":guilabel:`Event Name`: the title of the event. This field is **required**."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:60
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:65
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**."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:67
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**."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:69
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:76
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:79
msgid "Doing so reveals :guilabel:`Create Twitter Wall` pop-up window."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:0
msgid "The Twitter Wall pop-up window in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:85
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:88
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:92
msgid ""
"Users also have the option to add a brief :guilabel:`Description` to the "
"wall, as well."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:94
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:97
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:101
msgid ""
"Then, from the resulting file explorer window, select the desired image to "
"be added to the wall."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:104
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:108
msgid ""
":guilabel:`Template`: choose a pre-configured event template from the "
"resulting drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:110
msgid ""
"Or, create a new one directly from this field, by typing in the name of the "
"new template, and selecting either:"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:113
msgid ""
":guilabel:`Create` (which creates the template, and can be edited later) or"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:114
msgid ""
":guilabel:`Create and edit...` (which creates the template, and reveals a "
"separate template page to configure the template in greater detail)."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:117
msgid ""
":guilabel:`Tags`: add any corresponding tags to briefly describe the event "
"(e.g. `Online`, `Conference`, etc.). Multiple tags can be added per event."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:121
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:124
msgid ""
":guilabel:`Organizer`: designate the organizer of the event (a company, "
"contact, or employee)."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:125
msgid ""
":guilabel:`Responsible`: designate a user in the database to be responsible "
"for this event."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:126
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**."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:133
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:137
msgid ""
":guilabel:`Exhibition Map`: if desired, click the :guilabel:`Upload your "
"file` button to upload an image of the event venue map."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:139
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:142
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:144
msgid ""
":guilabel:`Badge Background`: if desired, click the :guilabel:`Upload your "
"file` button to upload a custom background image for event badges."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:147
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:150
msgid ""
"Those tabs are: :ref:`Tickets <events/event-tickets>`, :ref:`Communication "
"<events/event-communication>`, :ref:`Questions <events/event-questions>`, "
"and :ref:`Notes <events/event-notes>`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:157
msgid "Tickets tab"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:159
msgid ""
"Create custom tickets (and ticket tiers) for events in the "
":guilabel:`Tickets` tab of an event form."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid "A typical tickets tab on an event form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:165
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:168
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:174
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:180
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:185
msgid ""
"Next, set the registration cost of the ticket in the :guilabel:`Price` "
"field."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:188
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:192
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:196
msgid ""
"Then, if desired, designate a :guilabel:`Maximum` amount of that specific "
"ticket that can be sold."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:198
msgid ""
"The :guilabel:`Taken` column populates with the number of tickets that are "
"sold."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:200
msgid ""
"Optionally, in the :guilabel:`Color` column, add a custom color to "
"differentiate ticket badges. The selected color displays on ticket badges "
"when printed."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:203
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:207
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:211
msgid ""
"Then, tick the checkbox beside :guilabel:`Description` from the resulting "
"drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:213
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:219
msgid "Communication tab"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:221
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid ""
"Typical communication tab on an event form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:229
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:234
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:238
msgid ""
"There is no limit to the number of communications that can be added in the "
":guilabel:`Communication` tab of an event form."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:241
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:246
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:250
msgid ""
":doc:`WhatsApp <../../productivity/whatsapp>` templates **cannot** be edited"
" during active configuration. A separate approval from *Meta* is required."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:254
msgid "Mail"
msgstr "Sähköposti"
#: ../../content/applications/marketing/events/create_events.rst:256
msgid ""
"Select an existing email template from the :guilabel:`Template` drop-down "
"menu."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:258
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:261
msgid ""
"The :guilabel:`Unit` options are: :guilabel:`Immediately`, "
":guilabel:`Hours`, :guilabel:`Days`, :guilabel:`Weeks`, and "
":guilabel:`Months`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:264
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`."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:267
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:270
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:275
msgid ""
"To send a confirmation email an hour after an attendee registers for an "
"event, configure the following communication:"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:278
msgid ":guilabel:`Interval`: `1`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:279
msgid ":guilabel:`Unit`: :guilabel:`Hours`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:280
msgid ":guilabel:`Trigger`: :guilabel:`After each registration`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:283
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:288
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:295
#: ../../content/applications/marketing/surveys/create.rst:50
#: ../../content/applications/marketing/surveys/questions.rst:20
msgid "Questions tab"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:297
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:300
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid "Typical questions tab on an event form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:310
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:314
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:319
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid ""
"The Create Question pop-up window that appears in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:326
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:330
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:335
msgid "Next, select a :guilabel:`Question Type` option:"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:337
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:340
msgid ""
":guilabel:`Text Input`: lets the users enter a custom response to the "
"question in a text field."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:341
msgid ""
":guilabel:`Name`: provides registrants with a field for them to enter their "
"name."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:342
msgid ""
":guilabel:`Email`: provides registrants with a field for them to enter their"
" email address."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:343
msgid ""
":guilabel:`Phone`: provides registrants with a field for them to enter their"
" phone number."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:344
msgid ""
":guilabel:`Company`: provides registrants with a field for them to enter a "
"company they are associated with."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:347
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:352
msgid ""
"As questions are added to the :guilabel:`Questions` tab, the informative "
"columns showcase the configurations of each question."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:355
msgid "The informative columns are the following:"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:357
msgid ":guilabel:`Title`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:358
msgid ":guilabel:`Mandatory`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:359
msgid ":guilabel:`Once per Order`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:360
msgid ":guilabel:`Type`"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:361
msgid ":guilabel:`Answers` (if applicable)"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:363
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:367
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:370
msgid ""
"There is no limit to the number of questions that can be added in the "
":guilabel:`Questions` tab of an event form."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:376
msgid "Notes tab"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:378
msgid ""
"In the :guilabel:`Notes` tab of an event form, users can leave detailed "
"internal notes and/or event-related instructions/information for attendees."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst-1
msgid "Typical notes tab on an event form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:385
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:388
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:392
msgid "Publish events"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:394
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:398
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:403
msgid ""
"To learn more about website design functionality and options, consult the "
":doc:`Building block <../../websites/website/web_design/building_blocks>` "
"documentation."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:406
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:411
msgid "Send event invites"
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:413
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:417
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:421
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:426
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."
msgstr ""
#: ../../content/applications/marketing/events/create_events.rst:430
#: ../../content/applications/marketing/events/event_tracks.rst:310
msgid ":doc:`track_manage_talks`"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:5
msgid ""
"The Odoo *Events* application provides users with the ability to create "
"event booths, sell their availability, and manage their reservations."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:9
#: ../../content/applications/marketing/events/event_tracks.rst:12
#: ../../content/applications/marketing/events/sell_tickets.rst:18
#: ../../content/applications/marketing/marketing_automation.rst:44
msgid "Configuration"
msgstr "Asetukset"
#: ../../content/applications/marketing/events/event_booths.rst:11
msgid ""
"In order to create, sell, and manage booths for events, the *Booth "
"Management* feature must be activated."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:14
msgid ""
"To do that, navigate to :menuselection:`Events app --> Configuration --> "
"Settings`, and tick the :guilabel:`Booth Management` checkbox. Then, click "
":guilabel:`Save`."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid "The Booth Management setting in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:22
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*."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:26
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:31
msgid "Booth categories"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:33
msgid ""
"With the *Booth Management* setting activated in the *Events* app, the "
"*Booth Categories* option appears in the :guilabel:`Configuration` menu."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:36
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid "The Booth Category page in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:43
msgid ""
"On the :guilabel:`Booth Category` page, the following information for each "
"booth category is listed:"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:45
msgid ":guilabel:`Name`: the name of the booth category."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:46
msgid ""
":guilabel:`Create Sponsor`: if checked, booking this booth category creates "
"a sponsor for the user."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:48
msgid ""
":guilabel:`Product`: the *Event Booth* product associated with that specific"
" booth category."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:49
msgid ":guilabel:`Price`: the price of a booth in that booth category."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:51
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:56
msgid ""
"To edit an existing booth category, select it from the list, and proceed to "
"make any desired modifications from the event category form."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:60
msgid "Create booth category"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:62
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid "A typical booth category form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:69
msgid ""
"Start by entering a name for the booth category in the top :guilabel:`Booth "
"Category` field. This is a **requried** field."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:80
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:83
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:87
msgid ""
"When the :guilabel:`Create Sponsor` checkbox is ticked, two additional "
"fields appear beneath it: :guilabel:`Sponsor Level` and :guilabel:`Sponsor "
"Type`."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:91
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:97
msgid ""
"Select a desired level of sponsorship from the :guilabel:`Sponsor Level` "
"drop-down field."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:100
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:105
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:109
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:113
msgid "Doing so reveals a :guilabel:`Create Sponsor Level` pop-up window."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid ""
"The Create Sponsor Level pop-up window that appears in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:119
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:124
msgid ""
"If one is selected, that :guilabel:`Ribbon Style` appears with the sponsor's"
" name on the event website."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:127
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.)."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:133
msgid "Add booth to an event"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:135
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:139
msgid ""
"From the event form, to access the *Booths* for that specific event, click "
"the :guilabel:`Booths` smart button at the top of the page."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:142
msgid ""
"The :guilabel:`Booths` page is displayed in a Kanban view, by default, with "
"two different stages: :guilabel:`Available` and :guilabel:`Unavailable`."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:146
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:151
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:155
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:160
msgid "Booth form"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:162
msgid ""
"The booth form in Odoo *Events* lets users customize and configure event "
"booths in a number of different ways."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid "Typical booth form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:169
msgid ""
"Start by typing in a :guilabel:`Name` for the booth. This is a **required** "
"field."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:171
msgid ""
"Then, apply a :guilabel:`Booth Category` to the booth. This is a "
"**required** field."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:174
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:179
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`)."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:184
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:188
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*."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:193
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:197
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:203
msgid "Sell event booths"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:205
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:212
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:215
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:219
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:222
msgid ""
"Alternatively, enter :doc:`Debug mode <../../general/developer_mode>`, and "
"open the specific event form in the the *Events* application."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:225
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:229
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:232
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst-1
msgid "Typical Get A Booth page on the event website via the Odoo Events app."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:240
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:244
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:249
msgid ""
"If the selected booth has the *Create Sponsor* checkbox ticked, this page "
"reads as *Sponsor Details*."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:252
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:255
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:258
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)."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:262
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."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:267
msgid ""
"Click the *Sponsors* smart button to modify any information about the "
"sponsor, if necessary."
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:270
#: ../../content/applications/marketing/events/event_templates.rst:217
#: ../../content/applications/marketing/events/event_tracks.rst:309
#: ../../content/applications/marketing/events/sell_tickets.rst:143
msgid ":doc:`create_events`"
msgstr ""
#: ../../content/applications/marketing/events/event_booths.rst:271
msgid ":doc:`sell_tickets`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:5
msgid ""
"The Odoo *Events* application provides the ability to customize and "
"configure event templates, which can be used to expedite the event-creation "
"process."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:8
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:13
msgid "Event templates page"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:15
msgid ""
"In the Odoo *Events* application, event templates can quickly be created and"
" modified."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:17
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst-1
msgid "The Event Templates page in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:25
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:29
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:34
msgid ""
"To learn more about event forms, refer to the :doc:`create_events` "
"documentation."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:37
msgid "Create event template"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:39
msgid ""
"There are two ways to create and configure an event template in Odoo "
"*Events*."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:41
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:44
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:50
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:54
msgid ""
"The event template would have to be modified, by selecting it on the *Event "
"Templates* page (:menuselection:`Events app --> Configuration --> Event "
"Templates`)."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:58
msgid "Event template form"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:60
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst-1
msgid "A standard event template form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:67
msgid ""
"Start by providing the event template with a name in the :guilabel:`Event "
"Template` field, located at the top of the form."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:70
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:76
msgid ""
":guilabel:`Tracks Menu Item`: adds a submenu item to navigate to a page "
"displaying all planned tracks for the event."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:81
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`)."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:87
msgid ""
"First, users **must** create a booth product with the required *Event Booth*"
" option set as the :guilabel:`Product Type` on the product form."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:90
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:93
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:96
msgid ""
":guilabel:`Allow Room Creation`: allow visitors to create community rooms of"
" their own."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:97
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:100
msgid ""
"Once the desired checkboxes have been ticked, select an appropriate "
":guilabel:`Timezone` for the event from the available drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:103
msgid ""
"Then, for organizational purposes, there is the option to add "
":guilabel:`Tags` to this event template."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:106
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:110
msgid ""
"Beneath those general information fields at the top of the event template "
"form, there are five tabs:"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:112
msgid ":ref:`Tickets <events/event-tickets>`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:113
msgid ":ref:`Communication <events/event-communication>`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:114
msgid ":ref:`Booths <event_templates/event_template/booths>`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:115
msgid ":ref:`Questions <events/event-questions>`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:116
msgid ":ref:`Notes <events/event-notes>`"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:121
msgid "Booths tab"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:123
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:134
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:138
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst-1
msgid "A Create Booths pop-up window in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:145
msgid ""
"Start by providing a :guilabel:`Name` for this booth in the corresponding "
"field at the top of the pop-up window."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:148
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:154
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:159
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst-1
msgid ""
"The Create Booth Category pop-up window in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:167
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:172
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:175
msgid ""
"When all desired configurations are complete, click the :guilabel:`Save & "
"Close` button."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:177
msgid ""
"The same configurations and options are available by navigating to "
":menuselection:`Events app --> Configuration --> Booth Categories`, and "
"clicking :guilabel:`New`."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:180
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:186
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:189
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:194
msgid ""
"Once the booth has been saved, it appears in the :guilabel:`Booths` tab on "
"the event template form."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:197
msgid "Use event templates"
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:199
msgid ""
"Once an event template is complete, it is accessible on all event forms in "
"the Odoo *Events* application."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:202
msgid ""
"To use an event template, navigate to the :menuselection:`Events app` and "
"click :guilabel:`New` to open a new event form."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:205
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`)."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:209
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."
msgstr ""
#: ../../content/applications/marketing/events/event_templates.rst:213
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:5
msgid ""
"Odoo *Events* provides the ability to create, schedule, and manage talks, "
"lectures, demonstrations, presentations, etc., which known as *Tracks* in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:8
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)."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:14
msgid ""
"First, there are some settings that need to be enabled, in order to get the "
"most out of event tracks."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:17
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:21
msgid ""
"Also, when that setting checkbox is ticked, two additional setting options "
"appear beneath it: :guilabel:`Live Broadcast` and :guilabel:`Event "
"Gamification`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid ""
"The Schedule and Tracks setting in the Odoo Events app, along with "
"corresponding options."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:28
msgid ""
"The :guilabel:`Live Broadcast` option provides the ability to air tracks "
"online through a *YouTube* integration."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:31
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:35
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:39
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:43
msgid "Event Tracks page"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:45
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:48
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:51
msgid ""
"Once on the desired event form, click into the :guilabel:`Tracks` smart "
"button at the top of the form."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:55
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:59
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid "Typical event tracks page for an event in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:67
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:74
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:80
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:83
msgid ""
"Clicking into a track from the :guilabel:`Event Tracks` page reveals the "
"track form for that particular track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:87
msgid "Create event track"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:89
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid "Typical event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:96
msgid ""
"Start by giving this track a :guilabel:`Title`. This field is **required** "
"by Odoo."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:98
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:104
msgid ""
"Next, enter a :guilabel:`Track Date` and time for the track, and designate a"
" :guilabel:`Location` where the talk is planning to be held."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:108
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:111
msgid "Then, add a :guilabel:`Duration` to the track (in minutes)."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:113
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:116
msgid ""
"If the :guilabel:`Always Wishlisted` checkbox is ticked, the talk is "
"automatically set as a favorite for each registered event attendee."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:119
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:122
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:126
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:130
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>`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:137
msgid "Speaker tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:139
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid "The Speaker tab on an event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:147
msgid "Contact Details section"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:149
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:152
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:157
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:162
msgid "Speaker Bio section"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:164
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:170
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:173
msgid ""
"Start by entering a :guilabel:`Name`, :guilabel:`Email`, and "
":guilabel:`Phone` number for the speaker."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:176
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:181
msgid ""
"Then, enter a :guilabel:`Job Position` for the designated speaker, followed "
"by the :guilabel:`Company Name` associated with the speaker."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:184
msgid ""
"In the :guilabel:`Biography` field, proceed to enter in a custom biography "
"with any speaker-related information."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:190
#: ../../content/applications/marketing/surveys/create.rst:258
#: ../../content/applications/marketing/surveys/questions.rst:198
msgid "Description tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:192
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:199
msgid "Interactivity tab"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:201
msgid ""
"The :guilabel:`Interactivity` tab on an event track form features a single "
"option at first: :guilabel:`Magic Button`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid ""
"The Interactivity tab on an event track form in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:211
msgid ""
"With that checkbox ticked, three more options appear, all of which are "
"related to the :guilabel:`Magic Button`:"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:214
msgid ""
":guilabel:`Button Title`: enter a title to appear on the button for "
"attendees."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:215
msgid ""
":guilabel:`Button Target URL`: enter a URL that leads attendees, who click "
"the button, to a specific page."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:217
msgid ""
":guilabel:`Show Button`: enter a number in the field, and the button will "
"appear that number of :guilabel:`minutes after Track start`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:221
msgid ""
"The magic button **only** appears if there is more than one published track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:226
msgid "Add Quiz button"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:228
msgid ""
"The :guilabel:`Add Quiz` button **only** appears on event track forms if the"
" *Event Gamification* setting is enabled in the Odoo *Events* settings."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:231
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid "The Add Quiz page in the Odoo Events application for an event track."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:238
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`."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:242
msgid ""
"The :guilabel:`Event` and :guilabel:`Event Track` fields are non-modifiable,"
" and show the corresponding event and track this quiz is associated with."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:245
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
msgid ""
"The Create Questions pop-up window on an event-specific track quiz in the "
"Odoo Events app."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:253
msgid "**All** track quiz questions are multiple choice."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:255
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:259
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:262
msgid ""
"Then, there is the option to add a point value in the :guilabel:`Points` "
"column."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:264
msgid ""
"And, if there are any additional comments that should accompany an answer "
"option, type them into the :guilabel:`Extra Comment` field."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:268
msgid ""
"The :guilabel:`Correct`, :guilabel:`Points`, and :guilabel:`Extra Comment` "
"fields are all optional."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:271
msgid "Repeat this process for all the answer options."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:273
msgid ""
"To remove an answer option, click the :icon:`fa-trash-o` :guilabel:`(trash "
"can)` icon on the far-right."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:276
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:281
msgid ""
"To remove any question from the quiz, click the :icon:`fa-trash-o` "
":guilabel:`(trash can)` icon on the far-right of the question line."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:285
msgid "Publish event track"
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:287
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.)."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:292
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:295
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst:298
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."
msgstr ""
#: ../../content/applications/marketing/events/event_tracks.rst-1
#: ../../content/applications/marketing/events/track_manage_talks.rst-1
msgid ""
"The track-related event submenu options on an event website built with Odoo "
"Events."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:3
msgid "Registration Desk"
msgstr "Ilmoittautumispiste"
#: ../../content/applications/marketing/events/registration_desk.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:9
msgid "Registration Desk page"
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:11
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst-1
msgid "The Registration Desk page in the Odoo Events application."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:18
msgid ""
"At the bottom of the :guilabel:`Registration Desk` box, there are options to"
" either :guilabel:`Scan a badge` or :guilabel:`Select Attendee`."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:22
msgid "Scan a badge"
msgstr "Skannaa nimilappu"
#: ../../content/applications/marketing/events/registration_desk.rst:24
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:28
msgid ""
"Odoo **must** be granted access to the camera being used for the "
":guilabel:`Scan a badge` option to work."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:31
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst-1
msgid ""
"The Barcode Scanner window of the Registration Desk in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:39
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:43
msgid ""
"If the barcode being scanned is invalid, an error pop-up message appears in "
"the upper-right corner."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:46
msgid "Select attendee"
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:48
msgid ""
"Manually grant access to event attendees, by navigating to "
":menuselection:`Events app --> Registration Desk`, and selecting the "
":guilabel:`Select Attendee` option."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:51
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst-1
msgid ""
"The Attendees page, via the Registration Desk, located in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:58
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)`."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:63
msgid ""
"To grant access to a person, marking them as attended, click the :icon:`fa-"
"check` :guilabel:`(checkmark)` button on that attendee's card."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:66
msgid ""
"Click the :icon:`fa-undo` :guilabel:`(counter-clockwise arrow)` button on an"
" attendee's card to undo the previous action."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:70
msgid ""
"It is recommended to use an event-specific filter on the "
":guilabel:`Attendees` page, via the search bar drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/events/registration_desk.rst:82
#: ../../content/applications/marketing/events/revenues_report.rst:72
msgid ":doc:`../../essentials/search`"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:5
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*."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:8
msgid ""
"The following documentation focuses on the reporting options related to "
"event *Revenues*."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:11
msgid "Revenues reporting page"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:13
msgid ""
"To access the *Attendees* reporting page, navigate to :menuselection:`Events"
" app --> Reporting --> Revenues`."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst-1
msgid ""
"The default view of the Revenues reporting page in the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:20
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:26
msgid ""
"To learn more about the various graph views (and graph view options), refer "
"to the :ref:`Graph views <reporting/using-graph>` documentation."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:29
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:34
msgid "Measures"
msgstr "Näytettävät tiedot"
#: ../../content/applications/marketing/events/revenues_report.rst:36
msgid ""
"Choosing specific :ref:`Measures <reporting/choosing-measures>` is a quick "
"way to customize reporting pages."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:39
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`."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:43
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:46
msgid ""
"In graph view, only one of the :guilabel:`Measures` can be selected at a "
"time."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:48
msgid ""
"When the pivot option is selected, all :guilabel:`Measures` options are "
"selected, by default."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:50
msgid ":guilabel:`Revenues`: shows the revenues generated from events."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:51
msgid ""
":guilabel:`Untaxed Revenues`: shows the untaxed revenues generated from "
"events."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:52
msgid ""
":guilabel:`Count`: shows the total amount of registrants who attended "
"events."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:55
msgid "Filters and grouping options"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:57
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:60
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>`."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:65
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:69
msgid ""
"Only **one** selection can be made from the :guilabel:`Comparison` column at"
" a time."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:75
msgid "Filter options"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:80
msgid ""
"Multiple options in the :guilabel:`Filters` column can be selected at once."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:82
msgid "The :guilabel:`Filters` column has the following options:"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:84
msgid ""
":guilabel:`Non-free tickets`: event tickets/registrations that were **not** "
"free."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:85
msgid ":guilabel:`Free`: event tickets/registrations that *were* free."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:86
msgid ""
":guilabel:`Pending payment`: event tickets/registrations that were "
"purchased, but still have payment pending."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:88
msgid ""
":guilabel:`Sold`: event tickets/registrations that have been successfully "
"sold (and paid for)."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:89
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:92
msgid ""
":guilabel:`Upcoming/Running`: include revenue-related information for events"
" that are either currently running or are going to happen in the future."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:94
msgid ""
":guilabel:`Past Events`: include revenue-related information for events that"
" have already taken place."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:96
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:99
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:102
msgid ""
":guilabel:`Published Events`: Select this option to show revenue-related "
"data for published events."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:104
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>`."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:108
msgid "Group By options"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:110
msgid ""
"In the :guilabel:`Group By` column of the drop-down mega menu, there are "
"various event-related options to create custom groupings of data."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:113
msgid "Multiple :guilabel:`Group By` options can be selected at once."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:115
msgid "The :guilabel:`Group By` column has the following options:"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:117
msgid ":guilabel:`Event Type`: Group data based on the type of event."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:118
msgid ""
":guilabel:`Event`: Organize data into individual groups, separated by "
"events."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:119
msgid ""
":guilabel:`Product`: Group data based on the event registration product."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:120
msgid ""
":guilabel:`Ticket`: Group data based on the type of event ticket purchased "
"by attendees."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:121
msgid ""
":guilabel:`Registration Status`: Group data based on the status of "
"registrations."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:122
msgid ""
":guilabel:`Sale Order Status`: Group data based on the status of event-"
"related sales orders."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:123
msgid ":guilabel:`Customer`: Group data based on customer records."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:124
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:129
msgid "Sample report: event ticket analysis (graph)"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:131
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst-1
msgid ""
"The event ticket analysis sample report with unique filters and groupings in"
" place."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:139
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:142
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:145
msgid ""
"From here, select :guilabel:`Free` and :guilabel:`Sold` from the "
":guilabel:`Filters` column."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:147
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:150
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:155
msgid ""
"The order in which the options are selected in the :guilabel:`Group By` "
"column directly affects how the data is presented on the report."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:158
msgid ""
"From there, additional configurations can be added for more detailed data, "
"if desired."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:160
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:165
msgid "Sample report: event type analysis (pivot table)"
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:167
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst-1
msgid ""
"The event type analysis sample report with unique filters and groupings in "
"place."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:176
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:180
msgid ""
"Keep the default filters (:guilabel:`Non-free tickets` and :guilabel:`Event "
"Start Date: (year)`) in the search bar."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:183
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."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:186
msgid ""
"Then, click :icon:`fa-plus-square` :guilabel:`Total` above the column "
"titles, and select :guilabel:`Event Type` from the resulting drop-down menu."
msgstr ""
#: ../../content/applications/marketing/events/revenues_report.rst:189
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)."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:5
msgid ""
"Odoo *Events* provides users with the ability to create custom event tickets"
" (and ticket tiers), with various price points."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:8
msgid ""
"It *also* allows them to sell event tickets in two different ways: via "
"standard sales orders, and online through an integrated website."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:11
msgid ""
"Odoo also simplifies the ticket-purchasing process by providing plenty of "
"payment method options."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:14
msgid ""
"To learn more about how to create custom tickets (and ticket tiers) for "
"events, check out the :doc:`create_events` documentation."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:20
msgid ""
"In order to sell event tickets in Odoo, some settings must first be enabled."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:22
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`."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:26
msgid ""
"The :guilabel:`Tickets` setting allows users to sell event tickets with "
"standard sales orders."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:28
msgid ""
"The :guilabel:`Online Ticketing` setting allows users to sell event tickets "
"online through their integrated Odoo website."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:31
msgid ""
"To activate a setting, tick the checkbox beside the desired feature's label,"
" and click :guilabel:`Save` to finish enabling it."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:35
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst-1
msgid "View of the settings page for Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:42
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:47
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:0
msgid ""
"View of an event form highlighting the column product under the tickets tab "
"in Odoo."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:56
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst-1
msgid "View of an event's form and the sales smart button in Odoo Events."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:64
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:69
msgid "Sell event tickets with the Sales app"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:71
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:74
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:79
msgid ""
"Once an event registration product is selected, a :guilabel:`Configure an "
"event` pop-up window appears."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst-1
msgid ""
"Standard 'Configure an event' pop-up window that appears on an event ticket "
"sales order."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:86
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:91
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:96
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:100
msgid "Sell event tickets through the Website app"
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:102
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:106
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:111
msgid ""
"If different ticket tiers are configured for the event, the visitor is "
"presented with a :guilabel:`Tickets` pop-up window."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst-1
msgid ""
"The tickets pop-up window that appears on the event's website when "
"'Register' is clicked."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:118
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:122
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst-1
msgid ""
"The attendees pop-up window that appears on the event's website when 'Ok' is"
" clicked."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:134
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."
msgstr ""
#: ../../content/applications/marketing/events/sell_tickets.rst:139
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:3
msgid "Talks, proposals, and agenda"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:10
msgid "Event website"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:12
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:17
msgid ""
"On the event website, there is an event-specific subheader menu with "
"different options to choose from."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:20
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`."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:28
msgid ""
"To enable the :guilabel:`Schedule & Tracks` setting, navigate to "
":menuselection:`Events app --> Configuration --> Settings`, tick the "
"checkbox beside :guilabel:`Schedule & Tracks`, and click :guilabel:`Save`."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:33
msgid "Talks page"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:35
msgid ""
"The :guilabel:`Talks` link takes the attendee to a page filled with all the "
"planned tracks for the event."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst-1
msgid ""
"The Talks page on an event website built through the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:42
msgid ""
"At the top of :guilabel:`Talks` page, there are drop-down filter menus "
"beside a :guilabel:`Search a talk...` search bar."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:45
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`."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:49
msgid ""
"Selecting :guilabel:`Favorites` shows *only* the tracks that have been "
"favorited by the attendee."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:52
msgid ""
"If no tracks have been favorited, and the :guilabel:`Favorites` filter is "
"selected, Odoo presents all the event tracks."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:55
msgid ""
"Selecting :guilabel:`All Talks` shows *all* the tracks, regardless if they "
"have been favorited or not."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:58
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:62
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:66
msgid "Doing so reveals a :guilabel:`Create Tags` pop-up form."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst-1
msgid ""
"The Create Tags pop-up form that coincides with drop-down filter menus on "
"Talks page."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:75
msgid ""
"Lastly, there is the :guilabel:`Category` field, where users can either "
"select a pre-existing category for this new tag, or create a new one."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:81
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:84
#: ../../content/applications/marketing/events/track_manage_talks.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:88
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:92
msgid "Talk Proposals page"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:94
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst-1
msgid ""
"The Talk Proposals page on the event website built with the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:101
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:104
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:107
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)."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:110
msgid ""
"Once all the necessary information is entered into the form, the attendees "
"just need to click the :guilabel:`Submit Proposal` button."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:113
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:117
msgid ""
"At that point, an internal user can review the proposed talk, and choose to "
"accept or deny the proposal."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:120
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:125
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:129
msgid "Agenda page"
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:131
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."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst-1
msgid ""
"The event Agenda page on the event website built with the Odoo Events "
"application."
msgstr ""
#: ../../content/applications/marketing/events/track_manage_talks.rst:138
msgid ""
"Clicking any track on the calendar takes the attendee to that specific "
"track's detail page on the event website."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:5
msgid "Marketing Automation"
msgstr "Markkinointiautomaatio"
#: ../../content/applications/marketing/marketing_automation.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:11
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:15
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:19
#: ../../content/applications/marketing/sms_marketing.rst:17
#: ../../content/applications/marketing/social_marketing.rst:12
msgid ""
"`Odoo Tutorials: Marketing <https://www.odoo.com/slides/marketing-27>`_"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:46
msgid ""
"To begin, make sure the **Marketing Automation** application is "
":ref:`installed <general/install>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:49
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:53
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**."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:56
msgid ""
"The following documentation assumes that all three of these dependent "
"applications are installed on the database."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:62
msgid "Campaigns"
msgstr "Kampanjat"
#: ../../content/applications/marketing/marketing_automation.rst:64
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:67
msgid ""
"A new campaign can be created from scratch or from a :ref:`template "
"<marketing_automation/campaign-templates>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:70
msgid ""
"To create a campaign, navigate to the :menuselection:`Marketing Automation` "
"application and click the :guilabel:`New` button to reveal a new campaign "
"form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:76
#: ../../content/applications/marketing/marketing_automation/campaign_templates.rst:5
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:82
msgid "Campaign templates"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:78
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:83
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:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":icon:`fa-tag` :guilabel:`Tag Hot Contacts`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ""
":guilabel:`Send a welcome email to contacts and tag them if they click it.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":icon:`fa-hand-peace-o` :guilabel:`Welcome Flow`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ""
":guilabel:`Send a welcome email to new subscribers, remove the address that "
"bounced.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ""
":icon:`fa-check-square` :doc:`Double Opt-in "
"<marketing_automation/campaign_templates/double_optin>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":guilabel:`Send an email to new recipients to confirm their consent.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":icon:`fa-search` :guilabel:`Commercial prospection`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":guilabel:`Send a free catalog and follow-up according to reactions.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":icon:`fa-phone` :guilabel:`Schedule Calls`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ""
":guilabel:`If a lead is created for existing contact, schedule a call with "
"their salesperson.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ":icon:`fa-star` :guilabel:`Prioritize Hot leads`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:0
msgid ""
":guilabel:`Send an email to new leads and assign them a high priority if "
"they open it.`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst-1
msgid ""
"Six campaign template cards on the Campaigns dashboard of the Marketing "
"Automation app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:104
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:108
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:111
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:33
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:115
msgid "Targets and filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:117
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:121
msgid ""
"The target audience specifies the type of records available for use in the "
"campaign, such as *Lead/Opportunity*, *Event Registration*, *Contact*, and "
"more."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:125
msgid "Records"
msgstr "Tiedot"
#: ../../content/applications/marketing/marketing_automation.rst:127
msgid ""
"The contacts in the system that fit the specified criteria for a campaign "
"are referred to as *records*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:130
msgid ""
"The number of records that are displayed next to the campaign "
":guilabel:`Filter` represent the total number of records the campaign is "
"targeting."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:134
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:157
msgid "Participants"
msgstr "Ilmoittautuneita yhteensä"
#: ../../content/applications/marketing/marketing_automation.rst:136
msgid ""
"The records that are engaged by the campaign are referred to as "
"*participants*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:138
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:145
msgid ":doc:`Audience targeting <marketing_automation/target_audience>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:148
msgid "Workflow"
msgstr "Työnkulku"
#: ../../content/applications/marketing/marketing_automation.rst:150
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:154
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:19
msgid "Activities"
msgstr "Toimenpiteet"
#: ../../content/applications/marketing/marketing_automation.rst:156
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:160
msgid ""
"To create one of the following activities, click :guilabel:`Add new "
"activity` in the :guilabel:`Workflow` section of the campaign form:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:163
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:53
msgid ""
":ref:`Email <marketing_automation/email-activity-type>`: an email that is "
"sent to the target audience."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:165
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:55
msgid ""
":ref:`Server action <marketing_automation/sa-activity-type>`: an internal "
"action within the database that is executed."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:167
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:57
msgid ""
":ref:`SMS <marketing_automation/sms-activity-type>`: a text message that is "
"sent to the target audience."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:171
msgid ":doc:`marketing_automation/workflow_activities`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:174
msgid "Testing and running"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:176
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:179
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:183
msgid ":doc:`marketing_automation/testing_running`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:186
msgid "Reporting"
msgstr "Raportointi"
#: ../../content/applications/marketing/marketing_automation.rst:188
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:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:191
msgid ""
":guilabel:`Link Tracker`: displays the metrics of links to track the number "
"of clicks."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:192
msgid ""
":guilabel:`Traces`: displays the results of all activities from all "
"campaigns."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:193
msgid ""
":guilabel:`Participants`: displays an overview of the participants of all "
"campaigns."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:195
msgid ""
"Additionally, each activity within the workflow of a campaign displays its "
"engagement metrics."
msgstr ""
#: ../../content/applications/marketing/marketing_automation.rst:198
msgid ":doc:`marketing_automation/understanding_metrics`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:3
msgid "Double Opt-in"
msgstr "Kaksinkertainen markkinointivahvistus"
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:10
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:17
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:23
msgid "Use the Double Opt-in campaign template"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:25
msgid ""
"Open the :menuselection:`Marketing Automation` app, and select the "
":guilabel:`Double Opt-in` campaign template to create a new campaign for "
"confirming consent."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:29
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:37
msgid "Campaign configuration"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:39
msgid ""
"Upon creation of the campaign, the campaign form loads with a new "
"preconfigured campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:41
msgid ""
"The :guilabel:`Target` and :guilabel:`Filter` configurations of the campaign"
" are as follows:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:43
msgid ":guilabel:`Name`: `Double Opt-in`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:44
msgid ":guilabel:`Responsible`\\*: The user who created the campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:45
msgid ":guilabel:`Target`: :guilabel:`Mailing Contact`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:46
msgid ":guilabel:`Unicity based on`: :guilabel:`Email (Mailing Contact)`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:47
msgid ":guilabel:`Filter`:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:49
msgid ":guilabel:`Email` :guilabel:`is set`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:50
msgid ":guilabel:`Blacklist` :guilabel:`is not` :guilabel:`set`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:51
msgid ":guilabel:`Mailing lists` :guilabel:`contains` `Newsletter`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:53
msgid ""
"\\* The :guilabel:`Responsible` field is only visible with :ref:`developer-"
"mode` activated."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:56
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:60
msgid ""
"The *Double Opt-in* campaign template is intended to **only** use the "
":guilabel:`Mailing Contact` model."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:63
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*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:66
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:70
msgid ""
"The email activity uses the preconfigured *Confirmation* email template, "
"which contains a button for the contact to click to confirm their consent."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:80
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:84
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:90
msgid ""
"The email template should only include a single call-to-action link for "
"confirmation, other than an unsubscribe link."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:93
msgid ""
"Any click on a link (or button) included in the confirmation email, besides "
"the unsubscribe button, triggers the *Add to list* server action."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:96
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:100
msgid ""
"The `Add to list` server action activity triggers immediately after a click "
"in the parent `Confirmation` email activity is detected."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:103
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:107
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:111
msgid ""
"Consider setting an :guilabel:`Expiry Duration` to prevent executing the "
"activity after a specific amount of time."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:118
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:126
msgid "Double Opt-in use-case"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:129
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst-1
msgid "Newsletter sign-up form on Odoo website footer."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:137
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:141
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`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst-1
msgid "Activity metrics on the campaign form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:149
msgid ""
"Now, the *Confirmed contacts* mailing list is ready to be used for sending "
"newsletter marketing emails from an Odoo database."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:153
msgid ":doc:`../understanding_metrics`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:154
msgid ":doc:`../../email_marketing/mailing_lists`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/campaign_templates/double_optin.rst:155
msgid ":doc:`../../email_marketing`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:3
msgid "Audience targeting"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:5
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.)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:9
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:13
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:16
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:19
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:22
msgid ""
":guilabel:`Include archived`: allows or disallows the inclusion of archived "
"records in the target audience."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:26
msgid ""
"A :guilabel:`Responsible` user can be assigned to the campaign by activating"
" :ref:`developer-mode`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:30
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:36
msgid "Defining filters"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:41
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst-1
msgid "A new filter rule row on the campaign form Filters."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:49
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:54
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:59
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:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:62
msgid ":guilabel:`Target`: `Lead/Opportunity`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:63
msgid ":guilabel:`Unicity based on`: `Email (Lead/Opportunity)`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:64
msgid ""
":guilabel:`Filter`: :guilabel:`Match` :guilabel:`all 🔽 (down arrow)` "
":guilabel:`of the following rules:`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:67
msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`New`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:68
msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:69
msgid ":guilabel:`any 🔽 (down arrow)` :guilabel:`of:`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:71
msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:72
msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:74
msgid ""
"With the above configuration, the campaign targets :guilabel:`157 "
"record(s)`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:0
msgid "A domain configuration in a Marketing Automation campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:81
msgid ":ref:`Domain developer documentation <reference/orm/domains>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:82
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:153
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:50
msgid ":doc:`workflow_activities`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:83
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:335
msgid ":doc:`testing_running`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/target_audience.rst:84
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:336
msgid ":doc:`understanding_metrics`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:3
msgid "Testing/running campaigns"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:10
msgid "Test campaigns"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:12
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:15
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:20
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:23
msgid ""
"To start a test, click the :guilabel:`Launch a Test` button at the top of "
"the campaign form, to the right of the :guilabel:`Start` button."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"Launch a test button on a campaign detail form in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:30
msgid "When clicked, a :guilabel:`Launch a test` pop-up window appears."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid "Launch a test pop-up window that appears in Odoo Markting Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:36
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:41
msgid ""
"Only one contact can be selected from the :guilabel:`Launch a test` pop-up "
"window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:43
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...`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"Typing in a new contact directly from the launch a test pop-up window in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:50
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"A blank contact form from a launch test pop-up window in Odoo Marketing "
"Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:58
msgid ""
"When all the necessary fields have been entered, click :guilabel:`Save & "
"Close` to return to the :guilabel:`Launch a test` pop-up window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:61
msgid ""
"Once a contact is selected, click :guilabel:`Launch` to reveal the campaign "
"test page."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid "Test screen in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:67
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid "Workflow test progress in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:85
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:88
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:92
msgid "Run campaigns"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:94
msgid ""
"To run a campaign, navigate to :menuselection:`Marketing Automation app`, "
"and select the desired campaign to run."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:97
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:101
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"The status of a marketing campaign changing to running in the upper-right "
"corner."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:109
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"The workflow has been modified warning pop-up window of a marketing campaign"
" form."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:117
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:121
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:125
msgid ""
"These analytical smart buttons will *also* populate with real-time data as "
"the campaign progresses: :guilabel:`Templates`, :guilabel:`Clicks`, "
":guilabel:`Tests`, :guilabel:`Participants`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"The row of smart buttons that appear in a currently running marketing "
"campaign in Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:133
msgid "Stop campaigns"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:135
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"The stop button on a typical campaign detail form in Odoo Marketing "
"Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:143
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst-1
msgid ""
"Marketing campaign's stopped status on a campaign detail form in Odoo "
"Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:151
msgid ":doc:`Campaign configuration <../marketing_automation>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/testing_running.rst:152
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:337
msgid ":doc:`target_audience`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:3
msgid "Campaign metrics"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:10
msgid "Activity analytics"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:12
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst-1
msgid ""
"An activity block in the workflow section with useful analytical data in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:21
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:26
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`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:0
msgid ""
"Time trigger display when dependent on another activity in Odoo Marketing "
"Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:34
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:40
msgid ""
"The activity type name is also displayed in smaller font below the activity "
"title."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:42
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:45
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:53
msgid "Activity graph tab"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:55
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:59
msgid ""
"Numerical representations of both :guilabel:`Success` and "
":guilabel:`Rejected` activities are shown to the right of the line graph."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:63
msgid ""
"Hovering over any point in the line graph of the activity block reveals a "
"notated breakdown of data for that specific date."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:0
msgid ""
"Hovering over any point in line graph reveals notated breakdown of data in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:70
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:76
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:80
msgid "Activity filter tab"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:82
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst-1
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst-1
msgid ""
"What a campaign activity filter tab looks like in Odoo Marketing Automation."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:89
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:94
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:98
msgid "Link tracker"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:100
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:108
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:112
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:120
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:152
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:179
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:125
msgid "Traces"
msgstr "Jäljet"
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:127
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst-1
msgid "The Traces page in the Odoo Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:135
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:139
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:143
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:147
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:159
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst-1
msgid "The Participants page in the Odoo Marketing Automation application."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:167
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:171
msgid ""
"At the top of the graph, there's a color key that describes the type of "
"participants found in the graph."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/understanding_metrics.rst:174
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:3
msgid "Campaign workflow activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:13
msgid "A workflow in an Odoo Marketing Automation campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:13
msgid ""
"Workflow sequence of three activities; the last child activity has a "
":ref:`trigger type <marketing_automation/trigger-type>` of **Mail: not "
"opened**."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:21
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:24
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:29
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:33
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:37
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
msgid "The create activities pop-up window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:49
msgid "Activity types"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:51
msgid ""
"There are three different types of activities available in the *Marketing "
"Automation* app:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:63
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:288
msgid "Email"
msgstr "Sähköposti"
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:65
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:68
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
msgid ""
"The create and edit email drop-down option on create activities pop-up "
"window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:76
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:81
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:85
msgid ":doc:`Creating and configuring email templates <../email_marketing>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:90
msgid "Server action"
msgstr "Palvelintoiminto"
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:92
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
msgid "The Server Action drop-down menu on create activities pop-up window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:102
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:107
msgid ""
"To view all server actions in the database, activate :ref:`developer-mode`, "
"and navigate to :menuselection:`Settings app --> Technical --> Actions --> "
"Server Actions` dashboard."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:113
msgid "Create a new server action"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
msgid "The Create Server Action pop-up window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:124
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`:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:127
msgid ":guilabel:`Update Record`: update the values of a record."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:128
msgid ""
":guilabel:`Create Activity`: create an activity with the *Discuss* app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:129
msgid ""
":guilabel:`Send Email`: post a message, a note, or send an email with the "
"*Discuss* app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:130
msgid ""
":guilabel:`Send SMS`: send an SMS, and log them on documents, with the *SMS*"
" app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:131
msgid ""
":guilabel:`Add Followers` or :guilabel:`Remove Followers`: add or remove "
"followers on a record with the *Discuss* app."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:133
msgid ":guilabel:`Create Record`: create a new record with new values."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:134
msgid ":guilabel:`Execute Code`: execute a block of Python code."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:135
msgid ""
":guilabel:`Send Webhook Notification`: send a POST request to an external "
"system."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:136
msgid ""
":guilabel:`Execute Existing Actions`: define an action that triggers several"
" other server actions."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:139
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:144
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:151
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:315
msgid "SMS"
msgstr "SMS"
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:153
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:156
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:164
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>`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:169
msgid ":doc:`Creating and configuring SMS templates <../sms_marketing>`"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:174
msgid "Trigger"
msgstr "Liipaisin"
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:176
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst-1
msgid "The trigger field group on Create Activities pop-up window."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:184
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)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:188
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:192
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>`)."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:199
msgid "Trigger type"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:201
msgid ""
"To define the event occurrence that sets the activity into motion, select a "
"*trigger type* from the drop-down menu:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:204
msgid ""
":guilabel:`beginning of workflow`: the activity is executed when the "
"campaign is started."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:206
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`:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:211
msgid ""
":guilabel:`another activity`: to be executed after another activity in the "
"campaign."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:212
msgid ""
":guilabel:`Mail: opened`: the activity's email was opened by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:213
msgid ""
":guilabel:`Mail: not opened`: the activity's email was **not** opened by the"
" participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:214
msgid ""
":guilabel:`Mail: replied`: the activity's email was replied to by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:215
msgid ""
":guilabel:`Mail: not replied`: the activity's email was **not** replied to "
"by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:216
msgid ""
":guilabel:`Mail: clicked`: a link in the activity's email was clicked by the"
" participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:217
msgid ""
":guilabel:`Mail: not clicked`: a link in the activity's email was **not** "
"clicked by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:219
msgid ":guilabel:`Mail: bounced`: the activity's email has bounced."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:220
msgid ""
":guilabel:`SMS: clicked`: a link in the activity's SMS was clicked by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:221
msgid ""
":guilabel:`SMS: not clicked`: a link in the activity's SMS was **not** "
"clicked by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:222
msgid ":guilabel:`SMS: bounced`: the activity's SMS has bounced."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:225
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:232
msgid "Expiry duration"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:234
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:238
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`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:243
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:249
msgid "Activity domain"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:251
msgid ""
"The :guilabel:`DOMAIN` section of the :guilabel:`Create Activities` pop-up "
"window contains fields to further filter the target audience of the "
"activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:254
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:260
msgid ""
"The :guilabel:`# record(s)` beside the :guilabel:`Activity Filter` field "
"indicates how many records are currently being targeted by this "
":guilabel:`Activity Filter`."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:263
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:266
msgid ""
"The :guilabel:`# record(s)` beside the :guilabel:`Applied Filter` field "
"indicates how many records, in total, are currently being targeted by the "
"activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:272
msgid "Child activities"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:274
msgid ""
"Activities that are connected to, and triggered by, another activity are "
"known as, *child activities*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:277
msgid ""
"The activity that triggers a child activity is known as its *parent "
"activity*."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:279
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."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:282
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:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0
msgid "The trigger types for child activities of an email activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:294
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:321
msgid ""
"Each trigger the child activity on the following conditions of the parent "
"activity:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:296
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:313
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:323
msgid ""
":guilabel:`Add Another Activity`: to be executed after the parent activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:297
msgid ":guilabel:`Opened`: the email was opened by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:298
msgid ""
":guilabel:`Not Opened`: the email was **not** opened by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:299
msgid ":guilabel:`Replied`: the email was replied to by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:300
msgid ""
":guilabel:`Not Replied`: the email was **not** replied to by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:301
msgid ""
":guilabel:`Clicked`: a link in the email was clicked by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:302
msgid ""
":guilabel:`Not Clicked`: a link in the email was **not** clicked by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:303
msgid ":guilabel:`Bounced`: the email has bounced."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:305
msgid "Server Action"
msgstr "Palvelintoiminto"
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0
msgid "The trigger types for child activities of a server action activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:311
msgid ""
"Triggers the child activity on the following condition of the parent "
"activity:"
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:0
msgid "The trigger types for child activities of an SMS activity."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:324
msgid ":guilabel:`Clicked`: a link in the SMS was clicked by the participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:325
msgid ""
":guilabel:`Not Clicked`: a link in the SMS was **not** clicked by the "
"participant."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:326
msgid ":guilabel:`Bounced`: the SMS has bounced."
msgstr ""
#: ../../content/applications/marketing/marketing_automation/workflow_activities.rst:328
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:5
msgid "SMS Marketing"
msgstr "Tekstiviestimarkkinointi"
#: ../../content/applications/marketing/sms_marketing.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:11
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:49
msgid "SMS marketing dashboard"
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:51
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:55
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:60
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:63
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:66
msgid ""
"The :icon:`oi-view-list` :guilabel:`List` view provides the same useful data"
" related to SMS mailings, but in a more traditional list layout."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:69
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:3
msgid "Create SMS messages"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst-1
msgid "Creating an SMS marketing template."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:12
msgid ""
"First, give the mailing a :guilabel:`Subject`, which describes what the "
"mailing is about."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:14
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:20
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.)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:24
msgid ""
"To learn more about mailing lists and contacts, check out "
":doc:`mailing_lists_blacklists`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst-1
msgid "View of the mailing list page in the SMS marketing application."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:30
msgid ""
"To reveal all the possible options in the :guilabel:`Recipients` field, "
"click the field to see all the choices Odoo makes available."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:33
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:41
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:45
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:49
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`)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:0
msgid "Contact recipients on SMS marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:58
msgid "Writing SMS messages"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:60
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:66
msgid ""
"To check the price of sending an :abbr:`SMS (Short Message Service)` for a "
"country, click on the :guilabel:`Information` icon."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst-1
msgid "SMS price check icon."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:74
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:78
msgid "`Odoo SMS - FAQ <https://iap-services.odoo.com/iap/sms/pricing>`_"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:81
msgid "Track links used in SMS messages"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:83
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst-1
msgid "SMS Link Tracker page."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:92
msgid "Adjust SMS settings"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:94
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:98
msgid ""
"An employee can be designated as the :guilabel:`Responsible` in the "
":guilabel:`Tracking` section of the :guilabel:`Settings` tab, as well."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst-1
msgid "SMS Settings tab."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:106
msgid "Send SMS messages"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:108
msgid ""
"Once a mailing is created, choose when Odoo should deliver the message from "
"the following options:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:110
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.\""
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:112
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/create_sms.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:3
msgid "Mailing lists and blacklists"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:10
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:17
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:21
msgid ""
"Click :menuselection:`Mailing Lists --> Mailing Lists` to see an overview of"
" all mailing lists in the database."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid ""
"View of the main SMS mailing list page on the Odoo SMS Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:28
msgid ""
"To edit any existing list, select the desired list from the "
":guilabel:`Mailing Lists` page, and proceed to modify it in a number of "
"ways."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:31
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid "View of the mailing list pop-up window in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:43
msgid ""
"Checking the :guilabel:`Is Public` box is not required, but is recommended "
"to maintain good customer relations."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:46
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:49
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:52
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.)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:56
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:59
msgid ""
"To make changes to the mailing list itself, click the :guilabel:`Edit` "
"button in the upper-left corner of the mailing list detail form."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid "View of the mailing list template form in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:67
msgid ""
"Don't forget to hit the :guilabel:`Save` button once changes have been made."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:70
msgid "Mailing lists contacts"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:72
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid ""
"View of the mailing lists contact page in the Odoo SMS Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:81
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:86
msgid "Communication history in the Chatter"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:88
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:91
msgid ""
"Database users can reference the chatter to easily keep track of "
"communications, and see a history of interactions with contacts and "
"prospects."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:94
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid "View of what the chatter looks like in the Odoo Contacts app."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:104
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:108
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:112
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid "SMS Blacklist menu in the application."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:120
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:128
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:133
msgid "Importing blacklists"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:135
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst:139
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/mailing_lists_blacklists.rst-1
msgid "View of how to import a blacklist in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:3
msgid "SMS campaign settings"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:9
msgid ""
"But, before :abbr:`SMS (Short Message Service)` campaigns can be created "
"(and sent), a few specific settings and features must be enabled first."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:13
msgid "SMS campaign setting"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:15
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid "View of the mailing campaigns setting in Odoo."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:24
msgid ""
"Activating the *Mailing Campaigns* feature in the *General Settings* also "
"enables the *A/B Test* feature."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:27
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:32
msgid "A/B tests"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:34
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:38
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.`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:41
msgid "When clicked, a series of other options appear."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"The A/B Test tab is located on an Odoo SMS Marketing app campaign form."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:47
msgid ""
"In the first field, enter a desired percentage of recipients to conduct the "
"A/B Test on."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:49
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:53
msgid ""
"The following sections are available: :guilabel:`Manual`, :guilabel:`Highest"
" Click Rate`, :guilabel:`Leads`, :guilabel:`Quotations`, or "
":guilabel:`Revenues`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:56
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:62
msgid ""
"Quickly create different versions of the mailing to add to the A/B Test by "
"clicking the :guilabel:`Create an Alternate Version` button."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:66
msgid ""
"Remember, the winning mailing variation is based on the criteria selected in"
" the :guilabel:`Winner Selection` field."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:70
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:15
msgid "Campaigns page"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:72
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"Dasbhoard view of different Campaigns in the Odoo SMS Marketing app, "
"separated by stage."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:84
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid "View of an SMS campaign template in Odoo SMS marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:96
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:100
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:104
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:108
msgid "Sending SMSs through the Contacts app"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:110
msgid ""
"Sending :abbr:`SMS (Short Message Service)` mailings directly through a "
"contact's form is available by default."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:113
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"The SMS icon is located on an individual's contact form in Odoo Contacts."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:121
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"Select a number of contacts, click action, and select send multiple SMSs."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:130
msgid "Set up SMS templates for future use"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:132
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:137
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"Select the SMS Template option in the Technical dropdown on the Settings "
"app."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:149
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst:153
msgid ""
"On this page, :abbr:`SMS (Short Message Service)` templates can be edited or"
" created from scratch."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/marketing_campaigns.rst-1
msgid ""
"The SMS Templates page in Odoo is available after enabling developer mode in the General\n"
"Settings"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:5
msgid "SMS Pricing and FAQ"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:8
msgid "What do I need to send SMSs?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:10
msgid ""
"SMS Text Messaging is an In-App Purchase (IAP) service that *requires "
"prepaid credits* to work."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:13
msgid "How many types of SMSs are there?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:15
msgid "There are 2 types: GSM7 and UNICODE."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:17
msgid ""
"**GSM7** is the standard format, with a limit of 160 characters per message,"
" that includes the following characters:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst-1
msgid "GSM7 characters available in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:24
msgid ""
"**UNICODE** is the format applied if a special character, that *is not* in "
"the GSM7 list, is used. Limit per SMS: 70 characters."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:28
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:34
msgid "How much does it cost to send an SMS?"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:36
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>`_."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:40
msgid ""
"The number of SMSs a message represents will always be available in the "
"database."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst-1
msgid ""
"Number of GSM7 characters that fit in an SMS message in Odoo SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:47
msgid "How to buy credits"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:49
msgid "Go to :menuselection:`Settings --> Buy Credits`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst-1
msgid "Buying credits for SMS Marketing in Odoo settings."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:55
msgid "Or go to :menuselection:`Settings --> View my Services`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst-1
msgid "Using Odoo IAP to recharge credits for SMS Marketing in Odoo settings."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:62
msgid ""
"If Odoo Online (Saas) is being used, along with the Enterprise version, free"
" trial credits are available to test the feature."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:66
msgid "More common questions"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Is there an expiration time for my credits?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "No, credits do not expire."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"**Can I send an SMS to a phone number (which is not a mobile phone) because "
"I see the icon in front of the field “phone”?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "Only if that phone number supports SMS (e.g. SIP phones)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Do I receive an invoice to buy my credits?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "Yes."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Can the recipient answer me?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "No, it is not possible to reply to the SMS."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"**What happens if I send multiple SMSs at once, but I don't have enough "
"credits to send them all?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Do I have a history of the sent SMSs?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:91
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Can I send as many SMSs I want at once?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "Yes, if you have enough credits."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"**If an SMS is sent to a number that doesn't exist in the list of "
"recipients, will credits be lost?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"**What happens if I send my SMS to a paying number (e.g.: a contest to win a"
" ticket for a festival)?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"The SMS will not be delivered to that kind of number, so no charges will be "
"made."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"**Can I identify the numbers that do not exist when I send several SMSs?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "Only the ones that have an invalid format."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**How does the GDPR regulation affect this service?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid ""
"Please find our `Privacy Policy here <https://iap.odoo.com/privacy#sms>`__."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
msgid "**Can I use my own SMS provider?**"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/pricing_and_faq.rst:0
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>`_."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:3
msgid "SMS analysis"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:5
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.)"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:10
msgid ""
"Each :guilabel:`Reporting` metric view option allows for more extensive "
"performance analysis of :abbr:`SMS (Short Message Service)` mailings."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:13
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)."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst-1
msgid "Reporting page in SMS Marketing."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:22
msgid ""
"SMS messages can be sent using automation rules in Odoo. Odoo *Studio* is "
"required to use automation rules."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:25
msgid ""
"To install Odoo *Studio*, go to the :menuselection:`Apps application`. Then,"
" using the :guilabel:`Search...` bar, search for `studio`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:28
msgid "If it is not already installed, click :guilabel:`Install`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:30
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:34
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:38
msgid ""
"Enter a name for the automation rule, and select a :guilabel:`Model` to "
"implement this rule on."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:40
msgid ""
"Based on the selection for the :guilabel:`Trigger`, additional fields will "
"populate below. Set the :guilabel:`Trigger` to one of the following options:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:43
msgid ":guilabel:`Values Updated`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:45
msgid ":guilabel:`User is set`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:46
msgid ":guilabel:`State is set to`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:47
msgid ":guilabel:`On archived`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:48
msgid ":guilabel:`On unarchived`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:50
msgid ":guilabel:`Timing Conditions`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:52
msgid ":guilabel:`Based on date field`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:53
msgid ":guilabel:`After creation`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:54
msgid ":guilabel:`After last update`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:56
msgid ":guilabel:`Custom`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:58
msgid ":guilabel:`On save`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:59
msgid ":guilabel:`On deletion`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:60
msgid ":guilabel:`On UI change`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:62
msgid ":guilabel:`External`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:64
msgid ":guilabel:`On webhook`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:66
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:"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:70
msgid ":guilabel:`Email Events`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:72
msgid ":guilabel:`On incoming message`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:73
msgid ":guilabel:`On outgoing message`"
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:75
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:78
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`."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:84
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."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst-1
msgid ""
"Automation rule template with rule to do, SMS template and log as note "
"highlighted."
msgstr ""
#: ../../content/applications/marketing/sms_marketing/sms_analysis.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:5
msgid "Social Marketing"
msgstr "Some-markkinointi"
#: ../../content/applications/marketing/social_marketing.rst:7
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:28
msgid "Social media accounts"
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:30
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:34
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:44
msgid ""
"In multi-company environments, if every company doesn't activate a page at "
"once, it will result in a permission error."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:47
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:51
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:0
msgid ""
"View of the permission error that appears when incorrectly attempting to add"
" stream."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:59
msgid "Social media streams"
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:61
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst-1
msgid ""
"View of the pop-up window that appears when Add a Stream is selected in "
"Odoo."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:69
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst-1
msgid ""
"Sample of a populated social marketing dashboard with social media streams "
"and content."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:82
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:87
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:97
msgid "Social media page"
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:99
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:103
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst-1
msgid ""
"View of the social media page in the Odoo Social Marketing application."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:112
msgid "Social accounts page"
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:114
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst-1
#: ../../content/applications/marketing/social_marketing.rst-1
msgid ""
"View of the social accounts page in the Odoo Social Marketing application."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:124
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:128
msgid "Social streams page"
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:130
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:138
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:143
msgid ""
"To modify any stream's information, simply click the desired stream from the"
" list, and proceed to make any necessary adjustments."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:147
msgid "Visitors"
msgstr "Vierailijat"
#: ../../content/applications/marketing/social_marketing.rst:149
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst-1
msgid "View of the Visitors page in the Odoo Social Marketing application."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:156
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing.rst:160
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:3
msgid "Social marketing campaigns"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:9
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:17
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst-1
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst-1
msgid "View of the campaigns page in the Odoo Social Marketing application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:25
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:29
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:37
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:41
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:44
msgid "Clicking :guilabel:`Delete` removes the stage entirely."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:47
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:52
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:57
msgid "Create social marketing campaigns"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:59
msgid ""
"First, open the :menuselection:`Social Marketing` application, and select "
":guilabel:`Campaigns` from the header menu."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:62
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:67
msgid ""
"Both options reveal a new campaign detail window directly on the "
":guilabel:`Campaigns` dashboard when clicked."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst-1
msgid "View of the quick add option for campaigns in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:74
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:78
msgid "Edit social marketing campaigns"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:80
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:84
msgid ""
"After entering the pertinent information in the :guilabel:`Quick Add` "
"campaign drop-down, click :guilabel:`Edit`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:86
msgid ""
"Simply select the desired campaign from the :guilabel:`Campaigns` dashboard "
"in list or kanban view."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:88
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:91
msgid ""
"Any of the above routes will reveal the *Campaign Template* page for that "
"specific campaign."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:94
msgid "Social marketing campaign templates"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:96
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst-1
msgid "View of a sample campaign template page in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:105
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:111
msgid ""
"In order for the :guilabel:`Send SMS` option to appear, the Odoo *SMS "
"Marketing* application must be installed on the database."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:115
msgid "Add content and communications to campaigns"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:117
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:121
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:123
msgid ""
":guilabel:`Send SMS`: reveals a blank SMS template on a separate page, in "
"which a SMS communication can be created and configured."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:125
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:128
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:132
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`)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:137
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.)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_campaigns.rst:147
msgid ""
"The Odoo *Social Marketing* app is integrated with other Odoo applications, "
"such as *Sales*, *Invoicing*, *CRM*, and *Website*."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:3
msgid "Social posts"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:5
msgid ""
"The Odoo *Social Marketing* application provides various ways to create "
"posts for any type of social media outlet."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:9
msgid "Posts page"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:11
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:15
msgid ""
"There are four different view options for the :guilabel:`Social Posts` page "
"data: *kanban*, *calendar*, *list*, and *pivot*."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:18
msgid ""
"The view options are located in the upper right corner of the "
":guilabel:`Posts` page, beneath the search bar."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:25
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:29
msgid ""
"The kanban view is represented by an :guilabel:`inverted bar graph icon` in "
"the upper-right corner."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:0
msgid ""
"Kanban view of the posts page in the Odoo Social Marketing application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:43
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:46
msgid ""
"The calendar view is represented by a :guilabel:`calendar icon` in the "
"upper-right corner."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:0
msgid "Example of the calendar view in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:54
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:58
msgid ""
"There is also a helpful left sidebar that organizes all posts by "
":guilabel:`Status` and lists all connected :guilabel:`Social Accounts`, as "
"well."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:61
msgid ""
"The list view is represented by four vertical lines in the upper-right "
"corner."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:0
msgid "View of the list option on the posts page in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:67
msgid "Pivot view"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:69
msgid ""
"The pivot view option provides a fully customizable grid table, where "
"different measures of data can be added and analyzed."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:0
msgid "View of the pivot option on the posts page in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:76
msgid ""
"The pivot view option provides numerous analytical options, allowing for in-"
"depth, detailed analysis of various posts and metrics."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:79
msgid ""
"Click on any :guilabel:`➕ (plus sign) icon` next to a line in the pivot "
"table to reveal more metric options to add to the grid."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:82
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:86
msgid ""
"Next to the :guilabel:`Insert in Spreadsheet` are three options, specific to"
" the pivot view."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:88
msgid "From left to right, those options are:"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:90
msgid ""
":guilabel:`Flip Axis`, which switches the *X* and *Y* axis in the grid "
"table."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:91
msgid ""
":guilabel:`Expand All`, which expands each line in the grid, revealing more "
"detailed information related to it."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:93
msgid ""
":guilabel:`Download`, which, when clicked, instantly downloads the pivot "
"table as a spreadsheet."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:97
msgid "Posts"
msgstr "Julkaisuja"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:99
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.)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Sample of a social media post's pop-up window in Odoo Social Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:106
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:111
msgid "Create leads from comments"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:113
msgid ""
"Odoo *Social Marketing* also provides the ability to create leads directly "
"from social media comments."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:116
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:120
msgid ""
"Doing so reveals a drop-down menu with the option: :guilabel:`Create Lead`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"The drop-down menu beside a comment revealing the option to create a lead."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:126
msgid ""
"Upon clicking :guilabel:`Create Lead` from the comment's drop-down menu, a "
":guilabel:`Conver Post to Lead` pop-up window appears."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"The convert post to lead pop-up window that appears in Odoo Social "
"Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:133
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:137
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:140
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"New lead detail form generated from a social media comment in Odoo Social "
"Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:149
msgid "Insights"
msgstr "Näkemykset"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:151
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)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:154
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Visual of how the Insights link appears on the dashboard of the Social "
"Marketing app."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:162
msgid ""
"In a multi-company environment, if not *all* pages are selected, de-"
"authentication happens."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:164
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:168
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."
msgstr ""
"Varmista siis, että lisäät *kaikkien* yritysten *kaikkien* sivujen sivut "
"usean yrityksen ympäristössä, jotta vältät tämän ongelman. Jos sivulta "
"poistetaan tunnistus, poista virta ja luo se uudelleen."
#: ../../content/applications/marketing/social_marketing/social_posts.rst:172
msgid "Create and post social media content"
msgstr "Luo ja julkaise sosiaalisen median sisältöä"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:174
msgid ""
"Odoo *Social Marketing* offers the ability to create and post content for "
"social media accounts directly through the application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:177
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"New Post button on the main dashboard of the Odoo Social Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:185
msgid ""
"Or, navigate to :menuselection:`Social Marketing app --> Posts` and click "
"the :guilabel:`New` button."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"New button on the Social Posts page in the Odoo Social Marketing "
"application."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:192
msgid ""
"Either route reveals a blank social media post detail form that can be "
"customized and configured in a number of different ways."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid "Blank social media post detail page in Odoo Social Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:200
msgid "Post detail form"
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:202
msgid ""
"The social media post detail form in Odoo *Social Marketing* has many "
"different configurable options available."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:206
msgid "Company"
msgstr "Yritys"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:213
msgid "Post on"
msgstr "Julkaise kohteessa"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:215
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)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:220
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:224
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:228
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:232
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:237
msgid "Message"
msgstr "Viesti"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:239
msgid ""
"Next, there's the :guilabel:`Message` field. This is where the main content "
"of the post is created."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:241
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)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Sample social media post with visual samples of how it will appear on social"
" media outlets."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:250
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:255
msgid ""
"If :guilabel:`Twitter` is chosen in the :guilabel:`Post on` field, a "
"character counter appears beneath the :guilabel:`Message` field."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:259
msgid "Attach Images"
msgstr "Liitä kuvia"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:261
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:266
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Visualized samples of post with newly-attached images in Odoo Social "
"Marketing."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:274
msgid "Campaign"
msgstr "Kampanja"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:276
msgid ""
"Next, there is the :guilabel:`Campaign` field. This non-required field "
"provides the options to attach this post to a specific marketing campaign."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:279
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:283
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...`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Drop-down menu options of Create or Create and edit in the Campaign field."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:291
msgid ""
"Clicking :guilabel:`Create` creates the campaign, which can be "
"edited/customized later."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:293
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Create campaign pop-up window that appears on a social media post detail "
"form."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:301
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:305
msgid "When"
msgstr "Milloin"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:307
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:311
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Schedule date pop-up window that appears on social media post detail form in"
" Odoo."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:318
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)."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:322
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:326
msgid ""
"Doing so, locks in that specific date/time for Odoo to send the post, and it"
" changes the status of the post to :guilabel:`Scheduled`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:330
msgid "Push Notification Options"
msgstr "Push-ilmoitusvaihtoehdot"
#: ../../content/applications/marketing/social_marketing/social_posts.rst:332
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid "Push notification options section on a social media post detail form."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:340
msgid "It should be noted that *none* of these fields are required."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:342
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:345
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:349
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:352
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:356
msgid ""
"Once that's complete, Odoo automatically updates the visual preview of how "
"the icon appears on the push notification."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:360
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:0
msgid ""
"The Local Time option in the Push Notification Options section of features."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:369
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:373
msgid ""
"To utilize this field, click the :guilabel:`+ Add condition` button, which "
"reveals an equation-like rule field."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:376
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."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst-1
msgid ""
"Push notification conditions set up to match a specific amount of records in"
" the database."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:383
msgid ""
"To add an additional rule, click the :guilabel:`➕ (plus sign) icon` to the "
"far-right of the rule."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:385
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`."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:389
msgid "Lastly, click the :guilabel:`🗑️ (trash can) icon` to delete any rule."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:391
msgid ""
"The size of the specified target audience of recipients is represented by "
"the number of :guilabel:`Records` displayed beneath the rules."
msgstr ""
#: ../../content/applications/marketing/social_marketing/social_posts.rst:395
msgid ":doc:`social_campaigns`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:5
msgid "Surveys"
msgstr "Kyselyt"
#: ../../content/applications/marketing/surveys.rst:7
msgid ""
"Companies gather valuable insights from customers and employees through "
"surveys, aiding informed decision-making."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:10
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:16
msgid "`Odoo Tutorials: Surveys <https://www.odoo.com/slides/surveys-62>`_"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:46
msgid "Dashboard"
msgstr "Työpöytä"
#: ../../content/applications/marketing/surveys.rst:48
msgid ""
"Upon opening the *Surveys* application, Odoo presents the main dashboard of "
"the *Surveys* application, otherwise known as the :guilabel:`Surveys` page."
msgstr ""
#: ../../content/applications/marketing/surveys.rst-1
msgid "The Odoo Surveys application dashboard in the default Kanban view."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:56
msgid ""
"The *Surveys* dashboard can be accessed at any time throughout the "
"application by clicking :menuselection:`Surveys` from the header menu."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:59
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:62
msgid ""
"On the dashboard, all the surveys that have been created in the database are"
" displayed in a default Kanban view."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:65
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:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:68
msgid "Number of :guilabel:`Questions` in that particular survey"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:69
msgid ""
":guilabel:`Average Duration` of the survey (how long it typically takes a "
"participant to complete)"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:70
msgid "Number of :guilabel:`Registered` participants for the survey"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:71
msgid "Number of times that particular survey has been :guilabel:`Completed`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:72
msgid ""
"Percentage and data bar showcasing how many people have :guilabel:`Passed` "
"or become :guilabel:`Certified`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:76
msgid ""
"The :guilabel:`Passed` percentage and bar **only** appears when a *Required "
"Score* has been configured for that particular survey."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:79
msgid ""
"The :guilabel:`Certified` percentage and bar **only** appears if that "
"particular survey has the *Is a Certification* option enabled on the survey "
"form."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:82
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:85
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"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:89
msgid ""
"A half-trophy background image behind the survey name indicates that the "
"survey is a *Certification*."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:92
msgid ""
"To the far-right of those data points on the survey lines, located on the "
"*Surveys* application dashboard, are a collection of buttons."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:95
msgid "Those buttons are as follows:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:97
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:101
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:105
msgid ""
"Below that, a dynamic email template, complete with a :guilabel:`Start "
"Certification` button appears, which can be modified, as well, if needed."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:108
msgid ""
":guilabel:`Attachments` can be added to the email, as well as an "
":guilabel:`Answer deadline` can be set, if needed."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:111
#: ../../content/applications/marketing/surveys/create.rst:299
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:0
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The 'Share a Survey' pop-up window in Odoo Surveys with the Send by Email "
"toggled on."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:119
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`."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:123
msgid ""
"The :guilabel:`Send by Email` toggle switch is **not** present when the "
"survey line has zero questions."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:126
msgid ""
"The :guilabel:`Survey Link` only appears when the survey's *Access Mode* is "
"set to *Anyone with the link*."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:129
msgid ""
"The :guilabel:`Additional Emails` field only appears when the survey's "
"*Require Login* field is **not** active."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:132
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:134
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:136
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:139
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:143
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:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:147
msgid "The options are:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:149
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:151
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:153
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:156
msgid ""
":guilabel:`Color`: users can opt to choose a color to add to the survey line"
" on the dashboard for added organizational purposes, if needed."
msgstr ""
#: ../../content/applications/marketing/surveys.rst-1
msgid ""
"The three-dot drop-down menu of options that appears on the Odoo Surveys "
"dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:163
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst-1
msgid ""
"The Schedule Activities drop-down menu that appears on the Odoo Surveys "
"dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:174
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:177
msgid ""
"When the :guilabel:`≣ (bars)` icon is clicked, the survey related data is "
"displayed in a list view."
msgstr ""
#: ../../content/applications/marketing/surveys.rst-1
msgid ""
"The list view option located on the Odoo Surveys application dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:183
msgid ""
"The columns shown on the *Surveys* app dashboard, while in list view, are as"
" follows:"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:185
msgid ":guilabel:`Survey Title`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:186
msgid ":guilabel:`Responsible`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:187
msgid ":guilabel:`Average Duration`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:188
msgid ":guilabel:`Registered`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:189
msgid ":guilabel:`Success Ratio (%)`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:190
msgid ":guilabel:`Avg Score (%)`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:193
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:198
msgid "Activities view"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:200
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst-1
msgid "The activities view option located on the Odoo Surveys dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:212
msgid ""
"A new survey cannot be created in this view, as it is solely for the purpose"
" of creating and viewing scheduled activities."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:216
#: ../../content/applications/marketing/surveys/create.rst:3
msgid "Create surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:218
msgid ""
"Learn about all the different options and configurations that can be "
"utilized when creating a survey in Odoo."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:222
msgid ":doc:`surveys/create`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:225
#: ../../content/applications/marketing/surveys/scoring.rst:3
msgid "Scoring surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:227
msgid ""
"Discover how to measure a survey participant's performance, or overall "
"satisfaction, with Odoo's detailed (and fully customizable) survey scoring "
"options."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:231
msgid ":doc:`surveys/scoring`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:234
#: ../../content/applications/marketing/surveys/questions.rst:3
#: ../../content/applications/marketing/surveys/questions.rst:64
msgid "Create questions"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:236
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:240
msgid ":doc:`surveys/questions`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:243
#: ../../content/applications/marketing/surveys/live_session.rst:3
msgid "Live Session surveys"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:245
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:250
msgid ":doc:`surveys/live_session`"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:253
#: ../../content/applications/marketing/surveys/analysis.rst:3
msgid "Survey analysis"
msgstr ""
#: ../../content/applications/marketing/surveys.rst:255
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."
msgstr ""
#: ../../content/applications/marketing/surveys.rst:260
msgid ":doc:`surveys/analysis`"
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:9
msgid ""
"Fortunately, Odoo provides numerous ways to view survey responses, allowing "
"users to access and analyze survey responses as they are submitted."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:13
msgid "See results"
msgstr "Katso tulokset"
#: ../../content/applications/marketing/surveys/analysis.rst:15
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:18
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:22
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)."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:27
msgid ""
"To learn more about the different analytical elements found on the "
":guilabel:`Surveys` dashboard, check out the :doc:`Survey Essentials "
"<../surveys/create>` documentation."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:30
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The 'See Results' button present on the main dashboard of the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:37
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical survey results page when 'See results' is clicked from the Odoo "
"Surveys dashboard."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:45
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:48
msgid ""
"Beneath that, is the title of the survey, and its description, if one was "
"configured for it on its survey form."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:51
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:54
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:58
msgid ""
"When that drop-down menu is clicked open, another option, "
":guilabel:`Completed surveys`, appears."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The 'All surveys' drop-down menu opened on the 'See results' page of the "
"Odoo Surveys app."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:64
msgid ""
"With that drop-down menu open, the number corresponding to each filter "
"option appears to the right of each option."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:67
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:70
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:75
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:78
msgid ""
"When that second drop-down menu of filter options is clicked open, two "
"additional options appear: :guilabel:`Passed only` and :guilabel:`Failed "
"only`."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The 'Passed and Failed' drop-down menu on the 'See results' page of the Odoo"
" Surveys app."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:85
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:88
msgid ""
"Directly beneath the survey title, there is a :guilabel:`Print` button. When"
" clicked, the entire results page can be printed."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:91
msgid ""
"The :guilabel:`Results Overview` section is below the survey title, filter "
"option drop-down menus, and :guilabel:`Print` button."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The 'Results Overview' section on the 'See results' page in the Odoo Surveys"
" application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:98
msgid ""
"This section of the results page provides a summarized collection of useful "
"survey-related data and metrics for quick analysis."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:102
msgid "Question analysis"
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:104
msgid ""
"Directly beneath the :guilabel:`Results Overview` section is where the "
"results and responses of the survey are found."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:108
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:111
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:115
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:119
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Responded and Skipped indicators on the 'See results' page in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:126
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Sample of a 'correct' indicator on the 'See results' page in the Odoo "
"Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:135
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:138
msgid ""
"This would occur for opinion-based questions, like `When would be a good "
"time to hold another sale?`"
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:141
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical pie graph results on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:149
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical bar graph results on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:156
msgid ""
"Each multiple choice question has a :guilabel:`Graph` tab and an "
":guilabel:`Data` tab. The graph-related tab is shown by default."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:159
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical 'Data' tab on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:167
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:170
msgid ""
"The :guilabel:`Most Common` tab shows the :guilabel:`User Responses`, the "
":guilabel:`Occurrence`, and the :guilabel:`Score` (if applicable)."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical 'Most Common' tab on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:177
msgid ""
"The :guilabel:`All Data` tab shows a list of all the submitted responses to "
"that particular question."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical 'All Data' tab on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:184
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Maximum, Minimum, and Average indicators on the 'See results' page in "
"Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:192
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"Typical 'Filter' icon on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:200
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The applied filter on the 'See results' page in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:213
msgid "Participations"
msgstr "Osallistumiset"
#: ../../content/applications/marketing/surveys/analysis.rst:215
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Participations smart button at the top of a survey form in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:223
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Participations page for a singular survey in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:230
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"An individual participant's detail form in the Odoo Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:239
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Participations page for all surveys in the Odoo Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:247
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."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:250
msgid ""
"The :guilabel:`Participations` page can also be viewed in a Kanban layout, "
"as well."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst-1
msgid ""
"The Participations page in the Kanban view in the Odoo Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:257
#: ../../content/applications/marketing/surveys/live_session.rst:219
msgid ":doc:`create`"
msgstr ""
#: ../../content/applications/marketing/surveys/analysis.rst:258
#: ../../content/applications/marketing/surveys/create.rst:334
#: ../../content/applications/marketing/surveys/live_session.rst:221
msgid ":doc:`scoring`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:5
msgid ""
"To create a survey in the Odoo *Surveys* application, navigate to "
":menuselection:`Surveys app --> New` to reveal a blank survey form."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:9
msgid ""
"The :guilabel:`New` button is **not** present on the *Surveys* dashboard if "
"in the *Activities* view."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:13
msgid "Survey form"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid "How a blank survey form looks in the Odoo Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:19
msgid ""
"At the top of the survey form are four radio buttons, each representing a "
"survey style. The radio button options are:"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:22
msgid ":guilabel:`Survey`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:23
msgid ":guilabel:`Live Session`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:24
msgid ":guilabel:`Assessment`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:25
msgid ":guilabel:`Custom` (selected by default)"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:27
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:31
msgid ""
"The :guilabel:`Custom` option, selected by default, offers all the options "
"from every potential survey type (located in the :guilabel:`Options` tab)."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:34
msgid ""
"Beneath those radio survey type options is a blank field in which a name for"
" the survey **must** be entered."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:37
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:41
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:46
msgid ""
"Below those fields and options are four tabs: :guilabel:`Questions`, "
":guilabel:`Options`, :guilabel:`Description`, and :guilabel:`End Message`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:52
msgid ""
"View, access, add, and/or delete questions and sections to the survey in the"
" :guilabel:`Questions` tab."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:55
#: ../../content/applications/marketing/surveys/questions.rst:25
msgid ""
"By default, two columns are present in the :guilabel:`Questions` tab: "
":guilabel:`Title` (i.e. the question) and :guilabel:`Question Type`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:58
#: ../../content/applications/marketing/surveys/questions.rst:28
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:62
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The slider drop-down menu with the Mandatory Answer option selected in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:71
msgid "Add a question"
msgstr "Lisää kysymys"
#: ../../content/applications/marketing/surveys/create.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:76
msgid ""
"To learn how to create and customize questions, refer to the :doc:`create "
"questions <questions>` documentation."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:80
#: ../../content/applications/marketing/surveys/questions.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:85
msgid "Add a section"
msgstr "Lisää väliotsikko/osio"
#: ../../content/applications/marketing/surveys/create.rst:87
#: ../../content/applications/marketing/surveys/questions.rst:43
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:92
#: ../../content/applications/marketing/surveys/questions.rst:48
msgid ""
"The section line appears in dark gray in the :guilabel:`Questions` tab."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:94
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:98
#: ../../content/applications/marketing/surveys/questions.rst:54
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:102
#: ../../content/applications/marketing/surveys/questions.rst:58
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:108
#: ../../content/applications/marketing/surveys/live_session.rst:57
#: ../../content/applications/marketing/surveys/questions.rst:207
msgid "Options tab"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:110
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:114
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:118
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:123
#: ../../content/applications/marketing/surveys/live_session.rst:66
msgid "Questions section"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The Questions section of the Options tab on a survey form in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:129
msgid ""
"The first field in the :guilabel:`Questions` section revolves around the "
":guilabel:`Pagination`, or overall layout, of the survey."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:132
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:136
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:140
msgid ""
"Next, select one of the following options in the :guilabel:`Display Progress"
" as` field:"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:142
msgid ""
":guilabel:`Percentage left`: displays the percentage of the survey remaining"
" to participants."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:143
msgid ""
":guilabel:`Number`: display the number of questions answered along with the "
"total number of questions to answer."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:146
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:150
msgid ""
"In the :guilabel:`# Questions Randomly Picked` column, designate how many "
"questions, in that particular section, should be chosen at random to the "
"participant."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:153
msgid ""
"Lastly, there is the :guilabel:`Allow Roaming` option. When enabled, "
"participants are able to navigate back to previous pages in the survey."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:157
#: ../../content/applications/marketing/surveys/live_session.rst:85
msgid "Time & Scoring section"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The Time and Scoring section of the Options tab on a survey form in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:163
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:167
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:171
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:175
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:180
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:184
msgid ""
"When the :guilabel:`Is a Certification` option is enabled, three additional "
"fields appear -- one beside the option, and two below."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:187
msgid ""
"In the field that appears beside the option, users can select (and "
":guilabel:`Preview`) a certification template."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:190
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:194
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:198
#: ../../content/applications/marketing/surveys/live_session.rst:105
msgid "Participants section"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The Participants section of the Options tab on a survey form in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:204
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:208
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:211
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:215
#: ../../content/applications/marketing/surveys/live_session.rst:117
msgid "Live Session section"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The Live Session section of the Options tab on a survey form in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:222
msgid ""
"The :guilabel:`Live Session` section in the :guilabel:`Options` tab of the "
"survey form **only** pertains to *Live Session* surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:225
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:229
msgid ""
"Next, is the :guilabel:`Session Link` field, which **cannot** be customized,"
" but it *can* be sent out to potential participants."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:233
msgid ""
"If a :guilabel:`Session Code` has been entered, the URL in the "
":guilabel:`Session Link` field ends with that specific :guilabel:`Session "
"Code`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:236
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:241
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:245
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:250
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:255
msgid ":doc:`live_session`"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:260
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:265
msgid "End Message tab"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:267
msgid ""
"In this non-required tab, users can enter a custom message that participants"
" see upon completing the survey."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:271
msgid "Survey form buttons"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:273
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid "The various buttons on a survey form in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:280
msgid "Those buttons are the following:"
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:282
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst-1
msgid ""
"The 'Share a Survey' pop-up window that appears in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:290
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:301
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:305
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:310
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:314
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:316
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:321
msgid ""
"If the link in the blue banner is clicked, Odoo returns the user to the "
"survey form."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:322
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:324
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:327
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."
msgstr ""
#: ../../content/applications/marketing/surveys/create.rst:333
#: ../../content/applications/marketing/surveys/live_session.rst:220
#: ../../content/applications/marketing/surveys/scoring.rst:56
msgid ":doc:`questions`"
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:5
msgid ""
"With the Odoo *Surveys* application, users can enhance in-person "
"demonstrations and presentations with the *Live Session* feature."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:8
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:12
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:15
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst-1
msgid ""
"Rendered concept of how a Live Session question and answer result appears in"
" Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:24
msgid "Create Live Session survey"
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:26
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:29
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:33
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:38
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:41
msgid ""
"With the desired survey radio button option selected, proceed to "
":doc:`create a survey <../surveys/create>` with :doc:`questions and sections"
" <../surveys/questions>`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:44
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:48
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst-1
msgid ""
"The Live Session question time limit option for questions in the Odoo "
"Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:59
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:62
msgid ""
"The :guilabel:`Options` tab is organized into four sections: "
":guilabel:`Questions`, :guilabel:`Time & Scoring`, :guilabel:`Participants`,"
" and :guilabel:`Live Session`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:68
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:73
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:80
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:87
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:92
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:96
msgid ""
"If desired, any :guilabel:`Scoring` option, and subsequent "
":guilabel:`Required Score (%)` option are available to use with *Live "
"Session* surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:99
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:107
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:111
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:119
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:123
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:128
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:133
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/`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:137
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:141
msgid ""
"So, collectively, that sample :guilabel:`Session Link` would be: `sample-"
"database.odoo.com/s/1212`."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:145
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:150
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:155
msgid ""
"If any :guilabel:`Scoring` option has been enabled, the opportunity to "
":guilabel:`Reward quick answers` is also available with *Live Session* "
"surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:159
msgid "Start Live Session surveys"
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:161
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:165
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:170
msgid ""
"Additionally, a :guilabel:`Close Live Session` button appears on the survey "
"form. When that button is clicked, the *Live Session* survey closes."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:173
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:178
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:181
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:185
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:190
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*."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:195
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:199
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:203
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:207
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:212
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."
msgstr ""
#: ../../content/applications/marketing/surveys/live_session.rst:216
msgid "Repeat this process until the survey is complete."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:5
msgid ""
"In Odoo *Surveys*, crafting and tailoring survey questions is crucial for "
":doc:`creating and customizing surveys <../surveys/create>`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:8
msgid ""
"Fortunately, Odoo provides numerous ways to configure tailored questions for"
" any kind of survey."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:10
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:14
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`)."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:22
msgid ""
"On a survey form, users can view, access, add, and/or delete questions (and "
"sections) in the :guilabel:`Questions` tab."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:32
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The slider drop-down menu showing the Mandatory Answer option in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:41
msgid "Create sections"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:50
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:66
msgid ""
"To create questions for the survey, click :guilabel:`Add a question` in the "
":guilabel:`Questions` tab."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:69
msgid ""
"Clicking :guilabel:`Add a question` opens the :guilabel:`Create Sections and"
" Questions` pop-up window, in which a survey question can be created."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:77
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:81
msgid "Click :guilabel:`Discard` to discard the question entirely."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:84
msgid "Create Sections and Questions pop-up window"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid "The Create Sections and Questions pop-up form in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:90
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:93
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:96
msgid "Choose from the following :guilabel:`Question Types`:"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:98
msgid ""
":guilabel:`Multiple choice: only one answer`: a multiple choice question, "
"where only one answer is permitted."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:100
msgid ""
":guilabel:`Multiple choice: multiple answers allowed`: a multiple choice "
"question, where more than answer is permitted."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:102
msgid ""
":guilabel:`Multiple Lines Text Box`: an open-ended question, where "
"participants can type in a multiple line response."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:104
msgid ""
":guilabel:`Single Line Text Box`: an open-ended question, where participants"
" can type in a single line response."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:106
msgid ""
":guilabel:`Numerical Value`: a number-based question, where participants "
"must enter a number as a response."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:108
msgid ""
":guilabel:`Date`: a date-based question, where participants must enter a "
"date (year-month-day) as a response."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:110
msgid ""
":guilabel:`Datetime`: a date-based question, where participants must enter a"
" date *and* time (year-month-day, hour-minute-second) as a response."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:112
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:117
msgid ""
"Different features appear in the :guilabel:`Answers` and :guilabel:`Options`"
" tabs, depending on the chosen :guilabel:`Question Type`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:120
msgid ""
"However, the :guilabel:`Description` tab **always** remains the same, "
"regardless of the question type chosen."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:123
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:127
msgid ""
"Each tab offers a variety of different features, depending on what "
":guilabel:`Question Type` was chosen."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:131
msgid "Answers tab"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:133
msgid ""
"The :guilabel:`Answers` tab **only** appears if the selected "
":guilabel:`Question Type` provides answer options to the participant."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:136
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:140
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid "The Single Line Text box question type answers tab in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:148
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:152
msgid ""
"If the :guilabel:`Save as user nickname` option is enabled, Odoo saves the "
"participant's answer as its nickname."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:155
msgid ""
"For all other applicable :guilabel:`Question Type` options that provide "
"answer options to the participant, the :guilabel:`Answers` tab appears the "
"same."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The answer tab with a multiple choice answer option selected in Odoo "
"Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:162
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:166
msgid ""
"The entered answer options appear in the :guilabel:`Choices` column of the "
":guilabel:`Answers` tab."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:168
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:172
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:177
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:181
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:185
msgid ""
"To delete any answer option, click the :guilabel:`🗑️ (trash can)` icon to "
"the far-right of the question line."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:188
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid "The answer tab with a matrix question type selected in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:200
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:204
msgid "Entering a description is **not** required."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:209
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:214
msgid "Answers section"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:217
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:222
msgid "Multiple Choice question types"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:224
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:228
msgid ""
"When enabled, two additional fields appear: :guilabel:`Comment Message` and "
":guilabel:`Comment is an answer`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The answers section of the options tab when a multiple choice question type "
"is selected."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:235
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`)."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:238
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:243
msgid "Multiple Lines Text Box question type"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:245
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The placeholder field when a multiple lines text box option is chosen in "
"Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:253
#: ../../content/applications/marketing/surveys/questions.rst:276
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:257
msgid "Single Line Text Box, Numerical Value, Date, Datetime question types"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:259
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:263
msgid ""
"If the :guilabel:`Validate Entry` option is enabled, two additional fields "
"appear beneath: :guilabel:`Min/Max Limits` and :guilabel:`Validation Error`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The answers section of the option tab when a single line text box question "
"type is chosen."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:270
msgid ""
"In the :guilabel:`Min/Max Limits` field, designate the minimum and maximum "
"allowed quantities for that specific question."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:273
msgid ""
"In the :guilabel:`Validation Error` field, enter a custom message that Odoo "
"displays when an answer is not valid."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:280
msgid "Constraints section"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:282
msgid ""
"The :guilabel:`Constraints` section in the :guilabel:`Options` tab is the "
"same, regardless of the selected :guilabel:`Question Type`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid "The Constraints section in the options tab in Odoo Surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:289
msgid ""
"In the :guilabel:`Constraints` section, there is one option available: "
":guilabel:`Mandatory Answer`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:291
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:295
msgid ""
"In the :guilabel:`Error Message` field, enter a custom error message "
"prompting the participant to provide an answer for this question."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:299
msgid "Conditional Display section"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:301
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)."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:305
msgid ""
"The :guilabel:`Conditional Display` section of the :guilabel:`Options` tab "
"is **not** available when questions are randomly picked."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:308
msgid ""
"There is only one field in the :guilabel:`Conditional Display` section: "
":guilabel:`Triggering Answers`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The Conditional Display section of the options tab in the Odoo Surveys "
"application."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:315
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:320
msgid "Live Sessions section"
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:322
msgid ""
"The option in the :guilabel:`Live Sessions` section of the "
":guilabel:`Options` tab are **only** supported by *Live Session* surveys."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:325
msgid ""
"There is only one option available in the :guilabel:`Live Sessions` section:"
" :guilabel:`Question Time Limit`."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst-1
msgid ""
"The Live Sessions section of the Option tab in the Odoo Surveys application."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:332
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."
msgstr ""
#: ../../content/applications/marketing/surveys/questions.rst:336
msgid ""
"Survey text colors are directly linked to the colors used for the "
":doc:`website theme <../../websites/website/web_design/themes>`."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:5
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:9
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`."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:14
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:18
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:21
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:25
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:28
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:32
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 %`."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:36
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst-1
msgid ""
"Setting the Required Score (percentage), login required, and certification "
"template."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst:46
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."
msgstr ""
#: ../../content/applications/marketing/surveys/scoring.rst-1
msgid "Example of how a badge looks on the eLearning portion of the website."
msgstr ""
Reference in New Issue View Git Blame Copy Permalink