https://experienceleague.adobe.com/docs/platform-learn/implement-in-websites/overview.html?lang=en This is a very good tutorial here. 

There is a hard limit on the number of rule components you can and should use.   If this use case is really needed, I would use a custom code condition and then use a select case statement in the javascript, not an (if then).  This will execute much faster. 

Whatever route you go, the naming convention should be so easy to understand for folks inside of your company that it requires little to no explanation.   If you need a decoder, or if the rule names are so long they don't fully show in the UI, then you will be tied to having to explain it over and o...

The link you posted goes to a 404 page.  Can you provide more context, screenshots, etc. 

Some of my go to resources for the following topics: Computed Attributes https://experienceleague.adobe.com/docs/experience-platform/profile/computed-attributes/overview.html?lang=enhttps://experienceleaguecommunities.adobe.com/t5/adobe-experience-platform/release-update-drive-impactful-personalizat...

Disregard my comment above.  This can NOT be used to send profile data.  Working to get the UI & Docs updated to reflect that.  Sorry for any confusion. 

Disregard my comment above.  This can NOT be used to send profile data.  Working to get the UI & Docs updated to reflect that.  Sorry for any confusion. 

So it's not with the webSDK directly but within datastreams.  https://experienceleague.adobe.com/docs/experience-platform/datastreams/configure.html?lang=en   ""Profile Dataset Select the Platform dataset that customer attribute data will be sent to. This schema must use the XDM Individual Profile c...

For now there is no automated way to do this. 

There were a few updates to the debugger.  Are you still having this issue?