add_dashboard_report
ChatGPTAdd a report card to a dashboard. Same arguments as run_report, plus a report_name and chart_type — run it first and confirm the rows, because a card built on an unknown metric or dimension saves happily and then renders empty. Prefer time_period (a relative window such as "lastMonth") over fixed date_from/date_to: the card re-resolves a relative window every time somebody opens the dashboard, where fixed dates freeze it on the day it was made.
build_utm_link
ChatGPTBuild a LeadJourney tracking link (the UTM Builder, as a tool). Give it a channel and, for anything but a paid ad platform, a destination URL and what the placement is. Call list_utm_channels first for the channel ids and their kind. For a PAID channel the template is static — it is pasted into the ad platform's own tracking field and the platform fills the macros in at click time, so no destination URL is needed. To shorten the result onto one of the workspace's tracking domains, pass the built URL to create_short_link.
create_agent
ChatGPTCreate an AI agent workflow: pull a report, have a model write it up, and send it somewhere — on a schedule or on demand. Call describe_agent_config first. The config keys differ per step and are not guessable, and an unrecognised one is dropped in silence: the agent saves, opens looking correct, and does nothing. A new agent is a draft unless you set status: "active", and a draft never fires on its schedule. Try it once with run_agent before activating it.
create_app_trigger
ChatGPTCreate a trigger on a connected app: when trigger_type happens in the app, LeadJourney records a conversion_type conversion for the lead, built from mappings. Order: describe_app_triggers → preview_app_records (when available) → this. Map at least email or phone, plus revenue for paid/won events. When the app carries a click id, click_id is mapped to its canonical path automatically if you leave it out; read notes in the result and pass any click-id setup step on to the user. The trigger goes live immediately (the app's webhook is registered or refreshed as part of saving). Say what you are about to create and get a yes before calling.
create_custom_traffic_channel
ChatGPTCreate a custom traffic channel in the current workspace, for a source LeadJourney has no built-in channel for — a podcast, a partner, a print campaign. The channel KEY is derived from the label (snake_case) and is what UTM links and report filters use, so pick the label carefully: renaming later changes the key and links already in the wild keep pointing at the old one. Build the tracking link for it with build_utm_link. A channel can be detected two ways. Normally by the lj_channel param on the link. When the link cannot be tagged — a partner's listing page, a directory, a press article — pass referrer_domains instead and clicks referred by those domains are credited to this channel rather than counting as plain Referral.
create_dashboard
ChatGPTCreate an empty dashboard in the current workspace. It appears immediately, with no cards on it — add those with add_dashboard_report, which is where the actual reporting happens.
create_short_link
ChatGPTShorten a tracking URL onto one of the workspace's verified tracking domains, so a long parameter string can be pasted into a bio or a post. The result is https://{domain}/s/{slug}. Only a domain whose status is success can be used — call list_tracking_domains first. The destination URL should already carry its tracking parameters; build it with build_utm_link.
create_tag
ChatGPTCreate a tag, optionally with rules that apply it to leads automatically. Call describe_tag_rules first — the field, operator and value ids are not guessable, and a rule built on an unknown one saves and then matches nothing. apply_to_existing runs the rules over leads already in the workspace, in the background. Without it the tag only applies to leads that arrive from now on.
create_tracking_domain
ChatGPTAdd a tracking domain to the workspace. Use a SUBDOMAIN of the customer's own site, e.g. t.example.com — a first-party host is far less likely to be blocked than a shared one. Adding it here is only half the job: the customer must then create a CNAME record for that host pointing at package.leadjourney.io. Until that record propagates the domain sits in initialize and nothing on it resolves.
delete_agent
ChatGPTDelete an AI agent workflow, its steps, its destinations and its run history. To stop an agent without losing it, set its status to paused or archived with update_agent instead — that is usually what someone means by "turn it off". Pass confirm: true to delete.
delete_app_outbound
ChatGPTDelete a send-back rule. LeadJourney stops sending that event to the app; records already written there stay. The first call without confirm: true deletes nothing and explains what would stop — put that to the user and only call again with confirm: true once they agree.
delete_app_trigger
ChatGPTDelete one app trigger. Events of that type stop becoming conversions; conversions already recorded stay. The first call without confirm: true deletes nothing and explains what would stop — put that to the user and only call again with confirm: true once they agree.
delete_custom_traffic_channel
ChatGPTDelete a custom traffic channel. Built-in channels cannot be deleted — switch them off with update_custom_traffic_channel instead. Historic traffic already attributed to the channel stays in reports; the channel simply stops being offered. Links still carrying its key will no longer be classified, so retire the links first. Pass confirm: true to carry it out.
delete_dashboard
ChatGPTDelete a dashboard and every report card on it. There is no undo, and the cards are not recoverable — confirm with the user first, and pass confirm: true to carry it out.
delete_tag
ChatGPTDelete a tag, its rules, and the tag from every lead carrying it. Reports and saved filters that segment on the tag lose that segment. Pass confirm: true to carry it out.
delete_tracking_domain
ChatGPTDelete a tracking domain. Every tracking link and short link already published on that host stops resolving the moment it goes — including ones printed on material nobody can recall. Pass confirm: true to carry it out.
describe_ad_creation
ChatGPTBefore request_ad_creation: the fields a new campaign, ad set and ad take on this platform (required ones, allowed values, text limits, defaults), and the account's own building blocks to refer to by id — Meta Pages, pixels and images; Google conversion actions. Read-only.
describe_agent_config
ChatGPTDescribe how an AI agent workflow is put together: the report sources it can pull, the date ranges, the report formats, the destinations it can send to, and the schedule options. Call this before create_agent — the keys are not guessable, and an unrecognised one is dropped without an error. An agent is three steps in a fixed order: GET DATA (which report, over which dates) → GENERATE REPORT (a prompt, and the format) → DELIVER (email, Slack or webhook). The schedule decides when it runs.
describe_app_outbound
ChatGPTEverything needed to send LeadJourney data back to an app — e.g. push every new lead into HubSpot as a contact with its UTM source, or every won conversion into a Salesforce opportunity. This is the opposite direction of triggers. Returns the catalog (events LeadJourney can send with their source_fields, the app's objects, and the write modes each object supports), this workspace's conversion_types, the existing_rules, and app notes (for HubSpot: writing may need a reconnect). Pass object to also get writable_fields — the app fields that object can be written to. Call it before create_app_outbound, and again with object once you know what to write.
describe_app_triggers
ChatGPTEverything needed to build a trigger for one app without guessing. A trigger turns an event in the app (a booked meeting, a won deal, a paid invoice) into a LeadJourney conversion. Returns: - trigger_types — the only accepted values for trigger_type, with what each one fires on. - conversion_types — this workspace's conversion types; conversion_type must be one of them, exactly. - recommended_triggers — which trigger type fits a lead, a booked call, a sale. - default_fields, target_fields, preferred_paths, known_paths — which LeadJourney fields to map and the app paths that usually hold them. - click_id — how the click id reaches this app and which path carries it. Mapping it is what ties the conversion to the ad click. - extra_fields — app-specific options passed in options. Call this before create_app_trigger, every time.
describe_live_ad_data
ChatGPTWhat can be read live from one ad platform, and which of its accounts this workspace has connected. Call this before get_live_ad_report or get_live_ad_entities: metric, breakdown and field names are the platform's own and differ per platform, and an invented one fails. Live reads ask the platform at this moment, with every metric and setting it exposes — unlike get_campaign_report, which is LeadJourney's synced data joined with CRM revenue. Use the live tools for platform-side detail (search terms, impression share, frequency, quality ranking, targeting, bidding settings) and the LeadJourney reports for real leads and revenue; the best answers combine both.
describe_report_builder
ChatGPTList every metric, dimension, filter field and attribution setting the report builder accepts, for the current workspace. Call this BEFORE run_report or add_dashboard_report — the ids are not guessable, and an unknown one produces an empty report rather than an error.
describe_tag_rules
ChatGPTList every field, operator and value a tag rule can be built from in this workspace: rule fields, comparison operators, tag types, the integrations leads arrive from, the workspace's traffic channels and its conversion types. Call this before create_tag. A rule referencing a field or value that does not exist saves without complaint and then never matches a single lead.
detect_website_stack
ChatGPTLook at a website and work out which CMS it runs on and which form builder its forms use — the two things that decide how the tracking script and form capture get installed. Use it before walking someone through setup, so the instructions match what they actually have rather than a generic version.
disconnect_app
ChatGPTDisconnect an app from this workspace: its webhook is removed, its triggers go with it, and no more events arrive until the user reconnects in Settings → Apps (connecting again cannot be done from here). The first call without confirm: true disconnects nothing and explains what would be lost — put that to the user and only call again with confirm: true once they agree.
get_ad_creative_report
ChatGPTRetrieve ad creative performance data for the user's current workspace. Use this tool to analyze which ads, images, videos, and creative assets are performing best. Returns metrics like impressions, clicks, conversions, spend, revenue, ROAS, and cost per conversion for each creative. Supports filtering by date range, traffic channel (Facebook, Google, etc.), creative type, and attribution method (first_click or last_click). Call switch_workspace first if the user wants results for a different workspace.
get_ad_platform_recommendations
ChatGPTThe ad platform's own optimisation advice for a connected account: Google's recommendations with their estimated impact plus the account and campaign optimization scores; Meta's opportunity recommendations. Read-only — nothing is applied. Treat these as the platform's suggestions, not LeadJourney's: a platform optimises for the conversions it can see, so check a "raise budget" or "broaden match" suggestion against real leads and revenue in get_campaign_report before passing it on. describe_live_ad_data says whether a platform has recommendations at all.
get_ad_platform_setup
ChatGPTOne ad platform's whole setup as a checklist: connect → pick ad account → pixel (Meta, X) → choose which events are sent → map each event to the platform's event name. Each step says whether it is done, whether the user or Atlas does it, and a where link to that exact screen. Also returns the connected ad accounts (ids, names, pixel — never a token), every workspace event with its send_to_ads switch and its current name on this platform, and the platform's standard_events. Use it before update_ad_event_mapping, and to walk a user through what is still missing.
get_agent
ChatGPTRead one AI agent workflow back in full: every step and its config, the destinations, the schedule, and the last runs with their status and any error. Start here when an agent is not producing what was expected — the run log says which step stopped.
get_app_field_options
ChatGPTRead a CRM's real fields and values for trigger conditions ("only when <field> is <value>"): without field, the fields of object that can be a condition; with field, the values it can take — pipeline stage ids, lead statuses, picklist entries. Use the value (not the label) in create_app_trigger options, e.g. {"attribute_name": "stage_id", "attribute_value": "12"} or {"property_name": "dealstage", "property_value": "contractsent"}. Never guess a stage or status id.
get_app_outbound_deliveries
ChatGPTThe log of what LeadJourney sent to an app, newest first: each push's event, object, status (success / failed / skipped), HTTP status and error. Use it when the user asks whether leads are reaching their CRM, or why one did not.
get_app_status
ChatGPTShow one app's connection in this workspace: whether it is connected, which account it is connected to, a live health check against the provider (token revoked, webhook missing, unreachable), and every trigger with its id, trigger type, conversion type, field mappings and active flag. Use the trigger ids from here with update_app_trigger and delete_app_trigger. When health.healthy is false, tell the user the reason and that reconnecting in Settings → Apps fixes a revoked connection.
get_campaign_report
ChatGPTRetrieve campaign performance data for the user's current workspace. Use this tool to analyze marketing campaign metrics including clicks, conversions, revenue, spend, ROAS, cost per lead, and cost per conversion. Supports filtering by date range, traffic channel (Facebook, Google, TikTok, etc.), conversion type, and attribution method (first_click or last_click). Call switch_workspace first if the user wants results for a different workspace.
get_crm_webhook_info
ChatGPTGet everything a CRM needs to send conversions back to this workspace: the postback URL, how to authenticate, and which parameters the payload takes. The response includes the workspace's postback SECRET. Treat it as a credential — it belongs in the CRM's webhook settings, not in a chat log, a ticket or an email.
get_current_workspace
ChatGPTGet the authenticated user's identity (email) and currently selected workspace. Call this first whenever the user asks about "my" data so you know the active context.
get_lead_journey
ChatGPTFetch a single lead's full journey (events, tags, emails, phones) by lead_id. Same payload as the lead-overview modal.
get_leads
ChatGPTRetrieve leads and their conversion data from the user's current workspace. Use this tool to analyze lead performance, track conversions, and understand customer journey. Supports filtering by date range, traffic channel, conversion type, campaign, ad set, asset, keyword, ad, and attribution method (first_click or last_click). Call switch_workspace first if the user wants results for a different workspace.
get_live_ad_entities
ChatGPTThe account, campaigns, ad sets, ads or keywords exactly as the ad platform holds them right now — status, budgets, bidding strategy, targeting, networks, schedule, tracking templates, approval status. Read-only. Use this to audit settings ("which campaigns still run on the Display Network", "which ad sets have no frequency cap", "is auto-tagging on") before recommending a change. fields takes the platform's own field names; leave it empty for the defaults describe_live_ad_data lists. Without ids every live (not removed) entity at the level is returned, up to limit.
get_live_ad_report
ChatGPTPerformance straight from the ad platform's reporting API, right now: any metric and breakdown the platform offers, at account, campaign, ad set, ad or keyword level. Read-only — nothing on the ad account changes. Call describe_live_ad_data first for the platform's metric and breakdown names. Pass date in breakdowns for one row per day; leave it out for totals over the range. Conversions here are what the platform itself counts; for leads and revenue from the CRM use get_campaign_report or run_report, and compare the two.
get_my_profile
ChatGPTReturns the authenticated user's profile (id, name, email).
get_onboarding_status
ChatGPTShow where the workspace has got to in onboarding — the checklist, the current step, the detected website stack — together with the live state of the pieces that actually have to work: tracking domains and their verification, whether any conversion events are defined, and whether leads have started arriving. Start here when someone says setup is not working. The checklist can read as finished while a domain is still unverified, and that is the usual cause.
get_traffic_channel_report
ChatGPTRetrieve traffic channel performance data for the user's current workspace. Use this tool to compare performance across different advertising platforms (Facebook Ads, Google Ads, TikTok Ads, etc.). Returns aggregated metrics like total clicks, conversions, revenue, spend, ROAS, and cost per acquisition for each traffic source. Supports filtering by date range and attribution method (first_click or last_click). Ideal for understanding which channels drive the best results and where to allocate budget. Call switch_workspace first if the user wants results for a different workspace.
google_ads_field_metadata
ChatGPTWhich fields a Google Ads resource has, and which metrics and segments can be selected with it — so a google_ads_search query is right the first time. Pass resource (e.g. "campaign", "search_term_view", "keyword_view") to get its attribute fields plus the metrics and segments it accepts; pass field (e.g. "metrics.search_impression_share") to get one field's type, enum values and where it can be used.
list_ad_changes
ChatGPTThe ad changes asked for in this workspace — pending ones waiting for confirmation, and the log of applied, failed, cancelled and expired ones with before and after values — plus what the current user may ask for (per platform and action) and the workspace's money limits. Use it to answer "did my change go through", to avoid asking for a change that is already pending, and to check permissions before proposing one.
list_ad_platforms
ChatGPTEvery ad platform LeadJourney sends conversions to — Meta, Google, Microsoft (Bing), LinkedIn, Reddit, X, ChatGPT, Taboola, Outbrain, TikTok — with whether it is connected, whether an ad account is picked, whether the connection expired, and the next step. Start here when the user talks about ads, pixels, the Conversions API or offline conversions.
list_agents
ChatGPTList the AI agent workflows in the current workspace: what each one reports on, where it sends the result, its schedule, and when it last ran. Use it to find the agent_id for get_agent, update_agent, run_agent or delete_agent.
list_apps
ChatGPTList every app LeadJourney integrates with (Cal.com, Calendly, HubSpot, Salesforce, Typeform, Stripe, …) and, for each one, whether it is connected in this workspace and how many conversion triggers it has. The app value of each row is the key every other app tool takes. Start here when the user mentions an app, or asks what is connected.
list_dashboards
ChatGPTList the dashboards in the current workspace and the report cards on each. Use it to find the dashboard_id for add_dashboard_report or delete_dashboard, and the report_id for remove_dashboard_report.
list_tags
ChatGPTList the workspace's tags and the rules that apply each one automatically. A tag with no rules is applied by hand only.
list_tracking_domains
ChatGPTList the workspace's tracking domains and where each one has got to in verification. A domain only works once its status is success; anything else means the CNAME has not been seen yet, and links on it will not resolve.
list_traffic_channels
ChatGPTList the traffic channels configured in the current workspace: the built-in ones (Meta Ads, Google Ads, organic search, …) and any custom channels this workspace added. is_custom decides what can be done to a channel — only custom ones can be edited or deleted. traffic_channel_key is the id every report filter and UTM link uses.
list_utm_channels
ChatGPTList every channel the UTM Builder can produce a tracking link for, and which of the five link KINDS each one is. Call this before build_utm_link — the kind decides which arguments that tool needs. - paid: a static template the ad platform fills in at click time. Nothing to configure; it is pasted into the platform's tracking field. - organic: a link you tag by hand before posting. - email: a newsletter or automation link, optionally carrying the recipient's address so the lead is identified. - fixed: a built-in channel with a fixed lj_channel value, tagged by hand (Google My Business). - custom: one of this workspace's own custom traffic channels.
list_workspaces
ChatGPTList every workspace the authenticated user can access, with the current workspace flagged. Use this before any reporting work so the user can confirm which workspace is active or pick a different one with switch_workspace.
plan_app_event_mapping
ChatGPTMap ALL of the workspace's events (Settings → Events — e.g. Lead, BookedDemoCall, OpportunityCreated, ContractSent, ClosedWon, ClosedLost, Unqualified) onto one app, not just sales. Use it whenever the user sets up a CRM or asks to track their funnel. Per event it returns: what the event means (label, description, revenue_stage), which triggers already map it (mapped_by), and for unmapped ones a suggestion — a pipeline stage (kind: stage, with the ready-made options for create_app_trigger), one of the app's triggers (kind: trigger), or kind: ask when only the user can say. It also returns the CRM's live stages and how a "reached stage X" trigger is built (stage_trigger). Then go through the unmapped events with the user, confirm or correct each suggestion, and call create_app_trigger once per event with that event as conversion_type. Never create them without the user's yes.
preview_app_records
ChatGPTFetch the 3 most recent real records for a trigger type from a connected app — the same "Check for data" the dashboard shows — so field mappings use paths that actually exist in this account. suggested_mappings lists, per LeadJourney field, the preferred path that held a value in these records. Use those paths in create_app_trigger. Records hold personal data: summarise them, do not paste them back to the user in full.
remove_dashboard_report
ChatGPTRemove one report card from a dashboard. The dashboard itself and every other card stay. Get both ids from list_dashboards.
request_ad_change
ChatGPTAsk for a change to a live ad account: pause or enable a campaign / ad set / ad / keyword, change a daily budget or a bid, rename, delete, add or remove keywords and negative keywords. This does NOT change anything. It stores the change as pending and returns a confirm_url. The user must open that link in LeadJourney and confirm; high-risk changes (enable, raising a budget or bid, delete, adding or removing keywords) need a second confirmation there. There is no tool to confirm — never claim a change was made. Tell the user plainly what will change and give them the link. Before asking: read the entity with get_live_ad_entities so the id and current numbers are right, and say why in reason. Amounts are in the account currency, major units (150 = 150.00). The workspace's limits (max daily budget, max increase per change, max bid) and the user's own permissions apply — a refusal names the limit; do not retry the same request. Operations: pause, enable, set_daily_budget (amount), set_bid (amount, max CPC), rename (name), delete, add_keywords (level adset, keywords [{text, match_type exact|phrase|broad, bid?}]), remove_keywords (level adset, keyword_ids), add_negative_keywords (level campaign or adset, keywords [{text, match_type}]), remove_negative_keywords (level campaign or adset, keyword_ids). Keywords exist on google_ads and bing_ads only.
request_ad_creation
ChatGPTAsk to make something new in a live ad account: a whole campaign with its ad sets (Google: ad groups) and ads, more ad sets in an existing campaign, or more ads in an existing ad set. Google Ads (search campaigns, keywords, responsive search ads) and Meta Ads. This does NOT create anything. It stores the creation as pending and returns a confirm_url; the user confirms twice in LeadJourney. Everything is then made PAUSED with LeadJourney's tracking on it. Publishing is the user's own last step, in the ad platform itself (the change's publish_url) — LeadJourney never switches on what it made, and asking to enable it is refused. Never say it is live or created before the user confirmed. Call describe_ad_creation first: it lists every field per level, the limits, and the account's own Pages, pixels and images to refer to. Then send ONE request with the whole tree: - level "campaign": campaign {…} and ad_sets [{…, keywords?, ads: [{…}]}] - level "adset": id = the campaign, ad_sets [{…, ads: [{…}]}] - level "ad": id = the ad set, ads [{…}] Money is the account currency, major units. A refusal names the field to fix — fix it and send once more. At most 10 ad sets and 20 ads per request; the workspace's budget and bid limits apply.
run_agent
ChatGPTRun an AI agent workflow immediately, ignoring its schedule. It runs in the background and DELIVERS for real — emails go out, Slack messages post, webhooks fire — so use it to prove a new agent works before activating it, not to preview one. Read the outcome back with get_agent, which shows the run's status and any error.
run_report
ChatGPTRun a custom report against the current workspace and return the rows. Any combination of metrics, one dimension (group_by), an optional second dimension, filters and an attribution setting. Call describe_report_builder first for the valid metric / dimension / filter ids — an id this tool does not know produces empty rows, not an error. To keep a report, pass the same arguments to add_dashboard_report.
scan_website_for_apps
ChatGPTLook at a website and work out which apps it uses — a Cal.com or Calendly booking widget, a HubSpot / Typeform / Jotform form, a Stripe or Shopify checkout, a chat widget — and what to set up in LeadJourney for each. Per detected app it returns the matching embed URLs (e.g. the exact booking link a "Book a call" button opens), whether the app is connected here, its existing triggers, the recommended trigger types, how the click id reaches it, and a next_step. It also reports whether the LeadJourney tracking script is on the page, which is what passes the click id into embeds. Use it when the user gives a website and asks to set up tracking, then follow each next_step: describe_app_triggers → preview_app_records → create_app_trigger.
set_ad_platform_pixel
ChatGPTX Ads and TikTok Ads: without pixel_id, list an ad account's pixels (X Event Sources, TikTok pixel codes); with pixel_id, link that pixel so conversions are sent to it. Confirm the pixel with the user before linking. For Meta this returns the dashboard link instead: Meta's pixel needs a Conversions API access token, a secret the user pastes there — never ask for it in chat.
switch_workspace
ChatGPTSwitch the authenticated user's current workspace. Pass the workspace_id from list_workspaces. After switching, every reporting tool (campaigns, traffic channels, ad creatives, leads) will operate on the new workspace.
update_ad_event_mapping
ChatGPTMap workspace events to an ad platform's conversion events and choose which events are sent to ads. Per event: event_type "standard" with an event_name from standard_events (preferred — the platform optimises on it, e.g. Meta "Lead", "Schedule", "Purchase"), or "custom" with your own name; and/or send_to_ads true/false. send_to_ads is one switch per event for ALL connected platforms. On Google, LinkedIn, Microsoft and X a new name recreates the conversion action/goal on the platform (Google then needs ~6 hours). Show the user the full table of changes and get a yes before calling.
update_agent
ChatGPTChange an AI agent workflow: its name, its data step, its prompt, its destinations, its schedule, or its status (activate, pause, archive). destinations REPLACES every existing destination — send back the ones you are keeping, or they are gone. Call get_agent first and work from what is there. Anything you leave out entirely is left alone.
update_app_outbound
ChatGPTChange a send-back rule. Only what you pass changes: mappings merge into the saved ones field by field (an empty source removes that field) and anything omitted keeps its saved value. Pause a rule with active: false instead of deleting it. Get rule_id from describe_app_outbound (existing_rules) or get_app_status (send_back_rules).
update_app_trigger
ChatGPTChange an existing app trigger. Only what you pass changes: mappings are merged into the saved ones field by field (an empty path removes that field), filters replace the saved set when passed, and anything omitted keeps its saved value. Pause a trigger with active: false instead of deleting it. Get trigger_id from get_app_status.
update_custom_traffic_channel
ChatGPTRename a custom traffic channel, change its description or type, or switch it on and off. Built-in channels can only be switched on and off — their label and type are fixed. Renaming re-derives the channel key. Links already published with the old key keep reporting under it, so rename only when nothing is live yet, or accept the split.
update_tag
ChatGPTChange a tag's name, colour, type or rules. Passing rules REPLACES the whole set — every rule you mean to keep has to be sent back, or it is gone. Call list_tags first and send the existing rules along with the new one. Leave rules out entirely to change only the name or colour.
update_tracking_domain
ChatGPTChange a tracking domain's host, or retry verification on one that failed. Changing the host starts verification again from scratch, and every short link already published on the old host stops resolving — so treat it as creating a new domain, not editing a label. retry: true re-runs verification on a failed domain, which is what to do once the CNAME has actually been added.
verify_tracking_script
ChatGPTFetch a page and check whether this workspace's LeadJourney tracking script is actually on it. The single most useful check when leads are not appearing. It reads the page's server-rendered HTML, so a script injected later by a tag manager or a client-side app can be missed even though it works in a browser. A negative result is a reason to look, not proof it is absent.