The String CRM

Changelog

1.20.23

• Display independent WooCommerce commerce labels for active, cleared, abandoned, and ordered journeys.
• Stop cart lifecycle changes from overwriting the linked Submission CRM pipeline status; WooCommerce order-status mapping remains unchanged.

1.20.22

• Let the first due WooCommerce event batch run immediately instead of holding it behind an empty-queue synchronization lock.
• Preserve asynchronous batch delivery; storefront requests still do not wait for String when no event is ready.

1.20.21

• Record each synchronized WooCommerce cart action as its own String Submission note so it appears as a separate Activity Log entry.
• Mark individual cart actions synchronized only after String accepts their corresponding note, so acknowledged activities are not resent on normal retries.

1.20.20

• Populate the String Source selector when changing an existing mapping to WooCommerce Orders / Submissions, including immediately after a successful source refresh.

1.20.19

• Store and advance WooCommerce cart journeys locally when commerce event tracking is enabled, without requiring a String cart-to-Submission mapping.
• Keep remote String Submission creation and status synchronization optional and mapping-dependent.

1.20.18

• Commerce event tracking is now explicitly opt-in and consent-aware.
• API credentials can be managed outside WordPress with STRINGFORM_API_URL, STRINGFORM_CLIENT_ID, and STRINGFORM_CLIENT_SECRET.
• Page/referrer query strings are removed, public AJAX actions are rate-limited, raw event PII is administrator-only, and failed delivery retries are bounded.

1.20.17

• Queue authoritative WooCommerce cart abandonment, payment failure, purchase, order status, cancellation, and refund events.
• Keep retries idempotent with deterministic SHA-256 message IDs and link server events to the existing String client and Submission.
• Carry the checkout browser ID onto authoritative order events so first-touch and last-touch attribution stay connected without adding browser ad pixels.

1.20.16

• Add cart viewed, cart updated, checkout started, and payment info entered storefront events.
• Send cart contents, value, currency, stable cart journey ID, and the existing String Submission ID when available.
• Deduplicate repeated server hooks inside the same request while preserving each queued event’s stable retry message ID.

1.20.15

• Send WooCommerce commerce batches with the canonical woocommerce provider and customer key.
• Capture page URL, path, referrer, canonical UTM campaign fields, user agent, and available Meta/TikTok/Snap/Google/Microsoft click identifiers on storefront events.
• Reuse existing merchant ad cookies when present without injecting a second browser pixel.

1.20.14

• Restored the visible Events tab in The String CRM admin navigation.
• Added a dedicated Events page that reuses the existing WooCommerce storefront event log and filters.
• Restored Product Events access without bringing back the old top-level Entries model.

1.20.13

• Added an explicit Refresh String sources action to WooCommerce Orders / Submissions mapping.
• Empty/stale Source catalog cache is retried directly against String before showing an empty selector.
• Source API errors now show the actual response and explicitly identify the required sources.read scope for 403 responses.
• Preserves a previously saved source ID if the remote catalog is temporarily unavailable.

1.20.11

• Fix logged-in shoppers not creating an Active cart Submission until checkout on themes/custom AJAX flows.
• Reconcile the current cart immediately after classic WooCommerce and Woo Blocks add/remove events, while retaining the normal PHP hooks as the primary path.
• Add a late frontend fallback for non-empty logged-in carts; unchanged snapshots reuse the same cart journey and never create a duplicate Submission.

1.20.10

• Added a manual Fresh Sync action on Customers to reconcile local WooCommerce/customer records with String CRM.
• Resolves missing String Client IDs from existing String Submission IDs first, then falls back to phone-first client lookup and email lookup.
• Persists recovered client links back to carts, orders, browser identities and product events without creating duplicate customers or submissions.
• Shows the last Fresh Sync result and leaves unresolved customers explicitly marked as Not linked.

1.20.8

• Fix Customers admin styling after the Entries-to-Customers menu restructure by loading plugin assets using both the WordPress hook and explicit plugin page slug.
• Keep the legacy Entries route hidden and styled for backward-compatible bookmarks.

1.20.6

• Replaced the separate Entries area with Customers as the primary CRM record screen.
• Customer list now combines identities from form submissions, WooCommerce carts/orders, browser identities, and product activity.
• Form entries are treated as Submissions inside the matching customer profile instead of living in a separate global Entries screen.
• Customer table now shows Submissions, Orders, Carts, Product activity, String client, contact information, and last activity.
• Existing customer profiles keep Overview, Submissions, Orders, Carts, and Appointments; the Submissions tab now includes both form submissions and commerce submissions.
• Legacy Entries URLs remain compatible but render the new Customers screen, preserving old bookmarks without exposing a second record model.

1.20.1

• Phone-first WooCommerce identity resolution: if checkout phone and email belong to different String clients, the cart/order Submission belongs to the phone client instead of failing.
• Sends primary/secondary phone and email roles with WooCommerce cart and order Submission Additional Data; it does not auto-merge client contact records.
• Keeps one progressive checkout Submission; if email identifies Client A first and a later phone identifies Client B, the same Submission moves to Client B.
• Does not merge the two String clients automatically.

1.20.0

• Smart phone fallback: a high-confidence Egyptian local mobile number such as 010/011/012/015 is normalized with +20 even when the checkout/address country is different; customer country is never overwritten by phone country.
• Identity resilience: a valid email can create/sync the String client even when the supplied phone fails String phone/country formatting validation. Phone uniqueness conflicts are never bypassed.
• Keeps explicit international (+ / 00 / calling-code) normalization global and unchanged.

1.19.9

• Separate customer identity from activity/session/cart lifecycle: long-lived Browser ID (180 days, refreshed by activity), 2-hour inactivity Activity Sessions, and independent Cart Journeys.
• Persist a known browser-to-customer association server-side for up to 180 days from the shopper’s latest commerce activity; the first-party browser cookie contains only a pseudonymous ID, not email/phone.
• When a guest supplies email/phone, stitch anonymous Product Events from the same Browser ID for the previous 24 hours, even when they belong to multiple Activity Sessions.
• Cross-device identity: a laptop and phone keep separate Browser IDs, but the same normalized phone/email resolves to the same String Client ID. Each device then remembers that identity independently.
• A remembered browser identity also feeds the cart tracker after the Woo guest session expires, so a returning known shopper can create a new Active cart Submission without re-entering the same phone/email.
• If a browser later presents a different explicit phone/email, stop carrying the previous browser identity into the new observation; already-identified historical events are never reassigned.
• Product Events admin now shows Browser ID, Activity Session, and resolved String Client ID separately.

1.18.8

• Keep Cleared cart inside the same WooCommerce session and the same String Submission; clearing the cart no longer rotates the cart journey key.
• Adding a product again after Cleared cart reactivates the existing Submission as Active cart and restarts the inactivity timer.
• Record an explicit Cart reactivated activity note in String while retaining the exact product-added activity.
• Preserve one cart journey across add/remove/quantity/clear/reactivate activity until checkout is recovered or the WooCommerce session genuinely changes.

1.18.5

• WooCommerce cart/order Submissions now resolve the String WordPress source automatically and send that source on creation.
• Added a WooCommerce section inside The String CRM > Customers with Orders and Carts tabs.
• Orders show customer identity, cart state, WooCommerce payment/order status, total, String Submission ID, sync state, last sync/error, and WordPress source.
• Carts show captured identity, active/abandoned/failed/recovered state, linked Woo order/payment status, total, String Submission ID, and sync result.
• Commerce Entries read WooCommerce orders and the plugin cart table directly, so they do not create a second copy of the order data.

1.18.4

• Cart lifecycle now distinguishes checkout Pending payment from pre-checkout Active cart.
• Creating a WooCommerce order keeps the same Submission and uses the existing Pending payment Lead Journey mapping while the abandonment timer continues.
• If the pending checkout remains unpaid past the configured timeout, the same Submission moves to Abandoned cart and cannot be reset by background Pending-payment re-sync.
• An explicit WooCommerce Failed status now becomes a terminal failed cart state and uses the existing WooCommerce Failed -> String status mapping (for example Failed payment) instead of later being overwritten as Abandoned cart.
• A real retry from Failed/Cancelled/Abandoned back to Pending restarts the inactivity timer on the same Submission.
• No WhatsApp/recovery automation was added to the plugin; all follow-up remains in String Automations.

1.18.3

• Fixed cart -> order duplicate Submissions by attaching the existing cart Submission to the WooCommerce order before the order is first saved/live-synced.
• Added an early woocommerce_new_order adoption hook as a second guard so Pending payment continues on the same Active/Abandoned cart journey.

1.18.2

• Fix Pending payment cart lifecycle: creating a Woo order no longer marks the cart recovered before payment/checkout completion.
• Active cart now moves to Abandoned cart after the configured timeout even when WooCommerce has already created a Pending payment order.
• Preserve Abandoned cart on later Pending payment order syncs instead of resetting it from the Woo status mapping.
• Add a request-driven fallback scan in addition to WP-Cron so 5/10-minute transitions are more reliable on hosts with delayed cron.
• Clarify that Active cart and Abandoned cart are String CRM statuses, not WooCommerce order statuses.

1.17.16

• Harden WordPress database queries for Plugin Directory security checks by using prepared identifier placeholders and static query shapes.
• Fix translation calls so translatable strings use literal text as required by WordPress internationalization standards.

1.17.15

• Improve HPOS/admin live-order automatic synchronization when an early incomplete save occurs before final billing identity or line items are available.
• Include billing identity and line-item details in live-order change detection.
• Retry later hooks in the same request after a failed foreground sync instead of incorrectly treating the failed attempt as complete.
• Improve support for phone-only guest orders using unambiguous international numbers without a leading plus sign.
• Keep persistent queues/backfill as retry and repair paths while successful live saves remain deduplicated.

For older release history, see changelog.txt included with the plugin.