Connect a WordPress website to the correct client workspace in the Shopping Ads\nSolutions (SAS) back office. After the website administrator pairs the plugin,\nauthorized workspace users can browse published page text and import selected\nWooCommerce products and product categories into Products & Collections.\nWith separate administrator consent, SAS also synchronizes full order history\nand customer profiles for performance, purchase-frequency and retention analysis.<\/p>\n\n
This plugin is a connector for the external SAS service. An existing SAS account\nwith access to a client workspace is required. Contact\nShopping Ads Solutions<\/a> to arrange workspace\naccess. Installing the plugin alone does not create a service account.<\/p>\n\n WooCommerce is optional. Without it, the connection supports published pages.\nCommerce access requires WooCommerce 8.2 or later and supports legacy and HPOS\norder storage. Order line items include purchased variations. It does not publish\nads, send marketing, alter orders, or edit website content.<\/p>\n\n This plugin connects to Shopping Ads Solutions only after an administrator pairs\nthe website. The pairing request sends the one-use code, site URL, REST API URL\nand a dedicated random read-only credential over HTTPS to the selected environment:\nhttps:\/\/bo.shoppingadssolutions.com or https:\/\/staging.shoppingadssolutions.com.\nSAS can then request site name, plugin version, published non-password-protected\npage text\/URLs and WooCommerce product\/category names, descriptions, image URLs,\nprices, currency, SKUs and publication-update timestamps. The data supports\nconnection verification, page browsing and the catalog imports selected in SAS.\nWith the separate order\/customer checkbox enabled, SAS can read orders in all\nregistered order statuses (excluding trash and checkout drafts), dates, currency,\nitems and variations, native cost-of-goods values when enabled,\ncoupon\/fee\/shipping\/tax lines, refunds, notes, billing and\nshipping addresses, contact details, payment method and transaction reference,\ncustomer IP\/user-agent, WooCommerce attribution fields and registered customer\nprofiles. Customers without accounts are represented through their orders.\nCustomer\/subscriber accounts without orders are also included. Account creation\nor purchase does not prove email\/SMS marketing permission: normalized consent\nremains unknown. Owner-approved metadata can supply extension-specific consent,\nloyalty, subscription and shipment evidence; these require interpretation before\nautomation use. Arbitrary extension tables, abandoned carts and browsing events\nare not collected by this plugin. Password, order-key, payment-token and card-number\nfields are excluded, as are drafts\/private pages. No tracking scripts are added.\nCredentials and detailed commerce payloads are encrypted in SAS; only a credential\nhash and the approved permission\/metadata selection are saved in WordPress.<\/p>\n\n The administrator initiates pairing. SAS then requests data over authenticated\nHTTPS. Catalog requests are manual. With commerce consent enabled, the SAS worker\nperforms an initial history import, refreshes approximately every six hours and\nsupports manual refresh\/resume. There is no outbound data transmission at plugin\nactivation and no marketing delivery. Old catalog-only pairings do not gain\ncommerce access through an update: the administrator must pair again and check\nthe order\/customer permission. Connections and datasets are isolated per client.\nOrder\/customer details are restricted to SAS users with integration edit access;\nintegration viewers can see aggregate totals and sync progress.<\/p>\n\n Use Revoke website access, deactivate, or uninstall to immediately remove local\naccess. A later SAS connection check reports revoked credentials. Disconnect in\nSAS deletes its usable credential, imported orders\/customer profiles and pending\ncommerce sync runs; imported catalog cards are preserved as workspace content.\nRe-pair to restore access. Source deletions and anonymization propagate after the\nnext complete successful refresh, not immediately; a failed\/partial refresh never\ndeletes unseen records. Changing the approved metadata selection or re-pairing\nwithout commerce access clears the prior commerce dataset in SAS. To request\nremoval of workspace content, use\nthe contact route in the service privacy policy. Uninstalling this plugin removes\nits local connection information; it does not delete previously imported SAS data.<\/p>\n\n\n Both the website and REST API must use HTTPS on the same hostname. The server\nmust forward the Authorization header to PHP and allow inbound REST requests.\nSupports single-site installations, including WordPress in a subdirectory and\nthe default (plain) permalink configuration. On Multisite, activation succeeds without errors, but pairing and data access\nremain disabled. A notice in the plugin settings and Network Plugins screen\nexplains that a standalone installation is required.<\/p>\n\n\n No. An administrator confirms a pairing code. The plugin creates a dedicated\ncredential limited to its own read-only endpoints.<\/p><\/dd>\n In each SAS client workspace under Integrations > WordPress. In WordPress, use\nSettings > Shopping Ads Solutions to pair or revoke access.<\/p><\/dd>\n No. Choose the products or categories in the back office and select Import \/\nrefresh selected. Existing cards are updated without duplicating their source\nidentity or overwriting manually written strategy notes.<\/p><\/dd>\n\n<\/dl>\n\n\n Allow clean activation on Multisite while keeping unsupported pairing\/data access\ndisabled. Use a distinctive SHOPADSO prefix for plugin classes, settings, actions\nand query keys. Preserve existing single-site connections during the update.<\/p>\n\n Add separately approved WooCommerce order\/customer reads, complete business\nrecords, owner-selected extension metadata, safe legacy\/HPOS keyset pagination,\nrecurring SAS synchronization, encrypted datasets and performance\/retention data.<\/p>\n\n Prepared the directory package, documented the external service and account\nrequirements, added translatable interface text, and made form nonce checks\nexplicit at each administrator action.<\/p>\n\n Secure tenant\/site-bound pairing, published page browsing, optional WooCommerce\ncatalog selection\/import, credential rotation and local revocation.<\/p>","raw_excerpt":"Read-only connection between your WordPress website and your SAS client workspace.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/383745","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=383745"}],"author":[{"embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/shoppingadssolutions"}],"wp:attachment":[{"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=383745"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=383745"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=383745"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=383745"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=383745"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=383745"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
External service and data<\/h4>\n\n
\n
Revocation<\/h3>\n\n
\n
\n
Does this require a WordPress administrator password or WooCommerce API key?<\/h3><\/dt>\n
Where do I manage connected websites?<\/h3><\/dt>\n
Does it automatically update imported products?<\/h3><\/dt>\n
1.1.1<\/h4>\n\n
1.1.0<\/h4>\n\n
1.0.1<\/h4>\n\n
1.0.0<\/h4>\n\n