PulseEngage OSSign in
Customer engagement platformBuilt for travel, commerce, and lifecycle teams

Pulse

A commercial-ready enterprise engagement operating system for customer data, multi-product consoles, campaigns, web push, onsite experiences, social operations, AI-guided workflows, and one website container for Pulse, GTM, and GA4.

Launch consoleImplementation guide

Platform

From website events to governed customer engagement.

Pulse is designed around the full operator workflow: activate products, connect data, validate identity, build audiences, create content, launch responsibly, monitor exceptions, and keep Test and Live data separated.

Enterprise command center

Central admin, organizations, product activation, API keys, access control, billing readiness, and environment governance in one place.

Pulse Engage

Contacts, imports, events, lists, segments, workflows, campaigns, onsite notifications, web push, consent, and suppressions.

Pulse Social

A dedicated social console for campaigns, content studio, publishing queues, community inbox, analytics, and expert review.

AI-guided operations

Shola guides new users through campaign creation, segmentation, email drafting, image generation, QA, and launch decisions.

New capabilities

Built for enterprise teams, multiple markets, and production websites.

The latest Pulse build brings the web container, market-aware funnels, guided agent creation, visual email editing, and independent product consoles into one operating model.

One web container for Pulse, GTM, and GA4

Install one Pulse browser SDK. GTM and GA4 IDs live in Console and can be changed without a website redeploy.

Global Test and Live data view

Test and Live are hard boundaries across contacts, events, audiences, funnels, imports, and privacy.

Multi-country single-site reporting

One website can serve NG, GH, UK, and other markets while Pulse splits reporting by market, country, site, product, and route context.

Funnel console

Build page-by-page and event-by-event funnels with drop-off, conversion, timing, and sample dropped-off identities.

Segments, lists, and automation

Create static lists, dynamic segments, and workflow rules that auto-add users based on events like London search plus booking.

High-fidelity email workflow

Generate AI email campaigns, tune tone, then refine HTML with the visual drag-and-drop editor across campaign views.

Integration & SDKs

One website SDK for Pulse, GTM, GA4, consent, journey tags, and funnels.

Pulse is designed to fit into production websites without leaking server keys. Use browser-safe container keys for the website, server API keys for backend jobs, and context fields to split one website into market-specific reporting.

  1. 1Create TEST and LIVE Web Containers in Pulse Console and configure allowed origins.
  2. 2Add GTM ID, GA4 measurement ID, consent default, dataLayer name, and capture settings in Console.
  3. 3Install the Pulse container SDK once in the website shell.
  4. 4Set site context on app boot and whenever market, country, product, or SPA route changes.
  5. 5Call identify() at login, signup, checkout, manage booking, and every reliable data-entry point.
  6. 6Track canonical product events, then verify Events and Funnels by Test/Live plus market filters.

Container SDK install

Install one SDK once in the website shell. The browser key is scoped by workspace, environment, allowed origins, and public SDK endpoints.

Browser-safe
<script src="https://pulse.wakanow.com/sdk/pulse.global.js"></script>
<script>
  window.pulseClient = window.pulse.createPulse({
    containerKey: 'plsc_live_xxxxxxxxxxxxxxxxxxxxxxxx',
    apiUrl: 'https://pulse.wakanow.com',
    autoTrackPageViews: true
  });
</script>

App build install

Use the same container key from Settings -> Web Container in React, Next.js, Angular, or any SPA build.

npm
import { createPulse } from '@pulse/sdk-web';

export const pulse = createPulse({
  containerKey: process.env.NEXT_PUBLIC_PULSE_CONTAINER_KEY!,
  apiUrl: 'https://pulse.wakanow.com',
  autoTrackPageViews: true
});

pulse.identify(user.id, {
  email: user.email,
  phone: user.phone,
  first_name: user.firstName
});
pulse.track('booking_started', { product_area: 'flights' });

Markets and SPA routes

Keep one LIVE container for one organization and split reporting by structured context for market, country, site, product, and route.

Context
pulse.setSiteContext({
  market: 'NG',
  country: 'NG',
  site: 'wakanow-web',
  product_area: 'flights',
  route_name: 'flight_search',
  canonical_path: '/ng/flights/search'
});

pulse.setMarket('GH', {
  locale: 'en-GH',
  product_area: 'hotels',
  route_name: 'hotel_search'
});

GTM, GA4, and dataLayer

Pulse initializes the configured dataLayer, loads GTM first, loads direct GA4 only when needed, and can ingest existing dataLayer events.

Analytics
window.dataLayer.push({
  event: 'site_context',
  market: 'GH',
  country: 'GH',
  product_area: 'flights',
  route_name: 'flight_search'
});

window.dataLayer.push({
  event: 'booking_completed',
  booking_id: 'WK-2026-4821',
  amount: 125000,
  currency: 'NGN'
});

Server API keys

Server keys remain for backend ingestion, campaign operations, imports, and admin actions. They must never be shipped in browser code.

Backend only
POST /activity/add
api-key: pls_live_server_secret

{
  "contact_identifier": "user_123",
  "event_name": "booking_completed",
  "properties": {
    "market": "NG",
    "booking_id": "WK-2026-4821"
  }
}

Production QA checklist

Confirm page views, login identify, search, checkout, payment, manage booking, web push subscription, and onsite notification events in Pulse Event QA before a journey or campaign depends on them.

Open Event QAFull implementation guide

AI expert

Meet Shola, your marketing automation expert.

Shola combines marketing automation practice, digital marketing judgment, and live workspace data to explain what is happening, highlight exceptions, and send operators to the right Pulse tool.

  • Recognize returning customers without duplicate profiles
  • Track complete customer journeys from browse to purchase, renewal, or support
  • Launch campaigns with suppression, consent, and provider readiness checks
  • Use Shola to explain anomalies, recommend next actions, and guide setup

Shola insight

Checkout events are streaming, but identified contacts are lagging.

Verify identify calls on manage booking and checkout, then open Event QA to inspect anonymous events before launching abandoned booking journeys.

IdentityData QANext action

Ready for production workflows, not just admin screens.

Use the guided console for daily operators, advanced mode for deep controls, and Shola for diagnosis and recommendations across every organization.

Open PulseOperator sign in