How to Assign Source Values to Leads (MarketSharp)

Purpose

This article explains how to ensure leads are correctly tagged for MarketSharp attribution when using HeavySet Tech.
For MarketSharp users, it is critical that:

• sourceType matches the MarketSharp Primary Source name exactly

• source matches the MarketSharp Secondary Source name exactly

Exact matching ensures leads sync correctly and report accurately in MarketSharp.

---

1. Share a URL With Source Parameters

When sharing links to pages that contain HeavySet Tech forms, include source parameters in the URL.

MarketSharp requirement:

• sourceType = MarketSharp Primary Source

• source = MarketSharp Secondary Source

Example:

https://www.example.com/?source=SecondarySourceHere&sourceType=PrimarySourceHere

This method works on any page that embeds a HeavySet Tech form.

⚠️ The values must match the MarketSharp Primary and Secondary Source names exactly, including spelling and spacing.

For more details, see How to Use URL Parameters to Specify Lead Source and Source Type.

---

2. Pass Source Values Through an Embedded iframe

If your site embeds the HeavySet scheduler using JavaScript, you can pass MarketSharp source values directly into the iframe.

Using injectHeavySetIframe

window.injectHeavySetIframe(
  '12345678-1234-1234-1234-123456789abc',
  'iframeContainer',
  'width: 780px; max-width: 100%; height:450px; border: none;',
  'SecondarySourceHere',
  'PrimarySourceHere',
);

Using authHeavySetIframe

window.authHeavySetIframe(
  '12345678-1234-1234-1234-123456789abc',
  'iframeContainer',
  'SecondarySourceHere',
  'PrimarySourceHere',
);

Important notes:

• If a source parameter exists in the URL (Method 1), it will override the iframe values.

• If no source values are provided, referrers such as google, bing.com, or duckduckgo.com may be recorded automatically.

These auto-captured values can later be mapped to MarketSharp sources if needed.

---

3. Map Unidentified or Referrer-Based Traffic

Leads without a clearly defined source default to the website domain. You can map these to MarketSharp-friendly sources after the fact.

How to map traffic:

1. Go to Form Activity Audits

2. Set View Type to Form Views

3. Review the SOURCE column to identify incoming traffic

4. Configure mappings on the Attribution Mapping Page

When mapping:

• Map to the correct MarketSharp Primary Source (sourceType)

• Map to the correct MarketSharp Secondary Source (source)

For step-by-step instructions, see Using Source Mapping in HeavySet.

---

4. Manually Select the Source

Lead takers can manually select the appropriate source directly on the form. This is ideal for:

• Trade shows

• Home shows

• In-person or phone-based appointments

Enable the Source Selector:

1. Go to Form Style Settings

2. Enable Source Selector

3. Click Submit to save

Ensure staff are trained to select:

• The correct MarketSharp Primary Source

• The correct MarketSharp Secondary Source

---

Special Note for Google Ads (MarketSharp Users)

If you are running Google Ads:

• Append source parameters to ad URLs

  • Example:

    source=Google PPC
    sourceType=Paid Advertising
    

• Ensure the values exactly match your MarketSharp Primary and Secondary Source names

• Deploy Google Ads conversion tracking following the HeavySet Google Conversion Tracking Guide

• Track conversions for:

  • Form submissions

  • Appointment bookings

Conversion IDs and labels should be obtained from your Google Ads team.

---

Summary

Recommended methods:

• URL parameters

• iframe source injection

Fallback methods:

• Traffic mapping

• Manual source selection

For MarketSharp users, accuracy depends on exact name matching:

• sourceType → MarketSharp Primary Source

• source → MarketSharp Secondary Source

Using these methods—individually or together—ensures clean attribution and reliable MarketSharp reporting.