Requirements for Server-Side Forwarding

You must meet these Experience Cloud solution, service, and code requirements to implement server-side forwarding. These requirements also include instructions on how to check for code versions and where to get the latest code libraries.


Tip: Refer to the order of operations for the sequence of service and code changes you should follow when migrating to server-side forwarding.

Solution Requirements

Server-side forwarding works with Analytics and Audience Manager.

Service Requirements

Server-side forwarding requires the Experience Cloud services listed in the following table:

Service Description

Profiles & Audiences

Profiles & Audiences works in conjunction with the Experience Cloud ID service to enable server-side forwarding. You need to be provisioned for Profiles & Audiencesand deploy the ID service before server-side forwarding will work.

To get started with Profiles & Audiences, complete the Experience Cloud Integrations Provisioning form. The form contains important provisioning and implementation information. Review that information carefully before submitting the form.

Important: List the tracking servers you want to use for server-side forwarding in the implementation form.

Experience Cloud ID Service

The Experience Cloud ID service provides a universal ID that identifies site visitors across all the solutions in the Experience Cloud. You need to be provisioned for Profiles & Audiences and deploy the ID service before server-side forwarding will work.

Code Version Requirements

Server-side forwarding requires version 1.5 (or newer) of the code libraries listed below. As a best practice, we recommending using the latest versions rather than the required minimums.

  • AppMeasurement.js
  • AppMeasurement_Module_AudienceManagement.js
  • VisitorAPI.js

Determine Your Code Library Version

Any tool that monitors the HTTP requests made by a browser can show you the version number for your AppMeasurement and Visitor API code. The AppMeasurement_Module_AudienceManagement.js does not contain or return a version ID. The following examples show you what the version IDs for look like for AppMeasurement.js and VisitorAPI.js code.

  • AppMeasurement.js: Adobe Debugger returns the AppMeasurement version like this: Version of Code | JS-1.5.1. Other tools may use a different label, but the value always follows the pattern JS-X.X.X, where X is a version number.
  • VisitorAPI.js: Look for the d_visid_ver parameter. It will show you the Visitor ID service like this: d_visid_ver: 1.5.5.
Attention: Visitor API code older than version 1.5.2 did not include a version number. You're probably using an older code library (and need to upgrade) if your monitoring results do not return a version number. See the implementation steps for information about how to get the latest VisitorAPI.js file.