Skip to content

How to Track Instagram Ads in Pipedrive

Website analytics can tell you how many people arrived from an Instagram campaign. It cannot tell you, on its own, which of those visitors became a sales-qualified lead or a paying customer. This guide shows how to close that gap: tag the ads, capture the source in your forms, and let the resulting fields travel into Pipedrive so you can report on leads, customers and revenue by campaign.

Why visitor counts are not enough

A traffic report answers a narrow question: how many sessions did this ad produce? A revenue question is different. You need to know which ad clicks turned into form submissions, which submissions became opportunities, and which opportunities closed. That chain requires the source information to be present on the contact or deal record inside Pipedrive, not only in a web analytics dashboard. Once the source sits next to the lead and deal data, you can compare channels, campaigns and creative against actual commercial outcomes.

The four-step setup

The workflow has four stages: tag the Instagram destination URLs, install the tracking script and add hidden fields to your forms, let the script fill those fields at submission, then pass the form data into Pipedrive. Each stage has its own failure mode, so treat them as a sequence and verify each one before moving on.

Step 1: Tag Instagram ad URLs with UTM parameters

UTM parameters are text appended to the destination URL. They tell the tracking script which campaign sent the visitor. A tagged URL might look like the pattern below, with the medium, source and campaign values attached to the page path.

A practical UTM convention for Instagram

You can choose your own values, but a consistent convention makes reporting far easier. The following mapping is a sensible default for Instagram advertising.

Step 2: Install the tracking script and add hidden fields

After signing up, you receive a small piece of code to place on your website. The setup instructions explain where it goes. Then add hidden fields to every form that should capture source data. The field family is: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. The script works with many form builders, including Gravity Forms, Jotform, Webflow Forms and Typeform, and the hidden-field instructions vary by builder.

Step 3: How the source data reaches the hidden fields

Once the script is active, it observes where each visitor came from. It groups visitors into channels such as Paid Social, Paid Search and Organic Search, and stores that information in a cookie in the visitor's browser. When the visitor submits a form, the script writes the stored values into the hidden fields. Because the data lives in the browser cookie, it can follow the visitor across pages until the form is completed.

Step 4: Send the data into Pipedrive

When the form is submitted, your form tool captures the source fields alongside the lead's name, email and other details. That full payload can be sent to Pipedrive. Once it arrives, you can report on Instagram leads, conversions and revenue, and your sales team can tailor outreach based on the specific ad or campaign the lead responded to.

What gets captured

Each submission carries two families of information: marketing channel data and landing page data.

Marketing channel data

The channel fields describe how the lead arrived. Consider a fencing company running Instagram ads for a new line of robust fencing. A visitor who clicks an ad and submits a form would produce values like these, based on the UTM parameters attached to the ad.

Landing page data

The script also records the original landing page and its category. For example, a visitor who first landed on a blog article about fence types would be recorded with that page and the /blog category. This lets you compare lead volume and revenue across content categories, and then drill into individual articles.

Why use a dedicated attribution script

A dedicated attribution script does three jobs that a plain web analytics tag does not. It classifies every visitor into a channel — paid social, paid search, organic search and so on — so Instagram results sit alongside your other acquisition sources rather than in isolation. It keeps that classification in a browser cookie, which means the source recorded on the landing page is still available if the visitor converts several pages later. And it reconciles messy naming: if one ad uses "IG" and another uses "instagram", the script can still resolve both to the same channel, so your Pipedrive reports do not split one source into two.

Three reports worth building

Once the data is in Pipedrive, the value comes from how you slice it. These three reports answer different questions.

Leads by channel

Use this report as a monthly sanity check on acquisition mix. It counts new leads and groups them by channel, so you can see at a glance whether Instagram is a major or minor contributor relative to organic search, paid search and other sources. The useful comparison is between the share of leads a channel produces and the share of budget it consumes. A channel that generates a small slice of leads while absorbing a large slice of spend is the signal to revisit targeting or creative — not necessarily to abandon the channel.

Customers by network

Instagram rarely runs alone; most advertisers also buy on Facebook and other networks. This report counts closed customers per advertising network, which is a different question from lead volume. A network can deliver many leads but few customers, or the reverse. Comparing customer counts across networks tells you where to concentrate budget for conversion quality, while the leads report tells you where volume comes from. Read the two together before shifting spend.

Revenue by campaign

This report attributes closed revenue to each Instagram campaign, which is the closest view to return on ad spend. A campaign that produces revenue above its cost is a candidate for more budget; one that consistently underperforms is a candidate for revision or pause. Because the campaign value comes from your UTM tagging, the report is only as granular as your naming convention — keep campaign names stable so month-over-month comparisons stay meaningful.

Setup checklist and failure distinctions

Use this checklist to verify each stage, and use the failure distinctions to diagnose problems quickly.

Frequently asked questions

UTM parameter to Pipedrive field mapping
UTM parameterRecommended Instagram valuePipedrive field it populates
utm_mediumpaidsocialChannel
utm_sourceinstagramChannel Drilldown 1
utm_campaignCampaign nameChannel Drilldown 2
utm_termAd set nameChannel Drilldown 3
utm_contentSpecific adChannel Drilldown 4

Mapping follows the supplied convention; the exact field-to-parameter assignment should be confirmed against your form builder and Pipedrive field setup.

Setup checklist
StageCheckIf it fails
UTM taggingEvery Instagram ad destination URL carries medium, source, campaign, term and content values.Leads appear with missing or generic source values.
Script installationThe tracking code is present on every page that hosts a form.Hidden fields stay empty even when UTMs are correct.
Hidden fieldsAll five fields (Channel and Drilldown 1–4) exist on the form and are mapped to Pipedrive.Source data is captured but never reaches the CRM.
Cookie and consentThe visitor's browser accepts the cookie and consent settings allow it.Source is lost between the landing page and the form.
Pipedrive mappingForm fields map to the correct Pipedrive contact or deal fields.Reports cannot group by channel or campaign.

Checklist is a reader aid derived from the supplied four-step workflow; it does not represent a tested runtime procedure.

Frequently asked questions

Do I need UTM parameters if I already use Instagram's own reporting?

Instagram's reporting shows ad performance inside the platform. It does not automatically place the source on the Pipedrive contact or deal record. UTM parameters are what let the tracking script identify the campaign, ad set and creative at the moment a visitor submits a form, so the source can travel into Pipedrive with the lead.

What happens if a visitor lands on one page and submits a form on another?

The source information is stored in a cookie in the visitor's browser. When the form is submitted, the script reads the cookie and writes the values into the hidden fields, so the original source follows the visitor across pages.

Can I track more than Instagram with the same setup?

Yes. The script categorises visitors into channels such as Paid Social, Paid Search and Organic Search, and it recognises other social platforms and referring websites. That means the same hidden fields can support reporting across all your acquisition channels, not only Instagram.

What if my UTM values are inconsistent, such as "IG" in one ad and "instagram" in another?

The script is designed to recognise these variations and group them into the same channel, so reports stay consistent even when the underlying values differ slightly.

Which form builders are supported?

The script works with many form builders, including Gravity Forms, Jotform, Webflow Forms and Typeform. The process for adding hidden fields varies by builder, and step-by-step instructions are available for many of them.