When to use the network pixel (network-level conversions)

Below are common scenarios where the network pixel is the right choice.

Example 1: Same domain used across multiple accounts

Use case

You have multiple Taboola accounts that all send traffic to the same domain, and you don't want to implement multiple pixels on the same pages.

If the conversion rule is identical for all accounts, you can:

• Implement the network pixel on the site
• Define a single conversion rule at the network level (event or URL-based)
• Attribute conversions back to the correct campaigns in each account

Illustrative example – Nike

• Network: Nike
• Accounts:
  • Nike – US
  • Nike – Canada
  • Nike – Australia
• Funnel:
  • LP A – Seasonal Sales
  • Rule X – Lead (e.g., submit email for a discount)

Flow diagram:

flowchart TD
    subgraph Accounts
        US["Nike - US account"]
        CA["Nike - Canada account"]
        AU["Nike - Australia account"]
    end

    LP["Seasonal Sales landing page (shared domain)"]
    Pixel["Network pixel (Network ID)"]
    Conv["Network-level 'Lead' conversion rule"]

    US --> LP
    CA --> LP
    AU --> LP

    LP --> Pixel --> Conv

You set up one "Lead" conversion at the network level and run separate campaigns in each account. The system attributes conversions to the correct account and campaign, even though the pixel and conversion rule are shared.

Example 2: Arbitrage or lead generation with same funnel across sites

Use case

You operate multiple sites/accounts but they all share the same conversion funnel (for example, different refinance offers, but always a lead form).

This is ideal for a network-level conversion event.

Recommendation: In arbitrage/lead-gen scenarios, we strongly recommend turning off view-through conversions to avoid potential misattribution across sites.

Illustrative example – "Arbitrageur"

• Accounts:
  • Home refinance
  • Auto refinance
  • Credit refinance
• Funnel:
  • Rule X – Lead (form submission)
  • LP A – Home Site
  • LP B – Auto Site
  • LP C – Credit Site

You define a single "Lead" conversion event at the network level. All sites share the same funnel; the pixel and conversion rule are reused across accounts. Turning off view-throughs helps prevent cross-site "spillover" in reporting.

Example 3: Same funnel, different domains

Use case

You use different domains in different accounts (e.g., ccTLDs by country), but the marketing funnel and conversion definition are identical.

Illustrative example – Nike international sites

• Accounts:
  • Nike – US (us.nike.com)
  • Nike – Canada (ca.nike.com)
  • Nike – Australia (au.nike.com)
• Funnel:
  • Rule X – Purchase
  • LP A – US Site
  • LP B – CA Site
  • LP C – AUS Site

Each country has its own site, but the checkout process and final "purchase" event are consistent. You can define a single "Purchase" event at the network level and track purchases across all three accounts.

Example 4: Mix of shared and unique funnels

Use case

Some of your accounts share the same funnel, but others have unique flows that require different conversion logic.

You can combine:

• Network-level conversions for accounts with identical funnels
• Account-level pixels and conversions for accounts with unique funnels

Illustrative example – Nike with a UK microsite

• Accounts:
  • Nike – US
  • Nike – Canada
  • Nike – Australia
  • Nike – UK (unique microsite for a special campaign)
• Funnel:
  • Rule X – Lead (network-level)
  • Rule Y – Purchase (network-level)
  • LP A – Seasonal Sales
  • LP B – Canada Lead Page
  • LP C – UK-only Microsite (unique experience)

US, Canada, and Australia share the same funnel and use the network-level events. The UK microsite has a unique experience, so you can define account-level conversion rules specifically for that microsite, while still using network-level rules elsewhere as appropriate.

When not to use the network pixel

There are cases where a network-level pixel and shared conversions are not recommended.

Scenario 1: Different funnels and landing pages by account

If each account runs distinct content on different landing pages and uses different conversion definitions, you should not use a single network-level rule.

• Use account-level pixels and conversions instead.
• This ensures each account's conversions reflect its specific funnel and KPIs.

Scenario 2: Agency managing many different brands

If you are an agency and each account represents a different brand, using one network pixel + shared conversions can lead to unrelated cross-conversions in reporting.

• In this case, keep separate account-level implementations per brand.
• This prevents one brand's activity from being attributed to another's campaigns.