Data Sources and Pixels: One per Site, One per Brand or One Shared?

Editorial team Spend Ledger

Start with the question the structure needs to answer

A data source or pixel connects activity on a website with an advertising business’s measurement and audience tools. The choice is not simply how many sources to create. It is how the business wants to group its sites, brands and teams—and how clearly it needs to understand what happened on each one.

Three common approaches are a separate source for each website, one source for each brand, or a shared source for everything. Each can be workable. The right fit depends on how the sites relate, who needs access, what the business may sell or reorganise, and how much effort it can devote to keeping tracking events consistent.

A source is a work tool, not a shortcut around platform requirements. Its setup and permissions should follow the platform’s current rules. Before making structural changes, check the relevant help and policy pages; available features and requirements can change.

It also helps to separate two decisions. The first is where data is collected. The second is how teams organize campaigns, reporting and permissions around that data. A business may use a shared source while keeping campaigns and reporting separate, or separate sources while coordinating them under a common business structure. Do not assume that one automatically determines the other.

One source for each website

A source for each website gives each site a distinct measurement boundary. This can make it easier to inspect activity, troubleshoot missing or inconsistent events, and understand which website is associated with a particular audience or campaign. It is often the clearest arrangement when sites serve different purposes or are managed by different teams.

Separation can also help with access control. A team working on one site may need access to that site’s source without needing to inspect data from another. Clear boundaries can reduce accidental changes and make responsibilities easier to explain.

The trade-off is operational work. Each source needs suitable configuration, event definitions and ongoing checks. When several sites share the same business process, maintaining them separately can lead to differences in event names or in what an event means. A purchase, lead or registration should represent a consistent action wherever the business intends to compare it. Separate sources do not ensure that consistency; the team has to establish and maintain it.

This arrangement is less convenient when the business wants a unified view of related activity across sites. That may still be possible through reporting processes, but it can require more careful interpretation than using a common source. Consider whether the benefits of clear site boundaries outweigh the extra work of maintaining parallel setups.

One source for each brand

A brand-level source can be a useful middle ground when a brand operates more than one website or digital property, but those properties are managed as a connected business. It gives the brand a shared measurement structure without necessarily combining every brand’s data.

This approach can support consistent reporting across sites that share a customer journey or marketing team. It may also simplify coordination when campaigns involve more than one site belonging to the same brand. However, those benefits depend on thoughtful event design. If one site uses an event to mean something different from another, a shared source can make a report look unified while obscuring important differences.

Brand boundaries are not always obvious. A company may use one brand for several services, or several brands may share a website, checkout process or operational team. Choose a grouping that reflects how the business actually works, rather than relying only on names or visual identity.

Access needs deserve particular attention. If brand teams are distinct, a brand-level structure may make permissions easier to manage than a company-wide source. But the source itself is not a substitute for reviewing who has access and what they can do. Keep permissions aligned with current responsibilities, and use the platform’s supported controls.

One shared source for the business

A shared source can suit a business whose websites are closely connected and whose teams need a consolidated view. It may reduce duplicated setup and make it easier to apply common event definitions across properties. When the same action has the same meaning throughout the business, a shared structure can support clearer comparisons.

The central risk is loss of useful distinction. Reports may combine activity that should be understood separately, and audiences may draw on signals from sites that serve different purposes. The source can be shared without the business treating all visitors as interchangeable, but doing that well requires clear conventions and careful analysis.

A shared source can also make access decisions more consequential. A person or agency with access to a central source may be able to work with data connected to several parts of the business. Give access according to role and need, not merely because a team once helped with one project. Review permissions when responsibilities change.

Shared does not mean unstructured. The team still needs a reliable way to identify which site generated an event, what the event represents and whether the implementation is behaving as intended. If that context is difficult to preserve, the apparent simplicity of one source may shift work into reporting and governance.

Audience quality and reporting clarity

The number of sources does not, by itself, make an audience more or less valuable. Audience usefulness depends on the relevance and quality of the underlying activity, the way events are defined, and whether the audience matches the campaign’s purpose. Combining sites can add useful context when they genuinely relate; it can also mix unrelated activity and make an audience harder to interpret.

Ask what an audience is meant to represent. Is it people who took a particular action on one site, people who interacted with a brand across its properties, or a broad group from the whole business? The structure should make that definition understandable to the people who build campaigns and assess results.

Reporting clarity follows a similar principle. Separate sources can make site-level analysis more direct, while a shared source can make cross-site analysis more convenient. Neither guarantees accurate reporting. Clear event names, consistent meanings, sensible site identification and documented assumptions matter in every arrangement.

Before consolidating sources, check whether the reporting questions can be answered without merging the underlying data. Before separating them, check whether the team can still compare related activity in a consistent way. The best structure is the one that makes the important distinctions visible without creating avoidable maintenance.

What changes when a site is sold or an agency leaves?

A website sale, brand reorganisation or agency departure can expose weaknesses in a structure that seemed convenient during routine work. Before a change, identify which business owns or controls the relevant website, source, advertising assets and permissions under the platform’s rules. Do not assume that a source can simply be handed over, split or reassigned in whatever way is most convenient. Check the platform’s official guidance and use its supported process.

With a site-specific source, it may be easier to identify which measurement setup relates to the site being sold. That does not automatically settle what can transfer, what should remain with the existing business, or what data and access arrangements are permitted. Agree those points in writing as part of the commercial and operational handover, and confirm them through official support channels where the rules are unclear.

A brand-level or shared source can make a sale more complicated if several properties or teams depend on it. The parties may need to plan a new setup, preserve appropriate records, or change permissions in an orderly way. Do not treat access to an account or source as a substitute for clarifying ownership and authority.

When an agency leaves, review and remove access that is no longer needed through the platform’s official controls. Also confirm that the business retains access to its own work records and understands how events are configured. An agency’s departure should not depend on informal credentials or undocumented knowledge. Set expectations about access, configuration, reporting and handover in the agreement from the outset.

The effort of keeping events consistent

Event consistency is often the hidden cost of choosing a structure. A single shared source can make common definitions easier to centralize, but only if the sites implement them in compatible ways. Separate sources can make local changes easier to isolate, but each implementation needs its own review and documentation.

Start by listing the actions that matter for measurement and stating what each one means in plain language. Note where the action occurs, what evidence confirms it, and whether the meaning is the same across sites. Keep a record of changes so that reporting differences can be explained rather than mistaken for changes in business performance.

When sites have different customer journeys, do not force their events into identical definitions merely to make the structure look tidy. Preserve meaningful differences and label them clearly. Conversely, if the same action is being measured in several places, avoid allowing the definition to drift without a reason.

Assign responsibility for checking the setup. This may involve the site team, marketing team or agency, but the business should know who is accountable and how changes are reviewed. Use the platform’s supported diagnostics and documentation, and consult its help materials when behavior or requirements are uncertain.

A simple decision guide

Use these questions to compare the options:

• Do the websites serve distinct audiences or business purposes? If so, separate sources may make boundaries and reporting clearer.
• Do several sites belong to one brand and share a meaningful customer journey? A brand-level source may offer a practical balance.
• Are the sites closely connected, with common event meanings and a genuine need for combined analysis? A shared source may be easier to coordinate.
• Do separate teams need separate access? Prefer a structure and permission plan that limits access to what each role requires.
• Could a site or brand be sold, separated or moved to another team? Choose a structure that makes the relevant assets and responsibilities identifiable, then verify transfer rules with the platform.
• Can the business maintain consistent event definitions across the chosen setup? If not, reduce complexity or improve ownership and documentation before expanding it.
• Can the team explain what each audience and report includes? If the answer is unclear, the structure needs clearer boundaries or better labeling.

There is no universal best arrangement. A business with distinct sites and owners may value separation; a connected brand may favor a brand-level structure; closely integrated operations may prefer a shared source. Whichever approach is chosen, document the reason, keep access current, define events in plain language and revisit the setup when the business changes. Check current requirements on the platform’s own help and policy pages before making changes.