{"id":376643,"date":"2026-10-01T16:22:18","date_gmt":"2026-10-01T16:22:18","guid":{"rendered":"https:\/\/wordpress.org\/plugins\/radarsend\/"},"modified":"2026-10-04T22:56:37","modified_gmt":"2026-10-04T22:56:37","slug":"radarsend","status":"publish","type":"plugin","link":"https:\/\/frp.wordpress.org\/plugins\/radarsend\/","author":23573861,"comment_status":"closed","ping_status":"closed","template":"","meta":{"version":"3.2.0","stable_tag":"3.2.0","tested":"7.1.3","requires":"6.5","requires_php":"7.4","requires_plugins":null,"header_name":"RadarSend","header_author":"RadarSend","header_description":"Connect to RadarSend to track visitors, sync contacts, and automate lifecycle stages. If using WooCommerce, it automatically adds order events, subscription tracking, and product tagging.","assets_banners_color":"132116","last_updated":"2026-10-04 22:56:37","external_support_url":"","external_repository_url":"","donate_link":"","header_plugin_uri":"","header_author_uri":"https:\/\/www.radarsend.com","rating":0,"author_block_rating":0,"active_installs":0,"downloads":268,"num_ratings":0,"support_threads":0,"support_threads_resolved":0,"author_block_count":0,"sections":["description","installation","faq","changelog"],"tags":{"3.1.5":{"tag":"3.1.5","author":"radarsend","date":"2026-10-01 16:22:06","revision":3723472},"3.2.0":{"tag":"3.2.0","author":"radarsend","date":"2026-10-04 22:56:37","revision":3727894}},"upgrade_notice":[],"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3723472,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3723472,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3723472,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3723472,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3723472,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":{"radarsend\/form":{"name":"radarsend\/form","title":"RadarSend Form"}},"tagged_versions":["3.1.5","3.2.0"],"block_files":[],"assets_screenshots":[],"screenshots":[]},"plugin_section":[],"plugin_tags":[232,2736,1150,264,286],"plugin_category":[36,45,58],"plugin_contributors":[283912],"plugin_business_model":[],"class_list":["post-376643","plugin","type-plugin","status-publish","hentry","plugin_tags-analytics","plugin_tags-contacts","plugin_tags-crm","plugin_tags-email-marketing","plugin_tags-woocommerce","plugin_category-analytics","plugin_category-ecommerce","plugin_category-user-management","plugin_contributors-radarsend","plugin_committers-radarsend"],"banners":{"banner":"https:\/\/ps.w.org\/radarsend\/assets\/banner-772x250.png?rev=3723472","banner_2x":"https:\/\/ps.w.org\/radarsend\/assets\/banner-1544x500.png?rev=3723472","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/radarsend\/assets\/icon.svg?rev=3723472","icon":"https:\/\/ps.w.org\/radarsend\/assets\/icon.svg?rev=3723472","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"<!--section=description-->\n<p>RadarSend connects your WordPress site to your RadarSend account so that the\npeople who register, buy, or subscribe on your site become contacts you can\nsegment and email.<\/p>\n\n<p><strong>This plugin requires a RadarSend account.<\/strong> It is the client for a paid\nthird-party service; without an account it has nothing to connect to. See the\nExternal Services section below for exactly what data is sent and when.<\/p>\n\n<h4>What it does<\/h4>\n\n<ul>\n<li>Syncs WordPress users to RadarSend contacts on registration and login<\/li>\n<li>Keeps a durable link between each WordPress user and their RadarSend contact,\nso changing an email address moves the existing contact rather than creating a\nsecond one<\/li>\n<li>Optionally injects RadarSend's tracking script to record page views and\nattribute them to a known contact<\/li>\n<li>Records login and signup events<\/li>\n<li>Renders forms built in RadarSend, via a block or the <code>[radarsend_form]<\/code> shortcode<\/li>\n<\/ul>\n\n<h4>With WooCommerce<\/h4>\n\n<ul>\n<li>Purchase, refund, and payment-failure events<\/li>\n<li>Subscription activation, renewal, cancellation, and expiry events\n(requires WooCommerce Subscriptions)<\/li>\n<li>Product-based tagging rules<\/li>\n<li>Lifecycle stage mapping per subscription state<\/li>\n<li>Customer billing details and order totals synced to the contact record<\/li>\n<\/ul>\n\n<p>WooCommerce is optional. Without it, the plugin syncs users and tracks activity.<\/p>\n\n<h3>External Services<\/h3>\n\n<p>This plugin connects to RadarSend, a third-party contact management and email\nservice: https:\/\/www.radarsend.com<\/p>\n\n<p><strong>It transmits personal data to that service.<\/strong> RadarSend is operated by the\nsame authors as this plugin. You must have a RadarSend account, and you are\nresponsible for having a lawful basis to send your users' data to it.<\/p>\n\n<p>Nothing is sent until an administrator connects the site to a RadarSend\naccount from the plugin's settings screen. Before that, the plugin makes no\nexternal requests at all.<\/p>\n\n<h4>Endpoints contacted<\/h4>\n\n<ul>\n<li><code>https:\/\/app.radarsend.com\/oauth\/authorize<\/code> \u2014 only when an administrator\nclicks Connect. Opens RadarSend's authorization screen in the browser.<\/li>\n<li><code>https:\/\/mcp.radarsend.com\/oauth\/register<\/code>, <code>\/oauth\/token<\/code> \u2014 exchanges and\nrefreshes the OAuth credentials that authorize this site. Sends your site URL.<\/li>\n<li><code>https:\/\/mcp.radarsend.com\/wordpress\/*<\/code> \u2014 the API used for all contact and\nevent syncing described below.<\/li>\n<li>The tracking script URL supplied by your RadarSend account \u2014 loaded in\nvisitors' browsers only when tracking is enabled.<\/li>\n<li><code>https:\/\/mcp.radarsend.com\/wordpress\/api\/forms<\/code> and <code>...\/forms\/{id}\/embed<\/code> \u2014\nthe list of your forms and their rendered markup, fetched when you place a\nform and when the block editor loads.<\/li>\n<li>The forms script from your RadarSend tracking domain \u2014 loaded in visitors'\nbrowsers only on pages that contain a RadarSend form.<\/li>\n<\/ul>\n\n<h4>Data sent, and when<\/h4>\n\n<ul>\n<li><strong>On user registration and login:<\/strong> email address, first and last name,\nWordPress user ID, and username.<\/li>\n<li><strong>On a WooCommerce order or subscription change:<\/strong> the customer's account\nemail (a guest's billing email), name, billing email, phone, company,\naddress, city, state, country, order totals, product names, and\nsubscription status. Only if you set them up: the order and subscription\nfields you map on the Field mapping tab (such as lifetime value, order count\nand last order date), and the tags from your tagging rules.<\/li>\n<li><strong>On an email address change:<\/strong> the old and new addresses, so the existing\ncontact can be moved instead of duplicated, and your choice of whether an\nunsubscribe carries over to the new address.<\/li>\n<li><strong>From visitors' browsers, when tracking is enabled:<\/strong> each page view (the\npage address, title and referrer, the visitor's screen and window size and\ntime zone, and whether the browser is automated); time on page, how far the\nvisitor scrolls, and when they first interact with the page; whether the\nvisit came from a link in a RadarSend email; with WooCommerce, each product\nadded to the cart (product ID and name, price, quantity and currency); and\nthe email address of a logged-in user (or of a guest, on their order\nconfirmation page), used to attribute their activity to their contact. As\nwith any web request, RadarSend also receives the visitor's IP address and\nbrowser user agent. RadarSend's tracking script sets its own cookies for\nthis, and holds them back until consent when your RadarSend account\nrequires it.<\/li>\n<li><strong>When a visitor submits a RadarSend form:<\/strong> whatever that form collects \u2014\ntypically name, email address and any consent choices. These submissions go\n<strong>directly from the visitor's browser to RadarSend<\/strong> and are not received,\nstored or processed by your WordPress site. Which fields a form collects is\ndecided in RadarSend, not here.<\/li>\n<\/ul>\n\n<p>Tracking can be turned off in the plugin settings, in which case no script is\nloaded and nothing is sent from visitors' browsers.<\/p>\n\n<p>By using this plugin you agree to RadarSend's terms and privacy policy:<\/p>\n\n<ul>\n<li>Terms of Service: https:\/\/radarsend.com\/legal\/terms\/<\/li>\n<li>Privacy Policy: https:\/\/radarsend.com\/legal\/privacy\/<\/li>\n<\/ul>\n\n<!--section=installation-->\n<ol>\n<li>Install and activate the plugin.<\/li>\n<li>Go to <strong>RadarSend<\/strong> in the admin menu.<\/li>\n<li>Click <strong>Connect<\/strong> and authorize the site against your RadarSend account.<\/li>\n<li>Complete the setup wizard to choose tracking and lifecycle stage settings.<\/li>\n<\/ol>\n\n<p>Existing users can be synced in bulk from <strong>RadarSend \u2192 Sync Users<\/strong>.<\/p>\n\n<!--section=faq-->\n<dl>\n<dt id=\"do%20i%20need%20a%20radarsend%20account%3F\"><h3>Do I need a RadarSend account?<\/h3><\/dt>\n<dd><p>Yes. This plugin is a client for the RadarSend service and does nothing without\nan account. You connect by clicking Connect and authorizing the site; there is\nno API key to copy or paste.<\/p><\/dd>\n<dt id=\"do%20i%20need%20woocommerce%3F\"><h3>Do I need WooCommerce?<\/h3><\/dt>\n<dd><p>No. WooCommerce adds order, subscription, and product-tagging features, but the\nplugin syncs users and tracks activity without it.<\/p><\/dd>\n<dt id=\"what%20happens%20when%20a%20user%20changes%20their%20email%20address%3F\"><h3>What happens when a user changes their email address?<\/h3><\/dt>\n<dd><p>The plugin moves the existing RadarSend contact to the new address, so the\nperson keeps their history and subscription state instead of becoming a second,\nempty contact. If another contact already holds the new address, the plugin\nflags the pair for you to merge in RadarSend rather than guessing which record\nto keep. Pending merges are listed under <strong>RadarSend \u2192 Debug<\/strong>.<\/p>\n\n<p>By default the new address starts fresh: it can be emailed even if the old one\nhad unsubscribed. To carry an unsubscribe over instead, choose <strong>Keep\nunsubscribes<\/strong> under <strong>RadarSend \u2192 Overview \u2192 Contacts<\/strong>. Bounces and spam\ncomplaints never carry over; they belong to the old address.<\/p><\/dd>\n<dt id=\"which%20email%20does%20a%20woocommerce%20customer%27s%20contact%20use%3F\"><h3>Which email does a WooCommerce customer's contact use?<\/h3><\/dt>\n<dd><p>Their account email. A registered customer's orders, renewals and\nsubscription changes all update the contact for their WordPress account, even\nwhen checkout used a different billing email (for example, a purchasing\ndepartment's). The billing email is kept on the contact in the\n    billing_email field. A guest's contact is their billing email.<\/p><\/dd>\n<dt id=\"can%20i%20stop%20it%20tracking%20visitors%3F\"><h3>Can I stop it tracking visitors?<\/h3><\/dt>\n<dd><p>Yes. Turn off tracking in the plugin settings. No script is loaded and no\nbrowser-side data is sent.<\/p><\/dd>\n<dt id=\"does%20it%20bundle%20action%20scheduler%3F\"><h3>Does it bundle Action Scheduler?<\/h3><\/dt>\n<dd><p>Yes. Background jobs run through Action Scheduler so no API call blocks a page\nload. If another plugin (such as WooCommerce) also includes it, only the newest\ncopy is used \u2014 the copies do not conflict.<\/p>\n\n<p>Action Scheduler is developed by Automattic and licensed under the GPLv3\n(https:\/\/github.com\/woocommerce\/action-scheduler). Its files are included\nunmodified in <code>vendor\/woocommerce\/action-scheduler<\/code>.<\/p><\/dd>\n<dt id=\"how%20do%20i%20customize%20the%20data%20sent%3F\"><h3>How do I customize the data sent?<\/h3><\/dt>\n<dd><p>Three filters are available: <code>radarsend_contact_data<\/code> (contact fields before an\nupsert), <code>radarsend_event_properties<\/code> (event properties), and <code>radarsend_external_id<\/code> (the\nexternal identifier used per WordPress user).<\/p><\/dd>\n\n<\/dl>\n\n<!--section=changelog-->\n<h4>3.2.0<\/h4>\n\n<ul>\n<li>A registered customer's RadarSend contact is now always their account email. Orders, renewals and subscription changes used to sync the checkout's billing email instead, which could split one customer into two contacts. The billing email is now kept in a billing_email field.<\/li>\n<li>New setting under Overview \u2192 Contacts: whether an unsubscribe carries over when a customer changes their account email.<\/li>\n<li>A sync refused because another contact already holds the user is no longer retried, no longer pauses all syncing for five minutes, and is listed under Tools \u2192 Debug log for you to merge in RadarSend.<\/li>\n<li>The contact's name now comes from the WordPress account first and the billing details second.<\/li>\n<\/ul>\n\n<h4>3.1.5<\/h4>\n\n<ul>\n<li>Initial release on WordPress.org.<\/li>\n<\/ul>","raw_excerpt":"Sync contacts, track visitor activity and automate lifecycle stages with RadarSend. Adds WooCommerce order and subscription events.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/376643","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=376643"}],"author":[{"embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/radarsend"}],"wp:attachment":[{"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=376643"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=376643"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=376643"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=376643"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=376643"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/frp.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=376643"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}