The order exists in Shopify, but the advertising report is missing it, appears to count it twice or shows the wrong amount. Those three symptoms need different checks. Algoshop AI Sales Chatbot supports the customer conversation; Infinite Commerce's pixel workflow addresses how the completed purchase reaches intended advertising destinations.
Infinite Commerce's pixel app supports multiple advertising pixels and server-side tracking for Facebook and TikTok. Its practical value should be assessed by following a real test journey from browsing to purchase—not by assuming that a successful installation means every event is accurate.
Define what a purchase event should represent
An advertising purchase event is a report about a transaction. It is not the transaction itself, proof that an advertisement caused it, or a replacement for the store's order record.
For a test order, define the expected event, monetary value, currency and order reference before starting. Decide how discounts, shipping and taxes should be represented according to the supported platform setup. Otherwise two systems may appear inconsistent simply because they use different value definitions.
A page view, add-to-cart action and purchase are different stages. One customer can view several products and add an item multiple times while placing only one order. Those counts should not be compared as though each describes completed sales.
Understand the app and platform boundaries
The Infinite Commerce listing describes multiple Facebook/Meta and TikTok pixels, additional platforms including Snapchat, Pinterest and Twitter, Shopify web pixel integration, server-side tracking and Conversion API support.
It also discusses reports and UTM parameters. These are useful measurement components, but the listing's marketing language should not be interpreted as a promise of complete attribution or bypassing privacy choices.
Send purchase activity to Facebook through a server connection to support advertising measurement.
Follow the event path: Shopify shopping action → configured browser and/or server sender → intended Meta or TikTok pixel → platform processing and attribution. Infinite Commerce's multi-pixel and server-side capabilities help organize delivery across destinations. A store may also have another integration sending the same event, so the sender map is the starting point for interpreting what arrives.
Write down each active connection: this app, official channel integrations, theme scripts and tag-management setups. Do not disable or add live tracking blindly. Understand which system is responsible for each intended destination.
The reason to consider a multi-pixel tool is not simply to install more pixels. A store may have several intended destinations for different platforms or advertising arrangements and need a clearer way to manage them. Infinite Commerce's listing includes multiple Meta and TikTok pixels as well as other supported networks. Start with the business purpose of each destination, then review the resulting event route.
For a store advertising on both Meta and TikTok, the important question is whether each intended platform receives the relevant shopping activity. For a store with several pixel configurations, the question is which connection serves which use. A larger number of connections is not inherently better; it adds destinations that must be named, maintained and tested.
Swipe horizontally to read the full table.
| Measurement component | What it contributes | What it does not establish alone |
|---|---|---|
| Browser event delivery | A configured route from shopping activity to the platform | That every visitor or event is observable |
| Server-side delivery | An additional supported route for event data | Permission to ignore consent or a guarantee of full attribution |
| Multiple pixels | Management of several intended destinations | That all destinations should count as one combined sales total |
| UTM information and reports | Context for reviewing campaign-related activity | Proof that advertising caused the transaction |
The practical payoff is a setup the marketing team can explain. When a purchase seems absent, the team can investigate its expected route. When reports disagree, it can distinguish receipt of the event from attribution of the order. Those are more useful outcomes than accepting a broad promise of “perfect tracking.”
The app's official Facebook setup resource explains the link between a Meta dataset and the app's FB Dataset ID field. The dataset identifies the destination; it is different from the access token used for the supported server connection. Choose the intended business dataset before connecting it, and keep tokens private rather than placing them in shared test notes or screenshots.
Feature availability also matters. The current listing separates the free Facebook browser-pixel option from paid server-side support and plans offering multiple Meta/TikTok pixels or collection/tag targeting. Compare your actual destinations and routing needs with the current plan rather than assuming the free option includes every advertised capability. Collection or tag routing should serve a defined campaign purpose, not create unexplained extra senders.
Map one test shopping session
Use an approved test purchase and a non-sensitive internal reference. The checklist below identifies what to observe; it contains no claimed test results.
Swipe horizontally to read the full table.
| Stage | Intended observation | Evidence to record |
|---|---|---|
| Product viewed | Relevant product-view event | Destination, timestamp and product reference |
| Item added | Add-to-cart event | Selected item and quantity |
| Checkout begun | Supported checkout event | Time and value definition |
| Order completed | One purchase represented at each intended destination | Actual order reference, configured value, currency and available event details |
If your configured purchase value includes shipping or tax, document that definition and compare against the matching order components.
“One purchase” means one business transaction represented correctly at a destination. Browser and server deliveries may both describe it; simply counting two raw deliveries does not establish two counted purchases.
Use the platforms' current testing and diagnostic facilities. TikTok's official pixel guidance identifies Test Events in Events Manager as a testing route; its standard-event reference explains supported event terminology. Follow the current platform interface instead of an invented app menu.
Infinite Commerce's Meta installation guide distinguishes page-level checking with Meta Pixel Helper from checking received activity in Events Manager, including Test Events. That distinction is useful when browser activity looks correct but the server connection still needs verification. The guide also covers other installation methods; do not add all of them on top of an existing setup. Inventory your current senders first, then follow the documented route for the connection you intend to use.
Investigate missing or repeated events
Start with the event symptom
Purchase missing
First evidence to compare: Shopify order, destination, consent state and sender record
Investigation direction: Did the eligible event leave the intended connection and arrive?
Purchase appears repeated
First evidence to compare: Order reference, sender identities and platform diagnostics
Investigation direction: Do browser/server deliveries or competing integrations describe one transaction?
Amount or currency wrong
First evidence to compare: Order components against event value/currency parameters
Investigation direction: Is there a calculation-basis difference or an incorrect parameter?
For repeated events, inspect whether a theme script and another integration both send purchases, or whether refreshing the confirmation page generates another delivery. Diagnose the same order before changing a live connection.
Do not assume this app automatically resolves every duplication. Browser/server deduplication depends on the actual supported implementation and matching identifiers. Inspect the platform's diagnostics and the event details before concluding that a purchase is double-counted.
Manage several advertising tracking connections from one setup.
If the same order is intentionally sent to Meta and TikTok, that is not automatically a duplicate within either platform. Likewise, two pixels may serve different campaign or catalog purposes. Maintain an explicit destination map so the team can tell intended routing from accidental repetition.
After changing one configuration, repeat the same test conditions. Changing several tracking systems at once makes it hard to identify which adjustment resolved or introduced a problem.
Keep consent and attribution limits visible
Server-side tracking changes how event data reaches a platform. It does not grant permission to collect or send everything, and it does not guarantee complete measurement.
The app's listing describes GDPR-related tracking support. That description is not a legal-compliance certificate for the merchant's entire setup. Configure privacy choices and data handling appropriately, and test the intended behavior for different consent states.
Attribution is another boundary. An advertising platform can assign credit under its own window and model. Shopify may report the same order differently. A discrepancy is not automatically a tracking failure.
Separate three questions: did the order occur, did the platform receive an event, and how did the platform attribute it? Only the first is answered directly by the store's order record.
Record evidence before changing campaign decisions
For the approved purchase, keep a compact record of order time, value definition, currency, expected destinations, observed event details and unresolved differences. Mark a test as passed only after observing the actual result.
If it fails, record what is missing rather than writing “pixel broken.” A wrong currency, missing purchase and double-counted event are different issues with different remedies.
For advertising profitability after measurement, the Margeny order-profit guide covers costs and budget decisions. Correct event tracking does not itself establish profitability.
Explore Infinite Commerce's Shopify listing with a list of active senders and a defined test transaction. The desired outcome is a traceable measurement setup, not an unsupported claim of perfect attribution.
