Overview
Source Mapping allows you to standardize incoming Source and Source Type values before they are saved to your CRM and used in reporting.
Different traffic sources often produce slightly different values such as:
google.com
search.yahoo.com
Source Mapping converts these values into standardized values like:
Facebook/Instagram
Referral
Each row in the Source Mapping page represents a rule that transforms an incoming value into a standardized value.
Accessing Source Mappings
To configure source mappings:
Log in to the HeavySet Admin Portal
Navigate to:
CRM Settings → Attribution → Source Mappings
Select the appropriate CRM configuration from the Selected Config dropdown.
Mappings apply only to the selected CRM configuration.
Source Mapping Interface
Each mapping rule contains the following fields.
Type
Determines which values the rule applies to.
Available options include:
Source
Source Type
SourceType + Source
Match
The incoming value that will trigger the mapping rule.
This value may come from:
referrer domains
URL parameters
iframe parameters
marketing attribution values
Example:
search.yahoo.com
New Value
The standardized value that will be saved and sent to the CRM.
Example:
SourceType + Source Mapping
The new interface allows mapping rules that depend on both the Source Type and Source values.
When selecting:
SourceType + Source
Additional fields appear:
Match SourceType
Match Source
New SourceType
New Source
Example:
| Match SourceType | Match Source | New SourceType | New Source |
|---|---|---|---|
| cpc | google23 | paid | abc |
This rule only applies when both match conditions are true.
Adding a Mapping
To create a mapping rule:
Click + Add Mapping
Select the Type
Enter the Match value
Enter the New Value
Click Submit to save
Multiple mappings can be added before submitting.
Ignore UTM Parameters
The Source Mapping page includes an Ignore UTM Parameters toggle.
When this option is disabled (default), UTM parameters are used for attribution:
utm_source → Source
utm_medium → Source Type
When enabled, UTM parameters will be ignored and other attribution methods will determine the values.
Examples
Example 1 – Map Yahoo Search Traffic
Type: Source
Match: search.yahoo.com
New Value: Google
Example 2 – Group Instagram and Facebook
Type: Source
Match: Instagram
New Value: Facebook/Instagram
Example 3 – Standardize Referral Type
Type: Source Type
Match: referral
New Value: Referral
How Mapping Is Applied
Mappings are applied when a lead or form submission is processed.
Mapped values affect:
CRM sync values
reporting data
audit table filters
Mappings do not update previously saved leads.
Only leads created after the mapping is saved will reflect the new values.
Viewing Mapped Values in the Audit Table
Mapped values can be verified in the Audit Table.
Navigate to:
Reports → Audits
Common filters include:
Source Type
Filters leads by the mapped Source Type.
Examples:
web
paid
organic
Source
Filters leads by the mapped Source.
Examples:
Newsletter
Parent URL Domains
Filters leads by the domain where the HeavySet form was embedded.
Example:
godurante.com
This represents the page hosting the form and may differ from the traffic source.
Understanding Source vs Parent URL Domain
When reviewing lead activity in the Audit Table, it is important to understand the difference between Source and Parent URL Domain.
Source
The Source represents where the visitor originally came from.
Examples:
Newsletter
This value is determined from:
URL parameters (
?source=)marketing attribution
referrer domains
source mappings
Source values may also be standardized using Source Mapping rules.
Parent URL Domain
The Parent URL Domain represents the website page where the HeavySet form was embedded.
Example:
example.com
This tells you which site hosted the form, not where the visitor originated.
Example
A user finds your website through Google and fills out the form.
The audit record would show:
Source: Google
Parent URL Domain: example.com
Meaning:
Google sent the visitor
the form was hosted on example.com
Testing Source Mapping
To test mappings:
Open an incognito browser window
Append test parameters to your form URL:
?source=TestSource&sourceType=TestType
Submit a form
Check the results in:
Reports → Audits → Form Activity
Verify that the mapped values appear correctly.
Troubleshooting
Mapping not applied
Verify the raw value captured in the Audit Table and use that exact value in the Match field.
Case or spacing mismatch
Ensure the Match value exactly matches the captured value.
Incorrect configuration selected
Ensure the correct CRM configuration is selected in:
Selected Config
Mappings only apply to the selected CRM connector.
Comments
0 comments
Please sign in to leave a comment.