Cross-channel Source Groups used to take two tabs to build. Now you fix an unmatched field, while grouping the data.

You usually spot the gap at the worst moment. You've added the second integration to the group, and its Engagements aren't mapped to the unified metric the first one uses, so that channel's numbers don't land in the group. Fixing it meant leaving the builder, opening Organize, finding the field, adding the mapping, then coming back and picking up where you left off.

Now every field in the builder has a pencil on hover, in the unified column and in each channel's column. Click it, add the missing integration, save, and the group updates in place. One tab, one pass, nothing to rebuild.

Try it and let us know if it made your life easier.

Clients and stakeholders want every number. You want a report they'll actually read. Report shortcuts let you have both.

Until now, every report you shared was its own separate link. So either you crammed every channel into one report and hoped nobody gave up around widget 40, or you sent five links and left the client to work out which one held the answer.

Now you can add a Report shortcut widget to any report and pick another report from your account. Readers see a preview card and open the full report in one click. Passwords, themes, and interactive widgets all carry over, so the report you point to looks and behaves exactly as it does on its own.

When someone connects a source to Whatagraph, that source pulls data through their account. Fine, until that account stops working. A token expires, permissions get pulled, someone leaves the team, and the widget goes blank or throws a verification error.

If the account that owns a source loses access, Whatagraph checks whether anyone else on your team can reach that same source and quietly switches to their account in the background. Data keeps flowing. No blank widgets, no verification errors, no scramble to work out who needs to reconnect what.

Picture two people who both have access to the same Google Business Profile locations. If the account currently pulling that data breaks, Whatagraph moves to the other one automatically. Your reports or stakeholders never notice.

This matters most when you're running hundreds or thousands of sources across several people, where one expired login used to mean tracking down the right teammate and rebuilding a connection on a deadline.

The backup plan only kicks in if more than one person has connected their integration account to Whatagraph. They don't need to add any sources, just connect the account so Whatagraph knows what they can reach.

To do it: go to Sources -> click to add a new source -> pick the integration -> authorize your account. You'll see the sources you have access to, and you can stop right there. That's enough for Whatagraph to fall back on your account if another one breaks.

So, the more teammates who connect their accounts, the more resilient your sources are.

Got follow-up questions? Let us know!

Your client looks at the chart before the commentary, and at the number before the label. Three updates that give you control over how those are read, plus one that cut the time it takes to find the report you actually need.

Highlighting your best and worst rows meant defining thresholds for every metric and every client, then revisiting them each time performance moved.

Open Auto Colors instead, pick one base color, and the column shades itself across its own lowest-to-highest range in seven steps. Scan a campaign table and see where the weight sits, without maintaining a single rule.

Comparison bars used to land in an automatic shade, which doesn't always sit well next to a client's palette or leave enough contrast to tell the two periods apart at a glance.

Now you choose the color for the "Previous" period on each chart slot yourself: in the theme editor, the global editor, or on a single widget when one chart needs different treatment.

One table holding CPC and Impressions used to force the same precision on both. Either you lose the cents that matter on cost metrics, or you show impressions with two decimals no one asked for.

Decimal precision is now set on individual metric columns in tables, single-value, and media widgets. Cost per conversion to two places, impressions to zero, in the same widget.

A template name tells you less than a thumbnail does. The list/grid toggle now works on the Team templates tab, so you see the layout and the connected channels on each card and pick the right starting point without opening five of them first.

You can now track where your chosen keywords rank — and how they move against competitors over time — directly in your Whatagraph reports.

Define the keywords that matter to a client and report their positions right alongside every other channel in the same report. It's the keyword-level, competitive view that domain-level SEO data alone can't give you.

They answer different questions:

Most SEO reports are stronger with both connected.

The previous Basis (former Centro) connection loaded data live from the API every time a report opened, which meant slow widgets and frequent drops. The rebuilt integration stores data instead, so reports load reliably and breakdowns that weren't available before (tactic and line item group) are now supported.

Spend figures now align with Basis billing totals, including added value line items, so what clients see in Basis matches what you show them in Whatagraph.

Finding the right setting to style your report shouldn't require guessing which tab it lives in. Themes now control everything report-style related in one place, with a clear split between creating a new theme and editing the one already applied to your report.

All existing custom themes stay intact and can be selected exactly as before.

Long dimension values that get cut off mid-word. Stakeholders asking which campaign is which. Scrolling through 500 rows to find the one that matters. These are table problems that slowed down reporting, and we've fixed two of them.

Tables now support a built-in search bar. Turn it on from widget settings, and anyone viewing the report, editor or client, can type a value and instantly filter the table to matching rows. Campaign names, page paths, keywords, ad groups, whatever dimension you're working with.

No need to set up report-level filters or explain filtering logic to stakeholders. It's a search box.

Campaign names, GA4 page paths, UTM strings — cells now expand to show the full value instead of cutting it off. Enable wrap text from table settings.

You can now pull WhatConverts lead data directly into Whatagraph reports, no exports, no manual matching.

Blend lead count, lead score, quote value, and sales value with spend from Google Ads, Meta, or any other connected channel. Show partners which campaigns and keywords are driving real conversions, not just clicks.

Three integration updates to bring more of your data into Whatagraph, and make existing data more insightful.

Pull any dataset from your Snowflake warehouse directly into Whatagraph reports. First-party data, offline conversions, blended attribution tables. Report on it alongside your paid media and web analytics without exports or manual uploads.

Read more.

The CallTrackingMetrics integration has been completely rebuilt, and it's a meaningful upgrade for cross-channel reporting. Call data now works inside Source Groups, supports advanced aggregations, and can be segmented alongside paid media, SEO, or any other channel, the same way as all your other sources.

If you've been keeping a separate report for call performance, you don't have to anymore, just connect CallTrackingMetrics v2.

Read more.

Track orders, revenue, spend, and conversions from the Netherlands' largest e-commerce platform in the same report as every other channel. Essential for agencies and brands running retail media in the Benelux market.

Whatagraph supports two separate bol. integrations: one for retailer (sales) data and one for advertising data. They connect independently and use separate credentials. If you sell and advertise on bol., you'll need both.

Read more.