> For the complete documentation index, see [llms.txt](https://docs.adlibertas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adlibertas.com/the-platform/direct-sql-access.md).

# Direct SQL Access

![](/files/NxjakjYaJRLNxiBlDFjo)

### How it works

With just your credentials, AdLibertas will collect data from all of your data sources, unify, and store the compressed data in a customer-specific AWS account. You can use[ <mark style="color:blue;">Amazon Athena</mark>](https://aws.amazon.com/athena/) to directly SQL-query your normalized data from here.

Since Athena is an easy to use serverless Amazon-managed service, teams can get directly access their data using standard SQL. And since AdLibertas is pulling and storing the data, there is no need for data engineering effort to get up and running.

### Getting Started

AdLibertas customers can contact their account representative to request access to Athena. You will be given:

A Sign-in URL: `https://example.signin.aws.amazon.com/console`

User name: `example_account`

One-time Password: `*******`

* A Sign-in URL: <https://example.signin.aws.amazon.com/console>
* User name: example\_account
* One-time Password: \*\*\*\*\*\*\*

{% hint style="info" %}
Note: Once you have access to the AWS Management Console you will have administrative access for the purposes of Amazon Athena access and while data can’t be deleted via Athena, account access does allow the ability to permanently alter datasets.
{% endhint %}

Once you have access to your account:&#x20;

1. [<mark style="color:blue;">Apply Payment Method</mark>](https://us-east-1.console.aws.amazon.com/billing/home?region=us-east-1#/paymentmethods)<mark style="color:blue;">.</mark>
2. [<mark style="color:blue;">Access Athena</mark>](https://us-west-2.console.aws.amazon.com/athena/home?region=us-west-2#/query-editor)<mark style="color:blue;">.</mark>
3. Change Region to `Us-West-2`
4. Change workgroup to your `example_account`
5. Change database to your `example_account`

### Popular Use-cases

#### Custom or granular access:&#x20;

While AdLibertas out-of-the box user-level reporting allows highly sophisticated reports to be constructed without the need for custom SQL, customers do have the need to create more complex queries that are out of scope from a UI. Most often, these customers will lean on writing their own queries to access the data. A popular use case is downloading the members of an [<mark style="color:blue;">AB test</mark>](https://docs.adlibertas.com/the-platform/user-level-audience-reporting/advanced-reporting-methods/reporting-on-a-firebase-ab-test), then running user-level event counts to gain more sophisticated insights into test-outcome [<mark style="color:blue;">probabilities</mark> ](https://docs.adlibertas.com/the-platform/user-level-audience-reporting/report-layout/statistics-module)and [<mark style="color:blue;">confidence</mark>](https://docs.adlibertas.com/the-platform/user-level-audience-reporting/report-layout/measuring-confidence), not already supported.

#### Targeting or CRM management

Since all [<mark style="color:blue;">audiences</mark> ](/the-platform/user-level-audience-reporting/creating-reports/advanced-audience-builder.md)are readily available for SQL export, customers can easily export user IDs for the purposes of targeting or CRM management. A great example would be running a report on your [<mark style="color:blue;">top-performing users</mark>](https://www.adlibertas.com/introducing-report-filters/), then giving them a special offer to incentivize retention or conversion.

&#x20;