Taboola Ads

Datafly Signal delivers conversion events to Taboola server-to-server for native advertising attribution, campaign optimisation, and audience targeting.

This blueprint is currently in alpha.

Prerequisites

Before configuring Taboola in Signal, you need:

  • A Taboola Ads advertiser account
  • A Backstage API client ID and client secret (OAuth)
  • Your advertiser Account ID

Get your Taboola credentials

  1. Sign in to Taboola Ads.
  2. Your Account ID is shown in the dashboard URL and on account settings.
  3. Request a Backstage API application from your Taboola account manager; once issued you receive a Client ID and Client Secret.
  4. Exchange them for an OAuth access token via the Backstage authentication flow.

Configure the integration in Signal

  1. In the Management UI, go to Integrations → Add Integration.
  2. Select Taboola Ads from the catalogue.
  3. Give the integration a name (for your reference).
  4. Fill in the required fields:
FieldRequiredDescription
account_idYesTaboola advertiser account ID.
client_idYesBackstage API client ID.
client_secretYesBackstage API client secret.
  1. Choose which pipeline(s) this integration should run on.
  2. Select consent categories (defaults to marketing).
  3. Click Save.

Event mapping

Signal eventTaboola event
pagepage_view
Product Viewedview_content
Product Addedadd_to_cart
Order Completedpurchase

To customise, edit the integration’s Field Mappings.

Identity

Signal sends the following identity signals to Taboola, subject to consent and availability:

CapabilityNotes
Taboola user IDt_gid from the Taboola sync
Hashed emailSHA-256 (lowercase, trimmed)
Client IP / User-AgentForwarded from the original request

This integration is gated on the marketing canonical consent category.

Verify it’s working

  1. In the Management UI, open Pipelines → your pipeline → Live Events and trigger a test event.
  2. The event appears in the live feed; inspect the payload sent to Taboola.
  3. Check Reports → Conversions in the Taboola Ads dashboard.

Troubleshooting

401 Unauthorized. Confirm the client ID/secret are still valid in Backstage and that the resulting access token has the conversion-upload scope.

Missing t_gid on events. Taboola’s t_gid is set by their own sync; if you have no t_gid traffic, attribution falls back to hashed email / IP / UA.

See also