Developer guides

If you're using a JavaScript web app, we recommend that you get started in the following way:

• Real-time, unified tracking - start by capturing VIEW events because they are essential for tracking. Then, continue setting up tracking by capturing other events, such as IDENTITY and custom ones.

  Important

  Only set up tracking if your site visitor grants consent.

  Important

  Although tracking capabilities are available automatically, you must create a support case for any changes to the tracking configuration. This includes adding, removing, and configuring a site or destination. Creating a support case is to ensure that all of your sites are included in the tracking configuration. If any sites are not included, analytics data will not be collected for those sites.

• Personalization - you have already set up web personalization during initialization, so continue by setting up interactive personalization.

• Search experiences - Create a search results page. This involves requesting search content, displaying it on your site, and capturing events that occur during search.

If you're using a Content SDK or JSS app connected to SitecoreAI, certain capabilities automatically run, with no coding required. We recommend that you set up additional capabilities to ensure that your app uses the full potential of Sitecore DXP products.

The following Cloud SDK capabilities run in Content SDK and JSS apps automatically, with no coding required:

• Real-time, unified tracking:

  • VIEW event capturing - this tracks when a site visitor views a webpage in your app. By updating the default Cloud SDK code in your app, you can modify the VIEW event configuration or disable it.

  • FORM event capturing - this tracks when a site visitor views or submits an SitecoreAI form. The collected data is used to populate the SitecoreAI forms performance dashboard.

  Important

  Although tracking capabilities are available automatically, you must create a support case for any changes to the tracking configuration. This includes adding, removing, and configuring a site or destination. Creating a support case is to ensure that all of your sites are included in the tracking configuration. If any sites are not included, analytics data will not be collected for those sites.

• Personalization:

  • SitecoreAI personalizations - by updating the default Cloud SDK code in your app, you can configure and disable personalization.
  • SitecoreAI A/B/n testing.

In addition to the capabilities that run automatically, you can set up the following Cloud SDK capabilities in your Content SDK or JSS app. These capabilities are provided by different Cloud SDK packages that are independent of each other: you can set up all capabilities or only some of them, and in any order you prefer:

• Real-time, unified tracking - continue setting up tracking on your site by capturing more events:

  • Capture IDENTITY events - this event is used to resolve the identity of an anonymous site visitor to your app.

  • Capture Sitecore Search events - if you have created at least one search experience in your app, these events let you track a site visitor's interactions with the experience.

  • Capture custom events - custom events let you track any visitor behavior of your choice, for example, when the site visitor clicks a component.

  Important

  Only set up tracking if your site visitor grants consent.

• Personalization - you have already set up web personalization during initialization, so continue by setting up interactive personalization.

• Search experiences - Create a search results page. This involves requesting search content, displaying it on your site, and capturing events that occur during search.