Perion

Send conversion events to Perion for search and display advertising attribution, campaign measurement, and performance optimisation across the Perion ad network.

Prerequisites

Complete these steps in the Perion platform before configuring the integration in Signal.

Create or access your Perion account

Log in to Perion advertiser dashboard. If you don’t have an account, contact Perion sales to set up an advertiser account for search and display advertising across the Perion network.

Get your Advertiser ID from the dashboard

Navigate to your advertiser dashboard. Your Advertiser ID is displayed in the account overview or under Account Settings. If you cannot locate it, contact your Perion account manager who can provide it directly.

Generate an API key from account settings

Navigate to Account Settings > API in the Perion dashboard to generate an API key for server-side event delivery. If the API section is not available, contact your Perion account manager to request API access be enabled for your account.

Configuration

Field	Type	Required	Description
`advertiser_id`	string	Yes	Your Perion advertiser ID. Found in the Perion dashboard under Account Settings.
`api_key`	secret	Yes	API key for authenticating server-side event delivery. Generate in the Perion dashboard under Account Settings > API.

Signal Setup

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Perion or filter by Advertising.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/perion/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Perion",
    "variant": "default",
    "config": {
      "advertiser_id": "perion-adv-12345",
      "api_key": "ak_perion_abc123..."
    },
    "delivery_mode": "server_side"
  }'

Event Mapping

Signal Event	Perion Event	Description
`purchase`	`conversion`	Completed transaction with revenue
`sign_up`	`lead`	New user registration or lead capture
`page_view`	`page_view`	Standard page view tracking
`add_to_cart`	`add_to_cart`	Product added to shopping cart
Custom events	Custom conversion	Map any Signal event to a custom Perion conversion type via blueprint configuration

Event mappings are fully configurable through blueprints. The table above shows common default mappings — you can customise these to match your campaign goals.

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Perion API. No client-side scripts are loaded for this integration.

Testing

Install the integration with your Advertiser ID and API key.
Trigger a test event (e.g. a purchase) on your site with the Datafly.js collector active.
Check the Live Events view in Signal to confirm the event was captured.
Verify the event appears in the Perion advertiser dashboard under conversion reporting.
Check the Delivery Log in Signal for confirmation of successful delivery (HTTP 200 response).

⚠️

Conversions may take up to 30 minutes to appear in Perion reporting due to processing delays on the Perion side.

Troubleshooting

Issue	Resolution
`401 Unauthorized`	Verify your API key is correct and has not been revoked. Regenerate in Perion Account Settings > API if needed.
`404 Not Found`	Check that the Advertiser ID matches your account exactly.
Events not appearing in Perion	Confirm the integration is enabled in Signal and check the Delivery Log for errors. Conversions may take up to 30 minutes to appear.
`400 Bad Request`	Verify the event payload format. Check blueprint mappings for correct field names.
`429 Too Many Requests`	Perion rate limits are being hit. Signal will automatically retry with backoff.

Visit Perion documentation for full API documentation and credential setup instructions.

Nextdoor CAPI Pinterest Ads