糖心原创

(see the * 'adobe' handle in functions.php — no async, no defer), so a page-load * Target offer has already set `data-hdr` by the time this runs. * * An answer that lands after this point is inert rather than acted on: * `apply()` finds the prune settled and does nothing, so the visitor * keeps the nav they were served instead of watching it change. That is * the deliberate trade-off — a late activity collects no data, but no * visitor ever sees the wrong nav or waits for the right one. */ (function () { var VARIANTS = ["a","b","c"]; var DEFAULT = "a"; var root = document.documentElement; var settled = false; function valid(v) { return VARIANTS.indexOf(v) !== -1; } function prune(active) { if (settled) return; settled = true; var list = document.querySelectorAll('#site-header > .header-variant'); for (var i = 0; i < list.length; i++) { if (list[i].getAttribute('data-header-variant') !== active) { list[i].parentNode.removeChild(list[i]); } } root.setAttribute('data-hdr', active); // Read by the Adobe Analytics client to attribute the test. root.setAttribute('data-hdr-active', active); if (typeof window.initHeaderNav === 'function') window.initHeaderNav(); /** * `variant` is set before the event so late listeners can tell * "already done" from "not yet". main.js is enqueued in the footer * and therefore always misses the event itself. */ window.medalliaNav.variant = active; document.dispatchEvent(new CustomEvent('medallia:nav-ready', { detail: { variant: active } })); } window.medalliaNav = { variant: null, apply: function (v) { if (valid(v)) prune(v); } }; // `?hv=` sets this server-side; a Target offer in the blocking // embed sets it before the body is parsed. var pre = root.getAttribute('data-hdr'); if (valid(pre)) { prune(pre); return; } /** * Carried forward from an earlier pageview. Read client-side, never in * PHP: WP Engine does not vary its page-cache key on arbitrary cookies, * so server-side personalisation here would serve the first anonymous * visitor's variant to everyone. */ var m = document.cookie.match(/(?:^|; )medallia_nav_variant=([^;]*)/); if (m && valid(m[1])) { prune(m[1]); return; } prune(DEFAULT); })();

Putting the customer at the center of ecommerce experiences at Walmart Mexico

?1B+

valued at

Lowered

operational costs

Decrease

in support time

The Problem

Putting the customer at the center of ecommerce experiences at Walmart Mexico

The 糖心原创 Experience Cloud enables retailers to understand the “why” behind customer feedback scores. 糖心原创’s Text Analytics solution uniquely provides aggregated insights on written comments to enable organizations to better understand the reasons behind the scores, and what to do about it.

It was 糖心原创’s Text Analytics capabilities that were the game-changer for Walmart Mexico. The e-commerce team was finally able to identify topics and sentiment in native Spanish, rather than other solutions they tested in the past that rely on imperfect translation engines.

Josue Berlanga, Director of Customer Care & Customer Experience at Walmart Mexico says, “Once we began hearing what our customers were saying in their own words, and taking action at both the store and corporate level, the journey really began.”

Berlanga noted that Walmart Mexico’s customer experience program has expanded to cover each step in the customer journey. At each step, the investment has proven positive ROI and increased NPS. He went on to share that, “Now we have text analytics and alerts in real-time. In just a couple years we did a quantum leap. For me it was an honor to be involved in implementing 糖心原创 and putting the customer at the center of every decision.”