@alextran thank you for bringing this up here. Let me check the possibilities and get back to you. 

We have a few thousand mapping elements that a script can easily automate since we have specific naming rules. It would be a simple task to generate a list of mapping rules (even in MS Excel) and export them to Gainsight instead of manually putting all 4000 mapped elements. Also, it would be very helpful to maintain this mapping since a simple code change today would require manually updating all the mapping, sometimes dramatically rasing the implementation cost.

+1000. Being able to export and import our product mappings would be a game changer. It would save us tons of time and effort, especially when we're dealing with large-scale changes or audits.

Plus, having a list of mapped and unmapped elements would be a valuable tool for our team and leadership/other stakeholders. It would provide a clear overview of our product mapping, making it easier to track progress and make informed decisions.  

Having the product mapper as a table is essential for us. Until now, we have been managing it manually in Excel, and an export/import option would save us hours every week while significantly improving accuracy.

Use case 1: Double check my work, especially the URL rule within a UI Element rule. I need to ensure I have wildcards in there, as it pre-populates the current URL when adding the URL and I often miss this step. 

Use case 2: QA and future proofing. Provide a list of defined selectors that are part of our product mapping. Then, when our QA processes are reviewing new versions of the product, they can catch and alert if a selector no longer exists or other changes that could impact things. 

Hi!

ChatGPT and I have a workaround for this: 

1. Get the JSON:
   Open Product Mapper → Dev Tools → Network tab → refresh page → look for a large request (filter by “2”) → right-click → Copy as cURL (bash) → run it in Postman.

2. Convert to CSV:
   Save the JSON and upload it to ChatGPT with this prompt:

 “Extract all mappedElements and generate a CSV with:
parentId, parentName, id, name, eventType, urlScope, selector, propertyGroup, source, state, urlScopesCondition, lastModified, createdBy, lastModifiedBy, fullPath, and hierarchy levels (Level 0, Level 1, etc.).”

A couple of notes on that workaround:

In step 1, the request name will be numbered according to the channel, so the example ‘2’ shared above will apply for web app product maps. Note that mobile and desktop will be be ‘3’ and ‘4’ respectively.

Also in step 1, you can copy the request and rerun it in postman if you like, but the response from the initial request will be the corresponding product map in JSON form, so it can also be copied directly from the browser.

For users who do not need the rule-level details, there’s also the getFeaturesExtended request from the PX REST API. That response will also include the mapped elements, though not the rule-level details of the mappings themselves.

Our R&D team is investigating writing tests to check if tracked IDs are still present. Being able to download the full overview of Product Mapper Rules would be very beneficial for this purpose.

​@Mona ​@rschlette Thank you for the workaround information. I’ll share this with the team.

I have two products that are merging to become a single product (creating vertical integration). I intend to consolidate the Tag Keys for these products as they will have one tech stack. In doing this I am going to have to re-create the Product Map for one (or both) products as I move them. Having the ability to bulk export and import the Product Map would be great to assist with this large project.