What is inMarket?

inMarket is a digital advertising and analytics platform that leverages real-time consumer data to deliver personalized advertising experiences. The platform provides tools for location-based targeting, consumer insights, and campaign attribution. inMarket's technology helps marketers engage consumers at precise moments to drive conversions both online and offline.

Product Type: Advertising

Integration Type: Starter Kit & ID Sync

Capabilities

• Captures cm_mmc and itc from URL parameters and userNdat from a fetch response header.
• Enhances server-side event data with the inMarket identifiers for audience targeting and performance tracking.
• Supports user matching via REST call to inMarket's endpoint.
• Adds identifiers to server-side events for attribution and optimization.

Considerations

• Values from URL parameters are refreshed on every page load when present. In contrast, values retrieved via fetch (such as userNdat) are only refreshed once the corresponding storage marker expires.
• If the fetch request fails, a fallback marker (_inMarket_userNdat_failure) is stored for one day.
• Fetch-based ID resolution only occurs if a URL Path is provided in the sync settings.

Sync Details

• IDs:
  • cm_mmc – A campaign tracking identifier captured from the page URL for performance attribution.
  • itc – A traffic source or campaign-related parameter captured from the URL for analytics purposes.
  • userNdat – A user-level identifier returned in the response headers of a fetch request to inMarket’s endpoint.
• Description:
  • The sync captures cm_mmc and itc from URL parameters.
  • It also fetches userNdat from the response headers of a GET request to inMarket’s endpoint at the given URL path.
  • Each value is stored in first-party storage for the duration set by the Cookie Lifetime setting.
  • The identifiers are added to server-side event payloads for attribution and targeting.
• 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.
  JSON

  {
    "inMarket": {
      "cm_mmc": String,
      "itc": String,
      "userNdat": String
    }
  }
  

• Cookie Name:
  • Cookie: _meta_inMarket_cm_mmc, _meta_inMarket_itc, _meta_inMarket_userNdat, _meta_inMarket_userNdat_failure
  • IndexedDB: [your storage prefix]_inMarket_cm_mmc, [your storage prefix]_inMarket_itc, [your storage prefix]_inMarket_userNdat, [your storage prefix]_inMarket_userNdat_failure
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Gather Credentials

• No credentials are required. To enable userNdat resolution, you must provide the appropriate URL Path used for the fetch call.

2. Add an inMarket Sync in MetaRouter

To gather the cm_mmc, itc, and userNdat values, you must add an inMarket 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 inMarket sync.
3. Fill out the following fields:
   1. Cookie Lifetime (in days) – Defines how long to store captured identifiers. Example: 30
   2. URL Path – The REST path for the inMarket API call. If omitted, no fetch will occur. Example: "v1/lci/imp/adv/c-1?typ=online&chn=advertiser&xdv=0&cndat=1"
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.