# Hotmart

Connect a Hotmart account as a data source: the app credentials and webhook it needs, the buyers, subscriptions and purchases it syncs in real time, how its fields map to Instasent attributes, and how to map its marketing status to consent.

**Language:** en
**Audience:** platform
**TLDR:** Hotmart is a native connector for selling digital products that syncs buyers, subscriptions and purchases into Instasent, with real-time events that can trigger automations. You connect it with app credentials (Client ID and Client Secret) you create in Hotmart and paste into Instasent, plus a required setup step: paste an Instasent webhook URL back into Hotmart so it posts events.
**Translation key:** platform.data-sources.connectors.hotmart
**Search keywords:** Hotmart, digital products, content creator, infoproducts, API key, client id, client secret, webhook, buyers, subscriptions, purchases, connect Hotmart, Hotmart integration, Hotmart consent
**Related pages:** /platform/es/data-sources/connectors/hotmart, /platform/en/data-sources/connectors, /platform/en/data-sources/connectors/activecampaign, /platform/en/data-sources/managing, /platform/en/consent
**Docs index (every page):** https://docs.instasent.com/llms.txt
**This zone's index:** https://docs.instasent.com/platform/en/llms.txt
**This page:** https://docs.instasent.com/platform/en/data-sources/connectors/hotmart/ (HTML) · https://docs.instasent.com/platform/en/data-sources/connectors/hotmart.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/data-sources/connectors/hotmart.md

Hotmart is the native connector for creators and businesses selling digital products.
Once connected, it syncs your buyers, subscriptions and purchases into Instasent so your
audience and your sales activity stay current — and it delivers events in real time, so
you can trigger automations the moment a purchase happens.

## How to connect

Hotmart connects with an **[API key](/platform/en/data-sources/connectors#api-key)**:
you create app credentials in Hotmart, paste them into Instasent, and then finish setup
by pasting an Instasent webhook URL back into Hotmart. You provide two values — a
**Client ID** and a **Client Secret** — and complete a **required setup step** to
receive real-time events.

> **Warning**: Create the app credentials in Hotmart **before** connecting. The panel won't let you
> continue without valid credentials.

#### 1. Get your app credentials in Hotmart

In Hotmart, create the app credentials and copy the **Client ID** and **Client
Secret**.

#### 2. Add the data source

In **Data sources**, select **Add data source** and choose **Hotmart** from the
Integrations section.

#### 3. Enter your credentials and connect

On the **Connect** step, fill in your **Client ID** and **Client Secret**, then
connect.

#### 4. Complete the required setup

After connecting, Instasent shows a **setup step** with a webhook URL. Copy that URL
and paste it into Hotmart so it can post events to Instasent. Until this step is
done, real-time events don't arrive.

#### 5. Initial import

The connector imports your existing buyers and purchases, then keeps receiving new
events in real time.

After connecting, the wizard continues through **Mapping**, **Merge** and **Tags**, the
same steps as a CSV import.

![The Hotmart connector page with its description, what it imports, and the contact fields it maps, with Connect Hotmart to start](/platform/en/data-sources/images/hotmart--1-connect.png)
*The Hotmart connector page: what it brings into Instasent and the contact fields it maps, with Connect Hotmart to start.*

## What it syncs

- **Contacts** — your Hotmart buyers, with name, email and phone.
- **Purchases and subscriptions** — sales events, delivered **in real time** via the
  webhook, for use in segments and automations. Because events arrive as they happen,
  they can **trigger automations** immediately.

The direction is one-way, **from Hotmart into Instasent**. Contacts unify by email and
phone — see [unification](/platform/en/data-sources/managing#how-unification-works).

### The events it brings in

The real value of the connection is its **events**: every purchase and subscription
moment Instasent receives in real time becomes something you can segment on or trigger
an automation from. Hotmart is the richest ecommerce connector for events because it
covers the full **purchase lifecycle** (*order created*, *paid*, *cancelled*,
*chargeback*, *refunded*, *checkout abandoned*) **and subscriptions** — a
subscription-plan *change*, *cancellation* or *renewal*. That subscription layer is
what makes it powerful for recurring revenue: welcome a new subscriber, win back a
cancellation, or celebrate a renewal, all automatically.

![The Hotmart connector's Event triggers list: order created, updated, cancelled, paid, chargeback and refunded, checkout abandoned, and subscription plan change, cancelled and renewed](/platform/en/data-sources/images/hotmart--2-event-triggers.png)
*The purchase and subscription events Instasent receives from Hotmart in real time — including subscription-plan changes, cancellations and renewals you can automate around recurring revenue.*

## Field mapping

Hotmart buyer fields map to the matching Instasent attributes (email to `_email`, phone
to `_phone_mobile`, name fields to theirs), and purchase and subscription data arrives
as events. Confirm the mapping on setup; see
[field mapping](/platform/en/data-sources/managing#field-mapping).

## Consent mapping

{/* VERIFY: the exact Hotmart → Instasent consent mapping is not yet confirmed. The mapping below applies the consent golden rule; confirm against the connector's actual behaviour before treating it as definitive. */}

Map Hotmart's marketing status to Instasent's marketing-preference attribute
(`_accepts_marketing_*`) following the consent golden rule:

| Hotmart status     | Instasent value | Meaning                     |
| ------------------ | --------------- | --------------------------- |
| Opted in           | `true`          | Accepted marketing          |
| No status recorded | `null`          | No preference               |
| Opted out          | `false`         | Actively declined marketing |

Only an **active opt-out** becomes `false`. A buyer with no recorded marketing status
maps to **no preference** (`null`), never to `false`. See
[Consent](/platform/en/consent/marketing-preference-vs-suppression).

---

This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.