¶ Campaign and traffic source tracking (UTM)
Campaign and traffic source tracking in Hummerce records where a customer came from and keeps that source until the order is placed. Every order in the panel has a visible source - for example an email campaign, a price comparison site or a partner - regardless of whether the store uses Google Analytics.
Core platform feature - available in all current Hummerce versions; self-service source management in the panel since version 2.27. Last updated: 2026-09-29.
¶ Benefits and use cases
- Every order has its traffic source recorded - visible directly in the panel, with no reporting in external analytics needed.
- Self-service source management in the panel (Marketing -> Sources) - no config file editing by an implementation developer.
- Tracking by a link parameter, remembered in a cookie - a returning customer's later order can still be attributed to the first campaign, within the time set for that source.
- Source-dependent coupons - the coupon policy can make a discount depend on the source the customer came from.
- Consistent naming of sources, campaigns and medium - a condition for repeatable, comparable reports over time, e.g. in Google Analytics 4 - Full Sales Funnel, No Code and Reports - BigQuery and Looker Studio.
- Order source available in the export for further analysis - the source field also feeds into BigQuery reports.
- Source - a fixed, repeatable name (ideally domain-based, e.g.
example-portal.com) - the same source name in every campaign from the same channel, so data can be compared over time.
- Campaign name - unique to a given marketing action, optionally with a suffix marking a sub-campaign.
- Medium - the channel type (e.g. banner, email, cpc) - also a fixed name for that channel type.
- Content and term - optional, to distinguish several creatives or ad copy within the same campaign.
- Not every field needs to be filled in - an empty field is better than a meaningless value.
Example of a seasonal campaign advertised with two banners and a mailing:
| Element |
Small banner |
Large banner |
Email |
| Source |
example-portal.com |
example-portal.com |
newsletter |
| Campaign name |
spring2026 |
spring2026 |
spring2026 |
| Medium |
banner |
banner |
email |
| Content |
200x50 |
460x100 |
link-jacket |
| Term |
jackets |
jackets |
- |
- Regardless of UTM tags read by external analytics, the store has its own source mechanism: the customer reaches the store with a parameter in the address (
source by default, another name such as utm_source can be set) - the store records the source and, if enabled, remembers it in a cookie for the time set in that source's configuration.
- An order records one "winning source" plus a trail of earlier sources from the same customer session.
- The order source is visible in the panel on the order card and can be used as a condition in the coupon policy (a discount only for a selected source).
- List of sources: Marketing -> Sources - adding, editing, deleting and a change history, independent of sources defined in the store's config file (both sets work in parallel, source symbols must be unique across both).
- Source settings: symbol, whether the source is active, the name of the URL parameter and its value, whether the source can be used in coupon policies, whether it should be saved as a cookie (cookie name and value, expiry time in seconds - 604800 s, i.e. 7 days, by default).
- Advanced sources - e.g. dedicated to a selected partner, with its own tracking code attached to the order confirmation page - are configured in the sources file during implementation.
- Order source tracking - a core platform feature, available in all current versions.
- Self-service source management in the panel, without editing the config file - since version 2.27.
- A new source (e.g. for a new partner or campaign) is set up in the panel on your own - no implementation needed.
- Requires implementation: advanced sources with their own tracking code (e.g. a partner's pixel on the order confirmation page) and changing the default URL parameter across the whole store.
- Minimum estimated time: a dedicated source with its own tracking code - from 2 h.
- What the time depends on: the number and complexity of dedicated sources, integration with the coupon policy, the need to change the default URL parameter name.
- Tracking works within a single browser - a customer who returns from a different device or clears their browser data loses the remembered source.
- An order records one winning source - full multi-channel analysis requires external analytics, e.g. Google Analytics 4 - Full Sales Funnel, No Code.
- Renaming a source during a campaign makes it harder to compare data over time - it's worth settling on naming before launch.
- We do not verify the configuration for legal compliance - the promotion terms and cookie notice belong to the store.
- Fuller integration of source tracking with multi-channel reports.
- More ready-made source types for popular channels without extra technical configuration.
Does Hummerce record where a customer placing an order came from?
Yes. The source tracking module records the traffic source on the order, regardless of whether the store uses external analytics.
Can a new source, e.g. for a new partner, be added without a development request?
Yes, through the panel (Marketing -> Sources) - with no config file editing.
Can a discount depend on the source the customer came from?
Yes. The coupon policy can be limited to a selected source.
Does source tracking survive if the customer returns to the store on a different day?
Yes, if the source has cookie saving enabled - until the cookie expires, 7 days by default, set separately for each source.
Do you need implementation work to start tracking a new campaign?
No, if standard link tracking is enough. Implementation is only needed for a dedicated source with its own tracking code.
Want to check how campaign tracking could work in your store? Contact the Hummerce team (in Polish).
- Source management: Marketing -> Sources - list, adding, editing, deleting, change history.
- Source settings: Symbol, Active, URL parameter (
source by default), URL parameter value, Used in coupons, Save as cookie, Cookie (name), Cookie value, Cookie expires after (s) (604800 s by default).
- Order source: visible on the order card as the Customer source field.
- Saving UTMs on the order for further analytics (e.g. export to BigQuery): the Save UTMs to your order setting in the BigQuery group (Reports - BigQuery and Looker Studio).
- Advanced source configuration (the
sources.xml file) and global module settings (including whether to remember the source trail between sessions, and the trail cookie's name and expiry) - configured during implementation, outside the panel.
¶ REST API and MCP
Source configuration has no dedicated REST API or AI assistant (MCP) operations - the order source is a field read together with the order data.
The module has no customer-facing messages of its own - tracking works in the background, with no effect on page content.
The module doesn't add its own item or customer parameters - it uses order fields (source, source trail).