Degree Dynamic Meta Pixel WP Registry grade A. No security issues foundWP RegistryNo security issues foundOpen the reportA
Strict UTM Meta Pixel/CAPI routing for WooCommerce with paid/unpaid Telegram alerts
Install
Upload it under Plugins → Add New Plugin → Upload Plugin, then activate.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/propafinder/degree-dynamic-meta-pixel/releases/download/v1.2.3/degree-dynamic-meta-pixel-1.2.3.zipWordPress/WooCommerce plugin for strict UTM-only attribution and dynamic Meta Pixel + Conversions API routing.
Updates
The plugin uses the native WordPress update screen and checks the latest public GitHub Release from propafinder/degree-dynamic-meta-pixel. Only the release ZIP asset named degree-dynamic-meta-pixel-VERSION.zip or degree-dynamic-meta-pixel.zip is accepted. Successful release checks are cached for 15 minutes, and the plugin row includes a manual update check that clears stale release data. Automatic updates remain off unless enabled by a WordPress administrator.
Telegram alerts
Telegram is optional and sends only two order outcomes for orders carrying this plugin's UTM attribution:
ОПЛАЧЕНО: order number, UTM source, amount, currency and confirmed payment time.НЕ ОПЛАЧЕНО: order number, UTM source, amount, currency and order creation time.
Each order message and manual test starts with the configured store label, so multiple shops can use the same bot and Chat ID in one Telegram group without mixing their identities.
Failed and cancelled orders are reported as unpaid immediately. Pending and on-hold orders are reported only after the configured delay, so a normal payment redirect does not produce a false unpaid alert. Paid events are queued immediately. Sending runs through WooCommerce Action Scheduler, with WordPress Cron as a fallback, and retries up to four times without blocking checkout or payment callbacks.
The bot token is masked in the settings screen and never included in reports. Telegram messages contain no customer names, email addresses, phone numbers or delivery addresses.
What it tracks
- Recognized UTM visit: only when
utm_sourceexactly matches an enabled rule. - Checkout started: once per attributed UTM session.
- Checkout without an order: checkout started, but no WooCommerce order exists after the configured delay.
- Unpaid order: WooCommerce order exists but payment is not confirmed.
- Cancelled/failed/refunded order: shown locally and never sent as a Purchase.
- Paid order: WooCommerce confirms payment; Purchase is sent to the Pixel configured for that UTM source.
The plugin does not send PageView, ViewContent or AddToCart. It does not infer a source from referrer, fbclid, _fbc, IP address or a direct visit.
Attribution rules
- Default attribution window: 7 days, configurable from 1 to 30 days.
- A direct visit never creates or overwrites attribution.
- A new recognized
utm_sourcecreates a new last-touch attribution session. - Repeated loading of the same tagged URL within 10 minutes reuses the same session to avoid duplicate visits.
- An unknown UTM source sends no Meta event and clears an older recognized attribution, preventing a later source from being credited to the previous campaign.
Meta events
InitiateCheckout: browser Pixel and server CAPI use the same event ID.Purchase: browser Pixel on the paid thank-you page and server CAPI usedmuf_purchase_ORDER_IDfor deduplication.- Asynchronous payments are covered by server-side WooCommerce payment/status hooks even when the customer does not return to the thank-you page.
- CAPI retries failed Purchase requests up to five times. Tokens are never included in logs or reports.
Data and removal
- UTM sessions are stored in the
{prefix}dmuf_sessionstable without names, emails, phone numbers or raw IP addresses. - Order attribution is stored as
_dmuf_*WooCommerce order metadata. - Deactivation and deletion do not remove the table or order metadata.
- The plugin does not alter existing Meta Dynamic Pixel data and does not automatically import its noisy event log.
Safe rollout
- Install and activate the plugin. Tracking starts disabled.
- Add exact rules such as
CapPrice -> Pixel ID + CAPI token. - Use Meta Test Events with a temporary test code.
- Enable tracking and test one tagged checkout and one test payment.
- Verify that Pixel and CAPI show the same event ID.
- Only then decide which older pixel implementation should remain active. This plugin never disables another plugin automatically.
Releases
4 releases. Each count is every asset in that release; expand a row for the breakdown.