Home/Docs/Connectors/Meta Conversions API
Connect Meta Conversions API to ViralDM
Send leads, bookings and sales from your DMs, bio page and store to your own Meta Pixel, so your ads optimise on real results.
- Direction
- ViralDM → app
- Data flow
- ViralDM → Meta Conversions API
- How to connect
- Paste your Pixel ID and a token
- Updated
- 18 October 2026
How it works
The Conversions API (CAPI) sends conversions from ViralDM's server straight to your Meta Pixel — it works even when a browser blocks tracking.
Leads (lead.captured, bio.lead, form.submitted) go as Lead. Bookings go as Schedule. Store orders and DM payments go as Purchase, with the amount in INR.
Email, phone and name are hashed (scrambled one way) before they leave ViralDM. An event with no email, phone or username is skipped, because Meta could not match it to anyone.
If your Meta Pixel ID is also set on your bio page, the browser and the server send the same event id, so Meta counts each sale once.
What goes across
- Lead, Schedule and Purchase events to your own Pixel (dataset).
Where to find it
Where to find each value
No Meta app review is involved: it is your own Pixel and your own token, from Meta Events Manager.
Pixel (dataset) ID
- Open Meta Events Manager (business.facebook.com/events_manager).
- Under Data sources, pick your Pixel (also called a dataset).
- Open Settings. Copy the Pixel ID / Dataset ID — digits only.
Conversions API access token
- On the same Settings page, scroll to Conversions API.
- Press the Generate access token link (it sits under "Set up manually" or "Set up direct integration", depending on your screen). Only people with developer access to the business see it.
- Copy the token. Meta shows it once; keep it private.
Test event code (optional)
- In Events Manager open your Pixel → Test events.
- In the server events part (Conversions API), copy the test code shown there. It starts with TEST, for example TEST12345.
Only the Test button uses it. Real events never carry it.
After connecting
Check it works
- Press 🧪 Test on the connector in ViralDM. It sends one test event, so you can see it arrive before a real lead does.
- On the Connectors page, open the connector: it shows how many events were sent, when the last one went, how many failed, and the reason for the last failure.
"Add a Test Event Code … to send a test event".
The Test button needs the test code so the test event shows under Test events and not in your real numbers. Paste it in the third box.
Test fails with "answered HTTP 400".
The Pixel ID or the token is wrong, or the token belongs to a different Pixel. Generate a new token from the same Pixel's Settings.
I see fewer events in Meta than leads in ViralDM.
Leads with only an Instagram username and no email or phone may not be matched by Meta. Leads with an email or phone match best.
Do I need the browser Pixel too?
It helps. Set your Pixel ID on the bio page as well — see the Meta Pixel guide. The two are de-duplicated.
Works well with
Related guides
Put your own Meta Pixel on your bio page, store, e-books and booking page to retarget visitors and measure sales.
Read the guide → Calendly
Calls booked on your Calendly reach your Slack, Sheets, CRM and Telegram just like a ViralDM booking.
Read the guide → Google Sheets
Every new lead, booking and sale from ViralDM becomes a new row in a Google Sheet — automatically.
Read the guide →Connect Meta Conversions API now
Connectors are included on every ViralDM plan, including Free.