Skip to content

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.

Every Intake Bot submission records where the visitor came from:

FieldSourceWhat it tells you
utm_sourceURL parameterTraffic source (facebook, google, newsletter)
utm_mediumURL parameterChannel (paid, organic, email)
utm_campaignURL parameterCampaign name
fbclid, gclid, ttclidURL parameterPlatform click IDs
sessionIdCookieUnique visitor session
touchCountlocalStorageHow many visits before converting
embedTypeLoaderHow the bot was embedded
geoCountry, geoCityIP headersVisitor location
landingPageCapturedFirst page they visited
firstTouchUtmCapturedFirst campaign that brought them

This happens automatically. You don’t need to configure anything for basic attribution.

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?”

How you embed the Intake Bot affects what attribution data is available:

Embed typeDescriptionBest for
Direct linkStandalone page at app.iozen.aiEmail campaigns, social posts, QR codes
InlineEmbedded in your pageLanding pages
PopupModal triggered by a buttonCTAs, exit intent
WidgetFloating corner buttonPersistent 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.

Send conversion events back to ad platforms so their algorithms can optimize for your actual results, not just clicks.

PlatformWhat you needPlan
Meta (Facebook/Instagram)Pixel ID, Access TokenBusiness and Enterprise
Google AdsMeasurement ID, API SecretBusiness and Enterprise
LinkedInConversion URN, Access TokenBusiness and Enterprise
TikTokPixel ID, Access TokenBusiness and Enterprise
WebhookAny URLPro and above
  1. Go to FlowApp Settings → Integrations
  2. Select your ad platform
  3. Enter your credentials
  4. Choose which events to send (submission started, submission completed, etc.)
  5. 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.

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.

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.

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-2026

All UTM parameters in the URL are captured automatically. Custom parameters can be mapped to fields.

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