See whether the last 30 days of conversion events reached each ad platform, and why some completed cases produced none.
Intake Bot marketing settings now show whether conversion events from the last 30 days reached each ad platform: accepted, failed, and skipped counts, the most recent rejection reason, and how many completed cases produced no conversion event. Click ID and pixel cookie coverage are in the same panel, so a pixel that stops loading is visible without comparing dashboards by hand.
The TikTok Pixel can load on published Intake Bot pages again. The page policy had been blocking analytics.tiktok.com, so browser-side events never left. Server-side Events API delivery was already fine.
WhatsApp file questions can collect one document per field and run AI Document Extraction. The bot acknowledges the file, pauses while it reads, then sends one summary with Yes and Fix. Confirmed answers are skipped. Unread or corrected child fields are asked one at a time. Model a front and a back as two fields. WhatsApp is Business and Enterprise. Document extraction is Pro and above. Extraction uses plan AI credits. Bot messages use purchased credits.
Intake Bot marketing settings now show whether conversion events from the last 30 days actually reached each ad platform: accepted, failed and skipped counts per platform, the most recent rejection reason, and how many completed cases produced no conversion event at all. It also reports click ID and pixel cookie coverage, so a pixel that stops loading in the browser is visible without comparing dashboards by hand.
The Content Security Policy on Intake Bot pages did not allow analytics.tiktok.com, so the TikTok Pixel's transport script was blocked by the browser. The inline bootstrap still ran and still accepted track calls, which made the block invisible: no page views reached TikTok, the first-party _ttp cookie was never set, and browser-side SubmitForm conversions never sent. Server-side Events API delivery was unaffected. The origin is now allowed, and a test fails the build if any pixel references an origin the policy omits.
Intake Bots on WhatsApp can now collect one document per file question and run AI Document Extraction. The bot acknowledges the file and pauses while it reads, then sends one summary with Yes and Fix options. Yes skips high-confidence extracted child answers. Fix clears those child answers and asks them again while keeping the file and extraction provenance. Low-confidence or failed fields are asked normally, and failed or timed-out extraction skips confirmation. While reading, the bot sends one nudge, then stays silent until resume. Model a front and back document as two fields. Requires Business or Enterprise for WhatsApp and Pro or above for AI Document Extraction. Extraction uses plan AI credits; bot messages use purchased credits.
