Skip to content

How to get UTM parameters into Tableau

Tableau can only report on campaign performance if UTM and related attribution data reach the data store it connects to. This guide explains a four-step flow: tag campaigns, capture visits on the website, pass attribution data into a CRM or backend tool on conversion, and then build Tableau reports on leads, customers, pipeline and revenue.

Why UTM data must reach your backend first

Tableau dashboards are only as reliable as the data fed into them. To judge campaign performance, UTM parameters need to be captured on the website, stored with the visitor record, and delivered to the CRM or data warehouse that Tableau reads. The workflow below separates tagging, capture, delivery and reporting so each stage can be checked independently.

Step 1: Tag every ad and campaign

Add UTM parameters to every paid and bespoke campaign before capture begins, including social ads, search ads and custom promotions. Without consistent tagging at the campaign level, later attribution has nothing reliable to store. Use one naming convention across networks so source values do not fragment in reports.

Step 2: Install the attribution code

Install the attribution code on the website in the same way as other analytics or marketing tags. Depending on the site setup, it can be added through the CMS header settings or through a tag manager. Once installed, the code examines visit information such as referrer, UTM parameters in the URL and device, classifies the visitor into a channel such as Paid Search, Organic Search or Paid Social, and stores that information in a browser cookie.

Step 3: Send attribution data to your CRM

On form submission, move the stored data from the cookie into the CRM or other backend tool. Option A: add hidden fields to forms so the attribution values are written into those fields and submitted alongside name, email and other user-entered data. Option B: add a small script to the form that reads the values from the cookie and passes them onward. The script route is particularly relevant where sign-up with Google or sign-up with Facebook buttons let users convert without completing a standard form. Checklist before moving on: hidden fields or script present on every conversion form, field names match CRM fields, and a test submission creates a record containing UTM, channel and landing-page values.

Step 4: Build reports in Tableau

Connect Tableau to the CRM or data store that now holds the attribution fields, then build dashboards around leads, customers, sales opportunities and revenue. Useful starting questions include which Twitter ads generated leads, which LinkedIn campaign drove the most pipeline, how many sales opportunities came from Facebook ads, and how much revenue organic search generated. Example check: filter by channel, then by campaign, then compare lead volume against revenue to see whether high-volume campaigns also produce valuable customers.

What to look for beyond raw UTM capture

Raw UTM capture alone misses visits that arrive without UTM parameters, loses data when conversion happens on a different page, and fragments reports when tagging is inconsistent. A fuller attribution approach records channel for organic, direct and referral visits as well as tagged campaigns, persists data in a cookie across pageviews and sessions, normalises variant source spellings into one channel, and captures landing page plus landing page group. That combination lets Tableau show every visitor origin, preserve the first campaign through a multi-page journey, and report performance by site section and by individual page.

UTM-to-Tableau readiness checklist
CheckWhat to verifyWhy it matters
Campaign taggingUTM parameters present on social, search and bespoke campaignsCapture has a reliable value to store
Site installationAttribution code loaded via CMS header or tag managerVisits are classified and stored in a cookie
Form deliveryHidden fields or cookie-reading script on each conversion formAttribution reaches the CRM with the lead record
Tableau connectionCRM or warehouse fields available as Tableau data sourceReports can break down leads, pipeline and revenue by campaign

Pre-publication checklist derived from the described workflow; confirm field names against your own CRM and Tableau connection.

Two ways to deliver attribution data to a CRM
ApproachHow data movesBest fit
Hidden form fieldsAttribution values written into fields and submitted with user dataStandard forms where field mapping is available
Cookie-reading scriptScript retrieves stored values from the cookie and passes them to backend toolsForms and social sign-up flows without a standard form submission

Comparison of the two delivery methods described in the source workflow.

Frequently asked questions

How do UTM parameters get into Tableau?

Add UTM parameters to every ad and campaign first, install the attribution code on the site, pass the stored attribution data into your CRM or other backend store when a form is submitted, then connect Tableau to that store for reporting.

What are the two ways to send attribution data to a CRM?

Two approaches are described: hidden form fields that receive the attribution data on submission, or a small script on the form that reads the data from the browser cookie. The script approach is noted as useful when social sign-up buttons bypass a conventional form.

Why can attribution data survive across pages and sessions?

Because the data is stored in a browser cookie, it can survive navigation to other pages before the form is completed, unlike a method that requires the UTM parameters to still be in the URL on the conversion page.

Why do inconsistent UTM values distort Tableau reports?

Inconsistent tagging such as capitalised, lower-case and abbreviated source values can split one source into several report rows. Normalising those values into a single channel prevents inflated source counts.

What landing-page data can be reported alongside UTM data?

Alongside UTM and channel data, the landing page and its category or group can be stored, allowing reporting by site section as a whole and by individual page within that section.