Next Commerce orders,tied to the ad behind them

ClickFlare ties every Next Commerce order back to the ad click that brought the buyer, with the order total including tax. Orders are reported server to server through Zapier or Make, so ad blockers don't hide sales and ROI stays accurate.

NC
Next Commerce
DTC e-commerce platform

Next Commerce integration at a glance

How it connects
Next Commerce webhook through Zapier or Make, or event tracker
What syncs
Orders and order totals including tax
How fresh the data is
Real time, per order
What you can optimize
Ads, placements and landers by real order revenue
Works with
Storefront checkouts, product pages and custom funnels
Good to know
The click ID is kept for one day until the cart is created.
E-commerce platform
Server-side orders
Revenue per ad

Next Commerce orders, matched to every ad

Click ID saved on the order

Next Commerce keeps the ClickFlare click ID on the cart and the order, so every order can be tied to its ad.

Retries without double counts

Next Commerce retries a failed delivery up to 10 times, and a retried order replaces itself in ClickFlare instead of adding a copy.

Orders survive ad blockers

Orders are reported from Next Commerce's servers, so ad blockers and buyers who leave before the confirmation page don't lose the order.
How it works

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

01
Your ad
Visitor clicks
Ad on Next 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 Next Commerce
Through the Conversion API or postback
05
Cost API
Spend pulled in
Next Commerce cost matched to each campaign
01
Your ad
Next 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 Next 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
Next 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
Next Commerce
Offer or call
The network tracks the action
04
Next 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
Next 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
Next Commerce
Lead or call stored
The ad stays linked to the lead
04
Next 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
Next Commerce
Your workflow
Rules, apps or an AI assistant
04
Next 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
Next Commerce
Data lands
Tables refreshed on schedule
05
Next Commerce
Dashboards
Blended with your other data
E-commerce platform

From click to order, saved by Next Commerce

Your ClickFlare link passes the click ID to Next Commerce, which saves it on the cart and order. When an order is created, Zapier or Make reports it to ClickFlare with the total and order number.
  • Click ID saved on each Next Commerce order
  • Order total including tax as revenue
  • Order number prevents duplicates
Today, one campaign
example
Spend pulled from Next Commerce
cost
$412.30
Conversions recorded
today
38
Sent back to Next 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 Next 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
Next Commerce
3
Example numbers. You choose the breakdowns, date range and schedule.
One event, end to end
example
Conversion recorded
event
sent
Event delivered
Next Commerce
received
Workflow ran
Next Commerce
done
Team notified
your apps
done
Example run. What happens after the event is up to your workflow.
10
Webhook delivery retries
1 day
Click ID kept before cart
2.3B
Events tracked
Setup

Connected in three steps

You need a ClickFlare account with your own tracking domain, access to Settings in Next Commerce, and a Zapier or Make account.
  1. Add your store to a campaign Add your store, product page or checkout as the offer in a redirect campaign, with the click ID passed along.
  2. Send new orders to Zapier or Make Create a Next Commerce webhook for new orders and point it at a Zapier or Make workflow.
  3. Report each order to ClickFlare Have Zapier or Make send each order with its total to ClickFlare. Orders then land on the ad that drove them.
app.clickflare.com/integrations
NC
Next Commerce
E-commerce platform
Connected
Next Commerce account connected
Signed in from ClickFlare
Cost syncing
Spend matched to campaigns
Conversions sent back
Your chosen events
Next Commerce template selected
Macros pre-filled
Tracking URL in Next Commerce
Click ID captured
Conversions reported
Payout included where supported
Next Commerce connected
Credentials saved in ClickFlare
Conversion event set
Click ID passed to the feed
Revenue syncing
On the feed's schedule
Next Commerce added
Offer URL carries the click ID
Postback set in Next Commerce
Payout and event included
Conversions arriving
Matched to the click
Next Commerce connected
Click ID kept to checkout
Events mapped
View, cart, checkout, purchase
Purchases tracked
Order value in reports
Click ID stored in Next 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
Next 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
No Zapier or Make? Next Commerce can report the completed checkout from the browser instead. Run one route only, or orders count twice.
Next Commerce setup guide
Open the guide
In your reports

What you see once it's connected

  • Orders and revenue per campaign
  • Revenue per ad
  • ROAS by traffic source
  • Orders by country and device
  • Revenue per lander
Use cases

How media buyers run it

Meta → presell page → Next Commerce checkout

Meta → presell → store

The lander passes the click ID on, so orders tie back to each ad.
Native → Next Commerce product page

Native → product page

Judge each placement on orders and revenue.

Custom funnels on the Admin API

Funnels built on the Next Commerce Admin API report orders the same way, as long as they pass the same attribution.
Frequently asked questions

Next Commerce integration FAQ

Does ClickFlare integrate with Next Commerce?

Yes. ClickFlare passes its click ID to Next Commerce, which saves it on the order. A webhook through Zapier or Make, or a checkout tracker, reports the order to ClickFlare.

Why do I need Zapier or Make?

Next Commerce sends webhooks in its own fixed format. Zapier or Make translates each order into a ClickFlare conversion with the click ID, total and order number.

What if a webhook delivery fails?

Next Commerce retries a failed delivery up to 10 times. The order number keeps a retried order from counting twice.

How does Next Commerce handle repeat visits?

Last click by default: a new link overwrites the earlier click. You can set the offer to keep the first click instead.

Can I use it with Google Ads?

Yes, through a lander. Send the ad to a lander with the ClickFlare script, and ClickFlare passes the click ID on the way to the store.

Are refunds reported?

Not by this setup. It reports new orders only. Adjust refunds in ClickFlare if you need net revenue.

No items found.
Setup guides
Next Commerce setup guide
Tracking conversions with an S2S postback
{"@context": "https://schema.org", "@graph": [{"@type": "FAQPage", "mainEntity": [{"@type": "Question", "name": "Does ClickFlare integrate with Next Commerce?", "acceptedAnswer": {"@type": "Answer", "text": "Yes. ClickFlare passes its click ID to Next Commerce, which saves it on the order. A webhook through Zapier or Make, or a checkout tracker, reports the order to ClickFlare."}}, {"@type": "Question", "name": "Why do I need Zapier or Make?", "acceptedAnswer": {"@type": "Answer", "text": "Next Commerce sends webhooks in its own fixed format. Zapier or Make translates each order into a ClickFlare conversion with the click ID, total and order number."}}, {"@type": "Question", "name": "What if a webhook delivery fails?", "acceptedAnswer": {"@type": "Answer", "text": "Next Commerce retries a failed delivery up to 10 times. The order number keeps a retried order from counting twice."}}, {"@type": "Question", "name": "How does Next Commerce handle repeat visits?", "acceptedAnswer": {"@type": "Answer", "text": "Last click by default: a new link overwrites the earlier click. You can set the offer to keep the first click instead."}}, {"@type": "Question", "name": "Can I use it with Google Ads?", "acceptedAnswer": {"@type": "Answer", "text": "Yes, through a lander. Send the ad to a lander with the ClickFlare script, and ClickFlare passes the click ID on the way to the store."}}, {"@type": "Question", "name": "Are refunds reported?", "acceptedAnswer": {"@type": "Answer", "text": "Not by this setup. It reports new orders only. Adjust refunds in ClickFlare if you need net revenue."}}], "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": "Next Commerce"}]}]}