Skip to content

How to Capture UTM Parameters in Your Bubble.io App

Bubble does not record campaign source for new signups by default. That leaves a gap: you can see that accounts are being created, but not which ads, articles, or referrals produced them. This guide walks through a plugin-based setup that captures UTM parameters and related attribution data, stores them in the browser, and makes them available to Bubble workflows so they can be saved to your database or forwarded to a CRM, billing system, or analytics tool.

What the setup does

The approach has four moving parts. First, every marketing link carries UTM parameters. Second, the plugin's element is placed on the signup page of the Bubble app. Third, the plugin reads the visitor's arrival information and keeps it in a cookie. Fourth, the signup workflow reads the available values and writes them wherever you need them. The result is a record that connects an account to the campaign and landing page that brought the person in.

The four setup steps

  1. Tag your campaigns. Add UTM parameters to social ads, search ads, guest posts, trade-magazine placements, and any other marketing link. The plugin uses these values to identify the source.
  1. Install the plugin. If the plugin is available in your Bubble marketplace, add it and place its element on your signup page. Detailed installation instructions are available in the plugin's help article. Confirm plugin availability and support with the owner before relying on this step.
  1. Let the plugin capture arrival data. While visitors browse, the plugin watches for UTM parameters and stores the resulting attribution information in a cookie. When someone reaches the signup page, the values are ready for the workflow.
  1. Use the values in your workflow. Modify the signup workflow to save the attribution fields to your database, or pass them to a CRM, billing platform, or analytics tool through API calls, Segment, or Zapier.

Worked example: a Google Ads signup

Imagine a file-storage app called Boxdrop running a Google Ads campaign. A visitor searches for a way to share large files, clicks the ad, lands on the site, and later creates an account. Depending on the UTM parameters in the ad URL, the workflow could receive values like these:

Field map for the example

The following table shows the attribution fields and example values for the Boxdrop scenario. These are illustrative values, not fixed outputs; the actual values depend on the UTM parameters in the ad URL and the landing page.

What you can report on

Once the values are stored, you can answer questions such as how many leads or customers came from Google Ads, how much revenue those campaigns produced, and what return the spend generated. The same fields also support comparisons between campaigns and between landing pages.

Raw URL capture versus cookie-based capture

Bubble's 'Get data from URL' action can read UTM parameters, but it has limits that affect data quality. Use the checklist below to decide whether raw capture is sufficient for your app or whether a cookie-based approach is warranted.

Decision checklist

  • Does every signup page URL contain the UTM parameters? If not, raw capture will miss the source.
  • Do visitors ever move from a separate marketing site to the Bubble app before signing up? If so, parameters can be lost between pages.
  • Do you need to attribute organic search, direct, referral, or organic social traffic that arrives without UTM parameters? Raw capture will not see those sources.
  • Do your UTM values vary in capitalization or spelling, such as Google, google, and adwords? Raw capture will treat them as separate sources unless you normalize them.
  • Do you need landing-page and landing-page-group reporting? Raw capture alone does not provide those fields.

A common failure to watch for

Attribution breaks most often at a handoff. Consider a visitor who clicks a tagged ad, reads a landing page, then follows a link to a different signup URL before creating an account. A workflow that inspects only the URL of the signup page has nothing to read at that point, because the campaign parameters stayed behind on the earlier page. To check whether your app has this exposure, open a fresh private window, follow a tagged link, navigate the way a real prospect would, and inspect the signup page URL when you arrive. If the parameters are gone, URL-only capture will record an empty source. A cookie-based approach sidesteps the handoff because the values are written during the first page view and read back later, regardless of how many pages the visitor crosses in between.

Attribution fields and example values
FieldExample value
ChannelPaid Search
Channel Drilldown 1Google
Channel Drilldown 2Share Files Campaign
Channel Drilldown 3Free Account Ad
Landing Pagewww.boxdrop.com/features/share
Landing Page GroupFeatures

Example values for the Boxdrop scenario. Actual values depend on the UTM parameters in the ad URL and the landing page.

Frequently asked questions

Does Bubble capture UTM parameters automatically?

No. Bubble does not record campaign source for signups out of the box. You need either a plugin or a workflow that reads the parameters and stores them.

Can I use Bubble's 'Get data from URL' instead of a plugin?

Yes, but it only works when the UTM parameters are present on the signup page URL. If visitors arrive on a separate marketing site first, or if they come from organic, direct, or referral sources without UTM parameters, the data will be incomplete.

Where does the plugin store the attribution data?

Where the attribution values live depends on the implementation. A cookie-based plugin, if one is installed and supported for your app, would typically write the visitor's arrival data to a browser cookie and then expose those values to Bubble workflows once the person reaches the signup page. That behavior is a property of the specific plugin, not of Bubble itself, so verify the plugin's storage mechanism and workflow exposure with its provider before you build around it. A workflow that reads the current URL instead keeps nothing in the browser and depends entirely on the parameters present at signup.

What can I do with the captured values?

You can save them to your Bubble database, send them to a CRM or billing system, or forward them to analytics tools through API calls, Segment, or Zapier.