Where do I get the API base URL and the API key?

The base URL is the address of your Scaleo dashboard, for example https://yournetwork.scaletrk.com . The API key is issued in the Scaleo dashboard, in your profile settings. When you click **Save**, Renta checks the pair with a test request to Scaleo, so a wrong URL or an expired key surfaces at the **Save** step, not on the first pipeline run.

Can I join conversions to clicks?

Yes. The Clicks and Conversions reports share one field set, and every conversion carries the Click ID of the click that produced it, so the two tables join on that column.

In what time zone are the timestamps?

Scaleo returns dates and timestamps in the time zone configured for your network. The Added Timestamp and Date values in the destination table follow that time zone.

Why do Payout and Revenue load as text columns?

Scaleo returns monetary values as strings, and Renta keeps them as they arrive. Cast these columns to a numeric type in SQL when you build reports on top of the table.

Scaleo

Renta exports three Scaleo reports to your data warehouse: clicks, conversions, and affiliate billing invoices.

Each click and conversion loads as a separate row with amounts, tracking parameters, and details about the visitor's device and location. Invoices carry the amounts, statuses, and payment details of affiliate payouts.

Authentication

Renta connects to Scaleo with two values from your network account: the API base URL and the API key.

When you save the connection, Renta validates the credentials with a test request to your Scaleo network, so a wrong URL or an invalid key returns an error immediately instead of failing on the first pipeline run.

Connect Scaleo source

Follow these steps to add Scaleo as a source in Renta using an API base URL and an API key.

Go to the CatalogStep 1

Navigate to the Connections > Catalog section in the left sidebar.
Open the Finance category and click the Scaleo card.

Scaleo card in the Finance category of the Renta catalog

Enter the base URL and the API keyStep 2

API base URL.
The address of your Scaleo dashboard, for example https://yournetwork.scaletrk.com.
API key.
The key issued in the Scaleo dashboard, in your profile settings.

Add a new Scaleo connection page with the API base URL 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 your Scaleo network before creating the connection.

Scaleo 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 Scaleo source in the Active status

Create a pipeline

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

Create a Scaleo pipeline

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

Select Scaleo as the sourceStep 1

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

Select a source step with Scaleo under Already connected

Select your Scaleo connectionStep 2

Choose the Scaleo connection you created earlier and click Next step.

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, its fields, and how Renta loads them.

Report type

In the Report Types dropdown, choose which Scaleo report the pipeline loads. One pipeline loads one report, so create a separate pipeline for each report you need.

Report type	Description
Clicks	Every click registered in your network as a separate row.
Conversions	Every conversion transaction as a separate row. Each conversion carries the Click ID of the click that produced it.
Invoices	Affiliate billing invoices with amounts, statuses, billing periods, and payment methods.

Parameters

Check the Scaleo fields to load into the destination table.

Under each field the picker shows the name of its future column in the destination table. Select All checks the whole list at once, and the Selected tab keeps everything you have already picked.

The Clicks and Conversions reports share one field set.

Group	Parameters
Transaction	Transaction ID, Added Timestamp, Click ID, Suspicious
Money	Payout, Profit, Revenue, Currency
Tracking parameters	Sub ID 1-5, Aff Param 1-5, Aff Click ID
Network structure	Affiliate ID, Affiliate Value, Advertiser ID, Advertiser Value, Offer ID, Offer Value, Goal ID, Goal Value, Goal Parent ID, Goal Parent Value, Goal Type ID, Goal Type Value, Link ID, Link Value, Link Parent ID, Link Parent Value, Creative ID, Creative Value, Creative Parent ID, Creative Parent Value
Traffic	Source, Deep Link URL, Click Referer URL, Language
Device and network	Device Type Code, Device Type Value, Device Brand, Device Model, Device OS, Device OS Version, Browser, Browser Version, Connection Type, Mobile Operator, IP, IDFA, GAID
Geolocation	Geo Country Code, Geo Country, Geo Region, Geo City

The Invoices report has its own field set.

Group	Parameters
Invoice	ID, Invoice Number, Status, Period, Date
Amounts	Amount Value, Amount Currency, Referral Commission Value, Referral Commission Currency
Affiliate	Affiliate ID, Affiliate Name
Payment method	Payment Method ID, Payment Method Title, Payment Method Info, Payment Method Image, Payment Method Metadata
Other	Attachment, Internal Notes, Offers, Goal Types

Scaleo returns monetary values as strings, so Payout, Profit, Revenue, and the invoice amounts load into text columns. Cast them to a numeric type in SQL when you build reports.

In the Invoices report, Offers and Goal Types load as nested arrays of ID and title pairs, and Payment Method Metadata loads as a JSON column.

Include Added Timestamp in Clicks and Conversions and Date in Invoices. With this field the destination table is partitioned by day 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.

Integration name.
The name of the pipeline. It is used exclusively in the Renta interface.
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.

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

For Clicks and Conversions the range covers the moment the transaction was registered. For Invoices it covers the invoice date. Scaleo interprets the dates in the time zone configured for your network.

Schedule

Choose how often the pipeline runs.

Schedule type	Description
Manual	The pipeline runs only when triggered manually through the interface or via API.
Daily	The pipeline runs once a day at the specified update time.
Interval	The pipeline runs at specified time intervals.
Cron Expression	The 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 Scaleo integration

Sync strategy

The synchronization strategy depends on whether the report includes its date field.

Strategy	Supported report types	Description
Incremental	Clicks (with Added Timestamp selected), Conversions (with Added Timestamp selected), Invoices (with Date selected)	The destination table is partitioned by the day of `added_timestamp` (`date` for Invoices). On every run Renta re-requests the report from the day of the last successful run to the end of the date range and replaces those daily partitions. Older partitions stay untouched.
Full reload	Clicks (without Added Timestamp), Conversions (without Added Timestamp), Invoices (without Date)	The 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.