# Assetario onboarding

#### Introduction

Onboarding with Assetario is straightforward, thanks to our SDK-free platform. There's no need for extended data preparation hours; our concise tutorial ensures you get optimal predictions with minimal effort. Meanwhile, you can continue with your routine tasks, reaping the benefits of our engine.

#### Support During Onboarding

Assetario values its customers. During the onboarding phase, we assign a dedicated customer success manager to you, ensuring you have a primary point of contact throughout.

#### Data Sharing Requirements

1. **Unique User Identifier**: Every event data piece shared with Assetario must contain one (and only one) unique user identifier column. If using `user_id` as the identifier, ensure it's consistently present in all data. This consistency is critical as Assetario joins data across multiple events.
2. **Timestamp Requirement**: All event data provided to Assetario must include a `timestamp` column.
3. **Data Preparation**: Ready your raw event data according to our [data requirements](/docs/integration/data-requirements.md). Remember, no extensive data engineering is necessary on your part.
4. **Regular Data Dumps**: Set up frequent data dumps, at least daily. Inform Assetario about the specific time of day when the data undergoes a refresh.
5. **Data Partitioning:**
   1. **For Google BigQuery**:
      1. Generate a distinct table for each event or shard your events table by event name.
      2. Partition every table based on the date or event timestamp.
      3. Refer to our integration guide on [Creating a BigQuery service account](/docs/integration/data-input-integration-guides/google-bigquery-access-share.md).
      4. Visit [console.cloud.google.com/billing](https://console.cloud.google.com/billing) to complete the setup.
   2. **For AWS S3**:
      1. Establish the file structure detailed below. We strongly advocate using the Parquet format when sharing data.
      2. Follow our integration guide on [Creating and sharing an AWS S3 Bucket](/docs/integration/data-input-integration-guides/aws-s3-bucket-access-share.md).

```lua
root
|- game_name  
| |- date (YYYY-MM-DD format) 
| | |- event_name 
| | | |- part_1.parquet
| | | |- part_2.parquet 
```

6. **Access Keys**: Share both your public and private access keys for data storage.
7. **Data Definition Table**: Complete the identifier names by the Data Definition Table provided in the Data Requirements section.
8. Choose the desired product and follow the respective setup guide:
   * For **PLTV**: Follow the [PLTV: Setup](/docs/integration/pltv-setup.md).
   * For **RecIAP**: Go to [IAP Personalization: Setup](/docs/integration/iap-personalization-setup.md).

#### Post-Onboarding

Once the onboarding process concludes, you will receive:

* Dashboard access credentials (username and password).
* An estimated timeline for full deployment.

#### Additional Support

Have questions? Don't hesitate to inquire. If you can't locate a suitable database, reach out to our team, and we'll furnish all the necessary details.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.assetario.com/docs/integration/assetario-onboarding.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.