Integration Process

The integration process and flow is outlined in the steps below:

Step 1 - Authentication

To take advantage of this solution, you must authenticate using OAuth 2.0.

See the Authentication Guide for details on what an OAuth 2.0 solution would look like.

Step 2 - Conversion tracking implementation

Once authentication is implemented, attributed conversion data can be posted to the endpoint as the advertisers or partners system generates the attribution data. To pass data to the endpoint, follow the conversion tracking implementation steps outlined in the section below.

Step 3 - Data flow

Once conversion data begins flowing, data posted to this endpoint will be reportable in Yahoo DSP and Native ad platforms as a conversion metric. This data will flow into CPA optimization and will also power conversion metrics such as dynamic conversion values and ROAS.

The process flow is illustrated below:

flow enhanced attribution

The vmcid parameter and the click ID pass these values to the landing page URL, which includes a Dot JavaScript tag after a user clicks on an ad. The vmcid click ID is then captured by the Dot JavaScript tag on the page; then stored in the site’s first-party cookie and the browser’s local storage until the user eventually converts on the site within the lookback window controlled by the browser. (Currently, this lookback window is 24 hours for first-party cookies and seven days for local storage.)

A server-to-server integration with Yahoo is performed by sending the click ID value from a landing page when a conversion happens.


Server-to-server integration requires OAuth 2.0 authentication, which is described in the sections below. Once the authentication is successful, the click ID-based conversions can be received on the following endpoint: --data "id=id123&vmcid=${INSERT_VMCID_COLLECTED_FROM_CLICK}&dp=simple_dp&gv=1

The supported parameters in the URL are described in the table below.

Known Limitations


There is no capability to segment exposed users or clickers for use cases such as retargeting, exclusion, or lookalike modeling.

Data uploads

At this time, this solution only supports API upload; there is no batch upload mechanism currently available.

Reporting time

All conversion attributions are reported at upload time, not conversion time or impression/click time.