Record the configuration you are testing
In your store’s Settings, record the selected consent mode and browser/server tracking toggles. Identify the storefront consent manager and every independent pixel or purchase sender. Installing a consent banner alone does not establish that those tools receive its choices.
Consent behavior depends on the platform, integration and configuration. The checks below describe technical behavior, not a certification of GDPR, CCPA or Google Consent Mode compliance. Review the setup requirements that apply to your store.
Connect the storefront choice to the SDK
The WeProfit browser SDK accepts consent commands. Connect them to the corresponding choices from your consent manager after the SDK’s initialization instructions are in place. Do not fire a grant unconditionally on page load or copy this example as a replacement for your consent manager.
// When the shopper grants the applicable consent:
wp("consent", "granted");
// When the shopper denies or withdraws it:
wp("consent", "denied");Separate browser collection from server forwarding
In strict mode, the SDK waits for granted consent before sending browser events. Queued events are discarded on denial. Server ad delivery also requires granted consent.
Balanced mode can ingest events into WeProfit with their consent state; denied events are blocked from server ad delivery. Browser pixel behavior must be checked separately. Do not assume that the setting named Off disables all tracking: the current browser and server paths treat that mode differently.
Order webhooks and platform pixels are separate paths. Do not assume that storefront SDK behavior proves that every Shopify or WooCommerce order has the correct consent state. Verify those paths too.
Test a fresh session, grant, denial and withdrawal
Use a clean browser session and permitted test data. Record the store, mode, action, observed event state and delivery result so the same checks can be repeated after a release.
- Before making a consent choice, visit a product. In strict mode, verify that the SDK withholds browser events and marketing pixel activity.
- Grant consent through your actual consent manager. Generate a page view, product view or cart action and inspect the event’s consent state in WeProfit.
- Repeat with denied consent and after withdrawal. Check both browser requests and server destination logs rather than relying on the banner state.
- Test a permitted checkout or known order separately. Verify the order ID, value, currency, captured consent state and the intended network-delivery outcome.
- Run Installation > Verify your installation for script, key and recent-event checks. This check complements consent testing; it does not replace it.
- Review the connected network’s test and diagnostics tools where available. A network accepting an event does not prove attribution or legal compliance.
Resolve mismatches before depending on the reports
If the selected mode, captured consent state and actual delivery disagree, retain the reproduction steps and contact support. Avoid broad compliance claims based only on a successful event send. For Google, separately review user-data and personalization settings for your GA4 implementation.