Skip to content

Ad Source

The ad source is the source of data on ad spend, impressions, and clicks. In an attribution report, the ad source provides the data that will be matched against CRM data.

Supported ad sources

Full list: Supported Sources.

Configuration parameters

Selecting the integration

Choose an ad account from the list of connected integrations. The integration must be in Connected (Active) status.

Selecting the account

If the integration has multiple ad accounts, choose the one you need. Each account is analyzed separately.

Selecting the entity

Determines the level at which analysis happens:

  • Campaign — aggregation by campaign. Each row = one campaign
  • Ad Set / Ad Group — aggregation by group. Each row = one group
  • Ad — maximum granularity. Each row = one ad

The ad level gives the most accurate attribution, but requires UTM tags to be set at the ad level.

Selecting the period

Determines the time range for which ad data is loaded. Supported:

  • Presets: today, yesterday, 7 days, 14 days, 30 days, 90 days
  • Custom range: arbitrary start and end dates

Ad source fields

The ad source provides the following field groups:

Metrics (populate automatically)

  • Spend
  • Impressions
  • Clicks
  • CTR — click-through rate (Clicks / Impressions)
  • CPC — cost per click (Spend / Clicks)

UTM fields (used for matching)

  • utm_source — traffic source
  • utm_medium — traffic type
  • utm_campaign — campaign name
  • utm_content — ad content
  • utm_term — keyword

System fields

  • campaign_name — campaign name
  • campaign_id — campaign ID
  • adset_name / ad_group_name — group name
  • ad_name / creative_name — ad name
  • ad_id — ad ID

Source-specific notes

Meta Ads

  • UTMs are set in URL parameters at the ad level
  • Dynamic UTM parameters are supported ({{campaign.name}}, {{adset.name}}, etc.)
  • Auto-tagging is supported (gclid)
  • UTMs can be set via tracking templates
  • ValueTrack parameters ({lpurl}, {creative}, etc.)

TikTok Ads

  • UTMs are set in the ad URL / tracking template
  • Watch for consistent casing of values with the CRM

Maintained by the LightLead Documentation Team · Last verified: 2026-07-26