Analytics and Tracking

Blended Data Source

Also called Data blend, join

Two or more sources joined on a shared key so one chart can show fields from all of them together.

Quick facts: Blended Data Source

Category
Analytics and Tracking
Also called
Data blend, join
Level
Advanced
Affects
Cross-channel reporting, cost per result, data accuracy
Where to see it
Looker Studio (blend editor), BigQuery, spreadsheet lookups
In this article4
  1. How a blended data source works
  2. Why blended data sources matter
  3. Common mistakes with blended data sources
  4. How to act on it

How a blended data source works

You choose the sources, then choose a join key: a field that exists in all of them and means the same thing in each. Date is the most common. Campaign name, landing page address and country are the next. The tool lines the rows up on that key and hands you one table containing fields from every source.

The join type decides what happens to rows that do not match. A left join keeps everything from the first source and leaves blanks where the others have nothing. An inner join keeps only rows present in all of them, which silently discards the rest. A full outer join keeps everything and produces blanks on both sides. Choosing this carelessly is where most of the trouble starts, because a blend that has thrown away half its rows still draws a perfectly convincing chart.

Why blended data sources matter

Because the numbers a business actually manages by rarely live in one place. Cost sits in the advertising platform. Revenue sits in the shop or the accounting system. Enquiries sit in the website’s own records or a CRM. A cost-per-enquiry chart needs at least two of those, and no single source can produce it.

They also let you compare channels honestly. Once every platform’s spend is joined to one shared measure of outcome, the comparison stops depending on each platform’s own generous view of what it achieved.

Common mistakes with blended data sources

Joining on keys that are not truly identical. A campaign named slightly differently in two systems will not match. A landing page recorded with tracking parameters in one source and without them in another will not match. A date recorded in a different time zone will match the wrong day. Almost every wrong blend traces back to the key.

The other classic is duplication. When the key is not unique on one side of the join, each row on that side pairs with several on the other, and the totals inflate. Blending at the wrong level of detail causes it too: joining daily campaign rows to monthly revenue rows will multiply something. Adding a ratio on top makes the result confidently wrong, so check totals against each source before anyone sees the chart.

How to act on it

Fix the keys before you blend. Consistent campaign naming and disciplined tagging remove most future pain, and a UTM builder is the cheapest way to enforce it across a team. Strip parameters from page addresses if you intend to join on them.

Start with a left join from the source you cannot afford to lose rows from — usually spend — and confirm the blended totals still match that source on its own. Keep blends shallow: joining several sources at once inside a reporting tool becomes very hard to debug, and at that point the honest answer is to load the data into a warehouse and join it properly there, then report on the result.

Do and do not

Do

  • Standardise campaign names and tagging before joining
  • Start from the source you cannot lose rows from
  • Check blended totals against each source separately

Do not

  • Join fields that only look identical
  • Mix daily rows with monthly rows
  • Stack several blends until nobody can debug them

Questions people ask about this

Why do my blended totals not match the original reports?

Either rows were dropped or rows were duplicated. Rows are dropped when the join type keeps only matching keys, so anything that did not match disappears. Rows are duplicated when the key repeats on one side and each occurrence pairs with several on the other. Compare the blended total against each source separately to see which of the two happened.

What is the best field to join on?

Date is the safest starting point because every platform records it and it rarely varies in format, although time zones can shift a row by a day. Campaign name works when naming is disciplined across platforms. Landing page address works if parameters are stripped consistently. Whatever you choose, the field must mean exactly the same thing in every source.

When should I use a data warehouse instead of blending in the report?

When the blend needs more than a couple of sources, when the join keys need cleaning before they match, or when you need history that outlives the platforms' own retention. A reporting tool joins at the moment someone opens the page, which limits how much work it can do. A warehouse lets you clean, join and store once, then report on the tidy result.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.