Configuring RD Station as a Source
In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the RD Station option from the list of connectors. Click Next and you’ll be prompted to add your access.1. Add account access
- Click Next and you’ll be prompted to login with your account to grant permissions for Nekt to extract data from your RD Station Marketing account.
-
After successful authentication, you’ll be prompted to configure additional settings:
- Start Date: The earliest record date to sync. This defines the starting point for data extraction - only records created or modified after this date will be synchronized.
- Enable Contact Custom Fields: Define whether the user should have access to details about contacts or not. Should be used with caution since the extraction time can increase significantly when enabled, as it requires an additional request for each contact.
-
Contacts Extraction Mode: Define which segmentation lists the connector should extract. Each segmentation will be extracted to a separate table in your Lakehouse.
- Entire Lead Base: Extract all contacts from your account.
- Segmentation Lists: Extract only contacts from specific segmentation lists.
- Entire Lead Base and Segmentation Lists: Extract contacts from both the entire base and from specified segmentation lists.
Please note contacts who are in different segmentation lists may be extracted multiple times.-
Extract Custom Fields as JSON: When enabled, all contact custom fields are extracted as a single JSON string column (
custom_fields) instead of one column per field. This keeps the schema stable when custom fields are added or changed in RD Station, and prevents failures caused by inconsistent or out-of-range custom field values. - Segmentation List IDs: The IDs of the segmentation lists to extract contacts from if you want to filter only specific lists to speed up extraction. If not provided, contacts from all segmentation lists will be extracted.
-
Enable Contact Funnels: Extract the funnel of each contact (whether it is marked as an opportunity, its lifecycle stage and its fit and interest scores) into the
contact_funnelsstream. RD Station only exposes this per contact, so it costs one extra request per contact, capped at about 120 requests per minute on most plans (500 on Advanced). A good estimate of the extra time is the number of contacts divided by 120, in minutes.- Contact Funnels Segmentation List ID: Restrict the stream to the contacts of a single segmentation list. Leave it empty to read every contact in your lead base, which is much slower. Creating a segmentation list in RD Station filtered by “is an opportunity” and setting it here is the fastest way to track opportunities.
- Contact Funnels Parallel Workers: Number of funnel requests fetched in parallel (1 to 8, default 1). The gain is bounded by RD Station’s rate limit per account, so only raise it on an Advanced account.
-
Enable Contact Opportunity Events: Extract the history of when each contact was marked as an opportunity into the
contact_opportunity_eventsstream. It also costs one extra request per contact under the same rate limit. RD Station records no event when a contact stops being an opportunity, so this stream shows when contacts became opportunities and never when they left.- Contact Opportunity Events Segmentation List ID: Restrict the stream to the contacts of a single segmentation list. Leave it empty to read every contact in your lead base.
- Contact Opportunity Events Parallel Workers: Number of event requests fetched in parallel (1 to 8, default 1), bounded by the same rate limit.
- Analytics Backfill Months: How many months of history the analytics streams extract (default 12). RD Station limits these reports to 120 requests per hour, and the streams that must query day by day spend one request per day of history, so an unbounded backfill turns into a run that never finishes. Set 0 to remove the ceiling and crawl from August 2021, when RD Station analytics data begins.
- Click Next.
2. Select streams
-
The next step is letting us know which streams you want to bring. You can select entire groups of streams or only a subset of them.
Tip: The stream can be found more easily by typing its name.
Thecampaignsstream is only available for RD accounts with access to the Campaign Manager (Gerenciador de Campanhas) feature. When the account cannot consume the campaigns API, the stream is skipped with a warning and the other streams still run.Theanalytics_funnelstream is only available for RD accounts with access to the Advanced plan.Theanalytics_email_stats,analytics_workflow_email_statsandanalytics_conversion_assetsstreams are only available for RD accounts with access to the Professional plan.Thecontact_eventsandcontact_detailsstreams are only available if you extract the entire lead base, either by selectingEntire Lead BaseorEntire Lead Base and Segmentation Lists.Thecontact_funnelsandcontact_opportunity_eventsstreams are only discovered when the corresponding Enable contact funnels / Enable contact opportunity events setting is turned on. - Click Next.
3. Configure data streams
Customize how you want your data to appear in your catalog. Select the layer, a name for each table (which will contain the fetched data) and the type of sync.- Layer: companies in the Growth plan can choose in which layer the tables with the extracted data will be placed.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
4. Configure data source
Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc. To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times). Optionally, you can define some additional settings (if available).- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
5. Check your new source
You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.Streams and Fields
Available streams
The table below lists every stream, its slug (the exact identifier to pass when creating the source via API) and a short description. Streams marked optional are only discovered when the corresponding setting is enabled or the RD Station plan grants access.Fields by stream
Below you’ll find all available data streams from RD Station and their corresponding fields:Segmentations
Segmentations
Stream for managing segmentation lists in your RD Station account. Segmentations allow you to group contacts based on specific criteria for targeted marketing campaigns.Key Fields:
Segmentation Contacts
Segmentation Contacts
Stream for extracting contacts from segmentation lists. When extracting from the entire lead base, a single
segmentation_contacts table is created. When extracting from specific segmentation lists, separate tables are created with the naming pattern segmentation_contacts_{segmentation_id}.
Note: Streams for segmentation lists created in your RD Station account after this source was configured are skipped automatically. To extract a newly created segmentation list, you must refresh the source’s streams and select the new segmentation_contacts_{id} stream.
Key Fields:Contact Details
Contact Details
Detailed contact information including custom fields. This stream is only available when extracting the entire lead base and requires enabling the “Contact Custom Fields” option.
Note: Enabling this stream significantly increases extraction time as it requires an additional API request for each contact.Key Fields:
Contact Events
Contact Events
Stream for extracting conversion events associated with contacts. This stream is only available when extracting the entire lead base.Key Fields:
Contact Funnels
Contact Funnels
Current funnel state of every contact: the opportunity flag and the lifecycle stage. Only discovered when the “Enable Contact Funnels” setting is on. The stream pages through a contact listing (the entire lead base or the configured segmentation list) and fetches the funnel of each contact with one request per contact.
Note: This stream is always a full-table snapshot. No RD Station endpoint carries a timestamp that advances when a contact’s funnel changes, and a contact that stops being an opportunity has to disappear from the table. If most funnels cannot be read in a run, the stream aborts instead of replacing the table with null values.Key Fields:
Contact Opportunity Events
Contact Opportunity Events
History of when each contact was marked as an opportunity. Only discovered when the “Enable Contact Opportunity Events” setting is on. The companion of
contact_funnels: that one is the current state, this one is how the contact got there. The stream is incremental on event_timestamp.
Note: RD Station emits no event when a contact is unmarked, so the table shows when a contact became an opportunity (possibly several times) and never when it stopped being one. Pair it with contact_funnels if the exit date matters.
Key Fields:Campaigns
Campaigns
Stream for managing email marketing campaigns and their settings. Only available for accounts with access to the Campaign Manager (Gerenciador de Campanhas) feature; otherwise the stream is skipped with a warning.Key Fields:
Emails
Emails
Stream for managing individual email communications within campaigns.Key Fields:
Workflows (Automated Workflows)
Workflows (Automated Workflows)
Stream for managing marketing automation workflows.Key Fields:
Landing Pages
Landing Pages
Stream for managing landing pages used for lead capture.Key Fields:
Embeddables (Forms)
Embeddables (Forms)
Stream for managing embeddable forms that can be placed on external websites.Key Fields:
Popups
Popups
Stream for managing popup forms and lead capture overlays.Key Fields:
Analytics Funnel (Advanced Plan)
Analytics Funnel (Advanced Plan)
Daily funnel analytics showing lead progression through marketing stages. Only available for accounts with the Advanced plan.Key Fields:
Analytics Email Stats (Professional Plan)
Analytics Email Stats (Professional Plan)
Email campaign performance statistics. Only available for accounts with the Professional plan.Key Fields:
Analytics Workflow Email Stats (Professional Plan)
Analytics Workflow Email Stats (Professional Plan)
Email performance statistics for workflow automation emails. Only available for accounts with the Professional plan.Key Fields:
Analytics Conversion Assets (Professional Plan)
Analytics Conversion Assets (Professional Plan)
Performance statistics for conversion assets (landing pages, forms, popups). Only available for accounts with the Professional plan.Key Fields:
Data Model
The following diagram illustrates the relationships between the core data streams in RD Station. The arrows indicate the primary links mapping marketing assets to their respective analytics and contacts.Use Cases for Data Analysis
This guide outlines valuable business intelligence use cases when consolidating RD Station data, along with ready-to-use SQL queries that you can run on Explorer.Lead Generation Analysis
1. Marketing Funnel Performance
Track the progression of leads through your marketing funnel over time to identify bottlenecks and opportunities. Business Value:- Identify which funnel stages have the highest drop-off rates
- Track conversion rates between funnel stages
- Monitor trends in lead generation and sales performance
- Optimize marketing strategies based on funnel insights
SQL query
SQL query
- AWS
- GCP
Sample Result
Sample Result
2. Lead Source Attribution
Analyze which traffic sources and campaigns generate the most conversions to optimize marketing spend. Business Value:- Identify the most effective traffic sources for lead generation
- Understand which campaigns drive the highest conversion rates
- Allocate marketing budget more effectively
- Track ROI by marketing channel
SQL query
SQL query
- AWS
- GCP
Sample Result
Sample Result
Email Marketing Performance
3. Campaign Email Performance
Analyze the performance of email campaigns to optimize email marketing strategies. Business Value:- Identify top-performing email campaigns
- Track engagement metrics over time
- Reduce unsubscribe and spam report rates
- Improve email deliverability and click-through rates
SQL query
SQL query
- AWS
- GCP
Sample Result
Sample Result
4. Workflow Automation Performance
Track the effectiveness of automated email workflows to optimize nurturing sequences. Business Value:- Identify high-performing automation workflows
- Compare email performance across different workflow steps
- Optimize workflow sequences based on engagement data
- Reduce drop-off in nurturing campaigns
SQL query
SQL query
- AWS
- GCP
Sample Result
Sample Result
Conversion Asset Analysis
5. Landing Page and Form Performance
Analyze the performance of landing pages, forms, and popups to optimize conversion rates. Business Value:- Identify top-performing conversion assets
- Track conversion rates across different asset types
- Prioritize optimization efforts on high-traffic, low-conversion assets
- Compare performance across different time periods
SQL query
SQL query
- AWS
- GCP
Sample Result
Sample Result
6. Contact Base Analysis
Analyze your contact base to understand lead acquisition trends and engagement patterns. Business Value:- Understand lead acquisition trends over time
- Identify periods of high contact growth
- Track conversion activity patterns
- Monitor contact database health
SQL query
SQL query
- AWS
- GCP