Cart is empty
No reviews found
ChatGPT Ads conversions — the store returns its orders to the ad account
The browser pixel and the server Conversions API work on one Pixel ID and count as a single conversion. The ad click is stored next to the order, so the conversion still arrives when the payment is confirmed a day later.
Two channels, one conversion the pixel and the server share the event id
|
The order is not lost the server reports it even with an ad blocker on
|
A sending log what was sent, with which answer and for which order
|
CS-Cart 4.17.1+ and Multi-Vendor; its own Pixel ID for every storefront
|
Why a store needs it
The ChatGPT ad account sees only the clicks: how many people came through. What happened next — a purchase or a bounce — it does not know, and it has nothing to optimise the campaigns by. While the account gets no orders, the bids are set blindly and the advertising report lives separately from the sales report.
The account sees the revenue
Orders and amounts appear in the ChatGPT Ads reports, not just clicks: campaigns can be compared by money. |
The order is not lost
The main channel is the server: an ad blocker, a closed tab or a slow network do not affect the measurement. |
A payment on the next day
The click reference is kept next to the order rather than in a cookie: the conversion can be sent at the moment of the payment. |
You see what exactly was sent
The log shows the body of the event, the answer of the receiver and the order — there is something to reconcile discrepancies against. |
The conversion log: the state of every event, the answer of the receiver and whether the order came from the ads.
How it works
STEP 1
The click
The customer arrives through an ad link. The pixel picks up the click reference and stores it in a cookie of the store. |
STEP 2
The checkout
The reference moves to the order — into a table of the add-on rather than the session, which will be gone by the payment. |
STEP 3
The event
The store puts a conversion into the queue: the amount, the order contents, the click reference and the hashes of the customer data. |
STEP 4
The sending
A cron job sends the queue in batches and records the answer of the receiver. Failed events are retried. |
The checkout does not depend on the advertising
An order never waits for the ad receiver: the checkout hook only writes into the queue of the store.
What exactly is measured
- • The behaviour on the storefront: page and product views, cart additions, the start of the checkout.
- • The order — placed or paid, as you choose; the payment statuses are a setting.
- • The customer registration as a separate event when it matters as a conversion.
- • The order contents: product codes, quantities and amounts — the account sees what exactly was bought.
The event card: the body that went to the ad account, the answer of the receiver and a link to the order.
Customer data and consent
- • The e-mail, the name and the phone are sent as SHA-256 hashes. The original values are not in the request.
- • The Conversions API key is used on the server only and never reaches the browser.
- • The pixel is switched on by the consent banner of the store — the tag is handed to it the way the built-in CS-Cart counters do it.
- • With explicit consent the server stays silent too: the conversion is not sent until the customer agrees.
You see which orders the ads brought
- • A label right in the order list. The “ChatGPT” column marks the orders that arrived through an ad link — no need to open the log.
- • A “From ChatGPT ads” filter in the order search: narrow the list down to the ad orders, or to all the rest.
- • A tab on the order page: the click reference, the campaign, the utm data and the landing page — you see which ad brought the customer.
- • A counter of ad conversions in the log header.
The order list: the “ChatGPT” label on the orders that came from ads.
The order page: the click reference, the campaign and the utm data.
Settings and maintenance
- • Every setting belongs to a storefront — its own ad account, its own paid statuses, its own conversion point.
- • A test mode for the setup: the events are validated but not recorded in the account. A new storefront can be tried out while the others keep sending real data.
- • The cron line is right in the settings, with the paths of your own installation, and the time of the last run next to it.
- • The queue is under control: the batch size, the number of attempts, the retention of the log — and the option to keep no history at all.
- • A connection check in one click: the receiver answers — the keys are right.
Connection: the Pixel ID, the Conversions API key and the two measurement channels.
The scheduled task: the ready-made line and the time of the last run.
Frequently asked questions
Where do I get the Pixel ID and the key?
In the ChatGPT Ads Manager account, on the conversions tab: the Pixel ID belongs to the data source, and the Conversions API key is created next to it. The key is shown once, so save it right away.
Will the conversion be counted twice — by the pixel and by the server?
No. Both channels send the event with the same id, and the account counts them as a single conversion. This is the standard deduplication mechanism.
What happens if the ad account is unavailable?
Nothing bad: the event stays in the queue of the store and leaves with the next run of the job. The checkout does not depend on the receiver.
Will the add-on slow the storefront down?
No. Only a counter is added to the storefront, and the sending happens on the server as a separate job rather than during the checkout.
Does it work with several storefronts?
Yes. Every storefront has its own Pixel ID, its own key and its own log: the settings and the list filter follow the storefront.
And if the customer refused the cookies?
Then the conversion is not sent — neither by the browser nor by the server. The add-on reads the decision of the built-in consent banner of the store.
Try the add-on on the demo stand. The log is filled with events in every state: sent, queued, failed and skipped — you see both the body of the event and the answer of the receiver.
Payment type
One-time payment
Product
- Store Builder
- Store Builder Plus
- Store Builder Ultimate
- Multi-Vendor
- Multi-Vendor Plus
- Multi-Vendor Ultimate
Compatible versions
- 4.21.1
- 4.20.1
- 4.19.1.SP2
- 4.19.1.SP1
- 4.19.1
- 4.18.4
- 4.18.3
- 4.18.2.SP1
- 4.18.2
- 4.18.1.SP1
- 4.18.1
- 4.17.2.SP3
- 4.17.2.SP2
- 4.17.2.SP1
- 4.17.2
- 4.17.1
- 4.16.2
- 4.16.1
- 4.15.2
- 4.15.1.SP4
- 4.15.1.SP3
- 4.15.1.SP2
- 4.15.1.SP1
- 4.15.1
- 4.14.3.SP1
- 4.14.3
- 4.14.2.SP1
- 4.14.2
- 4.14.1.SP1
- 4.14.1
Localizations
- English
- Русский
|
CS-Cart development · in-house team · since 2013 We build, upgrade and speed up CS-Cart stores and marketplacesAnalysts, developers, designers, QA and support under one roof — no subcontractors. We ship add-ons you can buy on this page today, and we take on the work that no ready-made add-on covers. |
|
2013 Working with |
4.98 Rating from |
200+ Solutions on this |
500+ E-commerce projects |
Flagship products
Two add-ons that change how a store performs
Everything else we publish improves one screen. These two change the numbers: how customers find products, and how often they come back.
|
Add-on · Search & merchandising Smart SearchElasticsearch-powered search for large catalogues. The customer types two letters, sees products with images and prices, and buys from the dropdown — even after a typo or with the wrong keyboard layout. Visitors who use the search bar are 24% of traffic and 44% of revenue, and convert about 2.5× better than people who only browse categories. If search returns nothing, up to 80% of them leave. | ||||||||
| ||||||||
Try it on a live catalogue: open the demo store and search with a deliberate typo. |
|
Add-on · Mobile commerce PowerApp — mobile app for your storeA native iOS and Android app running on your CS-Cart data: the same products, prices, stock, promotions, reward points and orders. There is no second catalogue to maintain — everything stays in the admin panel you already use. A mobile site brings a customer in once; an app brings them back for free. Push notifications replace the retargeting budget you spend to buy the same customer a second time. | ||||||||
| ||||||||
Screens, block types and pricing tiers: see how the app is built. |
Services
When no add-on solves it, we do the work
Fixed scope, written specification, a named project manager and a warranty on what we ship.
|
Custom CS-Cart development Functionality the platform does not have: add-ons, marketplace mechanics, integrations with 1C, CRM, ERP, payment and delivery providers. We start from a written specification, not from an estimate on a phone call. Details → |
|
CS-Cart upgrade Move to the current version without losing data, custom code or add-ons. We audit every modification first, upgrade on a staging copy, adapt what breaks and switch over with little or no downtime. Details → |
|
Speed and performance optimisation Conversion falls by about 4.4% for every extra second of load time. We profile the server, the database and the front-end, then fix what actually costs the seconds — and show you the before-and-after numbers. Details → |
|
Design for CS-Cart Mobile-first storefront design built on CS-Cart's own template structure, so the layout survives the next platform upgrade instead of becoming a migration problem. Details → |
|
SEO for CS-Cart A technical audit of indexing, duplicates, redirects, structured data and Core Web Vitals — delivered as a prioritised fix list your developers can act on, or that we implement ourselves. Details → |
How we work
What you get besides the code
|
Before we start We discuss the goal, offer options and write the specification. You approve scope and price before development begins. |
While we build A named project manager reports progress on a fixed schedule. You always know what is in work and what is next. |
|
Before release A separate QA pass on every release — the developer who wrote the code is not the person who signs it off. |
After handover Documentation for everything we ship, plus a warranty on the modifications and the project. |
Tell us what the store needs to doDescribe the task in a couple of sentences and we will come back with options, a scope and a price. The consultation is free, and we will say plainly if a ready-made add-on already solves it.
|
Client cases, our full add-on catalogue and 184 customer reviews are in the tabs above.
Similar products
Live search and Search history
$120.00
Fast and convenient smart search. Search history. Flexible search settings.
Live Search
$75.00
The customer types and immediately sees products with a photo, a price and an «Add to cart» button. The add-on understands synonyms, word forms and typos, searches by product code and features, shows what customers did not find and lets you add a synonym right from the report. The word index keeps it fast on catalogs of hundreds of thousands of products. No subscription.
Integration with Base.com (baselinker)
$299.00
Manage catalogue, stock, prices and orders from your store and every marketplace in one place: BaseLinker pulls your products and orders and sends back stock, statuses and tracking numbers. For Store Builder and Multi-Vendor.
Make purchases for 200$ from our entire offer and get 20% discount
Make purchases for 200$ from our entire offer and get 20% discount
Wherefrom client + marketing report
$59.00
$89.00
Save 34%
This module can tell you order channel - paid channel, referall, search engine, social networks.
