Oracle Bronto is deprecated from May 3, 2022. Client should migrate to alternative platform.
- Basic Knowledge of Treasure Data.
- Basic knowledge of Oracle Netsuite Bronto.
Oracle Netsuite Bronto automatically removes the + in a phone number. For example, +085 becomes085 on the server-side.
A SOAP API Access Token is required.
- Open the Bronto platform.
- Navigate toSettings > Platform Settings > Data Exchange.
- In the SOAP API Access Token panel, select Add Access Token.
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.
Open TD Console.
Navigate to Integrations Hub > Catalog.
Search for and select Bronto.
Select Create Authentication.
Type the Bronto SOAP API access token to authenticate.
Type a name for your connection.
Select Done.
In this step, you create or reuse a query. In the query, you configure the data connection.
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
| Column name | Type | Required | Description of Expected Value |
|---|---|---|---|
| String | yes | For example, test.me@abc.com | |
| phone_number | String | optional | For example, +593979652820 |
| status | String | optional | transactional, onboarding, unconfirmed, unsub, bounce, active (default: onboarding) |
| source | String | optional | manual, api, import, webform, sforcereport |
| custom_source | String | optional | A source you define that states where the contact came from. |
| fields | Array JSON | optional | JSON or JSON array format with the following required fields: - fieldId - content |
| list_ids | Comma-separated string | optional | 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_pref | String | optional | The 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_ids | Comma-separated string | optional | An array of the SMS keyword ids you want to subscribe the contact to. |
| Column name | Type | Required | Description of Expected Value |
|---|---|---|---|
| id | String | Yes (unless the email is used) | The unique id assigned to the contact |
email | String | Yes (unless name the contact id is used) | The email address assigned to the contact |
| Parameter | Values | Description |
|---|---|---|
| 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 Name | String | List 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 |
SELECT id, email, phone_number FROM table my_tableYou can use Scheduled Jobs with Result Export to periodically write the output result to a target destination that you specify.
Treasure Data's scheduler feature supports periodic query execution to achieve high availability.
When two specifications provide conflicting schedule specifications, the specification requesting to execute more often is followed while the other schedule specification is ignored.
For example, if the cron schedule is '0 0 1 * 1', then the 'day of month' specification and 'day of week' are discordant because the former specification requires it to run every first day of each month at midnight (00:00), while the latter specification requires it to run every Monday at midnight (00:00). The latter specification is followed.
Navigate to Data Workbench > Queries
Create a new query or select an existing query.
Next to Schedule, select None.
In the drop-down, select one of the following schedule options:
Drop-down Value Description 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. None No schedule.
| 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 Value | Example | Example 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. |
- (Optional) You can delay the start time of a query by enabling the Delay execution.
Save the query with a name and run, or just run the query. Upon successful completion of the query, the query result is automatically exported to the specified destination.
Scheduled jobs that continuously fail due to configuration errors may be disabled on the system side after several notifications.
(Optional) You can delay the start time of a query by enabling the Delay execution.
You can also send segment data to the target platform by creating an activation in the Audience Studio.
- Navigate to Audience Studio.
- Select a parent segment.
- Open the target segment, right-mouse click, and then select Create Activation.
- In the Details panel, enter an Activation name and configure the activation according to the previous section on Configuration Parameters.
- Customize the activation output in the Output Mapping panel.
- Attribute Columns
- Select Export All Columns to export all columns without making any changes.
- Select + Add Columns to add specific columns for the export. The Output Column Name pre-populates with the same Source column name. You can update the Output Column Name. Continue to select + Add Columnsto add new columns for your activation output.
- String Builder
- + Add string to create strings for export. Select from the following values:
- String: Choose any value; use text to create a custom value.
- Timestamp: The date and time of the export.
- Segment Id: The segment ID number.
- Segment Name: The segment name.
- Audience Id: The parent segment number.
- + Add string to create strings for export. Select from the following values:
- Set a Schedule.
- Select the values to define your schedule and optionally include email notifications.
- Select Create.
If you need to create an activation for a batch journey, review Creating a Batch Journey Activation.
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.
_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