TrafficGuard Destination

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!

Getting Started

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.

WebMobileServer
📱 Device-based
☁️ Cloud-based
  1. From your Segment UI’s Destinations page click on “Add Destination”.
  2. Search for “TrafficGuard” within the Destinations Catalog and confirm the Source you’d like to connect to.
  3. Drop in the “API Key” into your Segment Settings UI which you can find in your property in the TrafficGuard dashboard.

  1. Calls will now be visible in TrafficGuard dashboards in real-time.

NOTE: For TrafficGuard to successfully validate calls, context.ip and context.userAgent values as well as either context.campaign.source, context.app.name or properties.url will need to be sent. Calls without those values will return an error.

Page

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:

analytics.page()

Page calls will be sent to TrafficGuard as a pageview event.

Screen

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 pageview event.

Track

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')

The following track calls will be sent to TrafficGuard as events.

Segment CallTrafficGuard event
Application Installedinstall
Application Opened, Email Openedopen
Products Searchedsearch
Product Viewed, Product Reviewed, Promotion Viewedviewcontent
Product AddedAdd
Checkout Startedcheckout
Product Shared, Cart Sharedshare

All other calls will be recorded as pageview events until TrafficGuard supports ad hoc event types.



If you have any questions, or see anywhere we can improve our documentation, please let us know!