Skip to content

Capture Marketing Channel Attribution Data in Qualified

When a visitor opens a chat on your site, the conversation is a lead source in its own right.

This integration lets you attach the channel, campaign and landing-page details behind that conversation to the chat session, so the same record can travel into your CRM, email platform, billing system or reporting layer.

How the Qualified integration works

The flow has three steps. First, you place the attribution code snippet on your website. Second, each time a visitor starts a new chat, the attribution script passes through information about where that visitor came from. Third, the attribution data is visible inside Qualified and can be forwarded to the tools you already use.

A useful way to think about it: the chat session becomes the moment of capture, and the attribution record becomes a property of that session rather than a separate spreadsheet you reconcile later.

Add attribution code to your website

Copy the snippet from your attribution account and place it on your site. The snippet is what allows the attribution script to read the visitor's channel and landing-page context at the moment a chat begins. If the snippet is missing, the chat will still open, but the attribution fields will be empty.

What information is captured

Two families of data are captured for each chat session.

Channel data. the attribution script records the channel a lead came from — for example Paid Search, Paid Social or Organic Search — along with further detail for that channel. For Paid Search, that includes the campaign, ad group and keyword.

Landing page data. the attribution script records the first page the lead saw on your site, such as a specific blog URL, plus the category of that page, such as Blog.

A quick field map helps when you are mapping these into a destination system:

  • Channel (e.g. Paid Search, Paid Social, Organic Search)
  • Campaign, Ad Group, Keyword (channel-dependent detail)
  • Landing Page (first page seen)
  • Landing Page Category (e.g. Blog)

Where the data can go

The integration is designed to carry the attribution record beyond the chat itself. The destination lists below describe the intended capability; the Qualified connection and each downstream mapping are configured and verified in your own account rather than assumed to be live.

Each destination below is a category of tool the attribution record can reach. The named products are examples, not a guarantee that a given connection is already wired up in your workspace.

  • CRM. Salesforce, HubSpot, Zoho, Pipedrive and similar systems. A chat lead arrives with its channel and campaign attached, so the record reads the same way in the CRM as it did at capture.
  • Email marketing. Mailchimp, Campaign Monitor, AWeber and similar platforms. New subscribers carry the campaign that first brought them in, which makes list growth traceable to a source.
  • Billing. Stripe, Square, PayPal and similar processors. A paying customer keeps the channel and campaign that first reached them, so revenue can be read against acquisition.
  • Analytics. Tableau, Power BI, Google Data Studio and similar BI tools. In your own reporting layer, key business metrics can be broken down by channel and campaign.

Using the data to understand leads, customers and revenue

The point of capturing channel and landing-page data at chat time is to answer a practical question: which marketing efforts are producing conversations that turn into customers? With the attribution fields attached to each chat session, you can build reports that group leads, customers and revenue by channel, campaign, ad group or landing page. That turns chat from a black-box lead source into a measurable one.

A short verification checklist

Before you rely on the data, confirm three things in order:

  1. Snippet present. Load a page with the attribution snippet and start a test chat. If channel and landing-page fields are blank, the snippet is the first thing to check.
  2. Chat trigger fires. Open a fresh session rather than reusing an existing one, because attribution is passed with each new chat.
  3. Destination mapping. Confirm the channel, campaign, landing page and page-category fields are mapped into the CRM, email, billing or analytics tool you are sending to. A missing mapping looks like missing data but is really a routing gap.

Get started

Before choosing a plan, check the current price, included usage and any trial conditions. Set up the Qualified connection in your own account, then test a new chat and its downstream field mappings before using the attribution data for reporting.

Frequently asked questions

When is attribution data captured for a Qualified chat?

Each time a visitor starts a new chat on your website, the attribution script passes through information about where that visitor came from. The attribution record is therefore tied to the start of the chat session, not to a later message in the conversation.

What attribution fields are available?

Two groups: channel data (channel, plus campaign, ad group and keyword where relevant) and landing-page data (the first page seen and its category, such as Blog).

Can the data be sent outside Qualified?

The integration is designed to send the attribution record to a CRM such as Salesforce, HubSpot, Zoho or Pipedrive; an email platform such as Mailchimp, Campaign Monitor or AWeber; a billing tool such as Stripe, Square or PayPal; or an analytics tool such as Tableau, Power BI or Google Data Studio. Each destination is configured and verified in your own account.

Why are the attribution fields blank on a chat?

The most common cause is that the attribution snippet is not on the page where the chat starts. A second cause is that the chat session was opened before the snippet loaded. Check the snippet placement first, then retest with a fresh chat.