Adobe Commerce orders,tied to the ad behind them

ClickFlare ties every Adobe Commerce order back to the ad click that brought the buyer, with the real order total. You see revenue and ROAS per campaign, ad and store view, and a reloaded success page never counts an order twice.

AC
Adobe Commerce
E-commerce platform, formerly Magento

Adobe Commerce integration at a glance

How it connects
Script on each store view plus one on the success page
What syncs
Store visits, orders and order totals
How fresh the data is
Real time, when the success page loads
What you can optimize
Ads, campaigns and store views by real order revenue
Works with
Any traffic source, with or without redirects
Good to know
A developer adds the success page script. Refunds aren't reported.
E-commerce platform
Real order totals
Orders per store view

Adobe Commerce revenue, per ad

Real order values

Each order reports its real total, so revenue per campaign in ClickFlare matches your store.

Reloads don't double count

A reloaded success page counts once. A second order from the same click counts on its own.

Works without redirects

Use a direct campaign for Google Ads and other sources that block redirects. The ad links straight to the store.
How it works

From ad click to profit per campaignattributed revenueattributed salesa matched conversionautomated actionyour dashboardsclosed revenue

01
Your ad
Visitor clicks
Ad on Adobe Commerce
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your offer
Conversion
Lead, sale or custom event
04
ClickFlare
Sent back to Adobe Commerce
Through the Conversion API or postback
05
Cost API
Spend pulled in
Adobe Commerce cost matched to each campaign
01
Your ad
Adobe Commerce click
Placement, device and country come along
02
ClickFlare
Click recorded
Zone, site and device data stored
03
Offer or lander
Visitor converts
On your page or the offer
04
ClickFlare
Conversion logged
With payout and event type
05
Postback
Reported to Adobe Commerce
So its optimization sees the result
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Your article
Keyword block
Click ID passed to the feed
04
Results page
Paid click
Conversion fired to ClickFlare
05
Adobe Commerce API
Revenue matched
Pulled on a schedule and reconciled
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
The click follows the visitor to the offer
03
Adobe Commerce
Offer or call
The network tracks the action
04
Adobe Commerce
Conversion
Lead, sale, call or rebill
05
Postback
Payout in ClickFlare
Matched to the original click
01
Your ad
Visitor clicks
Any traffic source
02
ClickFlare
Click recorded
Every click gets its own ID
03
Adobe Commerce
Store or funnel
Click ID kept through checkout
04
Events
View, cart, checkout
Each step tracked
05
ClickFlare
Purchase recorded
Order value matched to the ad
01
Your ad
Visitor clicks
Form, call or landing page
02
ClickFlare
Click recorded
Every click gets its own ID
03
Adobe Commerce
Lead or call stored
The ad stays linked to the lead
04
Adobe Commerce
Qualified or closed
Workflow or call rule fires
05
ClickFlare
Revenue recorded
Tied to the ad that drove it
01
ClickFlare
Event happens
Click, conversion or custom event
02
Webhook or API
Data goes out
Or comes back in
03
Adobe Commerce
Your workflow
Rules, apps or an AI assistant
04
Adobe Commerce
Action
Alert, update, pause or scale
05
ClickFlare
Back in reports
Changes show in your data
01
ClickFlare
Report data
Campaigns, sources, offers
02
ClickFlare API
Your numbers go out
Secured with your API key
03
Your setup
Scheduled refresh
A sheet, script or connector
04
Adobe Commerce
Data lands
Tables refreshed on schedule
05
Adobe Commerce
Dashboards
Blended with your other data
E-commerce platform

From store visit to successful order

ClickFlare records each visit to your store view and remembers the click. When the checkout success page loads, it reports the order total and number, and the order lands on the ad that brought the buyer.
  • Visit recorded in each store view
  • Order total sent from the success page
  • Each order counted once
Today, one campaign
example
Spend pulled from Adobe Commerce
cost
$412.30
Conversions recorded
today
38
Sent back to Adobe Commerce
per event
38/38
Profit
campaign
$227.70
Example numbers. Cost and conversions sit in the same report row.
ROI per placement
example
Placement A · mobile
cost
$38.20
Placement A
revenue
$71.40
Placement A
ROI
+87%
Placement B · desktop
ROI
−42%
Example numbers. Keep the placements that pay and cut the ones that lose money.
Revenue for one click
example
Paid click
day 0
$0.00
First revenue pull
+1h
$0.41
Scheduled updates
next days
$0.58
Final pull
last sync
$0.62
Example amounts. Sync timing for Adobe Commerce is in the facts above.
Events for one click
example
Lead
day 0
$0.00
Sale
day 0
+$40.00
Upsell
day 1
+$15.00
Refund
day 9
−$15.00
Example events. Each one arrives by postback and is matched to the click.
One visitor's path
example
Product view
step 1
—
Add to cart
step 2
—
Checkout
step 3
—
Purchase
step 4
$68.00
Example order. Each event is tied to the ad that brought the visitor.
One lead, followed to revenue
example
Lead created
day 0
$0.00
Qualified
day 2
+$25.00
Deal closed
day 14
+$480.00
Renewal
day 45
+$120.00
Example values. Each stage can be its own event type in ClickFlare.
A scheduled report refresh
example
Campaigns
in the report
1,240 rows
Cost, revenue, profit
per campaign
included
Refresh
your schedule
done
Dashboards fed
Adobe Commerce
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
Adobe Commerce
received
Workflow ran
Adobe Commerce
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain, Adobe Commerce Admin access, and a developer for the success page.
  1. Add your store to a campaign Add your store or product page as the offer, one campaign per traffic source. Use direct tracking for Google Ads.
  2. Add the ClickFlare script to your store Add the ClickFlare script to each store view that gets traffic, and allow your tracking domain so checkout pages don't block it.
  3. Report orders from the success page Your developer adds the conversion script to the success page with the order total. Each order then lands on its ad.
app.clickflare.com/integrations
AC
Adobe Commerce
E-commerce platform
Connected
Adobe Commerce account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Adobe Commerce template selected
Macros pre-filled
Tracking URL in Adobe Commerce
Click ID captured
Conversions reported
Payout included where supported
Adobe Commerce connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Adobe Commerce added
Offer URL carries the click ID
Postback set in Adobe Commerce
Payout and event included
Conversions arriving
Matched to the click
Adobe Commerce connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in Adobe Commerce
Hidden field or call data
Workflow or rule set
Fires on the stage you choose
Conversions arriving
With payout and event type
API key created
Settings, then Security
Report pull scheduled
Dimensions and date range set
Adobe Commerce dashboards live
Refreshed on schedule
Connection set up
Webhook, API key or MCP
Events chosen
Only what the workflow needs
Workflow running
Tested end to end
Ready to track
The conversion script belongs on the success page only. Placed site-wide, it would report a conversion on every page view.
Adobe Commerce setup guide
Open the guide
In your reports

What you see once it's connected

  • Sales per campaign
  • Revenue per ad
  • ROAS by traffic source
  • Orders per store view
  • Orders by country and device
  • Revenue per landing page
Use cases

How media buyers run it

Google Ads → Adobe Commerce product page

Google Ads → store

A direct campaign records the visit without a redirect.
Native → presell page → store

Native → presell → store

Compare presell angles on orders and revenue.

Several store views

Add the script to each store view that gets traffic and compare orders by store from the same campaigns.
Frequently asked questions

Adobe Commerce integration FAQ

Does ClickFlare integrate with Adobe Commerce?

Yes. The ClickFlare script runs on each store view, and a conversion script on the checkout success page reports each order with its total.

Do I need a developer?

For the success page, yes. Adobe Commerce has no Admin setting that adds order data to a script, so the order total needs a small template change.

Why doesn't tracking work on checkout?

Adobe Commerce blocks scripts on checkout pages unless their domain is allowed in its security settings. Add your ClickFlare tracking domain.

Does it work with Google Ads?

Yes. Use a direct campaign. The ad links straight to the store and the ClickFlare script records the visit without a redirect.

Can I report orders server-side?

Yes, with a developer. Adobe Commerce can send orders straight to ClickFlare once the click ID is saved on the order, and a failed call must never block an order.

Are refunds reported?

No. The success page only reports new orders. Adjust refunds in ClickFlare, or include them in a server-side setup.

No items found.
Setup guides
Adobe Commerce setup guide
Tracking conversions with an S2S postback
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Adobe Commerce?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. The ClickFlare script runs on each store view, and a conversion script on the checkout success page reports each order with its total."}}, {"@type": "Question", "name": "Do I need a developer?", "acceptedAnswer": {"@type": "Answer", "text": "For the success page, yes. Adobe Commerce has no Admin setting that adds order data to a script, so the order total needs a small template change."}}, {"@type": "Question", "name": "Why doesn't tracking work on checkout?", "acceptedAnswer": {"@type": "Answer", "text": "Adobe Commerce blocks scripts on checkout pages unless their domain is allowed in its security settings. Add your ClickFlare tracking domain."}}, {"@type": "Question", "name": "Does it work with Google Ads?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. Use a direct campaign. The ad links straight to the store and the ClickFlare script records the visit without a redirect."}}, {"@type": "Question", "name": "Can I report orders server-side?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, with a developer. Adobe Commerce can send orders straight to ClickFlare once the click ID is saved on the order, and a failed call must never block an order."}}, {"@type": "Question", "name": "Are refunds reported?", "acceptedAnswer": {"@type": "Answer", "text": "No. The success page only reports new orders. Adjust refunds in ClickFlare, or include them in a server-side setup."}}], "dateModified": "2026-11-12"}, {"@type": "BreadcrumbList", "itemListElement": [{"@type": "ListItem", "position": 1, "name": "Integrations", "item": "https://www.clickflare.com/integrations"}, {"@type": "ListItem", "position": 2, "name": "E-commerce", "item": "https://www.clickflare.com/integrations/e-commerce"}, {"@type": "ListItem", "position": 3, "name": "Adobe Commerce"}]}]}