If you run ads that send people into your DMs, Meta only sees the click. It does not see that the conversation qualified, booked a call, or ended in a sale. The Meta Conversions API sends those outcomes back, so your ad reporting reflects what actually happened.
Once it is connected, Meta can optimize toward the ads that produce customers instead of the ads that produce clicks.
Before you start
You need a dataset in Meta Events Manager with a Conversions API access token, and the Instagram account you use in Cloziq has to be connected to that dataset as a messaging data source. Cloziq sends the events; Events Manager is where the dataset lives.
Connect a dataset
- Open Settings from the sidebar and go to the Integrations tab.
- Find Meta Conversions API in the Third-Party Services section and open it.
- Click Add Connection.
- Paste your Dataset ID and your Access Token. Cloziq checks both with Meta when you save, so a bad token is caught right away instead of failing quietly later.
- Give it a Connection Name if you want one. It is optional, and it helps when you run more than one dataset.
Choose which channels feed it
Under Channels, tick the Instagram accounts whose conversations should send events to this dataset.
Each channel can only feed one dataset. If a channel is already mapped somewhere else, Cloziq tells you which connection has it rather than letting you split the same traffic two ways.
Choose which events to send
Under Events To Send, pick what Meta hears about:
- Qualified Lead when a conversation passes qualification.
- Call Booked when a prospect books a call.
- Purchase when a prospect completes checkout, with the sale amount attached.
Purchase is off by default. Turn it on deliberately, because it is the one that sends money amounts to Meta.
One thing worth being clear about: events are sent only for conversations that started from one of your ads. A prospect who found you organically and bought is a real sale, but it is not an ad conversion, so it is not reported here. Your Earnings page is still the place to see every sale.
Send a test event
Once a connection is saved, open it again with Edit and you will find Send A Test Event.
- Copy the code from the Test Events tab in Meta Events Manager.
- Paste it into Test Event Code. The code is required, so your test lands in Test Events instead of mixing into your live data.
- Click Send Test Event, then check the Test Events tab in Events Manager.
Seeing the event arrive there is the confirmation that the whole path is wired correctly.
Manage a connection
Each connection shows its state at a glance:
- Connected means events are flowing.
- Paused means you stopped it with Pause. Nothing sends until you click Resume. This is the one to use when you want to stop reporting for a while without taking the setup apart.
- Action needed means Meta rejected the credentials, usually an expired or revoked token. Open the connection with Edit and paste a fresh token into New Access Token.
Delete removes the connection and stops sending events for its mapped channels. Your dataset in Events Manager is untouched, so deleting here never costs you data on Meta's side.
Tips
- Set it up once per dataset, not once per campaign. Cloziq maps channels, not ads.
- If your ad reporting looks empty right after connecting, check that the conversations you expect actually started from an ad. That is the single most common reason nothing shows up.
- Running ads but not connected yet? Ad triggers already turn ad engagement into conversations. See Using ad triggers.