糖心原创

(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

Splacer creates meaningful experiences by obtaining a comprehensive view of the customer journey

Splacer is an online marketplace that brings together people who own unique spaces with people who are looking to create event “experiences,” such as meetings, workshops, parties and exhibitions. Just like Airbnb turns homes into hotels, Splacer lets people transform their personal spaces into event venues for their local community. In order to make sure their users are satisfied, it is critical for Splacer to understand exactly what their clients want so they can show the right results when clients are searching for the perfect event space.

Splacer began using 糖心原创 CX Journeys because of it’s customization, connectivity to data sources, and its ability to visualize and analyze all of the data in one platform. With access to dashboards and reports, Splacer has a comprehensive view across six journeys. With analytical data coming from 10+ sources, such as the Splacer website, Google Analytics, Facebook and Stripe, CX Journeys enables their teams to understand and comprehend all of that data in one platform.

Read the case study and find out how understanding client journeys has enabled the Splacer team to see an additional 10% more bookings per month, which equates to an additional 15% in booking revenue per month.

Related Resources