Where do I get the Getintent API key?

The key is the token that Getintent issues for its Reporting API. When you save the connection, Renta checks the key with a test request to Getintent, so an invalid or expired key is rejected at the **Save** step instead of failing on the first pipeline run.

Why is the Overwrite Period setting not visible?

The **Overwrite Period** control appears only when the **Day** dimension is selected. Without **Day** the destination table has no date column, so there is no window to overwrite and Renta reloads the whole date range on every run.

In what time zone are the statistics?

Getintent returns reports in Moscow time (UTC+3). The **Day** and **Hour** values in the destination table follow that time zone, so figures for a calendar day may differ from dashboards that use another time zone.

Can I change the selected dimensions and metrics after the pipeline is created?

Yes, edit the pipeline and change the parameter set. The change updates the destination table schema, so the next run reloads the entire configured date range.

Getintent

Getintent is a demand-side platform for programmatic ad buying. Its Reporting API returns one report, and you define its shape yourself: dimensions set the grouping, metrics set the figures. The metrics cover delivery and costs (impressions, clicks, CPM, CPC, CPA), post-click and post-view conversions, video completion by quartile, on-site behavior (sessions, bounce rate), and traffic quality (robots, anomalous impressions).

Renta exports this report to your data warehouse: from daily totals per campaign down to rows per site, app, creative, or user segment.

Authentication

Renta authenticates with a Getintent API key: the token issued for the Getintent Reporting API.

When you save the connection, Renta validates the key with a test request to the Getintent Reporting API, so an invalid or expired key returns an error immediately instead of failing on the first pipeline run.

Connect Getintent source

Follow these steps to add Getintent as a source in Renta using an API key.

Go to the CatalogStep 1

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

Getintent card in the Advertising category of the Renta catalog

Enter the API keyStep 2

In the API key field, paste the token issued for the Getintent Reporting API.

Add a new Getintent connection page with the API key field

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 key against the Getintent Reporting API before creating the connection.

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

Create a pipeline

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

Create a Getintent pipeline

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

Select Getintent as the sourceStep 1

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

Select a source step with Getintent under Already connected

Select your Getintent connectionStep 2

Choose the Getintent 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, assemble the report and choose how Renta loads it.

Parameters

Select the Getintent fields to include in the destination table. The parameters you choose here define both the report grouping and the table schema.

The parameters split into the Dimensions and Metrics tabs. 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.

On the Dimensions tab, check the fields that define the report grouping.

Group	Dimensions
Time	Day, Hour, Minute, Second, Month, Week Number, Unix timestamp
Campaign structure	Advertiser ID, Campaign Group ID, Campaign ID, Campaign Currency, Creative ID, Creative Size
Inventory	SSP, Site ID, Tag ID, Domain, Top Level Domain, Domain List, App ID, App Category, Application List, Content Category, Is App, Is Video, Is Native, Video Ad Placement, Video Inventory Format
Audience and environment	Country, City, Full Region Code, OS, Browser, Browser Version, Device Type, Carrier ID, User ID, User Segments, DMP Segment Billed
Conversions and traffic quality	Conversion Name, Click Anomaly

On the Metrics tab, check the figures to export.

Group	Metrics
Delivery	Impressions, Unique Impressions, Clicks, XClicks, CTR, View Rate
Cost	CPM, CPC, CPA, Budget, Agency Revenue, Agency Revenue Percentage
Conversions	PCC (post-click conversions), APCC (additional post-click conversions), PVC (post-view conversions), Unique Conversions
Video	Video Completion 25%, Video Completion 50%, Video Completion 75%, Video Completion 100%
On-site analytics	Sessions, Bounce Rate, Pageviews Per Session, Avg. Session Duration
Traffic quality	Robots, Anomaly Impressions, Passing Index

Include the Day dimension. With it, each row in the destination table is one day, the table is partitioned by the day column, and Renta loads data incrementally. Without it, Renta reloads the whole date range on every run.

When you click Create pipeline, Renta validates the selected set with a test request to Getintent. If Getintent rejects the combination of dimensions and metrics, Renta shows an error and does not create the pipeline.

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.

Getintent returns reports in Moscow time (UTC+3). The Day and Hour values in the destination table follow that time zone.

Overwrite period

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

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 options range from Without overwrite data to Overwrite all data. The default is Last 1 day.

The Overwrite Period control appears only when the Day dimension is selected. Getintent attributes post-view conversions to impressions from earlier days, so keep the overwrite period at several days if you export PVC or other conversion metrics.

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 Getintent integration

Sync strategy

The synchronization strategy depends on whether the report includes the Day dimension.

Strategy	Supported report types	Description
Incremental	Getintent report (with the Day dimension selected)	Each row is one day, and the destination table is partitioned by the `day` 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 reload	Getintent report (without the Day dimension)	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 dimensions or metrics 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.