Convertro Destination

Segment makes it easy to send your data to Convertro (and lots of other destinations). Once you've tracked your data through our open source libraries we'll translate and route your data to Convertro in the format they understand. Learn more about how to use Convertro with Segment.

Getting Started

Our Convertro destination let’s you track customer data from either your website data or your mobile data. When you send data via analytics.js we will use Convertro’s JS library to send .identify() and .track() data.

If you are sending data using our mobile libraries, we will use their server to server API to send .identify() and .track() data.

Using analytics.js Library

Identify

When you call our identify call we’ll call Convertro’s trackUser method with the traits object. If you don’t include the first argument in your identify call (the userId) nothing will be sent to Convertro.

Ecommerce

Ecommerce events are sent to Convertro as long as they include an orderId.

Amount

To record the transaction amount to Convertro we’ll pass the total from your Completed Order event and fall back to revenue if there’s no total.

Repeat Purchases

You can also include properties.repeat as a boolean if you need to specify between repeat and new purchasers.

With a value of true we will pass sale.repeat to Convertro.

If you record repeat: false we will pass sale.new to Convertro.

Attribution Model

Convertro has two main attribution models.

  1. You don’t know which users are new or repeat, so you’ll just send throgh Completed Order without a repeat property and it will get counted as a sale event in Convertro.
  2. You know which users are new or repeat, and when you pass through the Completed Order event with a repeat property set to true or false we’ll send through a sale.repeat or sale.new event to Convertro.

If over the course of your using Convertro, you switch between the first and second attribution model, we provide the ability to take advantage of a hybrid attribution model that will send both sale and sale.new or sale.repeat when you have a valid repeat property on the Completed Order event. This is necessary to combine the models and data from your old sale event with the new sale.new and sale.repeat events.

Using Mobile Libraries

In order for your mobile data to flow to Convertro, you want to first insert your Convertro Client Name, Site ID, and Domain into your destination settings.

Important: Convertro requires your Device ID for all API calls. Our mobile libraries automatically collect this value from your device so you do not need to worry about it. Just don’t overwrite your context.device.id property!

Identify

Convertro only accepts user data that includes a userId. Thus we will reject any anonymous .identify() calls that does not include the userId.

Convertro does not accept any user traits – meaning that .identify() calls will be used to tie your Device ID to the userId.

Track

When you call .track(), we will send that event to Convertro by setting the event_type as the name of your event. If you send a revenue property, we will send that as the event_value (Completed Order or Order Completed events will use the total). The event_value will be sent as 1 if no revenue value is provided.

Application Installed

We will send this automatically collected Application Installed event to Convertro’s Installs endpoint.


Supported Sources and Connection Modes

WebMobileServer
📱 Device-based
☁️ Cloud-based

To learn more about about Connection Modes and what dictates which we support, see here.

Settings

Segment lets you change these destination settings via your Segment dashboard without having to touch any code.

Domain

If you’d like to send mobile data to Convertro’s server side integration, please enter your Convertro Domain

Events

Convertro only wants to receive specific events. For each conversion event you want to send to Convertro, put the event name you send to Segment on the left, and the name you want Convertro to receive it as on the right.

Hybrid Attribution Model

This will make Completed Order events always send a sale event in addition to a sale.new or sale.repeat event if it has a boolean repeat property.

Site ID

If you’d like to send mobile data to Convertro’s server side integration, please enter your Convertro Site ID

Account

Enter your Convertro Account Name

Client Name

If you’d like to send mobile data to Convertro’s server side integration, please enter your Convertro Client Name


If you have any questions or see anywhere we can improve our documentation, please let us know or kick off a conversation in the Segment Community!