ioZen Docs

Integrations

Connect ioZen to ad platforms for server-side conversion tracking and attribution.

Send conversion events from your Intake Bots directly to ad platforms for accurate attribution — no client-side pixel required.

How It Works

When a visitor completes your Intake Bot (or answers a specific question configured for conversion tracking), ioZen sends a server-side event to every ad platform you've connected. This gives you:

  • Accurate attribution — server-side events aren't blocked by ad blockers
  • Automatic hashing — PII (email, phone, name) is SHA-256 hashed before sending
  • Field-level conversions — trigger events when specific questions are answered, not just on submission
  • Multi-platform — send the same event to Meta, Google, LinkedIn, and TikTok simultaneously

Available Integrations

Setup Overview

Each integration follows the same steps:

  1. Get credentials from the ad platform (Pixel ID, access token, etc.)
  2. Configure in ioZen — go to your Intake Bot → Settings → Marketing
  3. Enable the platform toggle and paste your credentials
  4. Test the connection using the built-in Test Connection button
  5. Configure conversion events — choose when to fire (on submission, on specific questions)

Purchase from a Process Board phase

Send the real sale amount as a Purchase when a case enters your won phase.

  1. On the Process Board, open the board menu → Board settings. Turn on Track amounts, pick the Currency, and save.
  2. On the won phase, open the column menu → Settings → Edit. Turn on Record conversion on enter, set Outcome to Purchase and Value to Case amount, then Save.
  3. Connect the platforms on the Intake Bot the cases come from (Settings → Marketing).

How it sends:

  • One Purchase per case per phase. Moving the case out and back after a send adds nothing.
  • value is the case amount and currency is the board currency, as is. No currency conversion.
  • A case without an amount (empty, 0, or Track amounts off) is not sent. You see a notice on the move. Add the amount, then move the case out and back into the phase.
  • Editing the amount after a send does not update the sent purchase.
  • The event goes through the submission the case came from, or the latest submission with ad attribution from its contact. A case with neither sends nothing to ad platforms.
  • Test cases go only to Meta Test Events, and only when a Test Event Code is set. Other platforms never receive them.

Phase conversions need a plan with marketing attribution. Platform specifics: Meta · Google Ads.

Need Help?

If you run into issues, each integration guide includes a troubleshooting section with common errors and fixes. You can also email us at hello@iozen.ai.

On this page