Back

Setting up the Radium Connect Tealium Webhook

  •       Open AudienceStream and navigate to Act > Connectors
  •       Add the Webhook connector
  •       Select the Actions tab
  •       Chose the GET Action and click the “+Create Action” button
  •       Give your Action a name
  •       Choose the Source of your data
  •       Enter your API URL

http://rs.gwallet.com/r1/pixel/{R1ApplicationID}

  • Replace {R1ApplicationID} with the application id for this specific app in your RadiumOne Mobile Analytics (Connect) account.  You can retrieve this ID by logging into your Connect account and clicking on “Settings” in the left navigation bar.  
  • radium.jpg

 

  • Leave the Header Cookie Data section empty

 

Data Section

Map keys and values following the table below for what are required and optional parameters.


Those that are optional should be left with an empty value but still defined as keys if you do not wish to include them.

Parameter Key

Notes

name

Required: Name of APP as Configured in Connect Dash

uid

User Id (your internal id for the user, useful for deduplicating users across multiple devices)

app_vs

Required: app version

bundle

Required: package name

carrier

device carrier

country

two letter country code

gaid

Google ad id (required for android devices)

idfa

ios ifa (required for iOS devices)

idfv

ios ifv (required for iOS devices)

opt_out

true or false based on if the user has opted out of tracking in their device settings

make

device brand (ie apple, samsung, htc, etc)

model

Device model

os

Device type (Required.  Value must be “Android” or “iPhone OS”. Value is case sensitive.)

os_ves

OS version

devicetype

Device type (ie Tablet or phone)

event_name

Name of the event to be recorded.  

event_type

The type of the event to be recorded

network

If media attribution data for this end user is available, you can include a Publisher name here.

tracker

If media attribution data for this end user is available, you can include a Campaign name here

site_id

If media attribution data for this end user is available, you can include the name or id of the site where the ad that drove this user’s install was displayed.

totalSale

Revenue recorded from the event, if any.

currency

ISO 4217 Currency Code

event_key_1 - event_key_9

Optional fields.  Can be used to identify additional custom segmentation data.  The field name goes here.

event_string_1 - event_string_9

Optional fields.  Can be used to identify additional custom segmentation data.  Value goes here.

lat

Latitude at time event occurred.

lon

Longitude at time event occurred

ts

Unix epoch timestamp

trans_id

Required - a unique identifier for this specific instance of the event.  If no such identifier exists in your system you may use a timestamp.

lang

Language - can be pulled from either the app-level language settings, if any, or from the device default language.

  •       Save the Action
  •       Save/Publish AudienceStream

 

Test the AudienceStream Webhook to Radium Connect

With Radium Connect configured to accept the data, and AudienceStream configured to send the data, you can now test the setup.

Begin a Trace then have your visitor complete the necessary steps to join the necessary Audience to trigger the Webhook.

If successful, Trace will state the action was processed and provide an output of the data sent in the Webhook.   Data will become available in your Connect dashboard within the next 24 hours.