EF Helpdesk

Traffic Blocking lets you filter out unwanted traffic sources by creating rules based on sub IDs and source parameters, helping maintain traffic quality and protect your Offers from unauthorized or low-quality traffic.

Overview

Traffic Blocking is one of the defense lines against unauthorized or low-quality traffic.

Instead of reactively dealing with poor-quality traffic, you can proactively prevent specific sources from accessing your offers based on their tracking parameters.

Key Terms

Key terms related to traffic blocking and filtering.

➔ Sub ID: Tracking parameter used to identify traffic sources.
➔ Match Type: How the blocking rule compares values (contains, equals, etc.).
➔ Source ID: Unique identifier for traffic sources.
➔ Traffic Block: Rule that prevents specific traffic from reaching Offers.
➔ Filter: Criteria used to identify unwanted traffic.

Why Use Traffic Blocking?

Protect Advertiser Relationships: Ensure only approved traffic reaches Offers
Maintain Traffic Quality: Filter out known problematic sources
Prevent Fraud: Block suspicious traffic patterns
Control Costs: Stop unwanted Clicks before they happen
Enforce Compliance: Ensure Partners follow traffic requirements

When to Use Traffic Blocking

Blocking specific subsets of partner traffic
Preventing unauthorized media buying accounts
Stopping traffic from prohibited geographic areas
Filtering out non-compliant traffic sources
Managing allowed traffic sources per Offer

Setting Up Traffic Blocking

Configure rules to block unwanted traffic from reaching your offers.

Creating a New Block

Navigate to Partners -> Traffic Blocking

Click Block New Source

Fill in required information:

Select Partner

Choose Offer

Set Status (Active/Inactive)

Configuring Sub ID Filters

For each Sub ID (1-5), you can:

Enable/disable filtering

Select Match Type:

Begins With

Contains

Does not contain

Does not match

Ends With

Exact Match

Enter Value to block

Source ID Filtering

Enable Source ID filtering

Select Match Type

Begins With

Contains

Does not contain

Does not match

Ends With

Exact Match

Enter Value to block

Save the block

Real-Life Examples

Let's see how traffic blocking works in a real scenario. This example shows how you can control traffic quality when dealing with multiple sources from the same Partner.

Scenario: Network needs to block specific platform identifiers associated with compromised traffic.

Setup

Partner: Selected Partner

Source ID: Enable

Match Type: Exact Match

Value: "875_432"

How it works

When Partners send traffic, each source gets a unique identifier (like "875_432")

Network can block specific source IDs when they detect:

Non-compliant traffic sources

Compromised tracking IDs

Unauthorized bot traffic

Blocking one Source ID doesn't affect other legitimate sources from the same Partner.

Real Application

Partner has multiple traffic sources

Each source automatically gets assigned an ID (e.g., "875_432", "875_433", "875_434")

If "875_432" is detected as problematic:

Create block with Exact Match for that ID

Other source IDs continue running normally

Partner can still send traffic from other legitimate sources

This setup allows for almost "surgical" precision in blocking problematic sources while maintaining good traffic flow from the same Partner's other legitimate sources.

This targeted approach to traffic blocking lets you maintain quality without disrupting your good traffic sources.

You can quickly address issues with specific sources while keeping your valuable partnerships running smoothly.