A new version of Data Query is here to make AT Internet’s decision-making platform even more powerful. Discover how the API query generator can considerably improve your reporting and analysis and help drive your decisions.

1. WEBINAR
INNOVATIONS 2014 / API V2 - DATA QUERY 2
July 2014
Mélanie CLAISSE - Product Manager
Clémence NOIZAT-TALLON - Product Manager

2. TABLE OF CONTENTS
I. Introduction
II. New features
III. Transition to the new version
IV. Q&A

3. I. INTRODUCTION
CONTEXT
- Databesity: a huge volume of data
- Difficulty to find the right information
at the right time
- To build easily, to automatize and
to custom reportings
- To share and to communicate data

4. I. INTRODUCTION
THE API 1 SUCCESS
- 80 000 000 calls in one year
(average)
- 2 600 users Data Query
- 15 000 templates Data Query
- ... and counting!

5. I. INTRODUCTION
WHY A NEW API?
- Faster and more powerful
- Flexibily
- Simplicity
- Evolution: 20 new features
- A new interface Data Query

6. I. INTRODUCTION
DATA QUERY 2
Exploring all the API new functionalities
Insuring an optimal user experience
A new environment, a new workspace

7. 1) NEW CALENDAR
II. NEW FEATURES
- A new calendar, entirely remade from the ergonomic point of view
- Relative periods
Pre-defined & custom periods, including real time
Simplification of calls on regular periods
Saving time: exports automation is easier
Example
- Multi-periods

8. 1) NEW CALENDAR
II. NEW FEATURES
Multi periods
Example: to identify the sales performances of 2 different periods
1st week of June & 1st week of July
Saturday June 14th, 21st and 28th
From the 1st to the 15th of June and July…

9. 1) NEW CALENDAR
II. NEW FEATURES
Product Orders
(May 25 - June 25)
Visits Orders
(June 25 – July 25)
Visits
TV 123 2 398 32 090 4 535 45 312
Tablet YX 1 873 24 350 2 435 25 644
Smartphone Z 2 109 18 724 4 356 24 320
Accessory ER 874 5 643 988 4 532
Multi periods
Example: to identify the sales performances of 2 different periods

10. 1) NEW CALENDAR
II. NEW FEATURES
Product Orders
(May 25 - June 25)
Visits Orders
(June 25 – July 25)
Visits
TV 123 2 398 32 090 4 535 45 312
Tablet YX 1 873 24 350 2 435 25 644
Smartphone Z 2 109 18 724 4 356 24 320
Accessory ER 874 5 643 988 4 532
With the API 1: 1 call per period and necessity to consolidate the products
Multi periods
Example: to identify the sales performances of 2 different periods

11. 1) NEW CALENDAR
II. NEW FEATURES
Product Orders
(May 25 - June 25)
Visits Orders
(June 25 – July 25)
Visits
TV 123 2 398 32 090 4 535 45 312
Tablet YX 1 873 24 350 2 435 25 644
Smartphone Z 2 109 18 724 4 356 24 320
Accessory ER 874 5 643 988 4 532
With the API 2: 1 call for all the table, product consolidation is already done
Multi periods
Example: to identify the sales performances of 2 different periods

12. 1) NEW CALENDAR
- Up to 3 periods
- P1 is the reference to the other ones
- Filters and sorts on P1
- 1 dimension per call (in progress)
- 100 lines per dataset
- 1 period can only contain once the same metric
II. NEW FEATURES
Multi periods
Functional scope of the multiple periods parameters in the API:

13. Example: to follow the evolution of sales per products during the running month
II. NEW FEATURES
Evolution of visits day by day on the period
Evolution hour by hour of the visits of the day, etc.
2) EVOLUTION

14. Functional scope of the EVO mode in the API:
- 1 dimension per call
- The EVO mode can’t be applied to multiple periods
- Maximum number of metrics in the dataset = 30
II. NEW FEATURES
2) EVOLUTION

15. Comparison between metrics over different dates
(variation in %, difference in value)
Example: to compare the sales per products between two periods.
II. NEW FEATURES
3) VARIATION AND DIFFERENCE

16. - You must select at least 2 metrics
- Evolution mode must be disactivated
Functional scope of the VAR / DIF mode in the API:
II. NEW FEATURES
3) VARIATION AND DIFFERENCE

17. Total “Displayed”: total of the metrics displayed in the dataset.
Total “Reference”: total of the reference site’s metrics (soon available).
Example: to get the weight of the 20 best sold products.
II. NEW FEATURES
4) TOTAL

18. Functional scope of the RATIO mode in the API:
- Need to activate the display of the Total
II. NEW FEATURES
5) RATIO

19. 6) META DATA
The Context parameter will transfer meta data information on the global call
scope.
Context for Space: label, currency, time zone, etc.
Context for Periods: period labels, list of dates
Context for Ranges: information linked to the result pagination (ex: Next URL)
Context for Profile: language, first day of week
II. NEW FEATURES

20. 7) FILTERS AND SORTS
II. NEW FEATURES
There are 9 new filters:
“Does not contain”
“Does not start with”
“Does not end by”
“Equals to value 1 or value 2”
“Is different from value 1 or value 2”
“Contains value 1 or value 2”
“Does not contain value 1 or value 2”
“Contains the word value 1 or value 2”
“Does not contain value 1 or value 2”
+ add of multi filter
Example: to isolate products whom title contains the words “Sony” OR “Samsung”
and which have generated a turnover >6,000.00€

21. 8) MAX RESULT
II. NEW FEATURES
With the Max result parameter, possibility to define the number of rows
required in the dataset.
By defaut Max result is 20.
Possibility to change the Max result parameter.
Value between 1 and 10 000.
If more than 10 000 is needed, necessity to make a pagination. Meta Data
are also made for this.

22. II. NEW FEATURES
9) OUTPUT FORMATTING
The output format has no longer to be written in the URL, it has to be
integrated in the header of API call.
Accept: application/json
Accept: application/xml
Accept: application/html
The default format is json

23. 10) FOCUS ON QUOTAS
Goal: to protect our infrastructures and provide an unified quality of service
to all users
- No limitation in number of API calls
- But a limitation of simultaneous calls
- 5 slots per user
- Possibility to have Premium accounts
II. NEW FEATURES

24. III. TRANSITION TO THE NEW VERSION
A NEW WORKSPACE, A NEW API
https://apirest.atinternet-solutions.com/data/v2/getData?querystring

25. III. TRANSITION TO THE NEW VERSION
THE TRANSITION
2 Data Query “ecosystems”:
V1 is still accessible from the DWS 2
V2 is accessible from the new workspace
Custom metrics and segments are the same on both apps
DQ v1 templates can be imported into DQ v2
Warning: once a template is imported in DQ v2, it will be closed in DQ v1.
The API v1 still continue to work

26. IV. QUESTIONS & ANSWERS

27. atcontact@atinternet.com
www.atinternet.com