Requirements for server-side forwarding

Last update: January 25, 2024

Topics:
Server-Side Forwarding

CREATED FOR:

Admin

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.

Solution Requirements

Server-side forwarding works with Analytics and Audience Manager and/or Audiences.

Service Requirements

Server-side forwarding requires the Identity Service. The Identity Service provides a universal ID that identifies site visitors across all the solutions in the Experience Cloud. You need to implement the ID service before server-side forwarding will work.

Code Versions

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 these required minimums.

AppMeasurement.js
AppMeasurement_Module_AudienceManagement.js
VistorAPI.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: The 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. 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.

recommendation-more-help