Should I use custom events or Product mapper to trigger engagements?

Hi @Souvik SInha ,

Thanks for reaching out us over community!

Using Product Mapper: 

• When you say you have dynamic list of data being rendered, its always best to have the data-attributes being rendered in the HTML content which can be used as the strong selectors to map the elements
• If you believe that list of elements that are being rendered has fixed with unique order - you can go with nth child selector option (NOT Recommended if the values are dynamic in nature)

Using Custom Events:

• Implementation should be a short liner code, however this is more effective, If you are interested in this approach, you can implement a single custom event for the entire dropdown list with multiple properties (Items in the list) being passed.
• Example: I have a list of States to be rendered based on Country

  aptrinsic('track', 'Dropdown List', {"StateName":"California"}); - // This will be triggered when some one clicks the list and choose california.-------------aptrinsic('track', 'Dropdown List', {"StateName":"Nevada"}); - // The same will be triggered when some one clicks the list and choose Nevada Here is the doc for custom events:

• https://support.gainsight.com/PX/API_for_Developers/02Usage_of_Different_APIs/Use_Custom_Event_API

For any further questions, I would recommend to reach us on pxsupport@gainsight.com

Thanks

Dileep Nalla

This has been here a bit but also wanted to add some thoughts. I love custom events, I am working to try to get our engineering team to use them more…

We recently added a new feature which can be three different states, under each state is different metadata:

1. empty
2. error
3. success

We trigger an engagement for each state where each is triggered by an accompanying Feature created within Product Mapper.  Then I realized that I could create unique elements with data reporting capabilities from each item within the product mapper - so that the custom event data was visible next to the user click data. 

We could report the number of times users ‘Viewed’ an indicator - by the state. Then we could also present the number of times a user ‘Clicked’ the indicator showing feature adoption and click through rates without having to connect data from the backend teams. In the end, we were able to connect three very valuable datapoints:

1. The number of items generated by the back end services (we don’t have gainsight in all products)
2. View: The number of items generated viewed by a user
3. Clicked: The number of items presented to a user which were clicked

But that’s not all… because we also used Product Mapper to define the hyperlinks from within (our Product and Engagements) out to our marketing website providing us the ability to track and (and more importantly) present how the new feature and gainsight drove user traffic to our website.

@kathleenkenny23 

@lpicone this is absolutely outstanding! I would love to dig into the outcomes of this more on our next call! Thank you for sharing these ideas with our community!!

jnies

Absolutely, I tried to tag you but couldn’t figure out your handle 😀