Gravity Field
English
English
  • Implementation
    • Gravity Field Implementation Types
    • Client-Side Implementation
      • 1. Gravity Field Script
        • Gravity Field Scripts Workflow
      • 2. Page Context
      • 3. Events
      • 4. Feed - General Requirements and Additional Parameters
        • Fashion
        • Electronics
        • Telecom
        • Banking and Fintech
        • eGroceries
        • Pets Supplies
        • DIY
      • 5. Cookies cloning with front-end implementation
      • Implementation on SPA-enabled sites
      • Multilingual / Multilocal Implementation
    • Server-Side API
    • Server-Side Hybrid API
    • Implementation Workflow
    • Passing User Data to Gravity Field
    • Client-side APIs
    • Obtaining "slid" from the browser console
    • Full Data Loader — Offline / Historical Purchases Onboarding
    • Full Data Loader — User Data Onboarding
    • Full Data Loader — Audience Export
  • GENERAL INFORMATION
    • Affinity Profile and How It Works
    • How to use regular expressions (RegEx)
    • Traffic Sources Identification
    • Targeting conditions definition and their applicability
    • Comparison of Targeting Conditions in Audiences, Front-end, and API Campaigns
    • Evaluators
    • Social Proof
    • What are Data Attributes
    • Technological Stack of Gravity Field
  • Platform Interface
    • Audience List View
    • Audience Creation Screen
    • Audience Targeting Conditions
    • Campaigns structure
    • Campaigns List Screen
    • Frontend campaigns creation
    • API Campaigns List Screen
    • API campaigns creation
    • Working with Templates
    • Working with Variables in Variations
    • API logs
    • Evaluators List View
    • Evaluator Creation Flow
    • Strategy List Screen
    • Recommendation Strategies Creation
    • Recommendation Strategies
    • User Management for GF Admins
    • Campaign Activity-logs
    • Dynamic Allocation
  • Running and QAing Campaigns
    • Disabling GF script
    • Campaign naming
  • Analytics
    • Personalization Campaigns Report
    • Outliers
    • Statistical Significance
    • A/B testing Approaches and Framework
    • A/A testing
    • Purchase data export
    • Campaings and Users Raw data Export
    • Approach to PoC Analysis
Powered by GitBook
On this page
  • Data Onboarding Goals and Objectives
  • Onboarding Options
  • Business Process
  • Update Frequency
  • Technical Requirements
  • General Requirements
  • CSV File Requirements
  • Sample CSV File

Was this helpful?

  1. Implementation

Full Data Loader — User Data Onboarding

Created: 27.07.2023

Updated: 27.07.2023

Author: Alexander Pushkin

To onboard data, please contact the team working on your project.

Data Onboarding Goals and Objectives

Onboarding user data allows for the improvement of segmentation in the personalization platform. You can onboard the information available in CRM and/or DMP. For example: RFM segmentation or segmentation based on loyalty program data. The onboarded data will be accessible in the audience creation screen of the Gravity Field platform, allowing you to create audiences by combining onboarded data with behavioral data already collected by the platform.

Additionally, some values from the onboarded data can be used directly in the personalization platform. For instance, you can onboard a user's pet's name into the platform and use it as a variable in personalization campaigns.

Onboarding personal user data into the platform is not allowed.

Onboarding Options

User data can be onboarded into the Gravity Field personalization platform by uploading a CSV file to a dedicated secure folder on our server.

Business Process

Before onboarding data, please provide a sample of the data (up to 1000 rows) for validation. Based on the sample, we will prepare a data schema according to which future uploads will need to be performed. Columns that should be available for use in campaigns (all existing columns are automatically available for use when building audiences) should be specified.

After the schema is approved on both ends, we will provide access to the folder where data files should be uploaded.

Update Frequency

When uploading a CSV, synchronization is initiated by uploading the file, but it may take some time (up to an hour) depending on the file size. You can determine the frequency of data uploads yourself (it is recommended to upload data once a day at night).

Technical Requirements

General Requirements

  • Use UTF-8 encoding.

  • The first column should contain the user identifier (the same one that is used in identification events on the website/app).

  • Transmission of personal user data that allows you to identify a specific user is not allowed (e.g., you can transmit the user's first name without the last name and age, but you cannot transmit phone numbers or email addresses).

  • A decimal separator is a period.

  • The following formats can be used in the data:

    • String

    • Date (in the dateTtime+offset format, following ISO 8601)

    • Array

  • The separator for array elements is a pipe (|), and this symbol should not appear anywhere else in the file, except within arrays.

CSV File Requirements

  • The file format is CSV, comma separated.

  • CSV upload does not allow incremental updates. Each uploaded file must contain a complete set of data.

  • The filename should end with customer_data.csv.

Sample CSV File

PreviousFull Data Loader — Offline / Historical Purchases OnboardingNextFull Data Loader — Audience Export

Last updated 1 year ago

Was this helpful?

1011B
user_data_example_customer_data.csv