Conversion tracking

How VLVTN Conversion Tracking Works

Updated 2026-08-08
The short answer
When a visitor clicks out from your smart link to a streaming service, VLVTN sends that conversion to Meta through the client-side Pixel and server-side Conversions API. Connecting one Pro Meta integration turns on both paths, and a shared event id lets Meta deduplicate them. The conversion is the click-out, not a 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.

Check the event path before judging ads

Conversion tracking and the Meta Pixel / CAPI section require a Pro plan. Open Dashboard and select Integrations. In the Meta Pixel / CAPI section, select + Add Meta Integration. Pixel ID and Access Token are required. Test Event Code is optional. Select Save Integration. Once the integration is saved, both tracking channels are active together.

  1. Send the test events
    Use Send Test Events on the connected integration. VLVTN sends VLVTNClick and Lead so you can confirm the connection in Meta.
  2. Assign the integration to the link
    Open the smart link in the editor, choose the Settings tab, and select the connected pixel in the Meta Pixel section. None means the link has no pixel assigned.
  3. Test the DSP button
    Click a streaming-platform button on the smart link. The event you judge should be the click-out to the destination, not the page view and not the ad tap.
  4. Read one conversion
    The browser and server copies share an event id, so the same click-out is treated as one conversion instead of two.

Use this preflight checklist

The quickest way to find a tracking problem is to test one question at a time. Start at Dashboard, move to the link assignment, then use the published DSP button. Keep the expected event in view: a DSP click-out is different from a page view or an ad tap.

CheckExpected result
Account setupThe Meta Pixel / CAPI integration has a Pixel ID and Access Token; Test Event Code is optional.
Connection testSend Test Events reaches Meta with VLVTNClick and Lead.
Link assignmentThe editor Settings tab names the connected pixel instead of showing None.
Live actionA visitor clicks a streaming-platform row and the event represents that click-out.
DeduplicationThe browser and server copies share one event id, so Meta treats the action as one conversion.

If the account test fails, fix the integration before checking the link. If the account test passes but the live button does not, check the link assignment and published page. If both copies arrive but the count doubles, check the shared event id. This keeps a wiring diagnosis separate from campaign performance.

What should you check when the numbers look wrong?

Start with the account test, then the link assignment, then the live button. This order tells you whether the issue is the integration, the link, or the action you are trying to measure.

SymptomFirst check
Test events do not arriveConfirm the Pro plan, Pixel ID, Access Token, and optional Test Event Code in the Meta integration.
The test passes but a link is quietOpen the link editor's Settings tab and confirm the connected pixel is selected instead of None. Test a published page.
The event is the wrong actionSeparate VLVTNClick for a DSP button click-out from Lead for an email signup. A page view is a different action.
One click appears twiceCheck that the browser and server copies represent the same action and carry the shared event id before changing campaign settings.

Know which event you are reading

VLVTN sends two fixed event names through the Meta integration. A DSP button click-out sends VLVTNClick. An email signup captured by a smart link sends Lead. These events describe different actions, so keep the one that answers your campaign question separate from the other.

Note
VLVTNClick is a tracked click-out to a destination. It is not a guaranteed stream, play, save, or follow.

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.

What do I need to connect a Meta integration?

The form requires a Pixel ID and Access Token. A Test Event Code is optional. After you save, the integration has a Send Test Events action, and creating the integration sends VLVTNClick and Lead test events automatically.

What do VLVTNClick and Lead mean?

VLVTNClick is the event for a DSP button click-out. Lead is the event for an email signup captured by a smart link. The event names are fixed in VLVTN.

What does a failed tracking check tell me?

A failed connection test points to the account integration. A missing event on one link points to its Meta Pixel assignment or the live page action. Two copies of one click indicate a deduplication problem. Test the checks in that order before changing campaign settings.