# JSON Parsing - Counting inside an array, not the array itself
**URL:** https://community.mp3tag.de/t/json-parsing-counting-inside-an-array-not-the-array-itself/50614
**Category:** Web Sources Discussion
**Created:** [October 27, 2020, 9:52pm UTC](https://community.mp3tag.de/t/json-parsing-counting-inside-an-array-not-the-array-itself/50614 "2020-10-27T21:52:59Z")
**Posts on this page:** 1
**Showing post:** 3
### Author:  [@vkostas](https://community.mp3tag.de/u/vkostas)
#### Post date: [December 15, 2020, 8:34am UTC](https://community.mp3tag.de/t/json-parsing-counting-inside-an-array-not-the-array-itself/50614/3 "2020-12-15T08:34:30Z")
I think this is feasible using the [JSON\_Normalize Tool](https://community.mp3tag.de/t/ws-json-normalize-manipulate-json-utility/51062/5) I have recently developed.
The idea is original Json is parsed (as a pure string) and each tagname includes full path. All arrays are generated an ascending index from this tool (some WS do not have track position).
Based on above it is feasible (if you know upfront the `tagname` and condition) to introduce a counter only for those array objects.
Tool would make tagname `"component"` under `"tracks"` as `"tracks˃component"`. Please note **`˃`** in the tag path is NOT the gt (`>`) character although they look the same.
Have a look on the script first.
You could add your additional logic after `# END OF CONVERSION` (around line 250) and before `restore escaped characters`.
---
_[View the full topic](https://community.mp3tag.de/t/json-parsing-counting-inside-an-array-not-the-array-itself/50614)._