Switching from network-level to account-level tracking

Overview

Sometimes you might start with network-level tracking and decide later that you want to track each account separately. This section explains what changes you need to make and what to expect.

How the setup changes

Before: network-level tracking. One pixel feeds a single set of network-level audiences and conversions.

flowchart LR
    S1["Site A"] --> NPixel
    S2["Site B"] --> NPixel
    S3["Site C"] --> NPixel
    subgraph NetworkAccount["Network account"]
        NPixel["Network pixel<br/>(Network ID)"]
    end
    NPixel --> NAud["Network-level audience<br/>and conversions"]

After: account-level tracking. Each site fires its own account pixel, with separate audiences and conversions per account.

flowchart LR
    S1["Site A"] --> AP1
    S2["Site B"] --> AP2
    S3["Site C"] --> AP3
    subgraph Accounts["Accounts"]
        AP1["Account A pixel<br/>(Account A ID)"]
        AP2["Account B pixel<br/>(Account B ID)"]
        AP3["Account C pixel<br/>(Account C ID)"]
    end
    AP1 --> A1["Account A audiences<br/>and conversions"]
    AP2 --> A2["Account B audiences<br/>and conversions"]
    AP3 --> A3["Account C audiences<br/>and conversions"]

The role of the pixel ID

The ID embedded in each page's pixel determines the tracking level:

• Network-level: embed the Network ID on every page, across all sites, regardless of which account a site belongs to. Conversions are attributed to the correct account using click data.
• Account-level: embed each site's own Account ID. That account's conversions and audiences remain isolated to it.

Conversions and audiences move together

When you switch from network-level to account-level tracking, both conversions and audiences will be separated per account. You cannot have account-level conversions with network-level audiences. If your pixel fires with an Account ID, both conversions and audiences will be tracked at the account level.

When to make this change

Moving from network-level to account-level tracking is recommended when:

• You manage different brands with different websites and do not want their data mixed.
• You need dedicated retargeting lists per brand.
• You want stricter separation of reporting, optimization and budgeting per account.

💁🏻

Need a hand?

If your setup is complex (multiple brands, shared domains, or mixed funnels), your Taboola Account Manager can review your current pixel implementation and recommend the safest migration plan.

How to switch

Step 1: Update the pixel implementation

1. Identify where the current pixel is implemented
   • Check which websites/brands are using the same Network ID today.
   • If all brands currently share the same Network ID, their audiences and conversions are combined.
2. Decide per site/brand which ID to use going forward
   • For completely different websites/brands, it usually makes more sense to use a different Account ID per brand (the Account ID of the relevant Taboola account).
   • For one site used by several accounts (e.g., country-based accounts pointing to the same domain), a Network ID can still be the right solution.
3. Implement the new Account IDs
   • On each site/brand where you want separate tracking:
     • Replace the existing Network ID with the relevant Account ID, or
     • Add a separate pixel instance that fires with the correct Account ID (depending on your setup and your tag manager).
   • Make sure this change is deployed on all relevant pages in the funnel (landing pages, forms, checkout, thank-you pages, etc.).

Your developer or tag manager owner will usually handle this step. Taboola support can confirm which IDs to use, but cannot change the code on your site.

Step 2: Create account-level conversion rules

Once the pixel is firing with the Account ID:

1. In each account that should track its own conversions:
   • Open Realize, and select that account (top, left).
   • In the sidebar (left), select Tracking.
   • Click New Conversion.
   • Recreate the conversion rules that you previously had at the network level (event-based or URL-based).
2. Confirm that:
   • The event names (for event-based conversions) match exactly what your pixel is sending.
   • The URL rules match the actual URLs for that brand/site.

From this point on, new conversions are logged only for that account, and network-level conversion rules no longer pick up events firing with just the Account ID.

Step 3: Create account-level audience rules

🚧

Rebuild your audiences

When you switch IDs, your audiences do not transfer. You must create new account-level audience rules for each account.

New audiences build only from events fired with the new Account ID. Your historical audience data remains available.

To create brand-specific retargeting audiences:

1. For each account that should have its own audiences:
   • Open Realize, and select that account (top, left).
   • In the sidebar (left), select Tracking.
   • Navigate to the Audiences section.
   • Click Create Audience or New Audience Rule.
   • Define your audience rules based on pixel events (for example: "Visited Brand A site", "Added to cart on Brand B").
   • Make sure the event names match what your pixel is sending with the Account ID.
2. Wait for audiences to build:
   • New account-level audiences start building from pixel events fired with the Account ID.
   • It may take time for audiences to reach sufficient size for targeting.
   • Historical network-level audiences remain available but will not update with new data.
3. Use account-specific audiences in campaigns:
   • Once audiences have built up, use them in your campaign targeting.
   • Each account only has access to audiences built from its own pixel events.

What to expect afterward

• Historical network-level conversions and audiences remain in your reports; they are not deleted.
• After the switch, new data starts populating at the account level based on the new pixel implementation.
• Expect a transition period where old network-level audiences still exist while new account-level audiences and conversions build up.