Set Up Conversion Tracking on VLVTN
Set up conversion tracking
- Connect a Meta integrationGo to Dashboard, Integrations. In the Meta Pixel / CAPI section, select Add Meta Integration and enter your Pixel ID and Access Token, then Save Integration.
- Send test eventsUse Send Test Events on the connected integration to send two events, VLVTNClick and Lead, so you can confirm the connection in Meta. VLVTN sends these automatically when you first create the integration.
- Pick the pixel on a smart linkOpen a smart link in the editor, go to the Settings tab, and choose your pixel in the Meta Pixel section. None means the link fires no pixel.
- Sync email signups (optional)Connect an email service provider under Dashboard, Settings, then turn on the Email Opt-in toggle on a smart link and choose your ESP so captured emails sync automatically.
In this guide
Each part of conversion tracking has its own walkthrough:
Add your Pixel ID and Access Token, then send test events.
Choose which connected pixel a single smart link fires.
Pixel plus CAPI, deduplicated, and what a conversion really is.
Connect an ESP and pick it on a link to auto-sync captured emails.
Frequently asked
Do I need a Pro plan for conversion tracking?
Yes. The Meta Pixel / CAPI section, email service providers, and custom domains all require a Pro plan. Without Pro you see a Pro badge and a gated message, and the per-link pixel dropdown is fixed to None and disabled.
Where do I set this up?
Account-level Meta setup lives at Dashboard, Integrations, under the Meta Pixel / CAPI section. Email service providers live at Dashboard, Settings, under Email Service Providers. You then pick a pixel or an ESP per smart link on the editor Settings tab.
Does a tracked conversion mean someone streamed my song?
No. 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, or save.
Do I have to turn on the Conversions API separately?
No. Once a Meta integration is connected, the client-side Pixel and the server-side Conversions API are both active. There is no CAPI-only toggle and no separate enable step. The two are deduplicated by a shared event id so the same conversion is not counted twice.