# RD Station

> Turning RD Station Marketing on in Ready-made integrations with the API key. Each event creates or updates the lead by e-mail with a conversion; a redone delivery may repeat the conversion in the history, but the lead is not duplicated. A visitor's form submission never changes an existing lead.

RD Station Marketing receives each event as a **conversion** on the lead: *"Creates or updates the lead in RD Station Marketing with a conversion for each event."* Whoever joins the community or buys becomes a lead (or updates the existing one), ready for your automation flows and segments.

*Role: owner and admin.* How to turn on, test, disable and remove any app is in [Ready-made integrations](/integracoes/integracoes-prontas).

## 1. Copy the API key in RD Station

1. In RD Station Marketing, open **Settings** › **Integrations** › **API keys**.
2. Copy the key (create one if there is none yet).

Keep it like a password: whoever has the key creates conversions in your account.

## 2. Turn it on in Memberfy

1. In **Settings › Integrations and APIs › Integrations**, click **RD Station Marketing**.
2. Paste it into **API key**.
3. Choose the events and check **This app will receive: The person's name, e-mail and phone and the product name.**
4. Click **Turn on** and then **Send test**. The test only checks the key: it creates no lead.

## What arrives

The lead is identified by **e-mail**: if it exists, it is updated; if not, it is created with the name and e-mail. When the member added a phone, it goes into the lead's **mobile phone** field (`mobile_phone`).

| Event | Conversion on the lead |
|---|---|
| A member joined the community | *Joined the {community address} community* |
| A purchase was completed | *Bought {product}* |
| A subscription was canceled | *Canceled {product}* |
| A form was submitted | *Submitted the form {form}*, with the name, e-mail, mobile phone, company and job title from the [form](/espacos/formularios) |

The conversion name goes out in the community's language. Use these names as automation triggers or segment filters in RD Station.

### Form submissions

- **A visitor never changes an existing lead.** Anyone can type someone else's e-mail into an open form. So a visitor's submission (or a member's with another e-mail) records **only the conversion**, without changing the lead's data or the legal basis.
- **A signed-in member's submission with their own profile e-mail** records the conversion and, when they accepted the consent, the communication legal basis (consent). With **Forms update existing contacts** on, it also updates the lead's name, phone, company and job title.
- **Turned RD Station on before?** The installation doesn't get the event on its own: open RD Station Marketing in **Integrations**, check **A form was submitted** and save. A new installation already comes with it.

> [!NOTE]
> A redone delivery (a retry after an answer got lost, or a **Resend**) may **repeat the conversion** in the lead's history. The lead **is not duplicated**: RD Station identifies it by e-mail.

## Common problems

- **"The provider refused the credentials."** The key was revoked or changed in RD Station. Paste the new one and save.
- **The app became Failing.** See [Turned off after failures](/integracoes/integracoes-prontas#turned-off-after-failures).

## Related

- [Ready-made integrations](/integracoes/integracoes-prontas)
- [HubSpot](/integracoes/hubspot)