Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Very simple! Before being able to export data, you have to define a Destination. It is the location the Export will arrive to.
We are regularly adding new Destinations, email is the default destination. But sending data goes through Analytics apps, Data Visualisation or Datamarts.
To add Destinations other than email, you must have the corresponding access rights. If you don’t have access to it, contact your administrator within your organization.
To add a destination, simply click on +Add in Export Destinations and choose the desired Destination in the list.
During the process of creating a destination, you will have to fill in a destination name. We advise you to give a precise name to each Destination you create, it will be easier later on.
To this day, the available Destinations are:
Nothing particularly difficult. Just type in the email adresses, separated by a comma in case of multiples email adresses.
See our dedicated Google Drive page.
See our dedicated FTP/SFTP page.
Adloop sends the export files into a Google Chat room. See our step by step explanation in our dedicated Google Chat page.
Adloop sends the export files into a Slack channel. See our step by step explanation in our dedicated Slack page.
Exports enables you to export sets of data (built in Reports ) in standart formats to applications outside Adloop. Those sets of data are automatically updated according to the chosen frequency #timesaver
Export Destinations
Details
Email adresses that the export file must be sent to (a single email adress is also possible)No authentification needed but be careful about the spaming
Sends the file into a file of your Google DriveAuthentification with Google credentials (see below)
Sends the file into a file of your FTP server (port 21)Authentification with login / password (see below)
Sends the file into a file of your SFTP server (port 22)Authentification with login / password (see below)
Adloop sends and updates the exports in a folder available on a FTP server (port 21) or sFTP (port 22).
The process and the fields to fill in are the same for FTP and sFTP. The only difference is that sFTP uses an encryption key to secure the data.
To allow Adloop to write in your FTP, you must connect it to Adloop with:
The server FTP address
Login and password
A folder name, if needed
The connection process is just filling in the form boxes.
Login and password (sent by a system admin)
Host : address of your FTP server
noteIt must look like this: ftp.company.com
It must look like this: ftp.company.com
21 is the FTP default port / 22 is the sFTP default port You can use another port, sent by your system admin
Destination Folder : indicate the folder in which the files will be dropped.
By clicking on Submit, your connection will be checked according to your parameters.
In case the connection fails, you will have an alert:
If the connection is OK, you just need to name this Destination and you are done!
Your FTP or sFTP destination will now appear in your destinations list.
Port : fill in the desired FTP port
Exports allow you to export datasets (built with Reports) into standard formats to applications outside of Adloop. Those datasets will update automatically according to the chosen frequency #timesaver
Adloop says to copying - pasting! Updating your Dashboards, Excels, Datamarts with marketing data must take 5 minutes per day, tops. Set up your exports and Adloop will send the data in time.
What will I be able to export?
You can export everything that is in your Dataset. All the normalized dimensions or the ones that are source-specific, all the standards or calculated metrics, EVERYTHING! We can’t do more than that .
What triggers the Exports?
They will be sent automatically depending on the frequency set-up once the data sources are updated.
Adloop is first getting fresh data from the Data Sources we are connected too, and then we send the exports. If some data couldn’t be updated, because the Data Source was unavailable, Adloop will nonetheless send the export. Then, we will do it again once the data have been updated.
@Timothée Leicht peux tu vérifier l’assertion ci-dessus ? How frequently?
You can choose how frequentLY the exports need to be sent: several times per day, daily, weekly etc.
Where do the Exports go?
Several Destinations are available, Exports can come under the form of CSV or Excel files, as well as data feeds to databases. Most of the time, our Exports are used to feed Dashboards built under Excel, Google Data Studio, Tableau… or Datamarts in AWS, Azure, Snowflake…
How do I select the data to put in my Export?
First, you have to build a Report containing all the data you want to send in your Export. A Date type column (day, week, month, year) will probably necessary in order for the external application to deal with the data.
Prerequisites - In order for the Exports to function, you need first to set-up:
One or several Data Sources \
A Report with the data to export \
One or several [[ Export Destinations |Export-Destinations]]
An Export needs several elements to function:
Go to the Exports page using the sidebar, you can create an Export by clicking on :Add:
![](.gitbook/Screenshot 33.png)
You can create an Export directly from the Report you are creating or editing by clicking on the button :more: ( More button) and by selecting the corresponding menu item.
Element
Details
Destination
The Destination is the application the Export will be send to. You must have created an [[ **Export Destination** |Export-Destinations]]
first.
Report
The Report with the data you want to export. > You have to create your Report and save it to find it the list of the Reports you can export. To find it easily, give it a distinct name.
Segmentation
By default, the data in the report are agregated on the selected timeframe. If you want to have a breakdown per day or per week, you have to segment your data. > Often, external applications will ask for segmented data (per day or per month).
Format
Adloop exporte les données dans des formats standards (Excel, CSV). Certaines destinations demandent des formats spécifiques qui sont gérés nativement par Adloop.
Frequency
How often you want Adloop to export your data
Name
The Export name is completely free, but we advise you to be precise. Indeed, if one day you have 15 active Exports, you will be happy you named them right in the beginning!
If you want to receive your exports to an email address (yours or someone else’s!), nothing simpler.
Just add the desired email destination in the Expot destination page, by clicking on the button.
Then, choose Email
You can write several addresses at once, just put a comma “,” between each address! And remember that if you choose this email export destination later, the export will be sent to all the email addresses in the destination .
Save your destination and you can already use it!
Write in the field the email address you want to use for the export.
Adloop sends and updates the exports with a file in a Google Drive Folder.
To enable Adloop to write in your Google Drive, you have to connect it to Adloop by using your usual ID.
The connection procedure is usual.
Si your Google account is also linked to Google Ads or Google Analytics, the authorization will be valid for all the Google applications, you will only have to give once the connection authorization.
Once the connection set, you can create a destination file or select an existing folder for the Adloop exports.
New folder creation:
Your Google Drive Destination will now appear in the destinations list.
Click on Google Drive > Select an account
Authorize Adloop to access your Google Drive account.
Existing folder selection:
Name this destination and you are done!
The Google Analytics export connector concerns what Google calls ' Cost Data ', i.e. the ability to import Impression, Clicks and Adspend metrics from the selected Data Sources in the Google Analytics Acquisition reports against the UTM dimensions.
Once the connector is in place, Adloop will send daily data from the previous day. To ensure quality data, Adloop will also send data from D-3 on a daily basis (this may change as we indicate in our [[quality policy|Data-Quality]]).
Only data from campaigns not managed by Google can be imported by this connector. Therefore, data from campaigns managed in Google Ads or Google Campaign Manager will not be imported.
Google Analytics identifies the acquisition sources thanks to the UTM parameters (Source, Medium, Campaign etc.). The Platforms Data Sources have another form of nomenclature with specific dimensions.
Matching consists in matching the dimensions of the Platforms Data Sources you want to import with the UTM values of Google Analytics . This way Google will know where to put the data.
For more information about Matching, see the [[dedicated section|Matching]].
To create a Dataset, follow the procedure below:
Admin > Data Import > Create
Select Cost Data then Continue
Give a name to the Dataset and select the Views it will impact (one or more)
Do not forget to select the Overwrite option. This is because Adloop sends data over several days to ensure that the indicators are completely reliable (see information on [[data quality|Data-Quality]]). If you leave the Summation option, the data will be added instead of replaced.
After validation the Google Analytics data set is created and you can copy its ID :
In the Export Destination, select the following connector:
Name of the Destination
Google Analytics account to send the data to
until you get to the screen where you are asked for the Data Set ID : (the ID retrieved from Google Analytics above)
Validate everything and that's it, your Destination is ready.
No difficulties in this process.
Step 2: Select the Data Sources you want to send to Google Analytics
This is where you need to make sure you have configured consistent matching rules for the Data Sources you want to send, otherwise you will get an error like this:
Step 3: Name your export
Indicate the Data that will be sent as shown in the screenshot below (in yellow, what must be added or selected) :
Follow the configuration process:
Step 1: Select the Destination you just created
For help with this Google Data Studio connector, please use the Adloop chatbot.
Creating a Google Data Studio Export Destination
In the connection process, Data Studio will ask you for 3 pieces of information from Adloop.
(1) The Auth Token can be found in your user profile in Adloop
(2) Workspace URL
This is the URL of the Workspace in which the Dataset you want to connect is located.
(3) Dataset ID
You can find it in the Dastasets page as a number: 1, 2, 3 ...
To start the connection, just click on :
This information can be pre-populated directly by Adloop but in some cases it is not present.
Profile Access
Adloop sends and updates the exports with a file in Google Sheets.
To enable Adloop to write in your Google Sheets, you have to connect it to Adloop by using your usual ID.
The connection procedure is usual.
![](.gitbook/Screenshot 2022-05-26 at 15.36.41.png)Click on Google Sheets > Select an account
![](.gitbook/Screenshot 2022-05-26 at 15.52.43.png)
Your Google account is also linked to Google Ads or Google Analytics, the authorization will be valid for all the Google applications, you will only have to give once the connection authorization.
![](.gitbook/Screenshot 2022-05-26 at 15.38.32.png)
Once the connection set, you can create a destination file or select an existing folder for the Adloop exports.
New folder creation:
![](.gitbook/Screenshot 2022-05-26 at 15.38.54.png) Existing folder selection:
![](.gitbook/Screenshot 2022-05-26 at 16.00.59.png)Name this destination and you are done!
Your Google Sheets Destination will now appear in the destinations list.