Reliable conversion tracking starts with permission to collect and share the data, then an accurate record of what happened. For a peptide store, do not assume every product page or purchase event is suitable for every advertising platform's business tools.
This audit checks the measurement chain without treating server-side tracking as a way around restrictions. Use it before judging ROAS or increasing spend. Apply the technical checks only to data and events the relevant platform permits.
1. Review data-sharing eligibility and consent
Inventory the pages, parameters and events sent by each tool. Product names, URLs, query strings, form fields and free-text inputs can reveal more than the event label suggests. Review the platform's current terms and any restrictions shown for your data source.
TikTok recommends inspecting transmitted data with Pixel Helper and avoiding sensitive data that its policies prohibit. See TikTok Pixel guidance. Hashing or moving a request to a server does not establish permission to share its contents.
Document which events may be sent, which must be excluded and how consent affects the implementation. If suitability is unresolved, pause the affected sharing while it is reviewed.
2. Inventory every installation
List native Shopify channel integrations, apps, custom pixels, theme scripts, Google Tag Manager tags and server-side connections. Identify who owns each event and which installation sends it.
Do not assume that adding another integration improves coverage. Two tools reporting the same order can create duplicate events unless they are deliberately coordinated. Retain the necessary integration and remove redundant paths only after a controlled review.
3. Confirm what counts as a purchase
A purchase should represent the completed transaction defined by your business, not an add-to-cart click or the opening of a payment page. Check the relationship between the order state and the event trigger.
Where permitted, place a controlled test order, record the order ID and amount, and inspect the event. Verify value, currency and the point at which it fires. Test a reload of the confirmation screen and another order to catch both duplicates and reused identifiers.
4. Check GA4 transaction identifiers
Google's web-stream guidance uses a unique transaction ID to deduplicate purchases. An empty ID or an ID reused for different orders can cause undercounting. IDs should not contain information identifying the customer.
Use a stable identifier for the same order and a different identifier for each distinct order. Review Google's transaction ID documentation alongside the store's implementation.
5. Check browser and server deduplication
If permitted copies of the same purchase are sent through a browser pixel and a server API, coordinate them according to that platform's documentation. Do not generate unrelated identifiers for two copies of one transaction.
TikTok's deduplication guidance requires an event_id across Pixel and Events API for overlapping events. Check the identifier and event details in the relevant diagnostics. See TikTok's event deduplication documentation.
A server event is not automatically an additional sale. Its purpose and relationship to the browser event need to be clear.
6. Reconcile the reports with store orders
Compare the same period and currency, then note the definitions behind each report. Attribution windows, consent, reporting delay, refunds and different event scopes can create legitimate differences.
Do not add Meta-attributed and TikTok-attributed purchases together and call the total unique store orders. Different systems may claim credit for the same order. Use the store record as the operational reference while interpreting channel attribution separately.
7. Write an audit record you can repeat
Record the integration, event, expected trigger, permitted parameters, identifier strategy and test outcome. Keep a list of unresolved questions and assign an owner to each fix. Repeat the checks after changes to checkout, channel apps, the theme or tracking configuration.
Frequently asked questions
Does server-side tracking recover every missing purchase?
No. It may improve an eligible implementation, but it cannot guarantee complete reporting or replace consent and data-sharing requirements.
Why does my store show sales that Ads Manager does not?
Store orders and attributed advertising results answer different questions. Check attribution and reporting context before concluding the pixel is broken.
Can I install every platform pixel on every page?
Only after checking permissions, consent and the data transmitted. Technical ability is not permission. See our tracking and attribution service or discuss a measurement review.