Skip to main content

Wire

Bring organic search, site traffic and social publishing from Wire into Level — linked per organization, on one screen next to your ad reports.

Paid campaigns are half the picture. The Wire section shows the organic half — search performance, site traffic and social publishing — pulled from Wire, Marketing Bar's content platform, and scoped to the organization you're in.

If your content team runs their projects in Wire, you link those projects to a Level organization once and their numbers appear here. No tab-switching, no exports.

What you need

  • The Business plan or above. Without it the section isn't in the sidebar at all.
  • The View Content Analytics permission in this organization — without it the page says "No access to Wire". Linking and unlinking projects additionally needs Manage Wire Projects. Both are granted through roles.
  • A Wire account with access to the projects you want to read.

Connecting your Wire account

With no connection yet, the page is a short explainer with three steps:

Sign in to Wire

Wire opens, you approve the access and land back here. If the browser is signed in to a personal Wire account, Use another account is offered right on this screen — it is usually the account you want.

Pick projects

Link the projects — or a whole Wire group at once — to this organization.

Read the analytics

Search, traffic and social on one screen, next to the ads.

The connection is personal — it belongs to you, the way an ad platform connection does. An organization reads Wire under a single account at a time.

Linking projects

The first time you connect, the whole screen is the project picker — the first pick is usually several projects at once. Afterwards, Add project on the project rail opens the same list as a dialog.

Linking a group takes one action and records the bundle as a group. Individual projects are linked one at a time, in order, so a half-finished batch is explainable.

Two rules keep the numbers honest:

  • A project belongs to one organization. The same project can't feed two organizations at once.
  • An organization reads Wire under a single account. If some projects here were linked under a colleague's account, a banner offers to move them to yours — one action re-homes all of them, no re-adding.

Removing a project only unlinks it from this organization. Nothing changes in Wire.

The project rail

Scope is a rail down the side, not a dropdown: the Wire account, then All projects → group → project. Every level is a real view of the data, so a single project is one click rather than a label you can't select.

The selection lives in the address, so a scoped view is linkable, and a scope that stops resolving falls back to the whole set rather than showing an error.

Search at the top of the rail filters it — useful once an agency has thirty projects linked.

Wire section with the project rail on the left, five headline metric tiles across the top, a chart below them and the content table underneath
The Wire screen: scope on the left, the five metrics across, one chart at a time.

When something is wrong

Banners sit above the numbers, never instead of them — stale figures beat an empty page as long as the page says they're stale:

BannerMeaning
Reconnect requiredWire rejected the connection — access revoked or the session expired. The numbers on screen are the last ones fetched.
Linked by someone elseProjects here were linked under another person's Wire account. Offers to move them to yours.
Access denied for some projectsYour Wire account can't read part of what's linked. The rest still shows.

Next

Reading the numbers — what the five metrics mean, which windows they cover, and how the comparisons are calculated.