Connect Payment Providers
Link Stripe or MercadoPago to attribute real revenue to your ad campaigns
Connecting your payment provider is what unlocks the most valuable metric in Atribu: real revenue attribution. Once connected, every payment is matched back to the ad campaign, ad set, and specific ad that originally brought the customer to your site. This lets you calculate ROAS (Return on Ad Spend) -- the amount of revenue you earn for every dollar spent on ads.
What gets tracked
When a payment comes through Stripe or MercadoPago, Atribu creates an outcome event -- a record that something valuable happened. The attribution engine then works backward through the customer's journey to find which ad touchpoints led to that payment.
For each payment, Atribu captures:
| Data | Description |
|---|---|
| Amount | The payment amount in its original currency |
| Currency | The currency of the transaction (automatically converted for reporting) |
| Customer email | Used to match the payment to a known visitor via the identity graph |
| Billing details | Name, phone, and address when available |
| Timestamp | When the payment occurred |
Connect your provider
Open Integrations
In your Atribu dashboard, go to Settings > Integrations.
Click Connect Stripe
Find the Stripe card and click Connect. You will be redirected to the Stripe authorization page.
Authorize in Stripe
Review the permissions and click Connect or Authorize. If you manage multiple Stripe accounts, select the one you want to connect.
Done
That is it. Stripe webhooks are configured automatically -- you do not need to set up any webhook endpoints manually. Payments will start appearing in Atribu as soon as they are processed.
Automatic webhook setup
When you connect Stripe, Atribu automatically registers webhook listeners for payment events. It listens for charge.succeeded, payment_intent.succeeded, and checkout.session.completed events. You do not need to configure anything in the Stripe dashboard.
How Stripe attribution works
Stripe payments typically do not contain UTM parameters or ad campaign data. Instead, Atribu uses the identity graph to connect payments to ad clicks:
- A visitor clicks your ad and lands on your site. The tracker records their anonymous ID and the campaign details from the URL.
- The visitor fills out a form (or completes a booking). The tracker automatically calls
identify()with their email, linking their anonymous browser ID to a known customer. - Later, when they pay via Stripe, the payment arrives with the same email. Atribu matches it to the same customer profile.
- The attribution engine traces back through the customer's touchpoints to find which ad brought them in.
This is why installing the tracker and having forms on your site is so important -- it creates the bridge between anonymous ad clicks and real payments.
Open Integrations
In your Atribu dashboard, go to Settings > Integrations.
Click Connect MercadoPago
Find the MercadoPago card and click Connect. You will be redirected to MercadoPago's authorization page.
Authorize access
Log in to your MercadoPago account and approve the connection.
Done
Payments will start flowing into Atribu automatically. Like Stripe, the webhook setup is handled for you.
Revenue types
Cash vs. pipeline revenue
Atribu distinguishes between different types of revenue. Only cash revenue (actual payments from Stripe or MercadoPago) counts toward your ROAS calculation. Here is why this matters:
- Cash revenue -- Real money received through Stripe or MercadoPago. This is the only number used for ROAS.
- Pipeline value -- Deal values from your CRM (GoHighLevel). These are projections of how much a deal might be worth, not confirmed payments. A "$5,000 deal" in your pipeline does not mean $5,000 has been collected.
If pipeline values were mixed into ROAS, a single large deal estimate could make an underperforming campaign look profitable. Atribu keeps these separate so your ROAS always reflects real, collected cash.
Payment Links
Atribu can generate Stripe Payment Links with built-in attribution tracking. These links carry metadata that connects the payment directly to the customer and campaign, providing the strongest possible attribution signal.
You can create Payment Links from the Atribu dashboard under Payment Links. Each link includes tracking metadata so that when a customer completes payment, Atribu can attribute it without relying solely on the identity graph.
Troubleshooting
Payments are not appearing
- Check the connection status: Go to Settings > Integrations and verify that your Stripe or MercadoPago connection shows as "Connected".
- Wait a moment: Webhook delivery is near-instant, but there can be a short delay (under a minute) before the payment appears in your dashboard.
- Test mode vs live mode: Make sure you connected your live Stripe account, not a test mode account. Test payments will not appear.
Revenue shows zero but payments are coming in
- Check conversion definitions: Go to Settings > Conversions and make sure
payment_receivedis configured. This is set up by default, but may have been modified. - Identity matching: If the customer email on the payment does not match any known visitor, the payment will be recorded but may not be attributed to a campaign. Make sure the tracker is installed and forms are being captured.