Conversion deduplication

Overview

Taboola uses deduplication logic to prevent duplicate conversions from being counted. The exact logic depends on various factors - e.g. single-method tracking vs dual-method tracking.

Key concepts

  • Click ID - When the user clicks on a creative, Taboola assigns a Click ID to that event. Only events from the same Click ID context (i.e. from the same click) are deduplicated.
  • Dual-method tracking - each event is tracked via 2 methods (S2S and pixel).
  • Single-method tracking - each event is tracked via 1 method only (S2S or pixel).
πŸ“˜

Best practice

Use dual-method tracking (i.e. both S2S and pixel). This provides redundancy and results in a more complete picture of your conversions.

Deduplication logic

The following logic applies:

  • If the same event (within the same Click ID context) is received via S2S and Pixel, the S2S event is kept.
  • Otherwise, events (within the same channel) are deduplicated using heuristic deduplication.

Dedup examples

Example 1: dual-method tracking

Click IDTimeMethodEvent NameOrder IDResult
ABC12310:00:00Pixelpurchase456❌ DEDUPLICATED
ABC12310:01:00S2Spurchase456βœ… KEPT

Same event received via S2S and Pixel - S2S event is kept


Example 2: same-method tracking

Click IDTimeMethodEvent NameOrder IDResult
ABC12310:00:00S2Spurchase456βœ… KEPT
ABC12310:01:00S2Spurchase456❌ DEDUPLICATED

Second S2S event deduplicated (within 1-minute window)


Example 3: different Click IDs

Click IDTimeMethodEvent NameOrder IDResult
ABC12310:00:00S2Spurchase456βœ… KEPT
XYZ78910:01:00S2Spurchase456βœ… KEPT

Different Click IDs = different user journeys, both events counted


Related docs