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

Renta exports Getintent advertising statistics to your data warehouse as a single report you assemble yourself from dimensions and metrics.

Dimensions set the grouping: from daily totals per campaign down to rows per site, app, creative, or user segment. Metrics cover delivery and costs, conversions, video completion, on-site behavior, and traffic quality.

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

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

Once the source is connected, link it 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.

Dimensions41Metrics27

Name	API name	Description
OS text	`os`	Operating system
Day date	`day`	Day timestamp
SSP text	`ssp`	Supply-side platform
City text	`city`	City
Hour int	`hour`	Hour of the day
Month int	`month`	Month of the year
App ID text	`app_id`	Application ID
Domain text	`domain`	Domain
Is App boolean	`is_app`	Is application
Minute int	`minute`	Minute of the hour
Second int	`second`	Second of the minute
Tag ID text	`tag_id`	Tag ID
Browser text	`browser`	Browser
Country text	`country`	Country
Site ID int	`site_id`	Site ID
User ID text	`user_id`	User ID
Is Video boolean	`is_video`	Is video content
Is Native boolean	`is_native`	Is native content
Campaign ID int	`campaign_id`	Campaign ID
Creative ID int	`creative_id`	Creative ID
Device Type text	`device_type`	Device type
Domain List expand_field	`domain_list`	Domain list
Week Number int	`week_number`	Week number
App Category text	`app_category`	Application category
Advertiser ID int	`advertiser_id`	Advertiser ID
Click Anomaly text	`click_anomaly`	Click anomaly
Creative Size text	`creative_size`	Creative size
User Segments int	`user_segments`	User segments
Carrier ID text	`carrier_id_str`	Carrier ID (text)
Unix timestamp int	`unix_timestamp`	Unix timestamp
Browser Version text	`browser_version`	Browser version
Conversion Name text	`conversion_name`	Conversion name
Application List expand_field	`application_list`	Application list
Content Category text	`content_category`	Content category
Full Region Code text	`full_region_code`	Full region code
Top Level Domain text	`top_level_domain`	Top-level domain
Campaign Currency text	`campaign_currency`	Campaign currency
Campaign Group ID int	`campaign_group_id`	Campaign group ID
Video Ad Placement text	`videoad_placement`	Video ad placement
DMP Segment Billed text	`dmp_segment_billed`	DMP segment billed
Video Inventory Format text	`video_inventory_format`	Video inventory format

Name	API name	Description
Impressions int	`imps`	Impressions
View Rate float	`view_rate`	View rate
Unique Impressions int	`unique_imps`	Unique impressions
Clicks int	`clicks`	Clicks
CPM float	`cpm`	Cost per thousand impressions
CPC float	`cpc`	Cost per click
CTR float	`ctr`	Click-through rate
Budget float	`budget`	Budget
PCC int	`pcc`	Post-click conversions
APCC int	`apcc`	Additional post-click conversions
PVC int	`pvc`	Post-view conversions
CPA float	`cpa`	Cost per acquisition
Agency Revenue float	`ag_rev`	Agency revenue
Agency Revenue Percentage float	`ag_rev_prc`	Agency revenue percentage
XClicks int	`xclicks`	Extra clicks
Video Completion 25% float	`video_completion_25`	Video completion rate at 25%
Video Completion 50% float	`video_completion_50`	Video completion rate at 50%
Video Completion 75% float	`video_completion_75`	Video completion rate at 75%
Video Completion 100% float	`video_completion_100`	Video completion rate at 100%
Sessions int	`an_sessions`	Analytics sessions
Bounce Rate float	`an_bounce_rate`	Analytics bounce rate
Pageviews Per Session float	`an_pageviews_per_session`	Pageviews per session
Avg. Session Duration float	`an_avg_session_duration`	Average session duration
Robots float	`robots`	Robots detected
Unique Conversions int	`unique_convs`	Unique conversions
Passing Index float	`passing_index`	Passing index
Anomaly Impressions int	`anomaly_impression`	Anomalous impressions

The parameters split into the Dimensions and Metrics tabs. Select All checks everything on the open tab.

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.