Connector Improvement: TEADS Connector: Add Seat filter to TEADS connector to enable pullling mulitple seats through 1 connector
Hi,
We're currently using the Teads Lite connector to pull data from Teads.
We have 12 seats, and have currently setup 12 connectors.
Problem we have, is we are hitting Teads rate limits on number of reports per day, especially with the historical synch.
We have asked Teads to raise their limits, which they are investigating, BUT, they have NEVER done this before.
They have suggested an alternative performance improvement which is to extend the scope of the API requests to include multiple seats. This means when the 7 reports are requested via 1 connector, data for all 12 of our seats can be retrieved.
To enable this option 5Tran need to make the following changes:
1. On the your API requests use the "ad_owner" parameter.
2. Add a field to connector setup to allow us to enter multiple Seat IDs, which can then be passed on to the ad_owner parameter.
3. As all tables in your databricks schema all contain seat_id, you shouldn't need to modify schemas as it will support multiple seats.
-
Further information. Here are the API rate limits, can you also check the Lite connector is complying with these limits. Thanks.
Please sign in to leave a comment.
Comments
1 comment