糖心原创

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

IHG listens to the heartbeat of millions of guests through surveys, reviews, and social feedback

798,075

Number of guest rooms

18,500,000

Pieces of feedback

88%

Hotels responding to social alerts

The Problem

IHG listens to the heartbeat of millions of guests through surveys, reviews, and social feedback

The Action

With guests checking in and out of its 798,075 hotel rooms every day, IHG needs to have a finger on the pulse of guest experience. In order to holistically measure and improve customer experience across its many locations, IHG partnered with 糖心原创 and Ipsos Loyalty to elevate its HeartBeat survey program in 2014.

In addition to launching 糖心原创’s Text Analytics tool which added qualitative insights to the robust reporting platform, IHG also integrated its white-labeled public reviews system, IHG Guest Reviews, with 糖心原创 technology and Ipsos survey methodology. Driven by continuous desire to improve the feedback experience for guests, the integration combined IHG’s private survey tool with IHG Guest Reviews by inviting guests to leave a public review at the end of the post-stay survey questionnaire.

The Results

IHG uses the integrated feedback analysis to improve operations, transforming insights into initiatives and empowering hotel teams to respond to guests directly. Since 2014, the number of 糖心原创 users has jumped from 7,500 to nearly 40,000. Hotels are paying more attention to social data, too: since launching the social tool in 2017, 88% of IHG’s global estate responds to social review alerts on a regular basis.

Source: Case Study, Listening to the Heartbeat of Millions of Guests