LexisNexis DDP Profiler node

The LexisNexis DDP Profiler node integrates the device intelligence and fingerprinting JavaScript tags onto a Page node to collect information about the event as part of a risk assessment use case. This node fetches the session ID and puts it in the shared state for use by other LexisNexis DDP nodes in the journey.

Example

Read the Example LexisNexis DDP journey.

Availability

Product	Available?
PingOne Advanced Identity Cloud	Yes
PingAM (self-managed)	Yes
Ping Advanced Identity Software (self-managed)	Yes

Product

Available?

PingOne Advanced Identity Cloud

Yes

PingAM (self-managed)

Yes

Ping Advanced Identity Software (self-managed)

Yes

Inputs

None. This node doesn’t read shared state data.

Dependencies

The DDP Profiler node is only needed for DDP products that combine information collected by JavaScript with the session ID, such as ThreatMetrix and BehavioSec.

You must set up integration with the LexisNexis DDP portal before using this node in a journey.

Configuration

Property Usage

Property	Usage
Org ID	The unique ID associated with DDP for your organization.
Page ID	An identifier to use if you place profiling on multiple page nodes. This parameter is optional and can be left blank.
Profiler URI	The DDP Profiler URI. This can be the basic profiling URL or the enhanced profiling hosted SSL URL. The default is the basic profiling URL for the global region.
Use Client Generated Session IDs	If DDP JavaScript tags have been separately integrated onto a customer-hosted web page or mobile device, enable this property to send the session ID to the platform through a `HiddenValueCallback` as part of an API request.
JavaScript Tag Location	Where the node should insert JavaScript tags in login or registration pages. This setting doesn’t change what the end user sees or where the Page node appears. Select `iFrame` so that the device-profiling script loads correctly and can provide the session information used for risk assessment.

Org ID

The unique ID associated with DDP for your organization.

Page ID

An identifier to use if you place profiling on multiple page nodes. This parameter is optional and can be left blank.

Profiler URI

The DDP Profiler URI. This can be the basic profiling URL or the enhanced profiling hosted SSL URL. The default is the basic profiling URL for the global region.

Use Client Generated Session IDs

If DDP JavaScript tags have been separately integrated onto a customer-hosted web page or mobile device, enable this property to send the session ID to the platform through a HiddenValueCallback as part of an API request.

JavaScript Tag Location

Where the node should insert JavaScript tags in login or registration pages. This setting doesn’t change what the end user sees or where the Page node appears.

Select iFrame so that the device-profiling script loads correctly and can provide the session information used for risk assessment.

Outputs

This node writes the following to the shared state:

ddp.session_id: the unique session ID value used with the JavaScript tags. The LexisNexis DDP Query node uses this value to invoke the DDP session query APIs.
ddp.failure_reason: text associated with the error condition, if an error outcome is triggered.

Callbacks

When integrating a client application through APIs, the node sends a HiddenValueCallback as a container for the client application to send the session ID to the platform.

Outcomes

Next: The profiling completed successfully.
Error: There is an integration error. Check the debug log files for any integration issues. If the configuration looks accurate, open a support case with LexisNexis.

Errors

This node doesn’t log any error or warning messages of its own.

Authentication nodes