Marketing¶
Marketing holds the promotions, the shopper feedback, the search wiring and the newsletters. The stock sub-menus are gone, so every entry sits directly under Marketing rather than inside Promotions, Communications, SEO & Search or User Content.
| Entry | What it is |
|---|---|
| Catalog Price Rules | Price changes applied to products before anything reaches the cart |
| Cart Price Rules | Discounts applied to the cart, with or without a coupon |
| Email Templates | The transactional emails. See Content |
| Email Header & Footer | The pieces every transactional email shares. See Content |
| URL Rewrites | Addresses that point somewhere else |
| Newsletter Subscribers | Every address on the list |
| Newsletter Templates | The newsletters you write |
| Newsletter Queue | The sending runs |
| Search Terms | What shoppers typed into storefront search |
| Search Synonyms | Words the search engine should treat as the same word |
| Site Map | The XML sitemaps the store writes |
| Reviews | Every product review |
| Pending Reviews | Only the reviews waiting for a decision |
Where this menu appears is a setting. Menu Position in Configuration under Nebula, Nebula Admin Theme, Settings puts the whole navigation in the sidebar, across the top, or in the Magento rail. See Finding your way around.
Rating is not a Marketing entry
The star scales themselves, Quality, Value, Price and any you add, are defined under Stores, Attributes, Rating. A rating record carries a Rating Title, per store view titles, a visibility list, an Is Active toggle and a sort order. Marketing is where you moderate the reviews people leave against those scales.
Catalog price rules¶
The list gives you ID, Name, a Status badge of Enabled or Disabled, From Date, To Date and Priority. Add New Rule starts one, clicking a row opens it, and there are no mass actions. See Working with lists.
The rule screen is two columns. Rule Information and Conditions run down the left, Actions sits on the right.
| Panel | Fields |
|---|---|
| Rule Information | Rule Name, Active, Description, Websites, Customer Groups, From Date, To Date, Priority |
| Conditions | The condition tree described below. Leave it empty and the rule applies to every product |
| Actions | Apply, Discount Amount, Discard Subsequent Rules |
Websites and Customer Groups are both required and both take more than one value.
Apply offers four ways to change the price.
| Apply | What the Discount Amount means |
|---|---|
| Apply as percentage of original | Take this percentage off the original price |
| Apply as fixed amount | Take this amount off the original price |
| Adjust final price to this percentage | Set the price to this percentage of the original |
| Adjust final price to discount value | Set the price to this amount |
Priority decides the order when several rules could apply to the same product, lowest first. Discard Subsequent Rules stops the lower-priority rules from running once this one has matched.
The action bar carries Back, Delete, Save and Continue and Save, and Delete asks first. See Working with forms.
Cart price rules¶
The list gives you ID, Rule, Coupon Code, Status, Start, End and Priority, with Add New Rule in the toolbar. Clicking a row opens the quick-edit drawer, which carries the row's quick-edit fields, Rule, Status and Priority. The row's Edit action opens the full rule.
| Panel | Fields |
|---|---|
| Rule Information | Rule Name, Active, Description, Websites, Customer Groups, From Date, To Date, Priority, Public In RSS Feed |
| Coupons | Coupon, Coupon Code, Use Auto Generation, Uses per Coupon, Uses per Customer |
| Conditions | When the rule applies at all, as a condition tree |
| Actions | Apply, Discount Amount, Maximum Qty Discount is Applied To, Discount Qty Step, Apply to Shipping Amount, Discard Subsequent Rules |
| Apply the rule only to cart items matching the following conditions | A second condition tree, this one narrowing which items in the cart get the discount. Left empty, every item does |
| Labels | Default Rule Label for All Store Views, the wording the shopper sees beside the discount |
Apply offers percent of product price discount, fixed amount discount, fixed amount discount for whole cart, and buy X get Y free where the discount amount is Y. Discount Qty Step is the X in that last one.
Coupons¶
Coupon has three settings and the rest of the panel follows it.
| Coupon | What you get |
|---|---|
| No Coupon | The discount applies on its own. The other coupon fields and both coupon buttons disappear |
| Specific Coupon | One code, typed into Coupon Code |
| Auto | Codes generated in bulk, one per shopper |
Uses per Coupon caps how many times a code may be redeemed in total. Uses per Customer caps it per shopper account.
While the rule uses coupons, two buttons appear in the action bar beside the rule's title: Manage Coupon Codes and Coupon Codes. Each opens its panel as a dialog over the page. Press Esc, the close cross, or click outside the dialog to put it away. Switch back to No Coupon and the buttons go, closing an open dialog with them.
Manage Coupon Codes is the generator.
| Box | What it sets |
|---|---|
| Coupons Qty | How many codes to make. Required |
| Code Length | How many characters the random part has, not counting the prefix, the suffix and the separators. Required |
| Code Format | Letters and numbers, letters only, or numbers only. Required |
| Code Prefix | Text put in front of every code |
| Code Suffix | Text put after every code |
| Dash Every X Characters | Where to break the code with dashes. 0 means no separator |
The boxes open pre-filled from the store's coupon defaults, so most of the time you set the quantity and press Generate.
Save the rule before you generate
On a rule that has never been saved the panel shows a Save the rule first chip and Generate does nothing. The generator also needs the coupon setting to be Auto, or Use Auto Generation switched on, and it reads the saved rule rather than what is on screen. Change either of those, save, then generate.
Generating queues the work rather than doing it there and then. The panel says it is queueing the request and then reports back in its own message area. Generated codes appear in the Coupon Codes dialog rather than under the generator, and they appear there once the store's queue has processed the job, so reopen that dialog or reload the page if it is empty straight afterwards.
Coupon Codes lists what has been generated for this rule: Coupon Code, Created, Used and Expires. Tick rows for three actions, Delete, which asks first, Export CSV and Export XML. On an unsaved rule the panel says to save the rule first.
The condition tree¶
Both rule screens build their conditions the same way, and so does the item filter on a cart rule.
Each group starts with a line reading If ALL of these conditions are TRUE:. Switch ALL to ANY to make the group match on any one of its rows instead of all of them.
- Condition adds a row to that group.
- Group adds a nested group, which gets its own ALL or ANY. Use one when part of the rule needs different logic from the rest.
- The cross at the end of a row or a group head removes it. Nothing is asked and nothing is written until you save the rule.
A row is three controls: what to look at, how to compare it, and what to compare it with.
| Operator | Reads as |
|---|---|
| is, is not | Exactly that value, or anything but it |
| greater than, equals or greater than | A number or a date above the value |
| less than, equals or less than | A number or a date below the value |
| contains, does not contain | The value appears somewhere in the text |
| is one of, is not one of | Any of the values you picked, or none of them |
| is undefined | Nothing is set. The value control disappears |
Which operators you get depends on what you chose in the first box, so a Yes or No attribute offers only is, is not and is undefined.
The value control changes to suit the attribute.
| Attribute | What you get |
|---|---|
| A plain text or number attribute | A box to type in |
| A dropdown attribute with up to ten choices | A dropdown |
| A dropdown attribute with more than ten choices | Chips for what you have picked and a Choose button that opens a searchable list |
| Category | The same chips and searchable list, with each category shown as its full path and its ID. It starts on is one of, because a rule usually targets a set of categories |
| SKU | Chips for the products already in the rule and a Products button that searches the catalogue by name or SKU |
On a catalog price rule, and in the item filter on a cart price rule, the first box lists the product attributes whose Use for Promo Rule Conditions property is Yes, plus Category and Attribute Set. Set that property on the attribute itself, under Stores, Attributes, Product, and it appears here. The item filter adds Quantity in cart, Price in cart and Row total in cart to that list.
The Conditions tree on a cart price rule works from a different list. It offers the cart attributes only: Subtotal (Excl. Tax), Subtotal (Incl. Tax), Subtotal, Total Items Quantity, Total Weight, Payment Method, Shipping Method, Shipping Postcode, Shipping Region, Shipping State/Province and Shipping Country.
The tree is part of the form, so it is written when you press Save. There is no separate save for conditions.
Reviews and pending reviews¶
Reviews lists everything. Its columns are ID, Created, a Status badge of Approved, Pending or Not Approved, Title, Nickname, the review text, Product, SKU, Visibility and a Type badge of Customer, Administrator or Guest. Pending Reviews lists only what is waiting and has the same columns without Status, since every row there is pending. Narrow screens drop the less important columns first.
Tick rows for two mass actions.
| Action | What it does |
|---|---|
| Delete | Removes the selected reviews. It asks first |
| Update Status | Asks which status to set, then sets it on every selected review |
Clicking a row opens the review.
| Field | What it is for |
|---|---|
| Status | Approved, Pending or Not Approved. Only an approved review reaches the storefront |
| Visibility | The store views the review shows on. Required, and it takes more than one |
| Nickname | The name shown with the review |
| Summary of Review | The review's headline |
| Review | The text itself. You may edit it, which is how a review gets published with a typo or an address taken out of it |
Detailed Rating underneath is a row of stars per rating scale. Click a star to set that scale. Where no scale applies to the review's store views, the panel says the rating is not available for this review's stores, and there is nothing to set.
The action bar adds Previous and Next with Save and Previous and Save and Next, so a moderation queue is worked through without going back to the list each time. Where you came from is remembered, so a review opened from Pending Reviews returns you to Pending Reviews.
Delete removes the review and asks first.
Search terms¶
The list is what shoppers actually typed: ID, Search Query, Results, Popularity, Store, Updated. Results is how many products the last search returned and Popularity is how often the term has been searched, so a term with a high popularity and zero results is a gap worth fixing.
Add New Search Term creates one by hand. Clicking a row opens the quick-edit drawer, where the query text can be corrected without leaving the list. The row's Edit action opens the full screen.
| Field | What it does |
|---|---|
| Search Query | The term this rule is about. Required |
| Store | Which store it applies to. Required |
| Redirect URL | Send anyone searching this term straight to an address instead of to results |
| Display in Suggested Terms | Whether the term appears in the storefront's suggestions |
Search synonyms¶
A synonym group makes several words match each other, so a search for one returns the others as well. The list gives you ID, Synonyms, Website and Store View, with New Synonym Group in the toolbar and a Delete mass action that asks first.
| Field | What it does |
|---|---|
| Scope | The websites and store views the group applies to. Required |
| Synonyms | The words, separated by commas. Required. Entering shoes,footwear makes a search for shoes return footwear too |
| Merge existing synonyms | When one of these words already belongs to another group in the same scope, merge the two groups instead of refusing to save |
Leave Merge existing synonyms off and a clash is refused at save time, which is the safer default: it tells you the word is already spoken for rather than quietly joining two groups together.
URL rewrites¶
A rewrite makes one address answer at another, or sends a visitor on to it. The list gives you ID, Request Path, Target Path, a Redirect Type badge, and Store. Clicking a row opens the rewrite, and there are no mass actions.
| Field | What it does |
|---|---|
| Store | The store view the rewrite belongs to. Required |
| Request Path | The address a visitor asks for. Required |
| Target Path | Where it actually goes. Required |
| Redirect Type | No serves the target at the requested address without telling the browser. Permanent (301) moves the address for good and search engines follow it. Temporary (302) moves it for now |
| Description | A note for whoever reads this next. It is worth writing |
Rewrites for a product, a category or a CMS page look different
This screen is the Nebula form for a custom rewrite. When you arrive at the rewrite screen having picked a specific product, category or CMS page, Magento's own screen for that case takes over and the layout is not the one described here.
Site map¶
The list holds one row per generated sitemap file: ID, Filename, Path, Store and Last Generated. Add Sitemap creates one.
| Field | What it does |
|---|---|
| Filename | The file to write, such as sitemap.xml. Required |
| Path | Where to write it, relative to the web root, such as /sitemap/ or /. Required |
| Store View | The store view the sitemap covers. Required |
There is no Generate action on this list. Files are written on the store's own sitemap schedule, and the Last Generated column is how you check that the schedule is running. A row whose date is old, or empty, means the job is not running rather than that the sitemap is misconfigured.
Newsletters¶
Three entries cover newsletters.
| List | Columns | Row actions |
|---|---|---|
| Newsletter Templates | ID, Template, Subject, Sender, a Type badge of Text or HTML, Added, Updated | Edit, Queue Newsletter, Preview |
| Newsletter Queue | ID, Subject, Status, Queue Start, Queue End, Processed, Recipients | Edit |
| Newsletter Subscribers | ID, Email, Status, Store, Changed | View Customer, Unsubscribe |
None of the three has mass actions.
Writing a newsletter¶
A template is the newsletter itself.
| Field | What it is |
|---|---|
| Template Name | What you call it in the list. Required |
| Template Subject | The subject line recipients see. Required |
| Sender Name, Sender Email | Who it comes from. Both required |
| Template Content | The newsletter, in the rich text editor described in Working with forms. Required |
| Template Styles | Optional styles applied to that content |
Two extra buttons sit in the action bar. Preview Template opens the newsletter rendered, in a dialog over the page, so you can read it as a recipient would without leaving the form. Reset reloads the screen and throws away what you have typed.
The list's Preview action does the same rendering from the list, and Queue Newsletter takes that template through to sending.
Sending it¶
The queue screen is where a template becomes a send.
| Field | What it is |
|---|---|
| Queue Date Start | When sending begins. Leave it empty to send manually |
| Subscribers From | The store views whose subscribers get it. It takes more than one |
| Subject, Sender Name, Sender Email | Copied from the template and editable here for this send |
| Newsletter Content | The same, in the editor |
| Newsletter Styles | Optional styles for this send |
The Newsletter Queue list is then the record of what happened.
| Status | What it means |
|---|---|
| Not Sent | Queued and waiting |
| Sending | Going out now |
| Paused | Stopped part way |
| Sent | Finished |
| Cancelled | Stopped and will not resume |
Processed against Recipients tells you how far a send has got.
Subscribers¶
The subscriber list carries a Status badge of Subscribed, Not Activated, Unsubscribed or Unconfirmed, the store the address signed up on, and when the status last changed.
View Customer opens the account the address belongs to. Unsubscribe takes the address off the list at once, without asking, so read the row before you press it.
Email templates and the shared header and footer¶
Both live on this menu and both are covered by Content, together with the split editor they share and the preview beside it.
One thing is worth knowing from here: the header and footer are saved per store view as a store-scoped setting, so what you save applies to the store view shown in the editor and nowhere else. Configuration has the detail, including how to put the shipped header or footer back.