What is Adobe Everest Tech?

Adobe Everest Tech is an identity resolution service within Adobe Advertising Cloud that helps advertisers recognize users across domains and devices. It supports cross-site user matching and audience targeting by assigning persistent identifiers, which can be leveraged for ad personalization, measurement, and retargeting. Everest Tech works in conjunction with Adobe's broader ad tech stack to improve identity coverage and performance across digital advertising campaigns.

Product Type: Identity

Integration Type: ID Sync

Capabilities

• Fires a pixel to Adobe Everest Tech to retrieve a partner_uid for identity resolution.
• Stores the returned ID in cookie and IndexedDB storage for long-term persistence.
• Injects the resolved ID into the server-side event payload under context.providers.adobeEverestTech.

Considerations

• This sync is not required for the Adobe Experience starter kit (e.g., Adobe Analytics). It is only needed for use cases involving partner_uid.
• The sync uses a redirect-based pixel flow and depends on successful client-side execution.
• If the pixel fails to resolve, a temporary failure marker is stored to prevent excessive retries.

Sync Details

• IDs:
  • partner_uid – A persistent identifier returned by Adobe Everest Tech, used for recognizing users across domains for ad targeting and identity resolution.
• Description:
  • Fires a GET request to the EverestTech pixel using your Partner Key and Redirect URL.
  • If successful, the partner_uid is returned via the redirect URL and stored in IndexedDB/cookie storage for the duration defined in the UI.
  • If the sync fails, a 1-day failure marker is stored to delay retries.
  • The resolved ID is added to the server-side event payload.
• Server-side Event Payload: Upon completion of all vendor's sync, the server-side events will incorporate all resolved identifiers as described above. The following object will be appended to the context.providers property within the event's JSON payload.

  {
     "adobeEverestTech": {
       "partner_uid": String
     }
  }
  

• Cookie Name:
  • Cookie: _meta_adobeEverestTech_partner_uid, _meta_adobeEverestTech_partner_uid_failure
  • IndexedDB: [your storage prefix]_adobeEverestTech_partner_uid, [your storage prefix]_adobeEverestTech_partner_uid_failure
  • Explicit Cookies Set
    • These are cookies set directly by Adobe Everest Tech as part of the pixel sync process and may appear in the browser after a successful sync.
      • everest_g_v2
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

To configure this sync, you’ll need the following values:

• Partner Key – A unique ID provided by Adobe to authorize the EverestTech sync.
• Redirect URL – Defines the URL to redirect everesttech.net to collect partner_uid. For clients using our own endpoint use https://[metarouter-cluster-domain].com/v1/sync/function.
  • Example: "https://mr-platform-staging1.mr-in.com/v1/sync/function"
• If you do not have your Partner Key or Redirect URL, please contact your Adobe account manager or Adobe Customer Support to request these values. Adobe does not provide a public interface for generating them.

2. Add an Adobe Everest Tech Sync in MetaRouter

To gather the partner_uid value, you must add an Adobe Everest Tech sync.

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 Adobe Everest Tech sync.
3. Fill out the following fields:
   • Partner Key – Your Everest Tech partner ID provided by Adobe.
   • Redirect URL – The URL EverestTech should redirect to after resolving the user. If using MetaRouter's ingestion endpoint, use: https://[metarouter-cluster-domain].com/v1/sync/function
     • Example: "https://mr-platform-staging1.mr-in.com/v1/sync/function"
   • Cookie Lifetime (in days) – Duration to store the partner_uid in browser storage.
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.