The String CRM

The String CRM connects WordPress and WooCommerce with the String CRM platform while also providing a native WordPress form builder.

Core capabilities:

• Build forms directly in WordPress and store submissions locally.

• Style form submit buttons with backward-compatible solid colors or sanitized two-color gradients, including safe theme custom-property fallbacks.

• Resolve signed context from any published public WordPress detail post, including validated?type=cash|drive&id=POST_ID links from a separate page, and attach a validated String Product relation or the WordPress title to the resulting Submission without adding an automatic visible context field.

• Prefill hidden or visible fields from the page title, a sanitized URL parameter, a configured WordPress custom field/meta key, or the previous page URL, with an optional read-only frontend display. Referrer values are intended for attribution and may be empty when browsers suppress them.

• Generate a same-site dynamic CTA URL for the current published public post with [string_request_url type="cash" url="/request/"]; no post ID, title, or price is hardcoded.

• Optionally send successful form submissions to String as CRM submissions.

• Map WordPress content such as products, doctors, cars, courses, or other post types to String Products or Services.

• Map WooCommerce order statuses to String Lead Journey stages and statuses.

• Synchronize WooCommerce customers to String contacts/leads.

• Synchronize each WooCommerce order as a separate String Submission while reusing the same String client when email/phone matches.

• Set the String source of new WooCommerce cart/order Submissions to WordPress automatically and expose WooCommerce order/cart sync state inside The String CRM > Customers.

• View WooCommerce Customers in a unified CRM-style profile with Overview, Submissions, Orders, Carts, and Appointments tabs, stitched anonymous-to-known timeline, String status, lifetime deal size, product affinity, and bought-together insights.

• Create a String Submission immediately for an identifiable WooCommerce cart: logged-in customers are known from their account, while guests are linked once email or phone is captured. Add/remove/quantity changes update the same Submission and are appended as String notes; clearing all items closes that cart journey, and a later add starts a new cart Submission even in the same WooCommerce session.

• Keep the cart Active before checkout, use the normal WooCommerce mapping for Pending payment / Failed payment after checkout starts, and move an unpaid pending checkout to Abandoned cart after the inactivity timeout.

• Attach mapped product/category context and order details such as total, currency, payment method, billing/shipping summary, notes, coupons, and line items.

• Track WooCommerce storefront product behaviour (search, list view/filter/sort, product view/click/share/review, add/remove from cart) in a local Product Events log. Browser ID, Activity Session, Cart Journey, and customer identity are tracked separately so a known shopper can be recognized across visits while carts remain independent.

• Queue identified storefront events for the String universal commerce-event API. String Automations own WhatsApp reminders, waits, eligibility checks, and frequency caps; the WordPress plugin sends no reminder itself.

• Automatic create/update synchronization with rate-limit-aware retry and backfill handling.

• Optional one-way WooCommerce coupon synchronization with store-bound identity, resumable reconciliation, and lifecycle retries.

• Arabic/RTL and English/LTR WordPress admin support.

A String account is optional for local form collection. String External Partner API credentials are required only when remote synchronization features are enabled by an administrator.

External service: String

net after an authorized WordPress administrator configures String External Partner API credentials or enables a synchronization feature that requires them.

Depending on the features enabled, the plugin may send:

• WooCommerce storefront behaviour events, product context, page URL/referrer, UTM campaign data, available advertising click/cookie identifiers, a pseudonymous first-party Browser ID and Activity Session ID, and customer name/email/phone when the shopper is identified, so String can store commerce activity and run configured automations. Browser cookies do not contain email or phone. Anonymous guest product events remain local until identity is known. The plugin does not inject Meta, TikTok, Snap, or other advertising pixels.

• String External Partner client credentials to obtain an API access token.

• WordPress form definitions and selected routing/catalog identifiers.

• Form submissions and the fields configured by the administrator, including selected Branch/Product values, signed current page/product/doctor/car title context, source/tracking data, and uploaded attachments when enabled.

• Selected WordPress or WooCommerce content mapped to String Product/Service fields, including names, descriptions, pricing, SKU/stock, URLs, categories, currencies, relationship IDs, and stable integration identifiers.

• WooCommerce workflow/status mappings used by String Lead Journey synchronization.

• WooCommerce customer identity and billing contact details.

• WooCommerce order details including order status, total, currency, payment method, billing/shipping summary, customer note, coupon codes, and line-item names.

• When Coupon Sync is enabled, WooCommerce coupon definitions including discount semantics, spend/usage limits, product/category restrictions, expiry, free-shipping eligibility, and privacy-preserving hashes for restricted email entries. Raw restricted customer emails are not transmitted.

• When the WooCommerce cart journey is enabled, checkout identity (email/phone), cart total, currency, line-item names, and cart/checkout URLs. The Submission is created as soon as identity is available. Commerce labels are derived independently from canonical WooCommerce events; only WooCommerce order states use the existing Lead Journey mapping. Follow-up messages remain configured separately in String Automations.

The plugin also retrieves String account/catalog data needed for configured integrations, such as forms, branches, products, services, sources, categories, currencies, stages, and statuses.

net/

net/privacy-policy/

No String API connection is made until an authorized administrator configures the connection or enables a synchronization feature that requires it. If the administrator changes the API URL in Connection settings, requests are sent to that configured HTTPS endpoint instead.

Privacy

The String CRM stores form submissions in the WordPress database. Stored information can include submitted values, source URL, an irreversible hash derived from the visitor IP address, assignment information, synchronization status/error details, and timestamps. Accepted file uploads are stored in the WordPress uploads directory.

When String synchronization is enabled, configured submission and integration data may also be transmitted to String as described above. The plugin adds suggested text to WordPress’s Privacy Policy Guide so site owners can document this processing.

Deactivation, replacement updates, and uninstall are intentionally non-destructive: String connection credentials, Content Sync mappings, queue/backfill state, site UUID, cart/order linkage metadata, forms, and entries are preserved so an update or reinstall cannot disconnect the site or silently remove business records.