June product update

11 Jul ‘17

Hi Everyone,

We’ve made a lot of useful product updates this past month:

Reports

We’ve released a big Marketing Master Report. The report is designed to analyse marketing metrics – the influence on profitability, unsubscribes, open and click rates.The report summarises information about all messages for a selected date range with the ability to drill down to a specific message. The data are aggregated into several sections: brand, campaign, tag, message name, month sent, and channel. 

The report shows all information about messages sent in the selected date range: number of unsubscribe requests; profitability by attribute (like in the Message Profitability Report, the numbers tally), number of orders, average check, order conversions from a message.

Reports

One of the report features is that the data in the graphs on profitability, orders and average check are shown for the month when the order was placed, not when the message was sent: if the message was sent in January and the order was placed in February, the report will record it for February. We do this to correlate with orders by month. If we record the revenue in the month the message was sent, then it will be calculated as though «here is how much you earned this month», even though that’s not the case. In fact, you look at the income in the month it was received. This is comparable with GA and other data sources. That said, you can choose to view the month the message was sent in the settings, so that you can see the trend and total income for the whole period.

The report is available to all our clients as part of the basic subscription.

We’ve also updated the Subscriber Database Trend report: now it can be viewed by month and week. We’ve added sections for «subscribed to a channel» and «subscribed to a topic».

Discounts and promo codes

When creating a customer through the UI, you can immediately specify a discount card. The discount card will be the customer ID and is all you need to add a new customer, without an email address or mobile number.

Discounts and promo code

On the promo code page (Campaigns → Promo codes), we’ve added a button to delete unused promo codes. If you accidentally add the wrong thing, you can fix everything without a programmer.

In the promo campaign availability conditions, you can now choose the type of promo code. The campaign will become available when someone uses that type of promo code.

promo-action-availability-condition

Essentially, this means that promo codes can now do everything: offer a discount on a product segment, add points for an order, and even just display a message. You can’t launch these types of promo codes through the UI yet, but we’re fixing that.

We’ve also added free delivery as a benefit. Given what we said above about promo codes, you can now offer promo codes for free delivery or just make delivery free for a certain customer segment.

V3 ops

V3 ops now also work through the tracker. The image below shows an example of registering an email with subscription:

V3 ops

Important updates:

  • operations can be pulled through the tracker by just transmitting the deviceUUID, without a secret service key — in the above image, this is the checkbox under description
  • when initialising a tracker, we need the endpointId; you can’t create it through the UI yet, but your manager can help you do it

We recommend using V3 ops instead of identification operations and web tracking, since unlike the old operations, V3 ops can update new contacts and customer identifications if there are no conflicts. Order processing and editing personal data are not currently supported in V3, but we’ll fix that soon. That said, we’ve added information about customer subscriptions to various topics to the reply for V3 ops.

You can now award prizes in one of the V3 ops steps. You’ll see the actual prize in the XML body of the request. Here’s what the standard operation to order a prize looks like.

13-1

As for Big Brother: in all projects, customer activity data are collected prior to identification. For example, any product views and cart operations in the tracker. This also works with asynchronous V3 ops, if we identify the customer by session. If we don’t use the session, then the operation will process right away, since we are obviously transmitting contact info or ID. We’re watching you, %username%.

Instructions are available at the following links:

Import & export

Now, if a product is deleted from the yml, we’ll automatically show it as unavailable; with the proper segment settings, it will not appear in messages. When the yml settings are deleted, if the product only came from importing that yml, then it will also become unavailable. We are also able to handle situations where the same product is updated from several yml feeds at once. And if a product disappears from the yml, it can still be used in messages and filters since it stays in the system.

When exporting customers, the selection fields now include the number, status and type of card that was last activated (or last card that was added, if none are currently active).

Import/export

We’ve added the possibility to create an operation for an export API action directly from the admin area. Using filters, you can choose which actions and which fields to export. For now, you can only export balance changes, but we will soon add actions related to products and categories in messages. For example:

img

We’ve changed how additional fields are processed in imports: additional fields are now prefixed `CustomField` in the CSV, or are grouped in the `customFields` xml nodes. We’ve preserved backward compatibility everywhere: this will not affect current work on projects, but new imports will look different now.

Batches

Not long ago, we added a search bar to the quick start page that can be called up anywhere and everywhere with Ctrl+K. We’ve now added a new search modifier: prefix your search with “m!” and you will only search messages. M! is for Messages!

post

We’ve improved utm-tag formatting: previously, we deleted all symbols except numbers, letters, hyphens and dots from the ${Message.EmailMailingUtmName} parameter. For example, underscores. A lot of people had problems. We’ve put an end to this tyranny and now show utm-tags the same way they came to us.

We’ve added a new SMS-message interface:

  • we’ve removed the utm-tag block, because humanity is not yet ready for it
  • in the test user search form, we’ve updated the search for mobile phone numbers: now it will search for incomplete phone numbers and ignore phone number formatting, so you can put a hyphen between every digit and we’ll still find it

New filter

We’ve added a birthday filter. We receive customer names and we already know when their birthdays are. This filter makes it possible to send birthday greetings and offer a gift, even if you’re just giving out the same old promo codes. If you don’t specify restrictions in the trigger or operation, then there will be as many birthdays as there are days in the calendar, so be careful here. Here’s the filter.

img

That’s all for today. Stay tuned!

Subscribe to our quarterly news digest

Tell us a little about yourself

We’ll respond within 24 hours

Partnership request

Typically we’re answering within 24 hours