API integrated traffic channels
Understanding which traffic channels connect seamlessly with RedTrack is key to unlocking automation, accurate attribution, and smarter campaign management. RedTrack.io has developed API and CAPI integrations with 20+ ad networks, giving users the ability to automate cost updates, send conversion data back to platforms, and enable advanced optimization features.
This guide helps you navigate the Traffic Channel integration status page so you can quickly see:
- Which networks support API or CAPI integrations
- What types of data each integration can exchange
- Which automation scenarios are available (CAPI events, cost updates, rules, etc)
- How these integrations impact your tracking accuracy and campaign optimization
If you’re looking to understand your current integrations or explore new automation opportunities, this guide provides a clear overview of everything RedTrack supports and how it benefits your workflow.
CAPI integrations
Why Conversion API (CAPI) matters in RedTrack
The purpose of this feature is to send conversion data back to the ad network for more accurate attribution and more intelligent campaign optimization driven by the ad network’s AI.
In addition to multiple S2S postbacks, RedTrack users can leverage prebuilt Conversion API (CAPI) integrations to share event and conversion data with their advertising platforms automatically. Unlike S2S postbacks, which only send conversions attributed to that specific network’s clicks, CAPI allows you to send all conversions — including those generated from other traffic channels or organic channels.
By sending richer and more complete conversion data directly to the ad network’s API, advertisers give the platform’s algorithms a deeper understanding of customer behavior. This allows the ad network to optimize targeting and bidding more effectively, deliver ads to higher-value audiences, and improve overall campaign performance. As a result, advertisers benefit from more accurate attribution, reduced cost per acquisition (CPA), and higher return on ad spend (ROAS).
CAPI-Integrated traffic channels in RedTrack
Check below the list of RedTrack’s available CAPI integrations:
API-based Cost updates
This feature lets RedTrack display real-time cost data for your campaigns. RedTrack can update performance data every 6 hours, 30, 15, or 5 minutes, depending on the traffic channel API and your subscription plan.
To enable this:
1. In your traffic channel settings, set the frequency and depth of cost updates.
2. In your campaign settings, select the CPC cost model.
For details go to:
– Auto update costs guide.
– Our YouTube video explaining API cost update logic in RedTrack.
The table below demonstrates traffic channels and their attributed levels of auto-cost update:
Rules
These rules are applicable depending on the Traffic channel and the depth of their integration level with RedTrack.
The purpose of this category of rules is to notify you when specific performance conditions are met. Notification rules do not make any changes to your traffic, they simply send alerts based on the criteria you define.
Notification rules can be configured to send alerts via:
- Webhook
These rules monitor the conditions you define. When the specified criteria are met, RedTrack sends a notification to the selected destination, allowing you to review the situation and take action if needed.
Notification rules are available for all Traffic channels and support all object types.
The purpose of this category of rules is to automatically resume traffic after it has been paused or stopped. Start rules help ensure that campaigns and other traffic objects become active again when the conditions you define are met.
Start rules can be of the following types:
- Start Campaign
- Start Ad set
- Start Ad
These rules monitor the performance of objects (campaign, ad set, ad). When user-defined criteria are met, the selected objects are automatically started.
Check out the table below to see which types of Start rules are currently available for RedTrack-integrated Traffic channels:
The purpose of this category of rules is to automatically exclude underperforming placements from your campaigns to reduce wasted ad spend and improve overall performance.
Blacklist Placement rules monitor the performance of placements. When user-defined criteria are met, the selected placements are automatically added to the traffic channel’s blacklist, preventing them from receiving further traffic.
Check out the list below to see which Traffic channels currently support Blacklist Placement rules:
The purpose of this category of rules is ad waste prevention. Pause rules can be of the following types:
- Pause Campaign
- Pause Ad set
- Pause Ad
These rules monitor the performance of objects (campaign, ad set, ad). When user-specified criteria are met, the set rule will pause the objects to prevent ad waste.
Check out the table below on which types of Pause rules are currently available for the RedTrack integrated Traffic channels:
The purpose of this category of rules is ad waste prevention as well. Meaning, these rules monitor the performance of objects (campaign, ad set, ad). When user-specified criteria are met, the set rule will pause the objects to prevent ad waste. The rule will continue to monitor paused objects’ performance. Should this performance improve because of delayed conversions, they will be reactivated.
Pause and Restart rules can be of the following types:
- Pause & Restart Campaign
- Pause & Restart Ad set
- Pause & Restart Ad
Check out the table below on which types of Pause and Restart rules are currently available for the RT integrated Traffic channels:
The purpose of this category of rules is to scale successful campaigns. These rules monitor the performance of objects (campaigns, ad sets). When user-specified criteria are met, the set rule will try to improve overall performance by increasing bid, budget, or by duplicating ad sets.
Scale rules can be of the following types:
- Change Campaign budget
- Change Ad set budget
- Change Ad set bids
- Duplicate Ad set
Check out the table below on which types of Scale rules are currently available for the RT integrated Traffic channels:
The purpose of this category of rules is to optimize traffic distribution. Change Weight rules can be applied to the following objects:
- Lander
- Offer
These rules monitor the performance of the selected object. When user-specified conditions are met, the rule adjusts its weight by the value you set: a positive value increases the weight, while a negative value decreases it.
The purpose of this category of rules is ad waste prevention. Remove from Rotation rules can be applied to the following objects:
- Lander
- Offer
These rules monitor the performance of the selected object. When user-specified conditions are met, the rule removes it from the rotation, so it no longer receives traffic.
If you haven’t found your traffic channel in this list, email us to [email protected]. We’ll be glad to add it for you.
Articles
- Google Ads and RedTrack
- Meta and RedTrack
- TikTok and RedTrack
- Bing Ads and RedTrack
- Snapchat and RedTrack
- ChatGPT Ads and RedTrack
- AppLovin and RedTrack
- Taboola and RedTrack
- Pinterest and RedTrack
- Outbrain and RedTrack
- BIGO Ads and RedTrack
- Exoclick and RedTrack
- MGID and RedTrack
- Zeropark and RedTrack
- Adskeeper and RedTrack
- Adnium and RedTrack
- Yeesshh and RedTrack
- TrafficStars and RedTrack
- ReachEffect and RedTrack
- MegaPu.sh and RedTrack
- HilltopAds and RedTrack
- TrafficJunky and RedTrack
- Revcontent and RedTrack
- Pushground and RedTrack
- Newsbreak and RedTrack
- AdMaven and RedTrack
- PropellerAds and RedTrack
- RichPush and RedTrack
- Tonic (traffic channel) and RedTrack
