RDStation

Creating the data source

Requirements

Your RD Station plan must be Light, Basic, Pro or Enterprise
Your user must have an access profile of Owner, Manager or Marketing

Instructions

1) Login to Kondado, go to add data source and select the RDStation data source

2) Click AUTHORIZE

3) On the RD authorization page, select the account you will use and click on “Continue

4) Then click Connect

5) You will be directed back to Kondado. Give your connector a name and click SAVE

6) If you are using webhook, check the additional instructions for the correct operation of the data source and its historical data at the end of this tutorial in "Webhook Configuration"

Pipelines

Relationship chart

Click to expand

Contacts

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

RD Station Marketing contacts. Each row represents a contact identified by its uuid, bringing name, email, main phone, creation date and date of the last conversion.

Campo	Tipo
uuid	text	[en] The unique uuid associated with each RD Station contact
created_at	timestamp	[en] Contact creation date
email	text	[en] Contact's email
last_conversion_date	timestamp	[en] Date of the contact's last conversion
name	text	[en] Contact's name
phone	text	[en] Contact's main phone (E.164 format)

Contacts: conversion events

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

Relationships:

contact_uuid → Contacts > uuid

Main object

Conversion events of RD Station Marketing contacts. Each row represents a conversion event of a contact (identified by contact_uuid), bringing the event identifier and family, date/time, type and origin data of the conversion.

Campo	Tipo
contact_uuid	text	[en] Unique user identifier code Contacts > > uuid
event_family	text	[en] Internal RDSM identifier
event_identifier	text	[en] Event identifier
event_timestamp	timestamp	[en] Event creation date/time
event_type	text	[en] The event type (CONVERSION or OPPORTUNITY)
payload_city	float	[en] City informed by the contact in the conversion event
payload_company_name	text	[en] Company name informed by the contact in the conversion event
payload_email	text	[en] Email informed by the contact in the conversion event
payload_name	text	[en] Name informed by the contact in the conversion event
payload_personal_phone	text	[en] Personal phone informed by the contact in the conversion event
payload_mobile_phone	text	[en] Mobile phone informed by the contact in the conversion event
event_number	float	[en] Event identifier created by Kondado

rdstation_contatos_eventos_conversoes_traffic_source

Traffic source parameters of contacts' conversions, in key/value format. Each row represents a traffic_source parameter of a conversion event, relating to the conversion events table by contact_uuid.

Campo	Tipo
contact_uuid	text	[en] Unique user identifier code
event_number	float	[en] Event identifier created by Kondado
traffic_source_param_key	text	[en] Key of the parameter identified in the traffic_source payload. The original string is identified as __kdd_raw. If the original string is a URL, the values __kdd_hostname for the hostname (for example app.kondado.com.br) and __kdd_path for the URL path (for example /signup for the URL https://app.kondado.com.br/signup) are also sent.
traffic_source_param_value	text	[en] Value of the parameter identified in the traffic_source payload
traffic_source_session_order	text	[en] Indicates whether the parameters refer to the current session (current) or the first one (first)

Contacts: custom fields

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

Relationships:

uuid → Contacts > uuid

Custom fields of RD Station Marketing contacts. Each row corresponds to a contact (identified by the uuid), with one column for each custom field configured in the account and its respective filled value.

Campo	Tipo
uuid	text	[en] The unique uuid associated with each RD Station contact Contacts > > uuid
custom_field_a	text	[en] Example of custom field
custom_field_b	timestamp	[en] Example of custom field
custom_field_c	text	[en] Example of custom field

Contacts: funnels

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

Relationships:

contact_uuid → Contacts > uuid

Status of contacts in RD Station Marketing funnels. Each row represents the position of a contact (identified by contact_uuid) in a funnel, with the lifecycle stage, fit and interest indicators, opportunity flag, origin and the email of the person responsible for the contact.

Campo	Tipo
contact_uuid	text	[en] Unique user identifier code Contacts > > uuid
contact_owner_email	text	[en] The email of the user responsible for the contact
fit	float	[en] The contact's fit score in the current funnel
interest	float	[en] The contact's interest score in the current funnel
lifecycle_stage	text	[en] The funnel stage the contact belongs to
opportunity	boolean	[en] Indicates whether the contact is an opportunity or not in the funnel
origin	text	[en] Origin of the contact in the funnel

Contacts: opportunity events

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

Relationships:

contact_uuid → Contacts > uuid

Opportunity-marking events of RD Station Marketing contacts. Each row represents an event in which a contact (identified by contact_uuid) was marked as an opportunity, bringing the event identifier and family, date/time, type and the associated funnel.

Campo	Tipo
contact_uuid	text	[en] Unique user identifier code Contacts > > uuid
event_number	float	[en] Event identifier created by Kondado
event_family	text	[en] Internal RDSM identifier
event_identifier	text	[en] Event identifier
event_timestamp	timestamp	[en] Event creation date/time, using the UTC format
event_type	text	[en] The event type (CONVERSION or OPPORTUNITY)
payload_funnel_name	text	[en] Funnel name

Contacts: tags

Replication type: Incremental with update window

Parameters:

Update window (days): How many days prior to the savepoint the data will still be replcated
Segmentation: Select the segmentation
Read start date (Savepoint): Data replication start date based on created date and last conversion date

Relationships:

uuid → Contacts > uuid

Tags of RD Station Marketing contacts. Each row corresponds to a contact (identified by the uuid) with the tags associated with it.

Campo	Tipo
uuid	text	[en] Unique identifier of the contact Contacts > > uuid
tags	text	[en] Contact's tags

Campo

Tipo

uuid

text

[en] Unique identifier of the contact

Contacts > > uuid

Email analytics

This integration is available only for Pro accounts (with a 45-day history limit) or Advanced accounts - other plans won't return data
The API returns data starting from August 2021. The data is consolidated up to the day before the analysis date (D-1) and is provided in UTC format.

Replication type: Incremental

Parameters:

Read start date (Savepoint): Data replication start date based on metric date
Period: Time granularity of the data
Update window: How many periods will be updated at each pipeline run

Relationships:

campaign_id → Emails > campaign_id

Performance metrics of RD Station Marketing e-mails (campaigns). Each row represents the statistics of an e-mail campaign in a period (interval between metric_start_date and metric_end_date), with counts and rates of deliveries, opens, clicks, bounces, discards, spam flags and unsubscribes.

Campo	Tipo
metric_start_date	timestamp	[en] Start date of the analysis period of the email metrics
campaign_id	text	[en] Campaign id Emails > > campaign_id
campaign_name	text	[en] Email campaign name
contacts_count	float	[en] Number of selected contacts
email_bounced_count	float	[en] Total of bounced e-mails
email_clicked_count	float	[en] Total of unique clicks per lead
email_clicked_rate	float	[en] Click rate compared to the number of delivered e-mails
email_delivered_count	float	[en] Total of delivered e-mails
email_delivered_rate	float	[en] Delivery rate
email_dropped_count	float	[en] Total of discarded e-mails
email_opened_count	float	[en] Total of unique opens per lead
email_opened_rate	float	[en] Open rate compared to the number of delivered e-mails
email_spam_reported_count	float	[en] Total reported as spam
email_spam_reported_rate	float	[en] Spam rate compared to the number of delivered e-mails
email_unsubscribed_count	float	[en] Total unsubscribed
send_at	timestamp	[en] E-mail send date
metric_end_date	timestamp	[en] End date of the analysis period of the email metrics

Emails

This pipeline is free

Replication type: Full

E-mails (e-mail marketing campaigns) from RD Station Marketing. Each row represents an e-mail, bringing name, type, status, associated campaign, send date, number of leads, predictive sending indicators and the contacts' behavior score distribution.

Campo	Tipo
id	text	[en] Email ID
behavior_score_info_disengaged	boolean	[en] Indicates whether disengaged leads are selected
behavior_score_info_engaged	boolean	[en] Indicates whether engaged leads are selected
behavior_score_info_indeterminate	boolean	[en] Indicates whether undetermined leads are selected
campaign_id	text	[en] Campaign ID
component_template_id	float	[en] ID of the email template component
created_at	text	[en] Email creation date
is_predictive_sending	boolean	[en] Indicates whether the campaign has predictive sending
leads_count	float	[en] Number of leads of the email
name	text	[en] Email name
send_at	text	[en] Email send date
sending_is_imminent	boolean	[en] Indicates whether the send is imminent
status	text	[en] Campaign status
type	text	[en] Email type
updated_at	text	[en] Email update date

Forms

This pipeline is free

Replication type: Full

Relationships:

conversion_identifier → Contacts: conversion events > event_identifier

Forms from RD Station Marketing. Each row represents a capture form, bringing title, conversion identifier, status and creation and update dates.

Campo	Tipo
id	text	[en] Unique identifier of the form
conversion_identifier	text	[en] Conversion identifier Contacts: conversion events > > event_identifier
created_at	timestamp	[en] Form creation date
status	text	[en] Publication status of the form
title	text	[en] Form title
updated_at	timestamp	[en] Date of the form's last update

Landing pages

This pipeline is free

Replication type: Full

Relationships:

conversion_identifier → Contacts: conversion events > event_identifier

Landing pages from RD Station Marketing. Each row represents a landing page, bringing title, conversion identifier, status, creation and update dates and indicators of active or already performed A/B tests (experiments).

Campo	Tipo
id	text	[en] Unique identifier of the landing page
conversion_identifier	text	[en] Conversion identifier Contacts: conversion events > > event_identifier
created_at	timestamp	[en] Landing page creation date
had_experiment	boolean	[en] Indicates whether the landing page has already had an A/B test
has_active_experiment	boolean	[en] Indicates whether the landing page has an active A/B test
status	text	[en] Publication status of the landing page
title	text	[en] Landing Page title
updated_at	timestamp	[en] Date and time of the landing page's last update

Pop Ups

This pipeline is free

Replication type: Full

Relationships:

conversion_identifier → Contacts: conversion events > event_identifier

Pop-ups from RD Station Marketing. Each row represents a pop-up, bringing title, conversion identifier, status, display trigger and creation and update dates.

Campo	Tipo
id	text	[en] Unique identifier of the pop-up
conversion_identifier	text	[en] Conversion identifier Contacts: conversion events > > event_identifier
created_at	timestamp	[en] Pop-up creation date
status	text	[en] Publication status of the pop-up
title	text	[en] Pop-up title
trigger	text	[en] Trigger for displaying the pop-up
updated_at	timestamp	[en] Date of the pop-up's last update

Webhook Leads

Replication type: Incremental

Main object

Leads from RD Station Marketing received in real time. Each row represents a lead with its profile data (name, email, phones, company, job title, location), funnel stage, Lead Scoring indicators (fit and interest), opportunity flag, number of conversions and details of the first and last conversion.

Campo	Tipo
id	text	[en] Lead ID in RD Station
bio	text	[en] Notes on the lead's profile
city	text	[en] Lead's city
company	text	[en] Name of the company associated with the lead
created_at	timestamp	[en] Date the lead was created
email	text	[en] Lead's email
first_conversion_conversion_origin_campaign	text	[en] Source campaign of the lead's first conversion
first_conversion_conversion_origin_channel	text	[en] Source channel of the lead's first conversion
first_conversion_conversion_origin_medium	text	[en] Source medium of the lead's first conversion
first_conversion_conversion_origin_source	text	[en] Origin source of the lead's first conversion
first_conversion_conversion_origin_value	text	[en] Source value of the lead's first conversion
first_conversion_created_at	timestamp	[en] Date and time of the lead's first conversion
first_conversion_cumulative_sum	float	[en] Cumulative total of the lead's conversions at the first conversion
first_conversion_source	text	[en] Source of the lead's first conversion
fit_score	text	[en] Lead Scoring fit profile of the lead
interest	float	[en] Lead Scoring interest of the lead
job_title	text	[en] Job title
last_conversion_conversion_origin_campaign	text	[en] Source campaign of the lead's last conversion
last_conversion_conversion_origin_channel	text	[en] Source channel of the lead's last conversion
last_conversion_conversion_origin_medium	text	[en] Source medium of the lead's last conversion
last_conversion_conversion_origin_source	text	[en] Origin source of the lead's last conversion
last_conversion_conversion_origin_value	text	[en] Source value of the lead's last conversion
last_conversion_created_at	timestamp	[en] Date and time of the lead's last conversion
last_conversion_cumulative_sum	float	[en] Cumulative total of the lead's conversions at the last conversion
last_conversion_source	text	[en] Source of the lead's last conversion
last_marked_opportunity_date	timestamp	[en] Date and time when the lead was last marked as an opportunity
lead_stage	text	[en] Lead's stage
mobile_phone	text	[en] Lead's mobile phone
name	text	[en] Lead's name
number_conversions	float	[en] Number of conversions
opportunity	boolean	[en] Whether the lead is an opportunity
personal_phone	text	[en] Lead's phone
phone	text	[en] Lead's main phone (E.164 format)
public_url	text	[en] Lead's public URL
state	text	[en] Lead's state
user	text	[en] Email of the lead's owner
uuid	text	[en] Unique identifier of the lead in RD Station
website	text	[en] Lead's website
__kdd_request_id	text	[en] ID of the request made to Kondado's webhook endpoint - returned to the application that made the POST
__kdd_request_unix_timestamp	float	[en] UNIX timestamp of the request made to Kondado's webhook endpoint - returned to the application that made the POST
__kdd_requester_key	text	[en] Key used to authenticate the POST made to Kondado's webhook endpoint

rdstation_leads_tags

Tags associated with leads. Each row represents a tag of a lead, relating to the leads table by lead_id (a lead can have several tags, generating several rows).

Campo	Tipo
lead_id	text	[en] ID of the lead the record refers to
tag	text	[en] Tag associated with the lead_id

rdstation_leads_first_conversion_content

Content of each lead's first conversion in key/value format. Each row represents a field filled by the lead in their first conversion, relating to the leads table by lead_id.

Campo	Tipo
lead_id	text	[en] ID of the lead the record refers to
key	text	[en] Field key of the first conversion
val	text	[en] Value filled in the first conversion by the lead_id for the field represented by the key in the key column

rdstation_leads_last_conversion_content

Content of each lead's last conversion in key/value format. Each row represents a field filled by the lead in their most recent conversion, relating to the leads table by lead_id.

Campo	Tipo
lead_id	text	[en] ID of the lead the record refers to
key	text	[en] Field key of the last conversion
val	text	[en] Value filled in the last conversion by the lead_id for the field represented by the key in the key column

rdstation_leads_custom_fields

Custom fields of each lead in key/value format. Each row represents a custom field and the value provided by the lead, relating to the leads table by lead_id.

Campo	Tipo
lead_id	text	[en] ID of the lead the record refers to
key	text	[en] Custom field key
val	text	[en] Value filled by the lead_id for the field represented by the key in the key column

Workflow email analytics

This integration is available only for Pro accounts (with a 45-day history limit) or Advanced accounts - other plans won't return data
The API returns data starting from January 2022. The data is consolidated and provided in UTC format.

Replication type: Incremental

Parameters:

Read start date (Savepoint): Data replication start date based on metric date
Period: Time granularity of the data
Update window: How many periods will be updated at each pipeline run

Performance metrics of e-mails sent by flow automations (workflows) of RD Station Marketing. Each row represents the statistics of an e-mail of a workflow in a period (interval between metric_start_date and metric_end_date), identifying the workflow and the action, with counts and rates of deliveries, opens, clicks, bounces, discards, spam flags and unsubscribes.

Campo	Tipo
metric_start_date	timestamp	[en] Start date of the analysis period of the automation email metrics
workflow_action_id	text	[en] Automation email id
email_name	text	[en] Name of the campaign sent by the automation
contacts_count	float	[en] Number of contacts reached by the automation email
count_processed	float	[en] Number of processed sends of the automation email
created_at	timestamp	[en] Creation date and time of the automation email
email_bounced_unique_count	float	[en] Total of bounced e-mails
email_clicked_rate	float	[en] Click rate compared to the number of delivered e-mails
email_clicked_unique_count	float	[en] Total of unique clicks per lead
email_delivered_count	float	[en] Total of delivered e-mails
email_delivered_rate	float	[en] Delivery rate
email_dropped_count	float	[en] Total of discarded e-mails
email_opened_rate	float	[en] Open rate compared to the number of delivered e-mails
email_opened_unique_count	float	[en] Total of unique opens per lead
email_spam_reported_count	float	[en] Total reported as spam
email_spam_reported_rate	float	[en] Spam rate compared to the number of delivered e-mails
email_unsubscribed_count	float	[en] Total unsubscribed
metric_end_date	timestamp	[en] End date of the analysis period of the automation email metrics
updated_at	timestamp	[en] Date and time of the automation email's last update
workflow_id	text	[en] Automation id
workflow_name	text	[en] Automation name

Asset analytics

This integration is available only for Pro accounts (with a 45-day history limit) or Advanced accounts - other plans won't return data
The API returns data starting from January 2022. The data is consolidated and provided in UTC format.

Replication type: Incremental

Parameters:

Read start date (Savepoint): Data replication start date based on metric date
Period: Time granularity of the data
Update window: How many periods will be updated at each pipeline run

Relationships:

asset_id → Landing pages > id
asset_id → Pop Ups > id
asset_id → Forms > id

Performance metrics of conversion assets (landing pages, pop-ups and forms) of RD Station Marketing. Each row represents the statistics of an asset in a period (interval between metric_start_date and metric_end_date), identifying the type and the asset, with total visits, total conversions and conversion rate.

Campo	Tipo
metric_start_date	timestamp	[en] Start date of the analysis period of the asset metrics
asset_id	text	[en] Unique identifier of the Asset Landing pages > > id Pop Ups > > id Forms > > id
account_id	text	[en] Unique identifier of the RD Station account related to the returned data
asset_identifier	text	[en] Textual name or identifier of the asset
asset_type	text	[en] Type of the asset (example: Landing Page)
asset_created_at	timestamp	[en] Date the asset was created
asset_updated_at	timestamp	[en] Date of the last update on the asset
visits_count	float	[en] Total number of visits to the asset during the requested period
conversion_count	float	[en] Total number of conversions generated by the asset in the requested period
conversion_rate	float	[en] Conversion rate of the asset
metric_end_date	timestamp	[en] End date of the analysis period of the asset metrics

Notes

Webhook Configuration

To finish configuring the webhook RD pipeline, follow the steps below:

1) It will be necessary to create a token on the Kondado platform so that the RD can send us data securely. At the top right, click your email and then Settings

2) On the settings page, click on the TOKENS menu and then on New token

3) Give the New Token a name (eg RD Token) and then click CREATE

4) After clicking CREATE, only this time Token Key and Token will be displayed. Copy these values into a text editor and click OK to continue with the tutorial

If you have not copied the Token value, it will not be displayed again. In this case, deactivate the previously generated key and restart the tutorial from step (4) onwards

5) Now, let's first create the pipeline and then continue the process. Go to the Kondado platform pipelines section and click on New Pipeline

6) Select your data destination, and as a data source use the one created in step (2)

7) Then select Leads (webhook) as the object to be replicated

8) Follow the normal creation flow and add a new pipeline

9) Once the pipeline is created, notice that the URL that will be in your browser's address bar will look something like

https://app.kondado.com.br/pipelines/123456

Copy the value after “pipelines/“, in this example it will be the value 123456 – this is your pipeline id (pipeline_id) and will be used next

10) Now login to RDStation marketing

11) In the upper right menu, click on “My account” and then on “Integrations”

12) On the integrations page, access the “My Integrations” tab, look for the “Webhooks” section and click on “Configure"

13) On the new screen, click on “Create Webhook”

14) In the popup that will open, fill in the information as follows:

Name: A name for internal use, for example “New Webhook”
URL: Fill in the URL by replacing values as instructed below:
Use https://k1.kondado.com.br?pipeline_id={pipelineid}&token={token}&key={tokenkey} replacing the values as follows:
- In {pipelineid} replace with the value obtained in step 11 (for example, 123456)
- In {token} replace with the value of the Token obtained in step 6 (it will be a large alphanumeric value and without hyphens)
- In {tokenkey} replace it with the value of the Token Key obtained in step 6 (it will be a smaller value than the token, and has hyphens)
Trigger: Select the trigger that will send data to the webhook:
- When sending Conversion data, leads that converted in RDStation Marketing will be sent, in addition you can choose below the Conversion Events that will be considered or leave blank to send all conversions:
- According to the RD Station website: “If the conversions are carried out in a Landing Page, Form or Pop-up of RD Station Marketing, the identifier will be the title of the page/name of the element created; if it is integrated (integrated forms, API, etc), they can be identified by the conversion identifier”
- When sending Opportunity data, leads marked as Opportunity will be sent – only after being marked as an opportunity (little star) manually or by an automation flow

In each execution of the integration, data from leads with the same id will be read only once. This means that if you use the same pipeline_id in the URL of different webhooks – for example one for Conversion and another for Opportunity, if a lead is sent twice, only one of these events will be considered. Therefore, we recommend that you create different integrations for Conversion and Opportunity – just repeat the step by step from step 7 for each Trigger, it is not necessary to create another token or another connector

15) Now just click on “Save Webhook” and you will see your new webhook that will start sending the data to your data warehouse or spreadsheet!

Historical Data

Webhook data is sent to its destination only from the time the webhook is created.

To send the leads that are already registered in your RD Station account (historical load), just click here and follow our tutorial

Only conversion events in RD Station cause leads to be sent to the webhook and thus replicated into your destination. If you want lead information to update in your destination when other types of lead changes are made, such as stage changes that don't set up conversion events, follow that tutorial here.

Tips on mismatches between integration and RD Station tool data

1) If you notice that any contact is not being sent to your destination table, we recommend checking that all conversion events are being correctly sent to the integration URL (check step 16 of the tutorial on this page).

2) Only conversion events in RD Station cause leads to be sent to the webhook and thus integrated into your destination. If you want lead information to update in your destination when other types of lead changes are made, such as stage changes that don't set up conversion events, follow that tutorial here.

3) Webhook data is sent to its destination only from the time the webhook is saved. To send contacts that are already registered in your RD Station account (historical load), just click here and follow our tutorial.

4)Some RD dashboard indicators are calculated differently. For example, the number of Leads on the dashboard shows all visitors who have at least one conversion in the period, whether it be the first one or not. Understanding what each metric in the tool's reports means is important for identifying possible divergences with the views created from Kondado's integration data. We recommend reading the RD Station documentation pages listed below to understand these differences:

5) Meaning of each metric in RD Station reports

6) RD Station dashboard indicators explained

Part of this documentation was automatically generated by AI and may contain errors. We recommend verifying critical information

Written by

Thassyo Pereira·Published 2025-12-09