Skip to main content
3C Plus is a Brazilian automatic dialer and call center platform. The connector extracts your company’s call history, agent login sessions, daily agent productivity per campaign, and scheduled callbacks, along with the setup of your operation: agents, users, teams, campaigns and their mailing lists, qualifications (call outcomes), work breaks, inbound queues, and IVRs. With it you can analyze your campaigns’ results and your team’s productivity in your Lakehouse.

Configuring 3C Plus as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the 3C Plus option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

3C Plus authenticates with a token. The connector reads 3C Plus reports, which 3C Plus only shares with users that have the manager (gestor) role, so the token must belong to a manager. You can use either:
  • A service token (recommended): in 3C Plus, go to Configurações > Integração > Tokens de serviço and create a token with manager permissions.
  • The API token of a manager user: in 3C Plus, go to Configurações > Usuários, open a user with the manager role, and copy the token from the advanced options.
A token of an agent, or a service token with the agent role, only reaches one agent’s data and is refused by the connector. The API token of a user does not expire on its own, but it stops working if a manager changes it in 3C Plus.
The following configurations are available:
  • API Token: the service token or the manager’s API token. Required.
  • Start Date: the earliest date from which calls, agent logins, agent daily metrics, and scheduled callbacks will be synced. Required. An earlier date makes the first sync longer, mainly for the agent daily metrics, which are read one day per campaign.
  • Include Mailing Data: also extract, with each call, the contact’s data from the mailing list (identifier, phone, and the list’s own columns) into the mailing_data column. On by default.
  • Lookback Days: how many days are re-read before the last sync point by the calls, agent logins, and agent daily metrics, to pick up the qualifications, logouts, and totals 3C Plus completes after a record first appears. The default is 1.
  • Time Zone: the time zone of your 3C Plus account. 3C Plus filters and returns dates in this time zone, and the connector converts them to UTC. The default is America/Sao_Paulo.
  • Requests Per Minute: how fast the connector may call 3C Plus. The default is 120.
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: Calls, Agent Login History, and Agent Metrics Daily support INCREMENTAL. The other streams are FULL_TABLE. Read more about Sync Types here.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings:
  • Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
  • Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from 3C Plus and their corresponding fields. API reference: 3C Plus API.
3C Plus sends dates in your account’s time zone; the connector converts every timestamp to UTC. Durations come as text (HH:MM:SS) and also as a number of seconds in the _seconds columns. Lists and objects (mailing data, feedback, settings, team members) are stored as JSON text.
Call history report of the company, one row per call (GET /calls). Read day by day in the account’s time zone; the last Lookback Days are re-read on every sync, because 3C Plus completes a call (qualification, feedback) after it first appears.Primary key: id
Login sessions of agents in campaigns (GET /agents/login_history). A session that is still open has no logout yet and is completed by a later sync.Primary key: row_key
Productivity totals of each agent in each campaign per day (GET /campaigns/{id}/agents/metrics/total, read one day at a time). Agents without any activity on a day are left out.Primary key: campaign_id, agent_id, date
Scheduled callbacks (GET /schedules), from the Start Date to one year ahead, so pending callbacks are included. Refreshed in full on every sync, since a schedule’s status changes after it is created.Primary key: id
Agents of the company, active and inactive (GET /agents).Primary key: id
Users of the company, active and inactive: managers, supervisors, and agents (GET /users). The API token, extension password, and confirmation code 3C Plus keeps for each user are never extracted.Primary key: id
Teams of agents and their supervisors (GET /teams).Primary key: id
Dialer campaigns, running and paused (GET /campaigns).Primary key: id
Mailing lists of each campaign with their dialing progress (GET /campaigns/{id}/lists).Primary key: campaign_id, id
Lists of qualifications (call outcomes) (GET /qualification_lists).Primary key: id
Qualifications (call outcomes) of each list (GET /qualification_lists/{id}/qualifications).Primary key: qualification_list_id, id
Groups of pause types (GET /work_break_group).Primary key: id
Pause types of each work break group (GET /work_break_group/{id}/intervals).Primary key: work_break_group_id, id
Inbound queues (GET /receptive_queues). Skipped when the account does not use inbound calls.Primary key: id
Inbound IVRs (GET /receptive_ivr). Skipped when the account does not use inbound calls.Primary key: id
Tags of the company (GET /tags). Skipped when not available for the account.Primary key: id
SMS mailing lists and their sending progress (GET /mailing_list_sms). Skipped when the account does not use SMS.Primary key: id