❗️

Deprecated Sync

This sync is no longer supported or maintained. To capture vmcid, we recommend using the Yahoo Media Sync instead.

Capabilities

• Captures vmcid from URL parameters and stores it for audience and campaign tracking.
• Enhances server-side events with captured identifiers for more precise attribution.
• Retains stored identifiers for a configurable duration set in the UI.
• Values refresh whenever the URL parameters are detected again.

Sync Details

• IDs:

  • vmcid – A Verizon marketing campaign identifier captured from the URL to attribute sessions or users to specific campaigns.

• Description:

  • The sync captures vmcid from URL parameters.
  • Each value is stored in first-party storage for a configured duration.
  • Values are refreshed when new data is detected.
  • The identifiers are added to server-side event payloads for attribution or 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

  {
    "verizon": {
      "vmcid": "value from url parameter vmcid"
    }
  }
  
  

• Cookie Name:

  • Cookie: _meta_verizon_vmcid
  • IndexedDB: [your storage prefix]_verizon_vmcid
  • For a general guide on ID Sync validation, see here.

Sync Setup Guide

1. Add a Verizon Sync in MetaRouter

To gather the vmcid value from URLs, you must add a Verizon 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 Verizon sync.
3. Fill out the following fields:
   1. Cookie Lifetime (in days)Defines the duration after which a stored value is removed unless renewed. Example: 365
4. Scroll down and click the Save and Build File button.
5. Deploy your AJS file to propagate changes to your web property.