TrafficGuard detects, mitigates, and reports on ad fraud before it hits digital advertising budgets. Three formidable layers of protection block both general invalid traffic (GIVT) and sophisticated invalid traffic (SIVT) to ensure that digital advertising results in legitimate advertising engagement.
This destination is maintained by TrafficGuard.
NOTE: The TrafficGuard Destination is currently in beta, which means that they are still actively developing the destination. This doc was last updated on March 4, 2019. If you are interested in joining their beta program or have any feedback to help improve the TrafficGuard Destination and its documentation, please let their team know!
The first step is to make sure TrafficGuard supports the source type and connection mode you’ve chosen to implement. You can learn more about what dictates the connection modes we support here.
- From your Segment UI’s Destinations page click on “Add Destination”.
- Search for “TrafficGuard” within the Destinations Catalog and confirm the Source you’d like to connect to.
- Drop in the “API Key” into your Segment Settings UI which you can find in your property in the TrafficGuard dashboard.
- Calls will now be visible in TrafficGuard dashboards in real-time.
NOTE: For TrafficGuard to successfully validate calls,
context.userAgent values as well as either
properties.url will need to be sent. Calls without those values will return an error.
If you haven’t had a chance to review our spec, please take a look to understand what the Page method does. An example call would look like:
Page calls will be sent to TrafficGuard as a
If you haven’t had a chance to review our spec, please take a look to understand what the Screen method does. An example call would look like:
[[SEGAnalytics sharedAnalytics] screen:@"Home"];
Screen calls will be sent to TrafficGuard as a
If you haven’t had a chance to review our spec, please take a look to understand what the Track method does. An example call would look like:
analytics.track('Clicked Login Button')
track calls will be sent to TrafficGuard as events.
|Segment Call||TrafficGuard event|
|Application Opened, Email Opened|
|Product Viewed, Product Reviewed, Promotion Viewed|
|Product Shared, Cart Shared|
All other calls will be recorded as
pageview events until TrafficGuard supports ad hoc event types.
For user-property destinations, an identify call will be sent to the destination for each user being added and removed. The property name will be the snake_cased version of the audience name you provide with a true/false value. For example, when a user first completes an order in the last 30 days, we will send an identify call with the property
order_completed_last_30days: true, and when this user no longer satisfies we will set that value to
When the audience is first created an identify call is sent for every user in the audience. Subsequent syncs will only send updates for those users which were added or removed since the last sync.
Segment lets you change these destination settings via your Segment dashboard without having to touch any code.
Your API Key can be found in your TrafficGuard property when the INPUT value is set to ‘Segment’
Adding TrafficGuard to the integrations objectTo add TrafficGuard to the
integrationsJSON object (for example, to filter data from a specific source), use one of the 1 valid names for this integration: