Skip to content

Track Affiliate Leads in FormAssembly

FormAssembly captures what a visitor types, but it does not know which affiliate sent them. This guide shows how to attach affiliate identity to each submission using UTM-tagged links and hidden fields, then route that data to a CRM or spreadsheet for reporting.

What you are building

You are creating a chain: an affiliate link carries UTM parameters, a script stores those parameters in the visitor's browser, and FormAssembly receives them through hidden fields at submit time. The result is a submission record that includes both the lead's manual answers and the affiliate source. The same record can then be sent to a CRM, exported to a spreadsheet, or included in email notifications.

Step 1: Tag affiliate links with UTM parameters

Give each affiliate a link that identifies the channel, the affiliate type, and the individual affiliate. A simple convention keeps reporting readable: set utm_medium to affiliates, utm_source to the affiliate type (for example bloggers, podcasters, or youtubers), and utm_campaign to the affiliate's name. The captured example uses a destination path plus utm_medium=affiliates, utm_source=bloggers, and utm_campaign=john-smith. Affiliate platforms such as Trackdesk and Rewardful can generate tagged links, or you can build them manually with a UTM builder.

Step 2: Add the hidden fields to your FormAssembly form

Create hidden fields on the form that will receive the attribution values. The captured setup uses six fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. FormAssembly supports adding hidden fields directly; the exact click path is documented in the platform's help material.

Step 3: Let the attribution script fill the fields

Picture the most common leak: a visitor clicks an affiliate's tagged link on Monday, reads a few pages, and only submits a form on Thursday. Without persistence, that submission looks direct. The attribution script closes this gap by reading the UTM values at arrival and keeping them in the browser, so the Monday click still counts on Thursday. When the form is finally submitted, those stored values are written into the hidden fields rather than being lost between sessions.

Step 4: Confirm FormAssembly captures the values

After submission, open the Responses section of the FormAssembly account. Each response should show the hidden-field values next to the lead's typed answers, such as name and email address. If the fields are blank, check the failure distinction below before changing the form.

Field and control map

Use this map to decide what each hidden field is for and where it should land downstream.

Failure distinction: why affiliate data may be missing

There are three separate failure points, and they need different fixes. First, the affiliate link may have no UTM parameters, so there is nothing to store. Second, the form may lack one or more hidden fields, so the script has nowhere to write the values. Third, the hidden field may exist but not be populated at submit time, which points to the script or field-name connection rather than the link. Check the Responses section after a test submission to identify which layer failed.

Where the data can go

The captured workflow lists four destinations. You can read the values directly in FormAssembly's Responses section. You can send them to a CRM such as Salesforce, HubSpot, or Pipedrive to report leads, customers, and revenue by affiliate. You can export to a spreadsheet through the FormAssembly Google Sheets Connector or a tool like Zapier, then chart the data in Looker Studio or Microsoft Power BI. You can also add the affiliate information to lead-notification emails when no CRM is in use.

Example: from tagged link to report row

Suppose an affiliate named John Smith, a blogger, shares a tagged link to your FormAssembly integration page. The link carries utm_medium=affiliates, utm_source=bloggers, and utm_campaign=john-smith. A visitor clicks it, browses your site, and later submits a demo request form. The hidden fields receive the affiliate values, and the submission record shows the lead's name and email alongside the affiliate source. In a CRM report grouped by affiliate, that row can be counted as a lead from John Smith and from the blogger affiliate type.

Reporting ideas

Three report shapes follow naturally from the captured data. A leads-by-channel report compares affiliates with paid search, paid social, organic social, and organic search. A customers-by-affiliate-type report groups new customers by blogger, podcaster, or other affiliate category. A revenue-by-affiliate report ranks individual affiliates by customers and revenue. The first report helps with budget allocation across channels; the second and third help decide which affiliate types and individuals deserve more attention.

Setup checklist

Before relying on the data, confirm each item: every affiliate link carries the agreed UTM parameters; the form contains all six hidden fields with matching names; a test submission from a tagged link shows values in the Responses section; the CRM or spreadsheet receives the same values; and at least one report groups submissions by affiliate. If a test fails, use the failure distinction above rather than adding duplicate fields. Note on commercial terms: any trial length, pricing, or setup-time details you see alongside this workflow are owner-supplied and must be confirmed with the tool owner before you rely on them; this guide does not verify them.

Hidden field and downstream use
Hidden fieldWhat it carriesTypical downstream use
ChannelTop-level source category, such as affiliatesGroup leads by channel
Channel Drilldown 1First breakdown, such as affiliate typeCompare blogger, podcaster, and other types
Channel Drilldown 2Second breakdown, such as individual affiliateRank affiliates by lead volume
Channel Drilldown 3Further breakdown where neededSegment campaigns or sub-affiliates
Landing PageURL of the page where the visitor arrivedSee which content attracts affiliate leads
Landing Page GroupGrouped path, such as /blogRoll up performance by content section

Field names and grouping behavior reflect the captured setup; confirm current FormAssembly field behavior in the platform documentation.

Frequently asked questions

Does FormAssembly track affiliates without extra setup?

No. FormAssembly captures the fields present on the form. Affiliate identity must arrive through tagged links and hidden fields, or through a similar attribution mechanism, before it can appear in a submission.

What happens if a visitor leaves and comes back before submitting?

The captured workflow stores UTM parameters in the browser, so the original affiliate values remain available when the visitor returns and submits the form later.

Can I use the affiliate data without a CRM?

Yes. The values appear in FormAssembly's Responses section, can be exported to a spreadsheet through the Google Sheets Connector or Zapier, and can be included in lead-notification emails.

Which UTM values should I standardize?

Use a consistent medium for affiliates, a source that describes the affiliate type, and a campaign that identifies the individual affiliate. Consistency matters more than the specific words because reports group by these values.