ioZen Marketing Attribution: UTM and ad tracking
Attribution tells you which campaigns bring paying customers, not just clicks.
You’re spending money to get people to your website. When someone submits an Intake Bot, whether it’s embedded on a landing page or used to replace your contact form, you want to know what brought them there.
ioZen captures attribution data automatically from embedded Intake Bots, so you can connect submissions to campaigns and send conversion events to ad platforms.
What gets captured
Section titled “What gets captured”Every Intake Bot submission records where the visitor came from:
| Field | Source | What it tells you |
|---|---|---|
| utm_source | URL parameter | Traffic source (facebook, google, newsletter) |
| utm_medium | URL parameter | Channel (paid, organic, email) |
| utm_campaign | URL parameter | Campaign name |
| fbclid, gclid, ttclid | URL parameter | Platform click IDs |
| sessionId | Cookie | Unique visitor session |
| touchCount | localStorage | How many visits before converting |
| embedType | Loader | How the bot was embedded |
| geoCountry, geoCity | IP headers | Visitor location |
| landingPage | Captured | First page they visited |
| firstTouchUtm | Captured | First campaign that brought them |
This happens automatically. You don’t need to configure anything for basic attribution.
First-touch vs last-touch
Section titled “First-touch vs last-touch”ioZen tracks both:
- First touch: The campaign that originally brought someone to your site (stored as
firstTouchUtm) - Last touch: The campaign that was active when they actually submitted
- Touch count: How many visits before converting
This lets you answer questions like “What campaign introduced them to us?” and “What campaign finally got them to convert?”
Embed types
Section titled “Embed types”How you embed the Intake Bot affects what attribution data is available:
| Embed type | Description | Best for |
|---|---|---|
| Direct link | Standalone page at app.iozen.ai | Email campaigns, social posts, QR codes |
| Inline | Embedded in your page | Landing pages |
| Popup | Modal triggered by a button | CTAs, exit intent |
| Widget | Floating corner button | Persistent availability |
Inline, popup, and widget embeds capture the most attribution data because they run on your domain and can access UTM parameters from the page URL. Learn more about embed options and other capabilities on our features page.
Ad platform integrations
Section titled “Ad platform integrations”Send conversion events back to ad platforms so their algorithms can optimize for your actual results, not just clicks.
| Platform | What you need | Plan |
|---|---|---|
| Meta (Facebook/Instagram) | Pixel ID, Access Token | Business and Enterprise |
| Google Ads | Measurement ID, API Secret | Business and Enterprise |
| Conversion URN, Access Token | Business and Enterprise | |
| TikTok | Pixel ID, Access Token | Business and Enterprise |
| Webhook | Any URL | Pro and above |
Setting up an integration
Section titled “Setting up an integration”- Go to FlowApp Settings → Integrations
- Select your ad platform
- Enter your credentials
- Choose which events to send (submission started, submission completed, etc.)
- Use Test mode to validate before going live
Send a test event where the platform has a test flag. LinkedIn has no test mode. Check the setup before you spend ad budget.
Conversion blocks
Section titled “Conversion blocks”A conversion block sits in the flow and records one outcome when the visitor passes it. It can also wait until earlier answers match. Turn on Record this conversion when in the block panel. The flow shows a branch mark when a condition is set.
Outcomes:
- lead
- qualified lead
- schedule
- initiate checkout
- purchase
- custom
Qualified lead reaches Meta and TikTok as the custom event QualifiedLead. Custom sends the name you type. You can include spaces in that name.
Order, rating, and review stay on Process Board phases. The picker lists only the platforms you have connected, and the exact event, conversion action, or webhook name each one receives.
Conversion blocks are on Business and Enterprise.
Ad networks
Section titled “Ad networks”Save Meta, Google, TikTok, LinkedIn, and webhook credentials once per workspace. One encrypted connection per network. Intake Bots and Process Boards opt in. A bot that does not link keeps sending from its own credentials.
You can copy a bot token into the workspace connection, then delete the bot secret.
Ad networks are on Business and Enterprise.
Pre-filling from URLs
Section titled “Pre-filling from URLs”Pass parameters in your Intake Bot URL to pre-fill fields or add tracking data:
https://app.iozen.ai/f/[id]?name=John&email=john@example.com&utm_source=google&utm_campaign=spring-2026All UTM parameters in the URL are captured automatically. Custom parameters can be mapped to fields.
Viewing attribution data
Section titled “Viewing attribution data”Attribution data appears in several places:
- Submission detail: See exactly where each submission came from
- Contact history: Track all touchpoints for a person across FlowApps
- Reports: Filter submissions by source, medium, campaign, or embed type
Next steps
Section titled “Next steps”- Ad Platform Integrations: Send conversion events to Meta, Google, LinkedIn, and TikTok
- Integration setup guides for step-by-step setup of Meta, Google, LinkedIn, TikTok, and custom webhooks
- API Documentation for embed codes, webhooks, and programmatic access
- Intake Bots for setting up what gets collected