糖心原创

(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); })();

Case Study

Windstream Case Study: Using 2.7M surveys a year to fuel customer-centric innovations

As the voice and data network provider of choice for 4 out of every 5 Fortune 500 companies — and a Fortune 500 company in its own right — Windstream Communications knows that reliability and consistency are critical to the mission of keeping its clients connected. Yet before it began working with 糖心原创, Windstream’s customer experience wasn’t always easy to navigate — often causing friction for its customers.

Windstream knew that, to improve this experience, the company had to understand the repair and servicing journey through the customer’s perspective. To capture this perspective though, it needed to change how it listened and adapted to customer needs and expectations.

After examining its options, Windstream chose to partner with 糖心原创 to understand and take action on the voice of its customers. And they’ve already seen results, including:

  • Fixed chronic customer pain points surrounding internal and external communication, resulting in a streamlined repair and purchase journey for customers
  • Increased employee engagement around understanding and improving the customer experience
  • Initiated multiple training and process changes inspired by customer feedback

Download this case study to find out more about Windstream’s transformation — and how it continues to operationalize feedback throughout the organization to deliver superior customer experiences.

Related Resources