Powered by

# Match Verifications and Identifiers

# Unique Identifiers

Verify provides two unique identifiers for each verification session:

# VerificationSessionID

A unique identifier generated by Verify for each verification session. This ID is automatically appended to the target URL.

Example:

https://example.com/survey?re-verification-session-id=5f9a8b7c6d5e4f3a2b1c0d9e

# UserId

Your internal user identifier that you can pass through the entry link. This allows you to match verifications with your own user database.

Example:

https://verify-eu.realeyesit.com/project/{projectSlug}?userId=user12345

The userId will be appended to the target URL:

https://example.com/survey?userId=user12345&verificationStatus=OK

# Multiple Suppliers

If you're working with multiple panel suppliers, you can use the supplierIdParameter to track which supplier each user came from.

# Configuration

When creating a project, specify the supplier ID parameter:

{
  "projectName": "Multi-Supplier Project",
  "targetUrl": "https://example.com/survey",
  "advancedSettings": {
    "supplierIdParameter": "panelProvider"
  }
}

# Usage

Each supplier includes their identifier in the entry link:

Supplier A:

https://verify-eu.realeyesit.com/project/{projectSlug}?panelProvider=supplierA&userId=user123

Supplier B:

https://verify-eu.realeyesit.com/project/{projectSlug}?panelProvider=supplierB&userId=user456

# Matching Duplicates

When a duplicate is detected, Verify appends the matching verification session ID and user ID to the target URL.

# Parameters

  • re-matching-verification-session-id: The verification session ID of the original verification
  • re-matching-user-id: The user ID of the original verification (if available)

# Example

If user tries to verify again:

https://example.com/survey?verificationStatus=Duplicate&re-matching-verification-session-id=5f9a8b7c6d5e4f3a2b1c0d9e&re-matching-user-id=user12345

This allows you to:

  • Track which users are attempting to verify multiple times
  • Link duplicate attempts to the original verification
  • Implement custom duplicate handling logic

# Best Practices

# Next Steps