📘
This integration requires activation of additional services. Contact your MetaRouter representative for assistance.

What Is Merkle?

Merkle is a global performance marketing agency specializing in delivering personalized customer experiences across digital channels. Merkury is Merkle's identity resolution platform designed to help businesses recognize and engage with anonymous website visitors, enhancing customer profiles by connecting online and offline data. It enables brands to deliver more personalized, relevant experiences by unlocking the full potential of customer data while maintaining privacy and compliance standards. Merkury allows businesses to improve customer engagement and marketing efficiency across digital channels through real-time identity management.

Capabilities & Considerations

Important Activation Details: This integration requires activation of additional MetaRouter services to enable the identity sync functionality. Once activated, the Merkury ID (hmid) can be securely retrieved and utilized across other third-party vendor integrations. For assistance activating these services, please contact your MetaRouter representative.
Identity Sync: Retrieves the Merkury ID (hmid) and confidence score from Merkle’s identity endpoint using a fetch-based request, and stores the resolved identifiers in first-party storage for persistent user identification.
Cross-Vendor Identity Resolution: Allows Merkury IDs to be utilized seamlessly in other vendor integrations, facilitating cohesive identity management across various marketing and analytics platforms.

Sync Details

IDs:
- hmid - Merkury ID
- svsid – A session-level identifier read from the _svsid first-party cookie and included in the POST body of the event call to support identity matching.
- confidence_score - Indicates the reliability of the match between a user's data and their Merkury ID. A lower numeric value indicates a higher confidence level in identity resolution. A confidence score of 1 signifies 100% certainty that the individual associated with the returned Merkury ID (hmid) is the same user visiting the site.
Description: This sync makes a fetch-based GET request to Merkle’s identity endpoint. When available, userId and email values are appended to the request URL as query parameters. These values are read from the analytics library after an identify() call has occurred (for example, after a user logs in or signs up); the sync itself does not trigger an identify() call. The endpoint response is parsed to retrieve identity markers, which are then stored in first-party storage according to the configured Cookie Lifetime and used to enrich server-side events.
Response example :
- { "d": { "data": { "confidence_score": 1, "hmid": "3f383895a329fada906df7c449941688fc817152aa99fcc97a6dbc881912cead", "anonymousId": "abc-123" }, "response": "match", "version": "1.0.0" }, "t": 1732222798126, "e": 1732222798126 }
Server-side Event Payload: Upon completion of the Merkle sync, server-side events are enriched with all resolved identity data returned by the identity endpoint. This enrichment may reflect signals derived from _svsid, userId, and email when available, while only supported identifiers are persisted and exposed in the providers object.

{
   "merkle": {
     "d": {
         "data": {
          "confidence_score": 1,
          "hmid": "3f383895a329fada906df7c449941688fc817152aa99fcc97a6dbc881912cead",
          "anonymousId": "abc-123"
         },
         "response": "match",
         "version": "1.0.0"
     }
}

Sync Setup Guide

1. Gather Credentials

Contact your Merkle representative to obtain your Client ID.

2. Add a Merkle Sync in MetaRouter

Submit Integration Request Ticket
- Submit a request through our support portal to enable services required for the Merkle Sync.
- Example ticket description:
  - Ticket Name: Enable Services for Merkle Sync
  - Ticket Description: Please enable services required for the Merkle Identity Sync.
Add the Merkle Sync
- Once you’ve received confirmation that the services have been enabled for Merkle Sync, you may add the Merkle sync in MetaRouter:
  1. From the Pipelines page, find the pipeline associated with the web property you’d like to add a sync to. Hover over the three dot dropdown and select “Build AJS File.”
  2. In the Identity Syncs section, select the Merkle sync.
  3. Fill out the following fields:
    1. CID - Enter your Merkle client ID.
    2. Cookie Lifetime (in days) - Specifies how long a stored value remains active before it is automatically removed from storage unless renewed. When this period expires, the associated storage marker is deleted. The default duration is 30 days.
    3. API Timeout (in miliseconds) - Specifies the duration to wait for a response before timing out the request. Defaults to 5000 milliseconds.
    4. Fire On ReSync - Defines if the sync should be fired again when an identity call is made.
    5. MetaRouter Ingestor URL - Specifies the MetaRouter ingestor URL used by your organization. Ensure the URL does not include https:// at the beginning or any path information after .com. This should be the same as your “Ingestion Website URL” in the Analytics.js settings of your Pipeline.
  4. Scroll down and click the Save and Build File button.
  5. Deploy your AJS file to propagate changes to your web property.