Platform.ly

Transactions
You can select what transactions you want to include in your Platformly sales reports:
<ul>
<li>All transactions</li>
<li>Successful purchases</li>
<li>Failed purchases</li>
<li>Refunded orders</li>
<li>Cancelled orders</li>
</ul>
Contacts Settings
1. New Users
Every new user is imported in Platformly immediately after registration. You can choose which segment to add them to and/or apply tags.
2. GDPR
If you want to be GDPR-compliant, you can request users to tick a box, to confirm subscription. This is optional.
If you decide to use it, the tick box will be shown on your checkout page.
If the user ticks the box, meaning he or she agrees to receive marketing communications from you, he or she will be added to the segment of your choice.
If the user doesn’t tick the box, meaning he or she does not agree to receive marketing communications from you, he or she won’t be added to that segment, so you know you cannot send marketing emails to this person.
You may apply tags instead of adding users to different segments.
3. Purchase Actions
You can add to a segment or apply a tag when:
<ul>
<li>A purchase is made</li>
<li>An order is refunded</li>
<li>A transaction fails</li>
<li>An order is canceled</li>
</ul>
Events Settings
You can track user actions.
Here is a list of events you can track:
<ul>
<li>
View product: when users visit a product page
</li>
<li>
Add to cart: when users add a product to their cart
</li>
<li>
View cart: when users move to the cart page
</li>
<li>
Checkout: when users move to the checkout page
</li>
<li>
Place order: when users place an order
</li>
<li>
Abandoned cart: when users add a product to their cart but don’t check out and leave the products in their cart for more than X minutes
</li>
<li>
Abandoned cart recovered: when users finish checkout after receiving an abandoned cart email.
</li>
</ul>
Event data of registered users will instant sent to Platformly.
For unregistered users, data will be stored in the user’s session and will be sent to Platformly after the user registers or makes an order.
Product Page
You can also choose to add users to a specific segment, or apply them a specific tag on a product level (for a specific product). To do so, simply open the product page in WordPress, scroll down to the Product Data section and open the Platform.ly tab.
You can add users to a segment, or apply them a tag:
<ul>
<li>When the product is added to cart</li>
<li>When the product is purchased</li>
<li>When the order is refunded</li>
<li>When the order has failed</li>
<li>When the order is cancelled</li>
</ul>
Please note that you will also be able to insert product information to your email in Plaformly (including the list of products added to cart), as well as set up automations using the events, segments and tags previously created, access detailed sales reports and more.
For more information, as well as updates and references for further reading, please visit the <a href="https://www.platform.ly/blog/" rel="noopener nofollow ugc">Platform.ly blog</a>.

Platform.ly for WooCommerce

Easily connect WooCommerce to your Platformly CRM, set up abandoned cart campaigns and access detailed customer reporting including lifetime value and …

erravi

Quantely Activity is a lightweight, privacy-conscious plugin that records visitor activity (pageviews and interactions).
It helps site owners understand what is happening on their website for monitoring, diagnostics, performance checks, and analytics validation. It also makes this data available to downstream analytics tools.
Quantely Activity runs fully on-site, uses no external services, stores data only briefly, supports cookie-free operation, does not depend on JavaScript, and does not store plain IP addresses.
<h3>Key features</h3>
<h4>Robust traffic monitoring</h4>
Quantely Activity captures activity reliably under imperfect conditions.
<ul>
<li>Server-side pageview capture (always-on baseline)</li>
<li>Optional browser signals (clicks, forms, engagement)</li>
<li>Server-side event capture from plugins, including WooCommerce</li>
<li>Server and browser alignment via <code>pv_id</code></li>
<li>Receive-order recording with preserved origin metadata</li>
<li>Lightweight deduplication of duplicate signals</li>
</ul>
<h4>Traffic context</h4>
Each hit is enriched with context for interpretation and downstream use.
<ul>
<li>UTM parameters (<code>utm_source</code>, <code>utm_medium</code>, etc.)</li>
<li>Click IDs (e.g. <code>gclid</code>, <code>fbclid</code>)</li>
<li>Channel classification (email, paid, social, ai, search, referral, direct, internal)</li>
<li>Visitor continuity via cookies and derived identifiers</li>
</ul>
<h4>Engagement signals</h4>
Engagement is captured efficiently using milestone-based signals.
<ul>
<li>One maximum engagement value per pageview</li>
<li>Fibonacci-based milestones (<code>2–89 seconds</code>)</li>
<li>No continuous timers or heavy scripts</li>
</ul>
<h4>Internal traffic filtering</h4>
Internal or irrelevant traffic can be excluded without losing visibility.
<ul>
<li>Role-based exclusions (e.g. admins)</li>
<li>IP-based exclusions</li>
<li>Path-based exclusions</li>
<li>Hits remain visible but are marked (<code>is_excluded</code>)</li>
</ul>
<h4>Bot filtering</h4>
Automated traffic is detected and classified at capture time.
<ul>
<li><code>is_nonhuman</code>, <code>bot_label</code>, <code>bot_reason</code></li>
<li>Detection based on patterns, endpoints, and behavior</li>
<li>Reclassification possible as patterns emerge</li>
</ul>
<h3>Privacy</h3>
Designed to minimize data exposure and keep control local.
<ul>
<li>No plain IP storage</li>
<li>Short retention window</li>
<li>GPC / DNT support</li>
<li>No external tracking services</li>
<li>Data stored fully on-site</li>
</ul>
<h3>Integrations</h3>
Captured data is structured so other tools can use it.
<ul>
<li>Activity data can feed downstream analytics tools</li>
<li>Events remain connected to their original page context</li>
<li>Compatible with analytics and processing workflows</li>
</ul>
Quantely Activity exposes a small developer API for integrations and downstream processing.
<ul>
<li><code>qmon_hit_before_insert</code> — Filter a normalized hit array before it is stored.</li>
<li><code>qmon_hit_recorded</code> — Action fired after a hit has been stored. This is the main integration point for forwarding or persisting captured records.</li>
<li><code>qmon_event_normalize</code> — Filter a normalized event payload before it is finalized.</li>
<li><code>qmon_event_db_dedupe_window_sec</code> — Filter the database deduplication window for events.</li>
<li><code>qmon_bot_verdict</code> — Filter the bot-classification verdict before it is finalized.</li>
</ul>

Quantely Activity

See what is really happening on your WordPress website.

Platform.ly for WooCommerce vs Quantely Activity