Two Minute Reports Logo
Custom fields

Blending across connectors

Map the same field from each of your connectors into a single unified custom field, summed for metrics or unified into one column for dimensions.

Every platform names its fields differently: "amount spent" on one, "cost" on another. The Blending method lets you map the equivalent field from each of your connectors into a single unified custom field. A cross-platform chart or goal can then use one field.

What you can do

  • Combine one field per connector into a single unified field
  • Build unified metrics like total Spend, Impressions, or Clicks across platforms
  • Build unified dimensions like a single Campaign name, Ad group, or Country column
  • Pair a unified name with a unified ID so each campaign, ad group, or ad keeps its own row
  • Give each connector its own field or its own formula

How blending works

When you choose Blending, you select the connectors to include. Then you tell the field which field to use for each connector.

For each selected connector, you can map either:

  • A single field - pick the equivalent field from that connector, or
  • A formula - turn on Set formula to build a calculation for that connector (and even add conditional rules for it)

Metrics are summed

For a custom metric, the values from each connector are added together into one total. Mapping "amount spent" from Meta, "cost" from Google, and "spend" from TikTok gives you a single blended Spend metric across all three.

Dimensions are unified

For a custom dimension, each connector's mapped field flows into one unified column. Mapping each platform's campaign-name field produces a single "Campaign name" dimension you can group by, whichever platform a row came from.

Blending is what makes cross-channel dashboards clean: one "Spend" metric and one "Campaign name" dimension instead of a separate field per platform.

Names are not unique

A blended field puts the data of more than one connector in one column. For example, the Campaign name field shows the campaign names from all your ad connectors, such as Google Ads, Facebook Ads and TikTok Ads, in one column. Two Minute Reports gives these fields. In the Google Sheets add-on, they are under Common Fields in the field list. In the Hub, they are under Built-in fields. You can also make your own blended field, as this page shows.

A name does not always identify one campaign, ad group or ad. The platform gives these names, and the same name can occur more than one time. For example, Meta names an ad that you make from a post "Instagram post:" and the start of the post text. Several ads from similar posts can then have the same name.

If you group a report only by a name, all the items with that name go into one row. Two Minute Reports adds their metrics together. The report does not show that this occurred. The row looks like one large ad, not three small ads.

To keep one row for each item, group by the name and by the ID:

  • Common Fields or Built-in fields: each name field there has an ID field. Add the ID beside the name:
    • Campaign name with Campaign ID
    • Ad Group Name with Ad Group ID
    • Ad Name with Ad ID
  • If you made your own name field with Blending: make the ID field in the same way. For example, you made a "Campaign" field: for each connector, you selected its campaign name field. Then make a "Campaign ID" field: for each connector, select its campaign ID field. Group by the two fields.

The ID keeps one row for each item, and the name makes the row easy to read. Meta and Snapchat call an ad group an "ad set", but the field is Ad Group ID.

Does a report that groups by a name show fewer campaigns, ad groups or ads than the platform? Do the rows cost too much? Then examine the names first. Add the related ID field to separate the rows.

Set it up

Choose the method

In the builder, select Blending. Then select Next.

Select your connectors

Under Select connectors, choose the connectors this field should span.

Map each connector

For every selected connector, map the field (or build a formula) that represents this value on that platform. Each selected connector must be mapped before you can save.

Preview and save

Use the live preview to confirm the blended values look right, then save.

A blended field only produces values for the connectors you mapped. Rows from a connector you didn't map fall back to the field's fallback value.

Next steps

Copyright © 2026