Integrating RD Station with Google Ads lets a lead that became an opportunity or a sale in RD Station return to the campaign as a conversion. Without it, Google only knows that someone filled out a form and optimizes to bring in more forms, good or bad. There are three ways. Store the click’s GCLID in the lead and import the stages, use a ready-made connector that sends the stage automatically, or use enhanced conversions for leads, which match the lead by email.
Why connect RD Station to Google Ads
Because qualification happens in RD Station, and bidding happens in Google Ads. As long as the two don’t talk to each other, the campaign learns from the wrong data.
A quote request form is worth the same to Google whether it came from a student doing research or a purchasing director. In RD Station, the first dies as a lead and the second becomes an opportunity. That difference is what needs to go back to the ad account, with a date and, if possible, a value, so the platform can learn which clicks actually led to real business. The general logic is in the guide on offline conversions in Google Ads. Here we cover the specific case of those who already use RD.
What needs to be in place before integrating
Before choosing a path, check four things in your account and on your site.
- Auto-tagging turned on in Google Ads. It is what adds the GCLID to the URL of each click.
- One import-type conversion action for each stage you will send, such as qualified lead, opportunity and sale.
- A form that stores the GCLID with the lead, in a dedicated field in RD Station.
- A cookie notice and consent in line with local rules, which Google also requires.
Google’s help page on offline conversions with GCLID, which we opened on 10/20/2026, lists these requirements and notes that the GCLID is case-sensitive. A field that converts everything to lowercase ruins the whole import.
It also says to wait four to six hours between creating the conversion action and sending the first data. If the upload goes out sooner, conversions can take up to two days to show up.
Path 1: GCLID in the lead and import
This is the most controlled path and the one that doesn’t depend on any third-party app.
- On the form page, a script reads the gclid parameter from the URL and stores it in a cookie, so the data isn’t lost if the person navigates elsewhere before converting.
- The form gets a hidden field that receives this value on submission.
- In RD Station, the hidden field becomes a custom lead field. Check the RD documentation to see how your form type, an RD landing page or your own site, handles hidden fields.
- When the lead moves to a new stage, you export the GCLID, conversion name, date and time, and value.
- The file goes into Google Ads through Data manager, via Google Sheets or a scheduled upload.
Timing matters. According to Google’s help pages, imports through Google Sheets, HTTP, SFTP and cloud storage accept conversions from clicks up to 90 days old. CRM connectors such as Salesforce and HubSpot work with a 14-day window. A sale that closes after that doesn’t make it back to the campaign.
The script and the hidden field are usually installed through Tag Manager. If you don’t have it yet, start with Google Tag Manager.
Path 2: ready-made RD Station connector
The RD Station integrations catalog lists an app that connects RD Station Marketing to the Google Ads API. According to the integration page, it is built by a partner company, not by RD itself, and it sends the conversions you choose and the leads marked as Opportunity, each tied to a Google Ads conversion action.
The setup described there has four steps: install the app, authorize access to the Google Ads account, choose the account and conversion actions, and map each RD event to an action. It only sends new events, after setup.
There are also Zapier templates that trigger an offline conversion in Google Ads when an opportunity is created in RD Station. Both shortcuts save you from writing code, but they have a monthly cost and put a third party between your leads and your account. Read what each one does with your data before authorizing.
Path 3: enhanced conversions for leads
Instead of the GCLID, Google matches the lead using the hashed email or phone number the person entered in the form. Google’s same help page recommends starting with this model if you don’t import offline conversions yet.
It solves a common RD problem: the GCLID that gets lost when the lead goes through a redirect, an iframe or WhatsApp. The email stays in RD either way. The setup details are in enhanced conversions in Google Ads.
| Path | What you need | Window | Who maintains it | Who it’s for |
|---|---|---|---|---|
| GCLID and import | Script, hidden field, export | Up to 90 days via Sheets | You or the agency | Those who want full control |
| RD catalog connector | Partner app and authorization | New events after setup | The partner | Those who want less code |
| Zapier | Zapier account and template | Depends on the flow | You | Low volume of opportunities |
| Enhanced conversions for leads | Email in the form and tag | Set by Google | You or the agency | Those who lose the GCLID along the way |
Which stage to send in the RD Station Google Ads integration
Send more than one stage, and let Google optimize for the deepest one that has volume.
The submitted form keeps being measured by the site tag. Qualified lead, opportunity and sale come from RD Station. At first, the form stays as the primary conversion and the RD stages are added as secondary, just for observation. Once the opportunity or the sale reaches steady volume, it becomes the primary one.
Assign a value to each stage, or bidding keeps treating every lead the same. The calculation is in conversion value in Google Ads.
Mistakes that make the sale disappear along the way
- GCLID lost because the ad sends people straight to WhatsApp, without going through the page. The case is covered in Google Ads for WhatsApp.
- Form inside an iframe, which can’t see the parent page’s URL.
- RD field that truncates the text or changes letter case.
- Old lead that came back through email marketing and is attributed to a click from months ago.
- Import done once a quarter, with part of the conversions outside the window.
- The same sale sent through two paths at once, connector and spreadsheet.
- Messy UTMs, which keep you from separating what came from paid Google in RD. The standard is in UTM.
How to check that the RD Station Google Ads integration worked
Compare three numbers from the same period: opportunities in RD Station with a filled GCLID, opportunity conversions recorded in Google Ads, and the import diagnostics report inside the account.
If RD shows 30 opportunities with a GCLID and Google Ads shows 12, something is being rejected. The Data manager diagnostics tell you the reason for each row, such as click outside the window, invalid GCLID or wrong conversion action.
How much people search for this
Small, very specific search volume. People searching for rd station google ads already have the problem in hand. In Google Ads Keyword Planner, in October 2026, rd station google ads had 10 searches per month in Brazil and no estimated top-of-page bid. Anyone typing this already has RD Station and a running campaign. Google Suggest shows that the neighboring question is integrating RD with WhatsApp, WordPress and RD Station CRM itself.
How Ciclicko makes this connection
We start with the RD funnel, stage by stage, and with the source of the leads entering it. Then we choose the path with you, install GCLID capture or enhanced conversions through Tag Manager, create the conversion actions and check the first import row by row. We don’t promise lower costs, because the effect depends on the volume of opportunities the account generates.
Want RD Station sales to teach your campaign?
The Google Ads conversion tracking with CRM service connects RD Station, or another CRM, to the ad account, with stage, date and value. It’s what makes Google stop buying forms and start looking for people who buy.
Frequently asked questions
How do you integrate RD Station with Google Ads? Store the click’s GCLID in a lead field and import the stages into Google Ads, use a connector from the RD integrations catalog, or turn on enhanced conversions for leads, which match by email.
Does the RD Station Marketing and CRM integration change anything for Google Ads? The opportunity and the sale are usually marked in the CRM. If the CRM and Marketing are integrated, the stage has to reach the lead that stored the GCLID, otherwise the import can’t match the click.
Does the RD Station integration with WordPress store the GCLID? Only if the site form has a hidden field for the GCLID and that field is mapped to a lead field in RD.
Do leads that arrive through WhatsApp get included in the integration? Only if they pass through a page that records the click before opening the conversation. An ad that opens WhatsApp directly loses the GCLID.
How long can I import a sale? By spreadsheet and file upload, up to 90 days after the click. Connectors like Salesforce and HubSpot work with 14 days, according to Google’s help documentation.