Access Parousya Component Data

Good to know: Some component data within the Parousya Component may not become available until the component has relevant data to present. For instance, the "Session Ended At" data element will remain empty until a session between a host and a customer has concluded.

How to access Component Data

In addition to actions, component data is another way to integrate the Parousya component into the Adalo ecosystem. This data can be accessed using Magic Text and can be used to improve the app user experience. For instance, when a Parousya session between a host and a customer starts, the app can display the location name in a notification, like "Store 83" or "Medical Waiting Room."

Component Data Descriptions

Makers can use component data via Magic Text.

Component Data	Description
Zone name	Beacon Zone Name: (e.g. Macy's Stores)
Beaconloc	Beacon Attachment 1: (e.g. Palo Alto Store)
Major	Beacon Attachment 2 (optional): only numeric
Minor	Beacon Attachment 3 (optional): only numeric
Beacon UUID	Beacon unique identifier (e.g. 14a42f12d900be6aaee94a9fb6595b2d)
Session ID	numeric
Customer ID	per session and pseudo anonymized alphanumeric
Host ID	per session and pseudo anonymized alphanumeric
Start Location	Session start address derived from device GPS coordinates
End Location	Session end address derived from device GPS coordinates
Start Time	Session start UTC time stamp
End Time	Session end UTC time stamp