The following fields are common to all request types.
|Name||Description and usage|
|type||Type of request.
Determines the format of the message. It should be one of the following:
IP address of the site visitor
If specified, you can use the IP address for a geolocation lookup to identify the approximate location of the visitor for a personalized online experience for Promote. The IP address is not stored.
|session||ID of the Episerver session established with the tracker.
Use new if no session was established with Episerver yet.
Returns the allocated session on a successful response. Use that session ID for subsequent requests for this cuid and session.
Sessions should expire after a period of user inactivity (such as four hours), so any requests after this period should revert to new.
|cuid||Consolidated user ID.
Use new if the cuid is unknown.
Returns the cuid value on a successful response. Store the cuid in persistent storage and send it back in future requests so you can track the same customer across multiple sessions (see Storing customer IDs).
Note: Use the same cuid for subsequent requests related to the same user/device.
|site||Site code of the Episerver customer.
Identifies the retailer's site with the site code provided by Episerver.
|clientToken||Authentication token for the Episerver customer; a token provided to the Episerver customer that must be included as part of the JSON data in every API call.
A separate clientToken is issued for each channel.
Ensure that you are using the correct token for your channel.
Note: Any clientToken provided by Episerver to access the RESTful service hosted on Episerver's UAT server is different from the one provided for the service on Episerver's live server. Make sure you are using the appropriate clientToken.
Access channel. It should be one of the following:
Contact Episerver if you need more channels. A separate clientToken is issued for each channel. Ensure that you are using the correct token for your channel.
See Language codes.
|currentURI||Site visitor's current URI.
For example, for web customers, this is the current URI (uniform resource identifier).
|previousURI||Previous URI of the site visitor before the current one.
For example, for web customers, this is the referrer header.
Note: When you provide user, also supply id. Use id instead because name and email are deprecated and kept for backward compatibility.
Information about the site visitor’s browser and operating system.
Mandatory from v1.3 of the Server-to-Server API.
Controls how much A/B test information to return in the response data.
Available values are:
See A/B testing for more information.
Recommendation content configuration for Recommendations.
Only applicable if you are using multiple Episerver products on a page. It overrides the configuration for a page, letting you switch off the generation of Episerver products for this request.
If smartProducts is not defined, the content for all Episerver products defined for the page is returned as normal.
An array of strings listing the Episerver products to include in the response for this page. Available values are smartRecs for Recommendations and smartContent for Promote.
For example, if Recommendations and Promote are configured for a page, but you only want results returned for Promote and not Recommendations, then include the smartProducts property in the request as follows:
To return no Episerver product information on a page, use smartProducts as follows:
Variable metadata information about clicks, A/B test information, and so on. See Click tracking and A/B testing.
Allows real-time filtering of recommendations based on the specified custom attributes.
A comma-separated list of attribute names and values. Attribute names must contain no spaces.
Custom attributes are used only in real-time; they are not stored in the system.
Used for B2B customers, customer is an all-encompassing object in the tracking model that contains information based on a client's customer.
Last updated: Nov 06, 2017