Page tree
Skip to end of metadata
Go to start of metadata

Oracle Netsuite Bronto is a Marketing Platform that combines email, mobile, and social messaging to design and execute personalized campaigns.



Prerequisites

  • Basic Knowledge of Treasure Data.

  • Basic knowledge of Oracle Netsuite Bronto.


Requirements and Limitations


Oracle Netsuite Bronto automatically removes the `+` in a phone number. For example, `+085` becomes`085` on the server-side.

A SOAP API Access Token is required.


Obtain SOAP API Access Token

  1. Open the Bronto platform.
  2. Navigate to Settings > Platform Settings > Data Exchange.
  3. In the SOAP API Access Token panel, select Add Access Token.

Use the TD Console to Create Your Connection

Create a New Connection

In Treasure Data, you must create and configure the data connection prior to running your query. As part of the data connection, you provide authentication to access the integration.

1. Open TD Console.
2. Navigate to Integrations Hub Catalog.
3. Search for and select Bronto.

4. Select Create Authentication.
5. Type the Bronto SOAP API access token to authenticate.

6. Type a name for your connection.
7. Select Done.



Define your Query and Column Mapping

In this step, you create or reuse a query. In the query, you configure the data connection.

Column Mapping

You need to define the column mapping in the query. The columns in the query represent a Contact object in Bronto data.

Depend on the selected Action, certain columns are required

Add/Update Contacts or Replace Contacts from List

Column nameTypeRequiredDescription of Expected Value
email
StringyesFor example, test.me@abc.com
phone_numberStringoptionalFor example, +593979652820
statusStringoptional

transactional, onboarding, unconfirmed, unsub, bounce, active (default: onboarding)

sourceStringoptional

manual, api, import, webform, sforcereport

custom_sourceStringoptional

A source you define that states where the contact came from.

fieldsArray JSONoptional

JSON or JSON array format with the following required fields:

  • fieldId
  • content
list_idsComma-separated stringoptional

The comma-separated list of List API IDs can be found at the bottom of each list detail screen.

For example, "list_id1,list_id2,list_id3".

They are incremental to lists that the contact may already be on. This means that the contact remains on any lists not specified in this call and it is also added to lists that you specify in this call.

msg_prefStringoptionalThe message preference for the contact. A contact can have a message preference of text or html. Only applies to the add action. The message preference is ignored for update.
sms_keyword_idsComma-separated stringoptionalAn array of the SMS keyword ids you want to subscribe the contact to.


Remove Contacts from List

Column nameTypeRequiredDescription of Expected Value
idStringYes (unless the email is used)The unique id assigned to the contact
email
StringYes (unless name the contact id is used)The email address assigned to the contact

  1. Complete the instructions in Creating a Destination Integration.
  2. Navigate to Data Workbench > Queries.

  3. Select a query for which you would like to export data.

  4. Run the query to validate the result set.

  5. Select Export Results.

  6. Select an existing integration authentication.
  7. Define any additional Export Results details. In your export integration content review the integration parameters.
    For example, your Export Results screen might be different, or you might not have additional details to fill out:
  8. Select Done.

  9. Run your query.

  10. Validate that your data moved to the destination you specified.


Integration Parameters for Bronto


ParameterValuesDescription
Action
  • Add/Update Contacts
  • Replace Contacts from List
  • Remove Contacts from List
  • Add a new Contact or update data associated with an existing Contact without replacing the existing Contact’s list membership (create a new Mail List if the provided List Name doesn't exist).
  • Remove all Contacts from the Mail List and Add new Contacts to the Mail List (create a new Mail List if the provided List Name doesn't exist)
  • Remove Contacts from provided Mail List
List NameStringList Name is required for Replace Contacts from List or Remove Contacts from List action. Add all users to this Mail List if the selected action is Add/Update Contacts.
Skip Invalid Data
  • true
  • false
  • Skip invalid data and continue uploading Contacts if an error occurred
  • Stop the job immediately if an error occur

Example Query

SELECT id, email, phone_number FROM table my_table



Optionally Schedule the Query Export Jobs

You can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.


1. Navigate to Data Workbench > Queries.
2. Create a new query or select an existing query.
3. Next to Schedule, select None.

4. In the drop-down, select one of the following schedule options.

Drop-down ValueDescription
Custom cron...

Review Custom cron... details.

@daily (midnight)Run once a day at midnight (00:00 am) in the specified time zone.
@hourly (:00)Run every hour at 00 minutes.
NoneNo schedule.

Custom cron... Details

Cron Value

Description

0 * * * *

Run once an hour

0 0 * * *

Run once a day at midnight

0 0 1 * *

Run once a month at midnight on the morning of the first day of the month

""

Create a job that has no scheduled run time.

 *    *    *    *    *
 -    -    -    -    -
 |    |    |    |    |
 |    |    |    |    +----- day of week (0 - 6) (Sunday=0)
 |    |    |    +---------- month (1 - 12)
 |    |    +--------------- day of month (1 - 31)
 |    +-------------------- hour (0 - 23)
 +------------------------- min (0 - 59)

The following named entries can be used:

  • Day of Week: sun, mon, tue, wed, thu, fri, sat

  • Month: jan, feb, mar, apr, may, jun, jul, aug, sep, oct, nov, dec

A single space is required between each field. The values for each field can be composed of:

Field ValueExampleExample Description

a single value, within the limits displayed above for each field.



a wildcard ‘*’ to indicate no restriction based on the field. 

‘0 0 1 * *’ configures the schedule to run at midnight (00:00) on the first day of each month.
a range ‘2-5’, indicating the range of accepted values for the field.‘0 0 1-10 * *’ configures the schedule to run at midnight (00:00) on the first 10 days of each month.
a list of comma-separated values ‘2,3,4,5’, indicating the list of accepted values for the field.

0 0 1,11,21 * *’


configures the schedule to run at midnight (00:00) every 1st, 11th, and 21st day of each month.
a periodicity indicator ‘*/5’ to express how often based on the field’s valid range of values a schedule is allowed to run.

‘30 */2 1 * *’


configures the schedule to run on the 1st of every month, every 2 hours starting at 00:30. ‘0 0 */5 * *’ configures the schedule to run at midnight (00:00) every 5 days starting on the 5th of each month.
a comma-separated list of any of the above except the ‘*’ wildcard is also supported ‘2,*/5,8-10’‘0 0 5,*/10,25 * *’configures the schedule to run at midnight (00:00) every 5th, 10th, 20th, and 25th day of each month.
5.  (Optional) If you enabled the Delay execution, you can delay the start time of a query.

Execute the Query

Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically imported to the specified container destination.


Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.



Optionally Configure Export Results in Workflow

Within Treasure Workflow, you can specify the use of this data connector to export data.

Learn more at Using Workflows to Export Data with the TD Toolbelt.

Example Workflow for Oracle Netsuite Bronto


_export:
  td:
  database: td.database

+bronto_export_task:
  td>: export_bronto.sql
  database: bronto_db
  result_connection: bronto
  result_settings:   
    type: bronto
    access_token: accesss_token
    action: add_or_update
	list_name: my list
    skip_invalid_data: false



  • No labels