Location Profile

The Location Profile stores information about a residential or business Location and is used by the Eliq platform to generate personalized energy insights, such as Energy Usage Categories and recommendations in Energy Advisor.

Accurate profiles are essential for high-quality insights. The more complete the profile, the more precise the analysis and recommendations become.

Eliq provides country-specific Location Profile configurations to ensure questions and options are relevant to local housing characteristics. Profiles can also be customized per customer on request. Location Profile data can additionally be used to better understand your customer base.

‍

How does it work – Introduction

A Location Profile is customised for each country to ensure that the questions asked and the options presented to the end user are relevant to the types of homes and appliances commonly used. Location Profiles can also be configured per customer upon request.

Customising the Location Profile for a customer is done in collaboration with our Data Science team to ensure that the content and properties are correctly integrated into Eliq’s algorithms, which provide energy insights.

The result is a profile tailored to each location, helping end users quickly and easily input the correct information, maximising the value of the app both during the onboarding journey and throughout the app’s continued use.

Location Profile Types

The Eliq Platform provides energy insights to both Residential Homes as well as for Businesses. In order for the Eliq platform to provide the right insights to each location, the Locations Profile type needs to be set:

• residential
• business

The profile type determines:

• Which onboarding questions are presented
• Which insights are returned by the Insights API

Profile type can be set via:

• POST /locations/{locationId}/profile/type
• Eliq Data Management API

By default, profile type is undefined until explicitly set.

Dynamic Questions (dependent_properties)

Location Profiles support dynamic question flows based on previous answers.

For example, if a user selects Apartment, questions related to pools or certain heating systems are automatically excluded.

This behavior is controlled by the optional dependent_properties field, which defines which profile keys must exist before a question is shown.

If users update their profile after onboarding, this logic should be reapplied to surface any newly relevant questions.

Required Fields (required_for_*)

Some profile questions include tags such as:

• required_for_euc_to_work
• required_for_sh_to_work

These tags indicate that a field is required for Energy Usage Categories or Similar Homes to function.

It is recommended to use these tags during onboarding to ensure users complete the minimum required information, while allowing optional questions to be answered later. This balances onboarding speed with insight quality.

Location Profile configurations, including content, dependencies, and required fields can be customized per country or customer. Contact Eliq for configuration requests.

API

Detailed information on how to implement the Location Profile including API request or response calls and possible errors can be found in the API Reference Documentation for the Location Profile. Below is an overview and explanation of what each Location Profile endpoint is for.

Get and Set Location Profile Type

Then Get Location Profile Type and Set Location Profile Type endpoints are used to get or set the Locations Profile Type which will determining whether the location is a residential home, which should receive residential energy insights from the Eliq platform, or if it is a business location, which should receive business energy insights. A location must have a set profile type value in order to receive the correct Location Profile for the user to fill in relevant questions.

Get Location Profile Questions and Values

The Get Location Profile endpoint returns profile questions, options for the end user to select or fill in, dependent properties for dynamic questions, and any already existing values (if the user has provided any previously).

Add New Location Profile Values

The Add New Location Profile endpoint is used to add new location values for a question and store them in the Eliq platform. It is used both for adding new values and for updating existing ones. For example, if an end user onboarded via the app and initially reported that four people live in their home, this value would be posted to the Location Profile using this endpoint. If the number of residents changes to five, the new value can be posted to the profile. The from parameter will determine the date from which the change is valid. The earlier value will remain in the Location Profile, providing a history of the home’s profile values.

Update Location Profile Value

To update or change existing values with specific dates in a Location Profile, the Patch Location Profile endpoint is used. This allows apps to enable end users to edit when a value is valid from and to update the location’s history.

Delete Location Profile Value

Use the Delete Location Profile Value endpoint to delete a value from a Location Profile that should no longer apply. This can be used to remove an unwanted change or to remove an unnecessary entry.

Get Location Profile Completion

An updated profile is crucial for providing the best insights. To help users understand whether they have completed all necessary profile information and if further details could improve the accuracy of energy insights, the Get Location Profile Completion endpoint can be used. This shows the user, within the app, a percentage of how many profile questions have been completed. It can also be used to encourage users to complete their home profile and reach “100% done!” (see the use case below).

Use Cases

Setting the Location Profile Type

The above screen showcases the question asked during the onboarding flow in where an end user is asked to fill in the Location Profile Type. This screen is shown if the value returned from the Get endpoint is undefined. The end user needs to be choose if the Location is a Residential Home or a Business ( residential or business). The chosen result is then Posted to the Eliq platform.

The next step is to ask the platform for the Profile Questions to allow the user to add information about their home or their business.

Standard Swedish Residential Profile, with required/not required

A set of questions in an onboarding flow for a residential location showing examples of questions that have required_for_euc_to_work or required_for_sh_to_work.

Additional questions in the onboarding flow of an app for a location with a residential location profile type. These questions that are not required for EUC or Similar Homes.

Intro and outro

Examples of how you can introduce residential profile and explain why it’s important.

Profile Completion Card

If you want a shorter and smoother onboarding it could be a good idea to let users only answer the required question in the home profile. In this case we have used the home profile card to let users complete the full home profile later. The Profile Completion card makes sense to have even if all profile questions are filled in so that the end user can see and feel satisfied that they are 100% complete with filling in their profile.

‍

‍