Already have an account? Sign in

Bronto (v1)

Bronto integration summary

Stitch’s Bronto integration replicates data using theBronto SOAP API. Refer to theSchema section for a list of objects available for replication.

Bronto feature snapshot

A high-level look at Stitch's Bronto (v1) integration, including release status, useful links, and the features supported in Stitch.

Connecting Bronto

Bronto setup requirements

To set up Bronto in Stitch, you need:

• Admin permissions in Bronto. This is required to create an API token.

Step 1: Create a Bronto API token

1. Sign into your Bronto account.
2. Navigate toHome > Settings.
3. ClickData Exchange in the left side menu.
4. UnderSOAP API Tokens, click theAdd Access Token button.
5. In theAPI Token Name field, enterStitch. This will allow you to easily identify what application is using the token.
6. Click the checkbox next toRead to allow read access for this token.
7. Ensure that the checkbox next toToken is active? is checked, and clickSave.
8. The access token will appear on the page under the nameStitch once the modal closes. Copy this to be used in setting up the connection from within the Stitch application.

Step 2: Add Bronto as a Stitch data source

1. Sign into your Stitch account.

2. On the Stitch Dashboard page, click theAdd Integration button.

3. Click theBronto icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch Bronto” would create a schema calledstitch_bronto in the destination.Note: Schema names cannot be changed after you save the integration.

5. In theBronto API Token field, paste the access token you created in Step 1.

Step 3: Define the historical replication start date

The Sync Historical Data setting defines the starting date for your Bronto integration. This means that dataequal to or newer than this date will be replicated to your data warehouse.

Change this setting if you want to replicate data beyond Bronto’s default setting of1 year. For a detailed look at historical replication jobs, check out theSyncing Historical SaaS Data guide.

Step 4: Create a replication schedule

In theReplication Frequency section, you’ll create the integration’sreplication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

Bronto integrations support the following replication scheduling methods:

• Replication Frequency

• Anchor Scheduling

• Advanced Scheduling using Cron (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See theUnderstanding and Reducing Your Row Usage guide for tips on reducing your usage.

Initial and historical replication jobs

After you finish setting up Bronto, itsSync Status may show asPending on either the Stitch Dashboard or in the Integration Details page.

For a new integration, aPending status indicates that Stitch is in the process of scheduling the initial replication job for the integration.This may take some time to complete.

Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Bronto table reference

contact.id = inbound_activity.contactId

contact.id = outbound_activity.contactId

inbound_activity.contactId = contact.id

inbound_activity.contactId = outbound_activity.contactId

inbound_activity.deliveryId = outbound_activity.deliveryId

inbound_activity.listId = outbound_activity.listId

inbound_activity.keywordId = outbound_activity.keywordId

inbound_activity.messageId = outbound_activity.messageId

inbound_activity.orderId = outbound_activity.orderId

inbound_activity.segmentId = outbound_activity.segmentId

inbound_activity.workflowId = outbound_activity.workflowId

inbound_activity.listId = list.id

list.id = inbound_activity.listId

list.id = outbound_activity.listId

outbound_activity.contactId = contact.id

outbound_activity.contactId = inbound_activity.contactId

outbound_activity.deliveryId = inbound_activity.deliveryId

outbound_activity.listId = inbound_activity.listId

outbound_activity.keywordId = inbound_activity.keywordId

outbound_activity.messageId = inbound_activity.messageId

outbound_activity.orderId = inbound_activity.orderId

outbound_activity.segmentId = inbound_activity.segmentId

outbound_activity.workflowId = inbound_activity.workflowId

outbound_activity.listId = list.id

Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.