Conversion tracking

How VLVTN Conversion Tracking Works

Updated 2026-06-14
The short answer
When a visitor clicks out from your smart link to a streaming service, VLVTN sends that conversion to Meta two ways: the client-side Pixel and the server-side Conversions API. Both fire from one connected integration and are deduplicated by a shared event id so the same conversion is not counted twice. The conversion is the click-out, not a guaranteed stream.

What happens on a click-out

  1. A visitor clicks a platform
    On your smart link, a visitor taps a streaming service to leave for that destination.
  2. The Pixel fires
    The client-side Meta Pixel records the conversion in the visitor's browser.
  3. The Conversions API fires
    The server-side Conversions API sends the same conversion from VLVTN's servers.
  4. Meta deduplicates
    Both events carry a shared event id, so Meta treats them as one conversion rather than counting it twice.

What a conversion is, and is not

Note
The conversion event is the click-out from your smart link to a streaming service. It is a recorded click to a destination, not a guaranteed stream, play, save, or follow. The click happened. What happens next on the streaming service depends on the song.

This matters for reading your ad results. The number Meta optimizes toward is people who clicked out to a platform, not people who streamed. Treat it as intent to listen, not proof of a stream.

Frequently asked

What is the difference between the Pixel and the Conversions API?

The Pixel is client-side and fires in the visitor's browser. The Conversions API, or CAPI, is server-side and sends the event from VLVTN's servers. Both are active once you connect a Meta integration.

Will I get double-counted conversions from both channels?

No. The Pixel and the Conversions API are deduplicated using a shared event id, so the same conversion is not counted twice in Meta.

Is a tracked conversion the same as a stream?

No. The conversion event is the click-out to a streaming service, a recorded click to a destination. It is not a guaranteed play, save, follow, or stream. What happens after the click depends on the song.

Do I have to enable CAPI separately?

No. There is no CAPI-only toggle and no separate enable step. Connecting one Meta integration turns on both the Pixel and the Conversions API.