If conversions aren’t showing up where you expect them, work through these in order. They’re arranged by how often each one turns out to be the cause.

1. Consent is holding the event

This is the most common cause, and it’s by design. Carticy is default-deny: until the visitor’s stored consent allows analytics or advertising, no tag fires and the order shows Waiting for consent in Recent events. Check your consent posture under Settings → Consent. If you run a Consent Mode v2 CMP or a WP Consent API plugin, confirm it’s actually granting consent for the relevant categories. See Consent, GDPR, and privacy.

2. The destination ID is wrong or in the wrong field

A transposed character is invisible until you check. Re-open Settings → Platforms and verify each ID against its source:

• The GA4 Measurement ID starts with G-, not the GT- tag ID or a property number.
• Google Ads needs both the Conversion ID (AW-...) and the conversion label. A missing label sends nothing.
• The Meta Pixel / Dataset ID is the numeric ID, not the account ID.

See Connect GA4, Google Ads, and the Meta Pixel for where each ID lives.

3. A duplicate tag is already on the page

If another plugin, your theme, or a GTM container already loads the same GA4 or Pixel ID, Carticy detects it and warns you in the Home notices instead of silently double-firing. Either remove the other tag, or use the duplicate-tag resolution to decide which integration owns the destination.

4. Caching is serving a stale page

After changing settings, clear your page cache and CDN. Purchase events fire from server-side order hooks and aren’t page-cached, but the tag configuration on your storefront can be. If you use a full-page cache, exclude the cart and checkout pages.

5. Allow time, and look in the right report

GA4 standard reports can lag 24–48 hours, so use Realtime and DebugView for immediate confirmation. Google Ads conversions can take hours to attribute. For Meta, use the Test events tab in Events Manager with a real order and you’ll see events arrive within seconds.

Read the debug log

For anything that survives the steps above, turn on logging under Settings → Advanced (the carticy_conversions_debug_log option). Carticy then writes a detailed trail to WooCommerce → Status → Logs under the source carticy-conversions, including why a given order was or wasn’t dispatched. Include that log when you contact support.