RevX Cloud (Actions) Destination

Destination Info
Partner Owned
  • This integration is partner owned. Please reach out to the partner's support for any issues.

RevX Cloud (Actions) helps app marketers achieve their growth objectives by simplifying programmatic advertising for them. With RevX, your reach extends to over 90% of app users globally, encompassing more than 1 million mobile apps. Leverage audience intelligence to achieve highly precise targeting, accompanied by personalized messaging. Employ advanced AI-driven audience segmentation to identify high-intent players, while optimizing creatives to amplify performance to new heights.

This destination is maintained by RevX. For any issues with the destination, contact their support team.

Getting started

  1. From the Segment web app, click Catalog, then click Destinations.
  2. Find the Destinations Actions item in the left navigation, and click it.
  3. Click Configure RevX Cloud (Actions).
  4. Select an existing Source to connect to RevX Cloud (Actions).
  5. Add Revx Client ID as provided by the tse team.

Destination Settings

Setting Description
Revx Client ID Required.

Revx specific client id. This can be found by contacting the RevX support team

Available Presets

RevX Cloud (Actions) has the following presets:

Preset Name Trigger Default Action
Send Revx Ping Event type = "track"
Event type ="screen"
Send Revx Ping

Available Actions

Build your own Mappings. Combine supported triggers with the following RevX Cloud-supported actions:

Mapping limits per destination

Individual destination instances have support a maximum of 50 mappings.

Send Revx Ping

Send event to revx

Send Revx Ping is a Cloud action. The default Trigger is: type = "track" or type ="screen"

Click to show / hide fields

Field Description
Platform* Type: STRING

Platform of the device.

Identifier For Advertiser (IDFA/GAID) Type: STRING

Identifier For Advertiser (IDFA/GAID)

Event name Type: STRING

A unique identifier for your event.

Request type Type: STRING

A unique identifier for your request type.

Identifier For Vendor (IDFV) Type: STRING

Identifier for Device Id for IOS and Android

Timestamp Type: DATETIME

The timestamp of the event. If time is not sent with the event, it will be set to the request upload time.

Event Properties Type: OBJECT

An object of key-value pairs that represent additional data to be sent along with the event.

User Properties Type: OBJECT

An object of key-value pairs that represent additional data tied to the user

App Version Type: STRING

The current version of your application.

OS Name Type: STRING

The name of the mobile operating system or browser that the user is using.

OS Version Type: STRING

The version of the mobile operating system or browser the user is using.

Device Brand Type: STRING

The device brand that the user is using.

Device Manufacturer Type: STRING

The device manufacturer that the user is using.

Device Model Type: STRING

The device model that the user is using.

Carrier Type: STRING

The carrier that the user is using.

Country Type: STRING

The current country of the user.

Region Type: STRING

The current region of the user.

City Type: STRING

The current city of the user.

Designated Market Area Type: STRING

The current Designated Market Area of the user.

Language Type: STRING

The language set by the user.

Product Type: OBJECT

The single product viewed or Added to cart.

Products Type: OBJECT

The list of products purchased.

Latitude Type: NUMBER

The current Latitude of the user.

Longtitude Type: NUMBER

The current Longitude of the user.

IP Address Type: STRING

The IP address of the user. Use “$remote” to use the IP address on the upload request.

Engage

You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule 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, Engage 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), Engage sets that value to false.

When you first create an audience, Engage 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.

Real-time to batch destination sync frequency

Real-time audience syncs to RevX Cloud (Actions) may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.

Settings

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

Setting Description
Revx Client ID
(required)
string. Revx specific client id. This can be found by contacting the RevX support team

This page was last modified: 07 Aug 2024



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