Assetario Documentation
  • Overview
    • Assetario Overview
    • Predicted Life-Time Value (pLTV)
    • In-App Purchase Personalization (IAP Recommendation)
  • Integration
    • Assetario onboarding
    • Data Requirements
    • Data input integration guides
      • DeltaDNA integration
      • Amplitude AWS integration
      • Google BigQuery access share
      • AWS S3 Bucket access share
      • Scheduling Queries in BigQuery
    • PLTV: Setup
    • IAP Personalization: Setup
      • Dynamic offer personalization
        • Offers definition table
        • API reference
      • Contextual price personalization
        • Price levels definition
        • API reference
      • A/B tests
      • Third Party Integrations
        • RevenueCat
  • FAQ
    • IAP Personalization FAQ
  • Dashboards
    • PLTV Dashboard
    • IAP Personalization Dashboard
  • Best practices
    • PLTV: Google Adwords
      • Offline conversions
    • PLTV: Facebook
      • Offline conversions
      • Value-Based Lookalikes
  • Data Security
  • Dictionary
Powered by GitBook
On this page
  1. Integration

Assetario onboarding

PreviousIn-App Purchase Personalization (IAP Recommendation)NextData Requirements

Last updated 1 year ago

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 . 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 .

      4. Visit 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 .

root
|- game_name  
| |- date (YYYY-MM-DD format) 
| | |- event_name 
| | | |- part_1.parquet
| | | |- part_2.parquet 
  1. Access Keys: Share both your public and private access keys for data storage.

  2. Data Definition Table: Complete the identifier names by the Data Definition Table provided in the Data Requirements section.

  3. Choose the desired product and follow the respective setup guide:

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.

For PLTV: Follow the .

For RecIAP: Go to .

data requirements
Creating a BigQuery service account
console.cloud.google.com/billing
Creating and sharing an AWS S3 Bucket
PLTV: Setup
IAP Personalization: Setup