Embedded data refers to additional data that can be displayed within the Loop inbox in the conversation view when customers respond to surveys sent to them with a URL. The purpose of utilizing embedded data is to contextualize the response with data that is generated outside of Loop.

Examples of embedded data may include (among others):

- Customer Name
- Customer Contact Details
- Customer Loyalty Number
- Event Details
- etc.

Embedded data within the context of Loop consists of a key/value pair included within the URL as an additional parameter. Prior to integrating your platform with Loop, identify which fields you would like to include as embedded data. Loop includes a certain set of standard fields. If any additional fields are required, these would need to be created as custom fields within Loop. This combination of keys and values (embedded data) allows for the creation of a personalized customer feedback mechanism.

Collecting feedback from your customers through your platform is accomplished via a customized Loop URL that the customer receives when contacted. These URLs contain the fields and values that uniquely identify each customer and help contextualize responses.

Standard URL Parameters

Loop supports the following URL parameters:

No custom work is required for the use of these standard parameters. Once your application has been integrated with Loop, these parameters can be included as objects in the URL by default. These standard fields are represented in the URL as follows: fieldname=value.

For example, if you are reaching out to a customer who's first name is Dave, the object for this standard field in the URL the customer would receive would be fname=Dave
Additional objects will be added on to the URL depending on which ones have values associated with them.

Custom URL Parameters

Should you require custom parameters (i.e. those not included in the list above), these can be created as custom fields within the Loop Admin view. These custom parameters can then be added to the URL and are represented as objects in the URL as follows: custom[fieldname]=value

For example, if you were to create a custom field named "eventId" and a customer were to attend an event with eventId = 333, the object for this custom field in the URL the customer would receive would be ?custom[eventId]=333

Embedded Data in Action (An Example URL)

The URL that customers receive will be generated based on the following:
1. Your Loop account URL
2. Custom and Standard Loop fields that will be added as projects

The example below depicts an event management use-case.

Let us look at a Loop customer with https://customerX.blazeloop.com as their account URL. They would like to contact their customer to collect their feedback post-event. Their customer's details are as follows:

As such, the custom URL generated through the application will be as follows:


Customer Workflow

Once the custom fields have been created and the integration is complete, your customers will receive a unique survey link when a message is sent through your application.

Clicking on the link in the email will take them to the survey which they can complete.

Responses submitted by the customer are recorded in the Loop inbox with customer information (Embedded Data) shown in the right panel along with the event URL.

Did this answer your question?