Purchase, meeting scheduled, or a named event, written once the first time a lead enters that phase.
Outcomes on a phase. A Process Board phase can record one outcome the first time a lead enters it: purchase, meeting scheduled, or a named custom event, with an optional value and currency. ioZen writes that first-party event once. Moving the same lead into that phase again does not write another. This is not a stored return on ad spend.
Campaign import. A new WhatsApp campaign can import contacts, tag them, and save a phone-ready segment as the audience. Campaigns target a saved segment, filters, or a simple search. Business and Enterprise.
Click-to-WhatsApp, in beta. Threads that start from a Meta Click-to-WhatsApp ad keep the referral and click ID so source analytics can group them. Organic WhatsApp stays unattributed. This stays beta until a live Test Events check is completed.
Also. Each WhatsApp number can publish a tracked link. Configured Google Ads connections send conversions through Data Manager. Draft and published Intake Bots both count toward the plan limit. Archived bots do not, and they cannot be restored while you are at the cap.
A Process Board phase can record one outcome the first time a case enters it: purchase, meeting scheduled, or a named custom event, with optional value and currency. ioZen writes one first-party lifecycle event. Moving the same case into that phase again does not write another. Network sends follow configured platform credentials and do not depend on Intake Bot On Payment or On Meeting Booked flags. If no submission is found, only the first-party event is recorded. Test cards send to Meta Test Events only when a test sink is ready.
New campaign can open the Contact Center import wizard. The imported rows are tagged and saved as a phone-ready segment, then selected as the campaign audience. Campaigns target contacts only: saved segment, filters, or a simple search.
Google Ads conversion delivery now uses Data Manager for configured connections. ioZen sends one click ID plus available hashed customer data, validates setup without ingesting a test conversion, and keeps eligible legacy Ads connections available without duplicate Google delivery.
maxIntakeBots counts draft and published bots. Archived bots stay free and cannot be restored at cap. Duplicate and FlowApp copy respect the same limit as create.
WhatsApp conversations that start from a Meta Click-to-WhatsApp ad now keep the referral and click ID. The Intake Bot submission is stamped so source analytics can group those cases. Organic WhatsApp stays unattributed. Optionally, each number can send server-side Meta business-messaging conversions (LeadSubmitted, Purchase) to the WABA-linked dataset using the raw click ID and an optional Test Events code. Meta attributes those events for 7 days from the click. This is beta until a live Test Events check is completed.
Each WhatsApp number can now publish first-party /l/[slug] links. A click stores UTMs and click IDs, then opens WhatsApp with a short reference marker that is removed before the conversation is stored. A surviving token is a deterministic match and can reach ad networks. A 10-minute unique fallback is a first-party estimate only. Click-to-WhatsApp referrals still take precedence. Phone is not a LinkedIn match key; capture email in the Intake Bot or keep li_fat_id.
