Integrations

Dodo Payments

Connect Dodo Payments so Bantico can attribute completed payments back to the tracked link, campaign, source, medium, content, and lead that drove the customer.

The strongest Dodo Payments attribution comes from passing Bantico context directly into payment metadata. That means sending fields like linkId, campaignId, source, medium, content, and leadId.

How to connect Dodo Payments

Here's the quickest way to connect Dodo Payments to Bantico.

Open Dodo Payments API keys.
Create a new API key for Bantico.
Name it something like Bantico.
Copy the generated key.
Open your Bantico project settings.
Go to Integrations.
Click Connect for Dodo Payments.
Paste the API key.
Save the integration.

After that, Bantico can start using Dodo Payments outcomes in your attribution reporting.

Bantico uses visitor and session cookies to persist attribution on the same site. If you need consent-first behavior for EU users, only load Bantico after consent is granted.

There is no separate data-persist flag in the current Bantico loader. Use the normal Bantico script and gate when you load it.

index.html

1<script>2  window.BANTICO_TOKEN = "YOUR_TOKEN";3</script>4<script src="https://app.bantico.com/bantico.js"></script>

How attribution works

When a Dodo payment arrives, Bantico tries to resolve attribution using the strongest available context.

Dodo Payments metadata
Tracked-link and campaign context already present on the session
Identified user data such as email, if available

The most reliable setup is always sending Bantico context directly into Dodo payment metadata when you create the payment session.

Dodo Payments metadata

When creating a Dodo payment on your server, pass Bantico attribution context into metadata.

app/api/checkout/route.ts

1import DodoPayments from "dodopayments";2 3const dodo = new DodoPayments(process.env.DODO_API_KEY!);4 5export async function POST(request: Request) {6  const { productId, bantico } = await request.json();7 8  const payment = await dodo.payments.create({9    billing_currency: "USD",10    product_cart: [{ product_id: productId, quantity: 1 }],11    success_url: "https://yourapp.com/success",12    cancel_url: "https://yourapp.com/pricing",13    metadata: {14      linkId: bantico?.linkId || "",15      campaignId: bantico?.campaignId || "",16      source: bantico?.source || "",17      medium: bantico?.medium || "",18      content: bantico?.content || "",19      leadId: bantico?.leadId || "",20    },21  });22 23  return Response.json({ url: payment.payment_link });24}

These metadata fields should match the same Bantico context you use in tracked links and events: linkId, campaignId, source, medium, content, and leadId.

Email fallback with identify

If a payment is missing full link metadata, Bantico can still use identified user data as fallback context.

Call bantico.identify() when the user signs in or becomes known:

app/page.tsx

1bantico.identify({2  id: "user_123",3  email: "jane@example.com",4  name: "Jane Smith",5});

Direct Dodo payment metadata is still the preferred setup. Identify-based fallback is helpful, but it should not replace proper payment metadata.

Learn more about identifying users.

Troubleshooting

If Dodo payments are showing up but attribution looks wrong, check the following:

You pass Bantico metadata when creating the payment.
The metadata values match the same tracked link, campaign, source, medium, content, and lead context used elsewhere in Bantico.
Dodo Payments is connected in your Bantico project settings.
If you use consent-gated loading, Bantico only loads after consent.
Your checkout flow actually sends the metadata to Dodo Payments on the server.