Adtriba Destination


Adtriba allows advertisers to track, control and optimize their marketing activities across all digital marketing channels through AI and user journey analysis.

This destination is maintained by Adtriba. For any issues with the destination, contact the Adtriba Support team.

This document is about a destination which is in beta

This means that the Adtriba Destination is in active development, and some functionality may change before it becomes generally available.

Getting Started

Before you start, make sure Adtriba supports the source type and connection mode you’ve chosen to implement. You can learn more about connection modes here.

Web Mobile Server
📱 Device-mode
☁️ Cloud-mode
  1. From the Segment web app, click Catalog.
  2. Search for “Adtriba” in the Catalog, select it, and choose which of your sources to connect the destination to.
  3. Enter the “Project Tracker ID / API Key” into your Segment Settings UI which you can find from your Adtriba dashboard.
  4. Validate the forwarded events by checking the Tracking Report under the “Tracking” tab.

Page

If you’re not familiar with the Segment Specs, take a look to understand what the Page method does. An example call would look like:

analytics.page()

Page calls will be sent to Adtriba as a pageview.

Identify

If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like:

analytics.identify('userId123', {
  email: 'john.doe@example.com'
});

Identify calls will be sent to Adtriba as an identify event.

Track

If you’re not familiar with the Segment Specs, take a look to understand what the Track method does. An example call would look like:

analytics.track('Conversion', {
  id: 'daaa61a2-7682-4ece-9adc-6b07d8020b94',
  revenue: 19.99,
  currency: 'USD'
})

Track calls will be sent to Adtriba as a track event.

Trigger additional events by using Semantic Events in order to enrich the Adtriba machine learning process.

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

You can find your API key on the project settings page in the setup area.

This page was last modified: 20 Oct 2020

Get started with Segment

Segment is the easiest way to integrate your websites & mobile apps data to over 300 analytics and growth tools.
or
Create free account