Requirements for server-side forwarding
- 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 patternJS-X.X.X
, whereX
is a version number.VisitorAPI.js
: Look for thed_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.
More help on this topic
Analytics
- Analytics Admin Guide
- Analytics Release Notes
- Adobe admin console
- Analytics admin tools
- Admin tools overview
- Code Manager
- Data Sources
- Exclude by IP address
- Logs
- Reporting Activity Manager
- Component migration
- Report Suite manager
- Edit settings of a report suite
- General
- General Account settings
- Internal URL Filters
- Customize Calendar
- Paid Search Detection
- Processing Rules
- Processing rules overview
- Processing Rules
- Processing rules examples
- Examples of processing rules
- Populate a campaign ID from a query string parameter
- Set the product view event from the product overview page
- Add a subcategory by concatenating the category and page name
- Determine a path by copying an eVar value to a prop
- Clean up values in a report
- Populate internal search terms using a query string parameter
- Copy a context data variable to an eVar
- Set an event using a context data variable
- Remove an event from a hit
- Processing rules tips and tricks
- Bot Rules
- Privacy Settings
- Timestamps Configuration
- Server-Side Forwarding
- Traffic
- Conversion
- Marketing Channels
- Traffic Management
- Default Metrics
- App Management
- Media Management
- Activity Map
- AEM
- Adobe Campaign
- Privacy Reporting
- Document Cloud Management
- Advertising Analytics Configuration
- Real-Time
- General
- Manage report suites
- Global report suites
- Save a report suite search
- Download report suite settings
- New report suite
- Report suite templates
- Edit settings of a report suite
- Company Settings
- Data Governance Privacy Labeling
- Server Call Usage
- User and Product Management (Legacy)
- Admin API
- Adobe Analytics 1.4 API EOL FAQ