Conversion Dashboard & Monitoring

Manage and monitor all conversion activities from a centralized dashboard. This page helps you verify that tracking is running smoothly and fix synchronization issues with ad platforms.

Dashboard Overview

The Tracking & Ads > Conversions menu opens the settings and the delivery log. To open this dashboard, press Ctrl K (⌘ K on Mac), type Conversion, then select the result. Here you can view the health of your tracking pipeline in real-time.

Status Filter

Use the status filter (Sent, Pending, Failed) above the table:

1. Pending: Events that are queued or still sending.
2. Sent: Events that already reached the platform. In the Delivery log, the status is Sent.
3. Failed: Events that failed to send. Events that were intentionally not sent show Skipped in the Delivery log.

Monitoring Events

Use the All Events filter above the table to see a complete list of conversions that have occurred.

Understanding the Table Columns

• Customer: Lead identity (Name, Email, Phone) and Unique Code.
• Event: Name of the event that occurred (see full list below).
• Value: Monetary value of the conversion.
• Platform Status: Status indicator for sending to each platform.

Supported Meta Standard Events

Konektor supports all Meta Pixel Standard Events:

Status Indicators

Each platform (Meta, Google, TikTok, ChatGPT Ads, LinkedIn) has a colored indicator:

• ● Green: Sent (Successfully sent)
• ● Yellow: Pending/Sending (In process)
• ● Red: Failed (Failed, check logs)

For the delivery route to LinkedIn, from the ad click to the Sent status, read LinkedIn ads tracking software.

Troubleshooting & Delivery log

One event per lead

Ad platforms count every event that reaches them. Konektor therefore sends each built-in event once per lead. When a later status change would repeat an event, its row shows Skipped.

• A purchase (Purchase) is also sent once per lead. A later won status does not send it again.
• For a lead from chat, Meta receives one LeadSubmitted, one QualifiedLead, and one Purchase.
• An event that you set yourself for a status is sent every time.

Meta delivery badges

The delivery badge appears in the Platform column. The badge identifies the path, not the acceptance result:

• Meta CTWA: Konektor tried the dedicated CTWA path to the WABA dataset.
• CTWA backup: Konektor tried the backup route through Meta CAPI because the CTWA route was not ready. Meta may not link it to the ad.
• Meta CAPI: Konektor tried a regular Meta event that was not a dedicated CTWA delivery.

Check the status column separately. A Meta CTWA row with Sent status proves that Meta received the dedicated event. The badge without Sent status is not acceptance proof. Acceptance does not prove that Ads Manager reported or attributed the conversion. The three separate proofs are explained in WhatsApp CAPI software.

The Resend as Meta CTWA action can appear only after the CTWA connection is ready:

• A CTWA backup row with Sent or Failed status can be eligible.
• A Meta CTWA row with a final Failed status can be eligible.
• A row with Queued status is not eligible.
• A Meta CTWA row with Sent status blocks a duplicate dedicated resend for the same event and dataset.
• A regular Meta CAPI row does not offer CTWA resend.

If you see a red indicator (Failed) or suspect missing data, use the Delivery log tab.

This tab provides technical details for each sending attempt:

1. Open "Delivery log" Tab: Open Tracking & Ads > Conversions, then click the Delivery log tab next to Mapping.
2. Find Errors: Look at the "Status" column, then click the row to see the reason and Automatic attempts. The Meta is not connected banner means Meta is not added in Website Tracking. Click Add Meta.
3. Resend Event: If the error is temporary (timeout or server busy), click the row, then click Resend to try sending again.

Manual Conversion Triggering

Sometimes you need to trigger a conversion manually, for example for offline orders or data correction.

1. Go to the Leads menu.
2. Select the Lead you want to convert.
3. Change the status of the lead to Purchase.
4. Enter the Closing value, then click Save closing.

The new conversion status will automatically appear on the Conversions dashboard and start processing to connected ad platforms.

Trigger via API

You can also trigger conversions programmatically (e.g., from external CRM or POS systems) by updating lead status and value using their Phone Number.

Please refer to the full guide in API Reference: Offline Conversions.

Next Steps

• Set up Meta CTWA with Meta login
• Setup Event Mapping
• Connect Ad Platforms
• How to choose ad tracking software
• API Reference for Custom Events