Third party API: what data is supported by Audience Republic?

Modified on Thu, 30 May at 11:10 AM

Audience Republic can handle the following data types, depending on the information provided by the client via an external API.

Before you get started

Make sure you have access to API tokens

Data supported by Audience Republic through an external API

Supported Data

events (name, date, location, capacity, etc.)
event images (the API supports multiple, but only one is imported to the product)
tours (linked to an event but not shown in the product)
purchase orders (a bunch of tickets bundled into one order)
tickets
ticket classes
contacts
- fans who have made purchases
- fans who have attended events (ticket holders)
message list subscriptions

Sync Time

The sync time is determined by who imports the data and how busy the API is.

When someone imports data into the API, it is added to a 'waiting list'; if the 'waiting list' is small, it will only take a few minutes to import the data into the product.

If there is a large amount of data on the 'waiting list,' this could take several hours to complete.

Throughput

Audience Republic has a scheduled task that scans this list every 5 minutes and processes it at a steady pace. Currently, there are approximately 50,000 of each type of entity, for a maximum of 400,000 entities. If all of the commonly large sets of data are full (contacts, orders, tickets, tags, subscriptions), then you're looking at approximately 250,000 records every 5 minutes at the highest rate of throughput.

Caching

Once the data from the 'waiting list' is imported into the product, it goes through a process of aggregation and caching (for faster access), which we call materialization. This is essentially a way to speed up your audience filtering.

Our platform has another set of periodic tasks that handle this, with periods ranging from 5 to 20 minutes. In general, they will be able to handle all outstanding tasks within each period, so 'caching' for audience filtering will typically take no more than 30 minutes.

This means that imported contact data with associated ticket sales, event attendance, etc. will be filterable in the Audience section of the product from as little as a few minutes, up to several hours, depending on when the period tasks next run and the number of pending tasks. In most cases, it will be available within 30 minutes.

Still need help?