Custom sources live in OrganizeSources. Use them to assign fixed UTM values to a tracking number, or to capture custom parameters from a visitor’s page URL and attach them to tracked calls.

Assign UTM values to a number

Manually assign UTM values to a tracking number so that every call to that number is attributed to the correct source in your reports. This approach is best suited for static or source-level tracking, for example offline campaigns, print placements, or any situation where calls are not linked to website visits.

Note

If you use Dynamic Number Insertion (DNI) for session-based tracking, UTM values are captured automatically from each visit and do not need to be assigned manually. Session-based UTM values also take precedence over any manually assigned source if both are present: field by field, the visit’s values win, and the number’s source only fills the fields the visit left empty (often utm_campaign).

  1. Open Add custom source

    • Go to OrganizeSources.
    • Click Add custom source.

    Tracking Sources

    Define how visits and calls are attributed to marketing channels.

    All 4 · 2 custom · 2 default
    Source NameTypeParameters
    Spring MailerCustomutm_campaign: spring-promoutm_medium: print · utm_source: mailer
    Monthly NewsletterCustomutm_campaign: newsletter
    Paid Search & DisplayDefault–
    Organic searchDefault–
    The Tracking Sources page lists your custom sources and the default ones. Click Add custom source (1).

  2. Create a Build your own source

    • In the Add a tracking source pop-up, select Build your own (1) from the list of source types.
    • Click the name at the top of the form (2) and enter a name for this source.
    • Fill in whichever fields apply: utm_source, utm_medium, utm_campaign and Referrer Domain, plus a field for each custom URL parameter you capture (see Capture custom URL parameters).
    • You do not need to fill in every field. For calls with no website visit, a utm_source or utm_medium you leave empty is reported as other (the medium as referral if you set a Referrer Domain), and an empty utm_campaign stays empty.
    • For those calls, use plain values: a value with a wildcard only counts if it ends in * (Nimbata drops the *), and values with * elsewhere or ! in front count as empty.
    • Make sure the values match exactly what you want to see in reports (for example, consistent use of lowercase).
    • Click Save source (3).
    ✕

    Add a tracking source

    Choose a source and define how Nimbata should recognize it.

    Build your ownDefine your own attribution rules1SearchOrganic and paid search trafficSocialSocial networks and postsGenerative AITraffic from AI assistants and answer enginesEmailNewsletters and campaignsOfflineEvents, print, and other offline channels

    Spring Mailer2

    Build your own · Define your own attribution rules

    Use * as a wildcard: brand matches exactly, brand* starts with, *brand ends with and brand contains. Put ! in front to exclude instead: !brand skips visits with that value. Case doesn’t matter.

    utm_source:
    mailer
    utm_medium:
    print
    utm_campaign:
    spring-promo
    Referrer Domain:
    example.com

    Matches referrers that contain this text

    Select Build your own (1), name the source (2), fill in the UTM values, then click Save source (3).

  3. Assign the custom source to a tracking number

    • Go to TrackingNumbers.
    • Find the number you want to assign the source to.
    • Click the Source dropdown for that number.
    • Select your new custom parameter source.

    Once assigned, all calls to this tracking number report the selected UTM values until the source is changed or removed.

Match part of a value, or exclude one

Each field takes one value, and * stands for any text:

You type The source matches visits where the value
brand is exactly brand
brand* starts with brand
*brand ends with brand
*brand* contains brand
* has any value

Put ! in front of a value to exclude it instead: !*brand* skips every visit whose value contains brand. Under each field, the form spells out what your value does, such as Contains “brand” or Skips visits where utm_campaign contains “brand”. Case doesn’t matter.

When you fill in more than one field, a visit has to match all of them. For example, to track all your paid search calls except your brand campaign on one source:

  • utm_medium: cpc
  • utm_campaign: !*brand*

A source needs at least one value to match, as well as its exclusions. A source with only exclusions can’t be saved (“Excluded values alone would match almost every visit”), because it would claim nearly all your traffic.

Sources created before wildcards were added match a plain value as “starts with”. When you open one to edit it, its values show with a * at the end, such as cpc*, so it keeps matching the same visits after you save.

Edit a custom parameter source

  • Go to OrganizeSources.
  • Find your custom source.
  • Click its name to open Edit tracking source.
  • Make your changes.
  • Click Save source.

Note

Changes to UTM parameters apply only to future calls. Historical call data is not updated.

🎉 Your tracking number is now set up to report calls with your chosen UTM values.

Detailed guide: How Nimbata fills UTM values
Detailed guide: Set up DNI step by step

Capture custom URL parameters

Custom URL parameters let Nimbata capture additional context from a visitor’s page URL and attach it to tracked calls. This is useful when standard attribution (source, campaign, medium) isn’t enough and you need to pass extra data, such as ad variant IDs, internal campaign codes, or product categories, through to your call records.

When a visitor lands on a page containing a Nimbata tracking number and the URL includes parameters you’ve configured, Nimbata stores those parameter values with the call record at the moment the call is placed. The data then appears in call details and exports.

  1. Create the custom URL parameter

    • Go to OrganizeSources.
    • Find the URL params panel next to the sources list (on a narrow screen, click URL params above the list to open it).
    • Under URL parameter name, enter a name for your custom URL parameter (1).
    • Click Add (2) to save it.
    URL params1 custom

    Reusable params for custom sources, workflows and reporting.

    ad_variant

    URL parameter name

    promo_code1
    Enter the parameter's name (1) and click Add (2). It joins the list above.

    A confirmation message appears and your new parameter is listed in the panel.

  2. Add the parameter as a column in your calls view

    • Go to ActivityCalls.
    • Click the three-dotted menu.
    • Select Edit columns.
    • Find your custom URL parameter in the Available column of the Edit Columns for Completed Calls View panel.
    • Click the blue arrow (1) to move it to the Selected column.
    • Close the panel.
    Your custom URL parameters carry a person badge. Click the blue arrow (1) to add one to the view.

🎉 Your custom URL parameter now appears as a column in ActivityCalls. Whenever Nimbata tracks a call from a URL containing that parameter, its value is visible there.

Detailed guide: How Nimbata fills UTM values
Detailed guide: Assign UTM values to a number