npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@sitecore/engage

v1.4.3

Published

© Sitecore Corporation A/S. All rights reserved. Sitecore© is a registered trademark of Sitecore Corporation A/S.

Downloads

30,918

Readme

Sitecore Engage

© Sitecore Corporation A/S. All rights reserved. Sitecore© is a registered trademark of Sitecore Corporation A/S.

Sitecore Engage lets you send behavioral and transactional data from your web application to Sitecore CDP or Sitecore Personalize.

Prerequisites

Before installing Sitecore Engage, you need:

  • Access to Sitecore CDP or Sitecore Personalize, or both.
  • Node.js version 18 and npm.
  • A web application (for example, React.js or Next.js).

    Note A Sitecore JavaScript Rendering SDK (JSS) Next.js application with the nextjs-personalize add-on automatically installs Sitecore Engage.

  • Details about your Sitecore CDP or Sitecore Personalize instance: your client key, target URL, and point of sale.

Installation

npm install @sitecore/engage

Importing

import { init } from '@sitecore/engage';

Usage

This section describes how to start using Sitecore Engage in a Next.js (version 12) app.

  1. In index.js, import useEffect from React and init from @sitecore/engage.
import { useEffect } from 'react';
import { init } from '@sitecore/engage';

export default function Home() {
  // ...
}
  1. In the Home function, create an empty, asynchronous function loadEngage for loading the Engage API, then call loadEngage in an Effect Hook.

    Tip You should use the Effect Hook because the window object must be present before you load the Engage API.

export default function Home() {
  const loadEngage = async () => {
    // ...
  };

  useEffect(() => {
    loadEngage();
  }, []);

  return <></>;
}
  1. In the loadEngage function:

    1. Load the Engage API by passing details about your Sitecore CDP or Sitecore Personalize instance to the init() function. Replace the placeholder values with your client key, target URL, point of sale, and cookie domain.

      Important

      • The init() function is asynchronous, so you must await the return value.
      • In production, call the init() function in a module once, then share it across the application using the state management solution of your choice, for example, React Context or Redux.
    2. Start sending VIEW events to Sitecore CDP or Sitecore Personalize by passing event details to the pageView() function. Replace the placeholder values with event details specific to your organization.

const loadEngage = async () => {
  // Load Engage API
  const engage = await init({
    clientKey: '<client_key_PLACEHOLDER>', // for example, "ZpHxO9WvLOfQRVPlvo0BqB8YjGYuFfNe"
    targetURL: '<stream_api_target_endpoint_PLACEHOLDER>', // for example, "https://api-engage-eu.sitecorecloud.io"
    pointOfSale: '<point_of_sale_PLACEHOLDER>', // for example, "myretailsite/ireland"
    cookieDomain: '<cookie_domain_PLACEHOLDER>', // for example, ".beta.myretailsite.com" or "localhost"
    cookieExpiryDays: 365,
    forceServerCookieMode: false,
    includeUTMParameters: true,
    webPersonalization: true,
  });

  // Send VIEW events
  const eventData = {
    channel: '<channel_PLACEHOLDER>', // for example, "WEB"
    currency: '<currency_PLACEHOLDER>', // for example, "EUR"
  };

  const optionalExtensionData = {
    customKey: 'customValue',
  };

  engage.pageView(eventData, optionalExtensionData);
};

Every time your webpage loads, a VIEW event is sent. You can verify this on the Network tab of your web browser's developer tools.

Documentation and community resources

License

Sitecore Engage uses the Apache 2.0 license.