Converly

View saved version →

---
name: diagnose-missing-conversions
description: Find out why Converly conversions aren't showing up. Use when the user says tracking isn't working, conversions are missing, a form submission didn't appear, or an ad platform isn't receiving conversions.
---

# Diagnose missing conversions in Converly

Work through the funnel in order. Each step rules out one layer, so report what you confirmed at each one.

## Steps

1. **Is anything being captured at all?** Call `get_install_status` for the site. If detection is "never_seen", no data has ever arrived. The most likely cause is that the Converly snippet isn't installed. Give the user the script tag from `get_install_snippet` and stop here until it's in place. If detection is "confirmed", note `last_seen_at` and continue.

2. **Is a flow live?** Call `list_flows`. A flow only tracks while its status is "published". If the relevant flow is a draft, run `validate_flow`, fix any problems, and publish it with `publish_flow`.

3. **Is the destination healthy?** Call `list_destinations`. A destination with `connected` false, or a status like "connection_broken", means deliveries fail even though capture works. Reconnect it with `connect_destination`.

4. **Did the events arrive but fail to deliver?** Call `list_events`, filtering by site, flow, status or the person's email if the user mentioned a specific lead. For anything that looks wrong, call `get_event_detail` and read the per destination delivery result. Report the platform's error plainly.

5. **Nothing wrong anywhere?** Consider quieter causes. The submission may have come from the user's own team (internal traffic rules exclude those, and `add_internal_traffic_rule` can add an exclusion), the form may not be one of the detected form tools (check `list_trigger_types`), or the flow's trigger may be limited to specific pages that don't include the one being tested.

6. **Prove the destination pipe.** `send_test_event` checks the destination-forwarding path only — it does NOT appear in the conversion log, and for any server-side ad destination without a valid sandbox test code (google-ads, chatgpt-ads, linkedin-ads, google-analytics, and meta/reddit/tiktok) it creates a REAL reported conversion, so it's refused unless you set `allow_real_conversion` (confirm with the user first). If the test is accepted but real submissions don't show in `list_events`, the problem is on the capture side (snippet/origin/trigger). If the test itself is rejected, the problem is the destination connection or its configuration.

## Cautions

- Never tell the user to "submit a form and wait" unless step 1 confirmed data has been captured before or the user has confirmed the snippet is installed.
- For Meta, Reddit and TikTok test events, pass the platform's test code so the test doesn't land in real campaign reporting.

Referenced files: 1

View saved version →

---
name: setup-conversion-tracking
description: Set up Converly conversion tracking end to end. Use when the user wants to track form submissions as conversions, send leads to an ad platform like Google Ads, Meta or Google Analytics, or set up Converly for the first time.
---

# Set up conversion tracking with Converly

Tracking only works when THREE things are all true. A flow is published, the destination platform is connected (for server side platforms), and the Converly snippet is installed on the website. Never end this workflow without all three handled or handed to the user.

## Steps

1. **Understand the goal.** Ask which form tool the site uses (Typeform, Webflow forms, Gravity Forms and so on) and which ad platform conversions should go to, unless the user already said.

2. **Check the destination.** Call `list_destinations`. If the target platform isn't connected and it is a server side platform (its entry in `list_destination_types` has a non empty `connection_types`), call `connect_destination`. Share the link it returns, explain the account owner must open it in their browser and authorize, and ask them to tell you when they've finished. Then confirm with `check_handoff_status`. Browser side pixel platforms (empty `connection_types`) need no connection step.

3. **Build the flow.** Call `list_trigger_types` for the trigger id and `list_action_types` for the exact action config the destination needs. Create with `create_flow`, then run `validate_flow` and fix any problems it reports.

4. **Publish.** Call `publish_flow`. Read its result carefully. If `install_status.detection` is "never_seen", the site has never captured data. That usually means the snippet still needs to be installed, but it is not proof (tag managers, consent banners, or a just-published first flow can all delay the signals), so offer the snippet and suggest a real test submission rather than declaring tracking broken.

5. **Get the snippet installed.** Call `get_install_snippet` and give the user the script tag. Tell them to add it to their site's head section, or through their website platform's custom code setting. This step needs the user to act. Do not skip it and do not suggest testing before it is done.

6. **Verify.** Once the user says the snippet is in place, suggest a real form submission, then check `list_events` for the captured conversion and `get_event_detail` for the per destination delivery result. `send_test_event` can fire a test conversion to a connected destination without a form submission.

## Cautions

- If a write is refused for billing, the account has no active trial or subscription. Tell the user to sort out their subscription in Converly, then continue.
- Never guess ids. Sites, flows, destinations and events all come from the list tools with prefixed ids.

Referenced files: 1