Data transmission via URL – Fastory

1. How does it work

The Data transmission via Url feature allows you to automatically retrieve information about users of your experience through attributes previously configured in your bot, and keys added to your URL.

Example : https://story.tl/xxxx?first_name=Nabil

Attributes correspond to data such as first names, email addresses or telephone numbers, which form the columns of user data on Audience.

The keys correspond to the different values that the attributes can take. They complement the corresponding columns in Audience.

2. The attributes you can recover

A. Automatically retrieve a default attribute

You can choose to automatically retrieve the various default attributes that you can find in Audience.

List of default attributes

First name

Last name

Phone

Date of birth

Address

Postal code

Region

Country

Username

Company job

Company size

Company website

⚠️

For the default attributes (email, username, phone number…), you do not need to configure the bot. The information will be automatically retrieved and viewable in the Audience tab of your workspace. However, you will need to customize the URL with attributes and keys, otherwise the feature will not work.

Example: Retrieving Default Attributes in a Game Embedded in an Application

You want to make your experience accessible from your application or your website in which the user has the possibility to connect (email + password), and you want to retrieve the email addresses of the participants without asking for them via the bot .

⚙

The technical team of your application will ensure that the email of the user attached to his account is dynamically passed in the URL.

The URL will then be displayed in the following form:

https://story.tl/game-in-app/?email=xxx@xxx.fr

Thus, when the user accesses your experience from your application on which he will have previously connected, the email addresses of the participants will be automatically transmitted to Fastory and collected in the Audience page of your workspace, in the “email” column.

You will then not need to request this same information through the chatbot, to maintain the user's immersion in the experience.

The data will therefore be recorded without a bot even being open.

💡

In the case of an Instant Winner, users using a valid email address will be able to participate in the contest directly without having to re-enter their email addresses in the chatbot. Our anti-cheat system is however applied, and users using blacklisted email addresses will not be able to participate in the instant win.

B. Create your own custom attribute

You can choose to create your own attribute.

Click on Data via Url

click on the + button

Write the Label for the attribute that you want to create, as well as the format of the attribute (text, number, date, true or false)

Here we have created a “rewards” attribute, “text” format.

In an experience where the user must choose the prize he wants to win between a Samsung or Apple device, you can put 2 redirect buttons with 2 partially different URLs

For the Apple button: https://story.tl/jeu-concours?dotation=apple

For the Samsung button: https://story.tl/jeu-concours?dotation=samsung

User data will thus all be retrieved normally in Audience, regardless of the choice of rewards.

But the column rewards of the .csv file will be filled with apple or samsung depending on the user's choice.

3. Custom URL

At the end of the URL you need to add attribute and key like this:

https://story.tl/xxxxxx?attribut=key

Example: https://story.tl/game-contest?rewards=apple

You can also add multiple attributes in the URL separated by &:

Example: https://story.tl/jeu-concours?dotation=apple&email=nabil@help.fr

4. Get information

In the "bot data" file in Audience, you will find the attributes as well as the keys inserted into the URLs.

***

5. Another example to better understand

You want to run an internal competition for different areas of activity (HR department, marketing department and accounting department) and find out which department the player(s) belong to.

In the bot parameters, you will need to add:

attribute > service

Participants will have access to the same URL: https://story.tl/mon-jeu-interne however you can add a parameter to your url to dissociate the participation of your players according to their services. URLs may appear as follows:

https://story.tl/my-internal-game?service=rh

https://story.tl/my-internal-game?service=marketing

https://story.tl/mon-jeu-interne?service=accounting

Once the game is closed, you can find the information in a CSV file. You will need to download it from your workspace, on the audience page