New Case Study:See how Anthropic automated 95% of dependency reviews with Socket.Learn More
Socket
Sign inDemoInstall
Socket

@adobe-mcid/visitor-js-server

Package Overview
Dependencies
Maintainers
1
Versions
13
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@adobe-mcid/visitor-js-server - npm Package Compare versions

Comparing version

to
0.0.7

2

package.json
{
"name": "@adobe-mcid/visitor-js-server",
"version": "0.0.6",
"version": "0.0.7",
"description": "Server compatible Visitor ID service",

@@ -5,0 +5,0 @@ "main": "lib/Visitor.js",

# Visitor JS - Server Side
A trimmed down version of the `VisitorAPI` JS library, that is meant to run on the server, either in a NodeJS or Rhino environment.
This is a trimmed down version of the `VisitorAPI` JS library. It is designed to run on your server, either in a NodeJS or Rhino environment.

@@ -17,7 +17,7 @@

Customer who are implementing Target client-side, don't need to worry about sdid.
`SDID` is a randomly generated string that is sent in on each call that needs to be combined into a single Analytics entry.
When implementing Target server side, and Analytics client side, you need some sort of mechanism to synchronize the states between the client and the server. `SDID` is part of this state, which is an ID that allows us to combine calls to Target and calls to Analytics into a cohesive set of data.
`SDID` is a randomly generated string that is sent in on each call that needs to be combined into a single Analytics entry.
Customer who are implementing Target client-side, don't need to worry about sdid.

@@ -27,2 +27,4 @@

`sdidConsumerID` is a unique string used to intentify the consumer.
All calls to Target that needs to combined must have the same `SDID`. Each of those calls need to have a unique `sdidConsumerID` in order for them to receive the `SAME SDID`.

@@ -43,3 +45,3 @@

```javascript
// 1. Try to retrieve the AMCV cookie from the request.
// 1. Retrieve the AMCV cookie from the request.
var cookies = cookie.parse(req.headers.cookie || "");

@@ -49,3 +51,3 @@ var cookieName = visitor.getCookieName();

// 2. Generate Visitor Payload by passing sdidConsumerID (mbox name/id) and AMCV Cookie if found in Req:
// 2. Generate Visitor Payload by passing sdidConsumerID (mbox name/id) and AMCV Cookie if found in Req.
var visitorPayload = visitor.generatePayload({

@@ -56,5 +58,3 @@ sdidConsumerID: mboxName,

// 3. At this point, you are ready to make the Target call. Mixin the `visitorPayload` with you target
// specific Target and make the call:
// For example:
// 3. Merge the `visitorPayload` with you target specific into and make the Target call.
var targetPayload = {

@@ -90,3 +90,3 @@ requestLocation: {

NOTE:
<strong>IMPORTANT:</strong>

@@ -120,3 +120,3 @@ - In order for those IDs to make it into the Target call, make sure you call `setCustomerIDs` before calling `generatePayload`.

[Read more](https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-authenticated-state.html)
See [Customer IDs and Authentication States](https://marketing.adobe.com/resources/help/en_US/mcvid/mcvid-authenticated-state.html)

@@ -123,0 +123,0 @@