⚠️ This article refers to Pico Version 1.17 and will be removed or updated in the future once we release Pico Version 2.0.

For communities that want to analyze their visitor behavior and interaction with the Pico plugin on site, it is possible to track specific events in the User journey. These range from signup through purchase. This requires some advanced coding knowledge, but can be configured as event listeners using the instructions below.

These fire on the following conditions:

pico.user.registered: A new signup occurs for the community. This includes email or social login for a contact that was not previously a member of the community.

pico.user.authenticated: A contact that existed already logs in. This will help to distinguish campaigns that did not create new users, but did prompt logging in (like registration walls).

pico.payment.paid: A new payment is made on site. This helps track conversions that lead to new payments, including gift purchases.

pico.paymentMethod.added: This is useful for measuring the conversion funnel of the checkout flow. If a user adds a payment method but ultimately does not pay, it may indicate hesitation around the total pricing amount.

<script type="text/javascript"> 
document.addEventListener('pico.user.registered',
(event) => {
console.log('a new user registered with event details: ', event.detail)

});
document.addEventListener(
'pico.user.authenticated',
(event) => {
console.log('a returning user authenticated with event details: ', event.detail)

});
document.addEventListener(
'pico.payment.paid',
(event) => {
console.log('a user paid with event details: ', event.detail)

});

document.addEventListener(
'pico.paymentMethod.added',
(event) => {
console.log('a user added a payment method with event details: ', event.detail)

});
</script>

In the above examples, these log console events, but could just as easily send conversion calls to Google Tag Manager, or other tracking pixels to measure campaign effectiveness.

For an example of these in action, please check out:

example.trypico.com and view the console.

Note: These events will not fire until the Pico plugin has loaded fully on-site.

Did this answer your question?