Network-level conversions
Overview
If you manage multiple Taboola accounts under a single network, you have 3 options for tracking conversions:
Flow 1: Separate setup per account - For each account, set up a separate pixel, a separate set of conversion rules, and separate audiences.
Flow 2: Network-level setup - Set up one network pixel, one set of network-level conversion rules, and network-level audiences. The network pixel can be embedded across different sites and will track conversions and build audiences for all accounts in your network.
Flow 3: Mixed approach - Use network-level conversions and audiences for accounts that share the same funnel, and account-level conversions and audiences for accounts with unique funnels. You can implement both network pixels and account pixels on different sites, or even on the same site if needed.
Audiences
Your choice of pixel setup also affects the audiences available to you:
- Network-level audiences include users from all sites/brands where the network pixel fires. If you target a network-level audience in one account's campaigns, you might reach users who interacted with other accounts in the network.
- Account-level audiences only include users from sites where that account's pixel fires, giving you brand-specific retargeting lists.
What are audiences?Audiences are lists of users who have taken specific actions on your website. You create audience rules based on pixel events, then use those audiences to target your campaigns — showing ads to people who have previously interacted with your site.
For more detail, and additional terminology, see the Glossary.
Not sure which approach to use?For beginners, start with account-level tracking. Network-level conversions are best when multiple accounts share the same conversion funnel and you want to simplify management with a single set of conversion rules.
How conversion tracking works
Standard flow (account-level conversions)
To track conversions for Account A:
- Open Realize, select Account A, and generate a pixel code snippet.
The pixel will contain the Account ID for Account A.
- Implement the pixel on the relevant website.
- Open Realize, select Account A, and create conversion rules.
These will track conversions for Account A.
- Run campaigns in Account A.
- When the account pixel fires an event, Taboola looks for a conversion rule under Account A with a matching event name.
- Conversions appear in Account A's reports.
Key point: Each account needs its own pixel implementation (with its own Account ID) and its own conversion rules.
flowchart TD
subgraph Accounts
A["Account A"]
B["Account B"]
C["Account C"]
end
UserA["User clicks ad"] --> A
UserB["User clicks ad"] --> B
UserC["User clicks ad"] --> C
A --> PixelA["Account A pixel fires<br/>(Account A ID)"]
B --> PixelB["Account B pixel fires<br/>(Account B ID)"]
C --> PixelC["Account C pixel fires<br/>(Account C ID)"]
PixelA --> ConvA["Account A<br/>conversion rule"]
PixelB --> ConvB["Account B<br/>conversion rule"]
PixelC --> ConvC["Account C<br/>conversion rule"]
Network-level flow (network-level conversions)
To track conversions across Account A, Account B, and Account C using 1 pixel:
- Open Realize, select the network account, and generate a network pixel code snippet.
The pixel will contain the Network Account ID.
- Implement the pixel on the relevant website(s).
The same code works for all accounts in the network.
- Open Realize, select the network account and create conversion rules.
You only need to do this once (not per account). These will be used across all accounts.
- Run campaigns in Account A, Account B, and Account C.
- When the network pixel fires an event, Taboola looks for a network-level conversion with a matching event name.
- Conversions are attributed to whichever account had the most recent click, and will appear in that account's reports.
Key point: One pixel implementation (with Network Account ID) and one set of conversion rules, but conversions are attributed to individual accounts based on which account's campaign had the most recent click. If a network-level conversion rule includes "total conversions", all sub-accounts will use it for optimization by default (can be overridden at the campaign level).
Mixed flow (network-level and account-level conversions)
You can use both network-level and account-level conversions together. This is useful when some accounts share the same funnel while others have unique conversion flows.
Example scenario:
- Account A, B, C share the same funnel → Use network pixel and network-level conversion rules
- Account D has a unique funnel → Use account pixel (Account D ID) and account-level conversion rules
How it works:
- Implement the network pixel on sites used by Account A, B, and C.
- Implement Account D's pixel on Account D's site.
- Create network-level conversion rules for conversions shared across Account A, B, and C.
- Create account-level conversion rules in Account D for its unique conversions.
- When a pixel fires:
- Events fired with the Network Account ID match network-level conversion rules.
- Events fired with Account D's Account ID match Account D's conversion rules.
Key point: Network-level and account-level conversions don't conflict because they match different pixel IDs. You can have both types with the same event name — each will match its corresponding pixel ID.
Where was the conversion created?To see where a conversion rule was created (network vs. account):
- Open Realize, and select your network account (top, left).
- In the sidebar (left), select
Tracking.- In the conversions list, look at the
Account Namecolumn for each conversion.
How to create the network pixel
To start using network-level conversions, first create the network pixel.
- Open Realize, and select your network account (top, left).
- In the sidebar (left), select
Tracking. - Click "Create Pixel" to generate your network-level pixel code.
- Implement this pixel on your site(s) according to your usual implementation process.
All accounts under this network will be able to use conversions defined at the network level.
How to create a network-level conversion
Once the network pixel is in place, you can define conversions that apply across all accounts in the network.
- Open Realize, and select your network account (top, left).
- In the sidebar (left), select
Tracking. - Click "New Conversion".
- Define your conversion rule, for example:
- Event-based: purchase, lead, registration, etc.
- URL-based: thank-you page URL, checkout confirmation URL, etc.
- Save your conversion.
Default optimization behavior
When you create a network-level conversion rule and include it in "total conversions", all sub-accounts in your network will use that conversion rule for campaign optimization by default. This means campaigns across all accounts will optimize for that network-level conversion unless you override it at the campaign level.
Campaign-level overrideYou can override the default network-level conversion at the campaign level by selecting a different conversion goal for that specific campaign. This allows you to:
- Use network-level conversions as the default across all accounts
- Customize optimization goals per campaign when needed
- Select any conversion visible to the account (network-level or account-level)
What's next?
- Switching from network-level to account-level tracking - Step-by-step guide for migrating from network-level to account-level tracking.
- Glossary - Definitions of key terms used in this documentation.
Related docs
Getting Help
Unsure whether to use a network pixel or account-level pixel? Reach out to your Taboola Account Manager for guidance.
Updated about 11 hours ago
