RDStation is a Brazilian marketing automation and CRM tool that allows thousands of companies to enter the era of inbound marketing.
Adding 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
Summary
Relationship Chart
Contacts
Campo | 5) Login to Kondado, go to add data sources and select the Pushwoosh data source |
|
---|---|---|
text |
[pt] O uuid exclusivo associado a cada contato do RD Station |
|
timestamp |
[pt] Data de criação do contato |
|
text |
[pt] Email do contato |
|
timestamp |
[pt] Data da última conversão do contato |
|
text |
[pt] Nome do contato |
Contacts : Custom Fields
Field | Type | |
---|---|---|
text |
[pt] O uuid exclusivo associado a cada contato do RD Station |
|
text |
[pt] Exemplo de custom field |
|
timestamp |
[pt] Exemplo de custom field |
|
text |
[pt] Exemplo de custom field |
Contacts: Conversion Events
Main Objct
Field | Type | |
---|---|---|
text |
[pt] Código de identificador unico de usuario |
|
text |
[pt] Identificador interno do RDSM |
|
text |
[pt] Identificador do evento |
|
timestamp |
[pt] Data/hora de criação do evento |
|
text |
[pt] O tipo de evento (CONVERSION ou OPPORTUNITY) |
|
float |
||
text |
||
text |
||
text |
||
text |
||
float |
[pt] Identificador do evento criado pela Kondado |
rdstation_contatos_eventos_conversoes_traffic_source
Field | Type | |
---|---|---|
text |
[pt] Código de identificador unico de usuario |
|
float |
[pt] Identificador do evento criado pela Kondado |
|
text |
[pt] Chave do parâmetro identificado no payload traffic_source. A string original é identificada como __kdd_raw. Caso a string original seja uma URL, também serão enviados os valores __kdd_hostname para o hostname (por exemplo app.kondado.com.br) e __kdd_path para o path da URL (por exemplo /signup para a URL https://app.kondado.com.br/signup) |
|
text |
[pt] Valor do parâmetro identificado do payload traffic_source |
|
text |
[pt] Indica se os parâmetros referem-se à sessão atual (current) ou à primeira (first) |
Contacts: Opportunity Events
Field | Type | |
---|---|---|
text |
[pt] Código de identificador unico de usuario |
|
float |
[pt] Identificador do evento criado pela Kondado |
|
text |
[pt] Identificador interno do RDSM |
|
text |
[pt] Identificador do evento |
|
timestamp |
[pt] Data/hora de criação do evento, utilizando o formato UTC |
|
text |
[pt] O tipo de evento (CONVERSION ou OPPORTUNITY) |
|
text |
[pt] Nome do funil |
Contacts: Funnel
Field | Type | |
---|---|---|
text |
[pt] Código de identificador unico de usuario |
|
text |
[pt] O e-mail do usuário responsável pelo contato |
|
float |
[pt] A pontuação de ajuste do contato no funil atual |
|
float |
[pt] A pontuação de interesse do contato no funil atual |
|
text |
[pt] O estágio no funil ao qual o contato pertence. |
|
boolean |
[pt] Indica se o contato é uma oportunidade ou não no funil |
|
text |
Contacts: Tags
Emails
Field | Type | |
---|---|---|
float |
[pt] ID do email |
|
boolean |
[pt] Informa se estão selecionados leads desengajados |
|
boolean |
[pt] Informa se estão selecionados leads engajados |
|
boolean |
[pt] Informa se estão selecionados leads indeterminados |
|
float |
[pt] ID da campanha |
|
float |
[pt] ID do componente do template de email |
|
text |
[pt] Data da criação do email |
|
boolean |
[pt] Informa se a campanha tem envio preditivo |
|
float |
[pt] Quantidade de leads do email |
|
text |
[pt] Nome do email |
|
text |
[pt] Data do envio do email |
|
boolean |
[pt] Informa se o envio é iminente |
|
text |
[pt] Status da campanha |
|
text |
[pt] Tipo do email |
|
text |
[pt] Data da atualização do email |
Forms
Field | Type | |
---|---|---|
float |
[pt] Identificador único do formulário |
|
text |
[pt] Identificador da conversão |
|
timestamp |
[pt] Data de criação do formulário |
|
text |
[pt] Status de publicação do formulário |
|
text |
[pt] Título do formulário |
|
timestamp |
[pt] Data da última atualização do formulário |
Landing Pages
Field | Type | |
---|---|---|
float |
[pt] Identificador único da landing page |
|
text |
[pt] Identificador da conversão |
|
timestamp |
[pt] Data de criação da landing page |
|
boolean |
[pt] Informa se a landing page já possuiu um teste A/B |
|
boolean |
[pt] Informa se a landing page possui um teste A/B ativo |
|
text |
[pt] Status de publicação da landing page |
|
text |
[pt] Título da Landing Page |
|
timestamp |
Pop Ups
Field | Type | |
---|---|---|
float |
[pt] Identificador único do pop-up |
|
text |
[pt] Identificador da conversão |
|
timestamp |
[pt] Data de criação do pop-up |
|
text |
[pt] Status de publicação do pop-up |
|
text |
[pt] Título do Pop-up |
|
text |
[pt] Gatilho para exibição do pop-up |
|
timestamp |
[pt] Data da última atualização do pop-up |
Workflow email analytics
Campo | Tipo | |
---|---|---|
timestamp |
||
text |
[pt] Id do email de automação |
|
float |
||
float |
||
timestamp |
||
float |
[pt] Total de e-mails de rejeitados |
|
float |
[pt] Taxa de cliques em comparação com o número de e-mails entregues |
|
float |
[pt] Total de cliques únicos por lead |
|
float |
[pt] Total de e-mails entregues |
|
float |
[pt] Taxa de entrega |
|
float |
[pt] Total de e-mails descartados |
|
text |
[pt] Nome da campanha enviada pela automação |
|
float |
[pt] Taxa de abertura em comparação com o número de e-mails entregues |
|
float |
[pt] Total de aberturas únicas por lead |
|
float |
[pt] Total reportado como spam |
|
float |
[pt] Taxa de spam em comparação com o número de e-mails entregues |
|
float |
[pt] Total não inscrito |
|
timestamp |
||
timestamp |
||
text |
[pt] Id da automação |
|
text |
[pt] Nome da automação |
Email analytics
Campo | Tipo | |
---|---|---|
timestamp |
||
float |
[pt] Id da campanha |
|
text |
[pt] Nome da campanha de e-mail |
|
float |
[pt] Quantidade de contatos selecionados |
|
float |
[pt] Total de e-mails de rejeitados |
|
float |
[pt] Total de cliques únicos por lead |
|
float |
[pt] Taxa de cliques em comparação com o número de e-mails entregues |
|
float |
[pt] Total de e-mails entregues |
|
float |
[pt] Taxa de entrega |
|
float |
[pt] Total de e-mails descartados |
|
float |
[pt] Total de aberturas únicas por lead |
|
float |
[pt] Taxa de abertura em comparação com o número de e-mails entregues |
|
float |
[pt] Total reportado como spam |
|
float |
[pt] Taxa de spam em comparação com o número de e-mails entregues |
|
float |
[pt] Total não inscrito |
|
timestamp |
||
timestamp |
[pt] Data de envio do e-mail |
Webhook Leads
Main Object
Field | Type | |
---|---|---|
text |
[pt] ID do lead no RD Station |
|
text |
[pt] Anotacoes no perfil do lead |
|
text |
[pt] Cidade do lead |
|
text |
[pt] Nome da empresa associada ao lead |
|
timestamp |
[pt] Data em que o lead foi criado |
|
text |
[pt] Email do lead |
|
text |
||
text |
||
text |
||
text |
||
text |
||
timestamp |
||
float |
||
text |
||
text |
[pt] Perfil do Lead Scoring do lead |
|
float |
[pt] Interesse do Lead Scoring do lead |
|
text |
[pt] Cargo |
|
text |
||
text |
||
text |
||
text |
||
text |
||
timestamp |
||
float |
||
text |
||
timestamp |
||
text |
[pt] Estagio do lead |
|
text |
[pt] Celular do lead |
|
text |
[pt] Nome do lead |
|
float |
[pt] Numero de conversoes |
|
boolean |
[pt] Se o lead e uma oportunidade |
|
text |
[pt] Telefone do lead |
|
text |
[pt] URL publica do lead |
|
text |
[pt] Estado do lead |
|
text |
[pt] Email do dono do lead |
|
text |
||
text |
[pt] Site do lead |
|
text |
[pt] ID do request feito ao endpoint de wehbook da Kondado - retornado para a aplicacao que fez o POST |
|
float |
[pt] UNIX timestamp do request feito ao endpoint de wehbook da Kondado - retornado para a aplicacao que fez o POST |
|
text |
[pt] Chave utilizada para autenticar o POST feito ao endpoint de webhook da Kondado |
rdstation_leads_tags
Field | Type | |
---|---|---|
text |
[pt] ID do lead ao qual o registro se refere |
|
text |
[pt] Tag associada ao lead_id |
rdstation_leads_first_conversion_content
Field | Type | |
---|---|---|
text |
[pt] ID do lead ao qual o registro se refere |
|
text |
[pt] Chave do campo da primeira conversao |
|
text |
[pt] Valor preenchido na primeira conversao pelo lead_id para o campo representado pela chave da coluna key |
rdstation_leads_last_conversion_content
Field | Type | |
---|---|---|
text |
[pt] ID do lead ao qual o registro se refere |
|
text |
[pt] Chave do campo da ultima conversao |
|
text |
[pt] Valor preenchido na ultima conversao pelo lead_id para o campo representado pela chave da coluna key |
rdstation_leads_custom_fields
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: