Salesforce has updated its commerce APIs and added a Mulesoft Accelerator to its Commerce Cloud for faster integrations. It also announced a new dashboard to track performance for its Einstein AI-powered recommendation system and released a Salesforce Order Management solution for e-commerce teams on Monday.

The announcements came during the kick-off for NRF 2020, the National Retail Foundation’s annual conference.

New Einstein AI dashboard. The new dashboard within Cloud Commerce reporting shows how Einstein AI-powered product recommendations are performing within a company’s storefront platform.

“Einstein AI dashboard provides near real-time metrics so merchandisers have actionable information the need across sites, storefront pages and custom date-ranges,” Salesforce said.

Improvements to commerce APIs and Commerce Cloud. Salesforce’s updates to its commerce APIs and Commerce Cloud solution are designed to help shorten the production process for custom commerce apps built on Salesforce’s platform and aim to help marketers and e-commerce teams, “Reach shoppers at any touch point.”

Salesforce added the Mulesoft Accelerator to Commerce Cloud to “jump-start” commerce solution integrations. The Mulesoft Accelerator comes with pre-built templates for enterprise resource planning (ERP) and product information management (PIM).

A Salesforce Order Management platform. Salesforce said the new solution “bridges the gap” between physical and digital channels, connecting and automating fulfillment and customer service processes.

The platform works with Salesforce’s mobile POS partners Mad Mobile, NewStore and PredictSpring.

A community-driven initiative for developers. Salesforce has also launched a Commerce Cloud Developer Center to create a “community” for those building e-commerce APIs. The center will provide resources, best practices and a way for API developers to engage with others in the field. It will also include developer toolkits and sample apps.

Why we care. Salesforce’s latest updates are aimed at providing more holistic commerce martech solutions, from the Order Management platform that offers a unified view of the commerce experience to enhanced commerce APIs to faster app development and easier integrations with Commerce Cloud and finally to the additional layer of e-commerce analytics with the Einstein AI dashboard.

About The Author

Amy Gesenhues is a senior editor for Third Door Media, covering the latest news and updates for Marketing Land, Search Engine Land and MarTech Today. From 2009 to 2012, she was an award-winning syndicated columnist for a number of daily newspapers from New York to Texas. With more than ten years of marketing management experience, she has contributed to a variety of traditional and online publications, including MarketingProfs, SoftwareCEO, and Sales and Marketing Management Magazine. Read more of Amy’s articles.


As 2019 comes to a close, we here at Emojipedia have been reflecting on all the emoji updates that took place throughout the year.

We’ve seen long-request designs such as white heart and flamingo be introduced to all major vendors.

Gender neutral people were made the default appearance for many emojis starting on Android. A bunch of additional gender inclusive emojis also came to iOS in the past few months, and the world didn’t collapse as a result.

So with all that in mind, what else happened in the world of emojis this year?

Two infamous new emojis added in 2019 were the ? Yawning Face and the ? Pinching Hand.


Above: the new ? Yawning Face emoji as it appears across various vendors.


Above: the new ? Pinching Hand emoji as it appears across various vendors when sent without a skin tone modifier.

A total of 25 emoji releases were added to Emojipedia throughout the year across 9 different active emoji vendors. Of these updates, 14 included the introduction of brand-new emojis from the Unicode Consortium‘s two official emoji recommendations this year, as well as a couple of new emojis not yet recommended for general interchange (RGI) by Unicode.

The year’s first major emoji update from Unicode, Emoji 12.0, was released by in March 2019. It recommended 230 new emojis, all of which can be seen in their Google designs in the image below.


Above: New Emoji 12.0 emojis added in Android 10 in September 2019. Image: Google designs / Emojipedia composite.

Following a proposal by Google in early March, Unicode also recommended another 168 new emojis in October 2019: Emoji 12.1.

These additional emojis provided a gender neutral option for existing profession and identity-focused people emojis (e.g. ?‍⚖️ Judge and ?‍? Person: Red Hair), as well as expanding the skin tone combinations available for the holding hands emojis introduced in Emoji 12.0.

At the time of writing only Apple support Emoji 12.1, with Apple releasing both Emoji 12.0 and Emoji 12.1 updates simultaneously in October via iOS 13.2. Apple’s designs for both updates are shown below.


Above: All 398 new emojis brought to iOS devices in 2019. Image: Apple designs / Emojipedia composite.

The release of the new Emoji 12.0 designs throughout the year enfolded as follows:

Having already compared the ? Yawning Face and ? Pinching Hand, further highlights from Emoji 12.0 are shown below. First, the new ? White Heart.


? Flamingo had also been a popular request for a number of years.


The biggest new set of additions from early 2019’s Emoji 12.0 was the introduction of various people holding hands with one another, such as the non-gender-specifying ?‍?‍? People Holding Hands emoji shown below.


71 of the 230 new emojis in Emoji 12.0 – roughly 31% – featured some combinations of one or two ? Woman emojis, one or two ? Man emojis, or two ? Person emojis. All of the existing skin tone modifiers options are available for each of the people holding hands: for example, the ??‍?‍?? Women Holding Hands: Dark Skin Tone, Medium-Light Skin Tone emoji shown below shows one ? Woman modified by the ? Dark Skin Tone and the other modified using the ? Medium-Light Skin Tone.


Emoji 12.0 also featured a selection of new emojis intended to represent a selection of differently-abled people. One such new emojis is the ? Mechanical Arm.


Others new accessibility-focused emojis include ? Deaf Person, ? Ear With Hearing Aid and ? Guide Dog.

In the Animals & Nature category, the new ? Orangutan has received a very positive response, though that may due to Apple’s version resembling a certain meme.


? Otter has also received a strong response for both its cuteness and its LGBTQ associations.


The new ? Drop of Blood was initially proposed as a means of allowing discussing menstruation via emoji.


The creation process for ? Drop of Blood was one of the focuses of the 2019 documentary film Picture Character alongside Emoji 5.0‘s ? Woman With Headscarf and this year’s ? Mate, shown below.


However, across vendors’ implementation of Emoji 12.0 an old adversary has raised its head.

Emoji fragmentation is a term often used to describe when at least one fundamental attribute an emoji’s design is notably different between vendors. While some emoji differences don’t overtly change the meaning of what is being conveyed, others completely change what is attempting to be said.

Example of both a minor and major variation in emoji design can be seen in the new ? Person Kneeling emoji.


The relatively minor difference seen across vendor’s ? Person Kneeling is the color of the person’s top. While Google, Facebook, Twitter, and JoyPixels have all opted to use an orange attire for this gender neutral designs, each of the other vendors have used a different color (e.g. a light grey in the Apple design).

However, a potentially major fragmentation is that Google’s ? Person Kneeling is only kneeling on one knee. Since 2016 this posture has become associated with the U.S. national anthem protests : a connotation not present in any of the other vendor’s designs, since all others are kneeling on both of their knees.

Other new instances of both major and minor design fragmentation from Emoji 12.0 are highlighted below.

The new ? Oyster emoji has been largely categorised as a food emoji by vendors’ emoji keyboards. However, many vendors have chosen to display a pearl on top of the creature’s fleshy interior: indicating instead that it is a non-edible Pinctada genus, and therefore not technically a food. However, as the Apple, Facebook and JoyPixels ? Oyster emojis lack the pearl, they can be considered an edible Ostreidae oyster.


The fruit juice contained within ? Beverage Box is highly varied between vendors: apple, grape, orange, lemon, and a combination of pear, apple and cherry all appear.


The ? Razor emoji alternates between a modern safety razor and a Sweeney Todd-esque straight razor.


Alongside the 398 new emojis recommended by Unicode in 2019, there were two emojis not yet RGI introduced by a number of vendors throughout 2019: the ⚧️ Transgender Symbol and the ?️‍⚧️ Transgender Flag.


While ⚧️ Transgender Symbol has had non-RGI support from Microsoft and Samsung since 2012 and 2013 respectively, it was also given an emoji version by both Twitter and WhatsApp this year alongside the ?️‍⚧️ Transgender Flag. Facebook also began to suppor the ?️‍⚧️ Transgender Flag as an emoji this year, although it does not feature an emoji version of the ⚧️ Transgender Symbol.

Both of these emojis are candidates for full emoji status in Emoji 13.0, which is currently being drafted.

?? Gender Neutral Changes In 2019

By far the biggest change seen across various emoji vendors in 2019 was the introduction of gender neutral designs to many previously-released emojis.

Throughout the year Google, Apple, Twitter and Joypixels all introduced over 300 new gender neutral designs to their emoji design sets, following the declared intent of Google detailed in the “Using Gender Inclusive Designs” submission. ? Person Shrugging, ?️ Detective, and ? Merperson are shown as examples below.


Above: a selection of new gender neutral designs introduced for previously-released emojis as they appear in the Apple, Google, Twitter and JoyPixels sets.

When many earlier person-based emojis such as ? Police Officer and ? Person Getting Haircut were recommended by Unicode, they did not have a specified gender. Instead, Unicode recommended that:

“human-form emoji should normally be depicted in a gender-neutral way unless gender appearance is explicitly specified”

However, instead of adhering to this recommendation, most vendors opted to display human-form emojis with gender presentations: the ? Police Officer appearing as a man and ? Person Getting Haircut appearing as a woman.

After issues were raised relating to how emojis were depicting men and women, Emoji 4.0 introduced gender-specific versions of most person emojis, leading to the creation of the gender-specific ?‍♂️ Man Police Officer and ?‍♀️ Woman Police Officer. However, the non-gender-specific ? Police Officer emoji still retained its previous gender-specific appearance, continuing to reinforces stereotypes related to the “default” gender for certain roles and activities.


Above: the ? Police Officer as it appeared across vendors at the start of 2019.

In addition to this, when new human-form emojis such as ? Zombie were recommended, vendors would inconsistently designate gender.


Above: the ? Zombie as it appeared across vendors at the start of 2019.


Above: A comparison of several ? Woman, ? Man and non-gender-specifying emoji designs between Google’s Android 9.0 (before) and Android 10 (after).

At the end of 2019, both ? Police Officer and ? Zombie now appear as shown below.


Above: the ? Police Officer as it appeared across vendors near the close of 2019.


Above: the ? Zombie emoji across vendors at the end of 2019.

While this wider representation for emoji users who do not identify with a specific gender identity, it does lead to further new instances of emoji fragmentation.

In early 2018 Emojipedia CEO Jeremy Burge mused about whether 2018 would go down as “the year of emoji convergence“. This ultimately came to pass, with the growth of design convergence epitomised by the changing of the ? Pistol emoji across all vendors to display a toy waterpistol instead of a legitimate firearm.

In 2019, this trend towards design greater convergence was best encapsulated by Samsung’s historically divergent emojis undergoing a large-scale redesigns to be visually in-keeping with those of other vendors.

For example, this year Samsung updated its ?‍♀️ Women With Bunny Ears emoji to display two women clad in black dresses and bunny ears, as opposed to a single woman wearing white bunny ears.


Additionally, Samsung’s ? Elephant also now appears as a much more realistic animal, losing the cartoon heart by its trunk.


Other examples of emoji design revisions being made in the name of design convergence are highlighted below.

Facebook’s ? Grinning Face lost its clenched-teeth grin in favor of an open-mouth smile of other vendors.


Google updated ? Drooling Face to have its eyes closed and mouth smiling.


Facebook’s ? Face Vomiting now has its eyes shut in discomfort instead of featuring an intense wide-eyed stare, rowing back a divergent change originally made in the Facebook 3.0 update.


Google changed the position of the sweat drop on their ? Sad but Relieved Face to better match the appearance of other vendors.


Samsung also updated its ? Smiling Face With Hearts to displays three hearts floating around its face instead of four[8].


Windows’s ☕ Hot Beverage is now a white cup on a matching saucer instead of a pale blue mug.


Despite the trend towards emoji design convergence seen throughout the last few years, 2019 still introduced some new instances of emoji fragmentation. An example in which both convergence and fragmentation occurred simultaneously can be found in Facebook’s 4.0 update.

Following their September 2019 update, the ? Angry Face and ? Pouting Face now both display the same design – one in-keeping with other vendors’ ? Angry Face design. However, in losing its red gradient ? Pouting Face is now notably inconsistent with the design of other vendors.


Above: the update to the ? Angry Face emoji introduced in Facebook 4.0., swapping gritted teeth for a more convergent frowning mouth.


Above: the new ? Pouting Face design in Facebook 4.0., which now diverges with the red-faced design of other vendors.

There were also some instances of fragmentation that were not widely addressed by vendors in 2019.

One such outstanding vein of continued fragmentation can be found in the implimentation of animal emojis. While where certain vendors display a full-bodied creature for some animals, other vendor’s just display the animal’s head. ? Gorilla is shown as an example of this below.


However, perhaps the biggest outstanding instance of fragmentation can be found in the ? Dizzy Face emoji designs.


The inconsistent shape of the eyes in ? Dizzy Face (spirals or x-shaped) can lead to confusion between users as these two symbol types have different connotations: specifically, the x-shaped eyes are often used as an indication of unconsciousness or even death in the visual language of comics, cartoons, and emoticons.

Despite the substantive changes seen across all active emoji sets in 2019, a couple of major cross-platform quirk remains within the Samsung emoji set. Since Samsung TouchWiz 7.1 in 2016, ? Regional Indicator Symbol Letter U displays a capital “V” (instead of U) and ? Regional Indicator Symbol Letter V displays a “U” (instead of V).


Above: ? Regional Indicator Symbol Letter U and ? Regional Indicator Symbol Letter V as they are displayed across a series of major vendors’ emoji sets.

As regional indicator letters are not intended to be displayed in isolation (they are intended solely for the creation of flag emojis) this design mis-match isn’t of major consequence to most users, but is an odd bug to last for so many years despite there being 7 Samsung emoji updates since this oddity’s introduction.

Additionally, the ?️‍?️ Eye in Speech Bubble emoji remains absent in Samsung One UI 1.5, having been removed from Samsung’s emoji set in 2018. This is of note considering that in February Samsung One re-introduced a selection of emoji previously made unavailable on Samsung devices in an August 2016 update: ✝️ Latin Cross, ☪️ Star and Crescent and ‼️ Double Exclamation Mark.

There was, however, an oddity from an update to Facebook’s emoji set in December 2018 that was rectified in 2019.


The ? Non-Potable Water emoji was corrected to display the standard cross-through-tap design, as opposed to indicating a ban on binning litter. This bizaare change echoed Windows’ 2016 design for ? No Littering, which instead of discouraging littering also appeared to condemn proper garage disposal.

As of December 2019 Apple currently supports the emojis added in Emoji 12.1.

It is expected that all major vendors will provide support to this emoji update in the first half of 2020. Google will likely be one of the next vendors to implement support, given that they have already previewed a selection of Emoji 12.1 mock-ups.


Above: a selection of Google’s Emoji 12.1 designs, as previewed within their initial proposal document.

Also expected in Q1 of 2020 is the release of Emoji 13.0. While the list of new emojis is not yet final, a few that could be on the way include Bubble Tea, Fondue, and Seal.


With the 2020 emoji list due to be finalized in the coming months, expect to see any that make the final version of Emoji 13.0 to hit phones in the second half of the year.


The martech management tool is available to CabinetM’s Professional and Enterprise subscription users.

  • More

CabinetM has released a new version of its Stack Map visualization tool that allows martech teams to create a visual of their martech stacks. Updates include the ability to:

  • Isolate products within the martech stack to identify which platforms are dependent on one another.
  • See non-integrated martech solutions alongside integrations — making it easy to identify integration requirements.
  • Upload a custom backdrop to differentiate technology attached to different business contexts (customer journey products, sales tech solutions, etc.)
  • Fully document all integration details within the stack, which can then be exported in a PDF.
  • Export the Stack Map image as a PNG file.

Why we should care

CabinetM CEO Anita Brearton says it’s not unusual for martech stacks to include upwards of 100 to 250 technology tools. Managing a martech stack of that size is no small task, and keeping external teams aware of available marketing technology can be just as difficult.

CabinetM’s Stack Map helps martech teams stay on top of their martech stacks and integration details, while providing a visual representation of the available marketing technology that can be shared with external teams and company executives. (Never has the adage “a single picture is worth a 1,000 words” ever been more true than a visualization tool that highlights how a 100 technology platforms are inter-connected.)

More on the news

  • The Stack Map visualization tool is available to CabinetM’s Professional and Enterprise subscription users.
  • The Stack Map interactive features make it possible to click on integration links to see more information on how products are integrated and how data flows through different solutions.
  • CabinetM’s martech management database includes more than 12,000 marketing technology platforms.

About The Author

Amy Gesenhues is a senior editor for Third Door Media, covering the latest news and updates for Marketing Land, Search Engine Land and MarTech Today. From 2009 to 2012, she was an award-winning syndicated columnist for a number of daily newspapers from New York to Texas. With more than ten years of marketing management experience, she has contributed to a variety of traditional and online publications, including MarketingProfs, SoftwareCEO, and Sales and Marketing Management Magazine. Read more of Amy’s articles.


Email delivery firm, SparkPost, has announced new enhancements to its validation service, SparkPost Recipient Validation. According to SparkPost, the enhancements include additional data which doubles the number of bad email address it is able to detect. The feature identifies the bad email addresses using historical bounce data and analyzes the sending behavior of other SparkPost customers to allow customers to filters the bad emails.

“SparkPost uses typo detection, DNS checks, and especially historical bounce data from thousands of other customers, based on its sending 37% of the world’s B2C and B2B email,” said Charlie Reverte, chief product officer at SparkPost. “That way customers can remove bad emails from their lists before sending so they don’t hurt your sender reputation with ISPs.”

MarTech East in Boston, September 16-18. I hope to see you there!

More about the MarTech Conference

About The Author


Sameer Samat

VP of Product Management, Android

Published Aug 22, 2019

Over the last decade, Android’s open platform has created a thriving community of manufacturers and developers that reach a global audience with their devices and apps. This has expanded beyond phones to tablets, cars, watches, TVs and more—with more than 2.5 billion active devices around the world. As we continue to build Android for everyone in the community, our brand should be as inclusive and accessible as possible—and we think we can do better in a few ways.

Android with map

First, we’re changing the way we name our releases. Our engineering team has always used internal code names for each version, based off of tasty treats, or desserts, in alphabetical order. This naming tradition has become a fun part of the release each year externally, too. But we’ve heard feedback over the years that the names weren’t always understood by everyone in the global community. 

For example, L and R are not distinguishable when spoken in some languages. So when some people heard us say Android Lollipop out loud, it wasn’t intuitively clear that it referred to the version after KitKat. It’s even harder for new Android users, who are unfamiliar with the naming convention, to understand if their phone is running the latest version. We also know that pies are not a dessert in some places, and that marshmallows, while delicious, are not a popular treat in many parts of the world. 

As a global operating system, it’s important that these names are clear and relatable for everyone in the world. So, this next release of Android will simply use the version number and be called Android 10. We think this change helps make release names simpler and more intuitive for our global community. And while there were many tempting “Q” desserts out there, we think that at version 10 and 2.5 billion active devices, it was time to make this change. 

A refreshed look for the brand

The Android brand has evolved over time. Back in 2014, we updated our logo and brand color, and this year, we’re introducing a more modern, accessible look.

Android new logo with robot

The design of the logo draws inspiration from the most recognizable non-human member of the community, the Android robot. The robot belongs to everyone in the community, and has long been a symbol of the fun and curiosity at the heart of Android. Now, it has a special place in our logo. 

We also changed the logo from green to black. It’s a small change, but we found the green was hard to read, especially for people with visual impairments. The logo is often paired with colors that can make it hard to see—so we came up with a new set of color combinations that improve contrast.  

We’ll officially start using the updated logo in the coming weeks with the final release of Android 10. Thank you to the community for supporting Android and inspiring us over the years.