Renta / Docs / Sources / Calltouch

Calltouch

Calltouch is a call-tracking service: it links incoming calls and website requests to the ad session that brought the visitor. Its API exposes two datasets.

  1. The call journal keeps one row per tracked call: the outcome (duration, status, target and unique flags), the numbers involved, and session attribution down to the keyword and UTM tags.
  2. The request log keeps one row per lead, whether it came from a website form or a callback widget, with the same attribution plus nested order and client details.

Renta exports these datasets to your data warehouse as two report types: Call report and Lead report.

Authentication

Renta authenticates with three values from your Calltouch account: Site ID, Counter ID, and API key. Calltouch shows all three on one screen: open your project and go to Integrations > API and Webhooks.

When you save the connection, Renta checks the credentials with a test request to the Calltouch API, so a typo in the Site ID or API key returns an error at the Save step instead of failing on the first pipeline run.

Connect Calltouch source

Follow these steps to add Calltouch as a source in Renta using your Site ID, Counter ID, and API key.

Go to the CatalogStep 1
  1. Navigate to the Connections > Catalog section in the left sidebar.
  2. Open the Call Tracking category and click the Calltouch card.
Calltouch card in the Call Tracking category of the Renta catalog
Enter the Calltouch credentialsStep 2

Fill in the three fields with the values from the API and Webhooks tab of your Calltouch project.

  1. Site ID.
    The identifier of your Calltouch personal account.
  2. Counter ID.
    The identifier of the Calltouch counter installed on your website.
  3. API key.
    The token for the Calltouch API.
Add a new Calltouch connection page with the Site ID, Counter ID, and API key fields
Name the connection and saveStep 3

In the Source name field, specify a name for this data source. It is used exclusively in the Renta interface.

Click Save. Renta checks the credentials against the Calltouch API before creating the connection.

Calltouch connection setup with the source name field and the Save button
Source createdStep 4

The new source appears in the Sources list with the Active status. You can now use it in pipelines.

Sources list with the new Calltouch source in the Active status

Create a pipeline

Once the source is connected, create a pipeline to sync your Calltouch data into your destination.

Create a Calltouch pipeline

Link your Calltouch source to a destination and configure the pipeline.

Select Calltouch as the sourceStep 1

In the left sidebar, click New pipeline. On the Source step, select Calltouch under Already connected and click Next step.

Select a source step with Calltouch under Already connected
Select your Calltouch connectionStep 2

Choose the Calltouch connection you created earlier and click Next step. The card shows the Site ID of the connected account.

Select your Calltouch connection step with the Site ID shown on the connection card
Select a destinationStep 3

On the Destination step, select your destination (for example, Google BigQuery) and click Next step.

Select a destination step with Google BigQuery under Already connected
Select the destination connectionStep 4

Choose the destination connection you want to load data into and click Next step.

Select your Google BigQuery connection step

Pipeline configuration

On the final step, choose the report, pick its fields, and set how Renta loads them.

Report type

Select which Calltouch dataset the pipeline exports. One pipeline loads one report type.

Calltouch pipeline settings with the Report Types dropdown set to Call report
Report typeDescription
Call reportThe call journal. One row per tracked call: outcome, numbers, statuses, and session attribution (source, keyword, UTM tags).
Lead reportThe request log. One row per lead: request attributes, traffic attribution, and nested order and client details.

Parameters

Select the Calltouch fields to include in the destination table.

Calltouch parameters picker with the Parameters and Selected tabs and the Select All button

Use the search field to find a parameter by name, or click Select All. The Selected tab shows everything you picked, and the Selected Parameters list below the picker lets you remove a parameter.

The Call report covers these fields.

GroupParameters
CallCall ID, Date, Call Phase, Duration, Waiting Connect, Manager, Caller Number, Redirect Number, Phone Number, Subpool Name, Orders
Call flagsSuccessful, Status Details, Unique Call, Target Call, Unique Target Call, Callback Call, Attribution
Traffic attributionSource, Medium, Keyword, URL, Call URL, Referrer, Hostname, UTM Source, UTM Medium, UTM Campaign, UTM Content, UTM Term
VisitorCity, IP Address, User Agent
IdentifiersSession ID, CT Caller ID, Client ID, Yandex Client ID, SIP Call ID, Site ID

The Lead report covers these fields.

GroupParameters
RequestRequest ID, Request Number, Request Type, dateLeadCreated, DateUnix, Date String, Subject, Manager, Status, Request URL, Widget Info
Request flagsUnique Request, Target Request, Unique Target Request, Attribution
Traffic attributionSource, Medium, Keywords, Referrer, Entry URL, UTM Source, UTM Medium, UTM Campaign, UTM Content, UTM Term, Yandex Direct, Google AdWords, DCM
VisitorCity, IP Address, Device, Operating System, Browser Name, Browser User Agent
IdentifiersSession ID, CT Client ID, CT Global ID, GUA Client ID, Yandex Client ID, Site ID
Nested objectsOrder [Object], Client [Object]

Order [Object] and Client [Object] load as nested records: order amounts and statuses, and the client's name with up to ten phone numbers and contacts.

Include the Date parameter in the Call report. With it, each row carries the call date, the destination table is partitioned by the date column, and Renta loads data incrementally. Without it, Renta reloads the whole date range on every run.

Table name

Name the pipeline and the destination table.

Calltouch integration name and table name fields
  1. Integration name.
    The name of the pipeline. It is used exclusively in the Renta interface.
  2. Table name.
    The destination table name. You can keep the auto-generated name or enter your own.

Date range

Set the historical period to load.

Calltouch date range with date start and date end
  1. Date start.
    The first date of the extraction period.
  2. Date end.
    The last date of the extraction period. Leave it as Today to keep collecting new data on every run.

Calltouch allocates a daily API quota that depends on your plan. Renta requests the report one day at a time, so the first load of a long history takes longer and consumes more of that quota than regular scheduled runs.

Overwrite period

The overwrite period defines how many recent days Renta reloads on every run.

Calltouch overwrite period selection with the Last 3 days option

On each run, Renta re-fetches the report starting from the date of the last successful run minus the overwrite period. The affected days are deleted from the destination table and inserted again, while older data stays untouched. The default is Last 3 days.

Calltouch records keep changing after the day they were created: a manager gets assigned to a call, order details and deal statuses are updated. The overwrite window is how those changes reach the destination table.

The Overwrite Period control appears only for the Call report with the Date parameter selected.

Schedule

Choose how often the pipeline runs.

Calltouch schedule type selection with the Daily option checked
Schedule typeDescription
ManualThe pipeline runs only when triggered manually through the interface or via API.
DailyThe pipeline runs once a day at the specified update time.
IntervalThe pipeline runs at specified time intervals.
Cron ExpressionThe pipeline runs on a schedule defined by a cron expression.

For Daily schedules, set the Update time, the exact time each run starts, then click Create pipeline.

Update time selection and the Create pipeline button

Renta also supports API triggers and integration with external orchestrators such as Apache Airflow, Dagster, and Prefect. See the full scheduling documentation for details.

The new pipeline appears in the Pipelines section under the ETL tab, where you can track its runs, progress, and the destination table name.

Pipelines list with the new Calltouch integration

Sync strategy

The synchronization strategy depends on the report type and whether the Date parameter is selected.

StrategySupported report typesDescription
IncrementalCall report (with the Date parameter selected)Each row carries the call date, and the destination table is partitioned by the date column. On every run Renta reloads the window from the last successful run minus the overwrite period to the end of the date range: those daily partitions are deleted and inserted again, and older partitions stay untouched.
Full reloadCall report (without the Date parameter), Lead reportThe destination table has no date column to partition by, so Renta requests the whole configured date range and replaces the dataset on every run.

Changing the selected parameters updates the table schema, so the next run after the change reloads the entire date range.

Frequently asked questions

Ready to get started?

Build your data pipeline today or get a personalized demo. Start free!

Need help?

Get expert support to ensure your project succeeds. We're here to help!

Feature requests?

Help shape our product! Share your ideas for new features and integrations.