Back

Tengence Data Center User Guide: API Push, MySQL, and Behavior Datasets

Tengence Team ·
API Integration Data Analytics User Data
Tengence Data Center User Guide: API Push, MySQL, and Behavior Datasets

This guide explains how to connect your business data to the Tengence Data Center: how to open the Data Center, create the three dataset types (API Push / MySQL / Behavior), and view and manage the datasets you have created.

1. Data Center Overview

The Data Center supports three data ingestion methods. Choose the dataset type that fits the source and shape of your data:

Dataset Type Best For Ingestion Method
API Push dataset Business data is complex and needs processing and formatting first Assemble the data, then push it to the dataset via API
MySQL dataset Data is stored in a single MySQL table Automatically synced from the MySQL data source
Behavior dataset You need to collect user behavior data on your pages Automatically reported after the behavior data SDK is integrated on the frontend

2. Opening the Data Center

  1. Log in to the Tengence console and find "Data Center" in the left navigation, then click to enter.

    The "Data Center" entry in the left navigation
    Figure 2-1 The "Data Center" entry in the left navigation

  2. You arrive at the Data Center overview page. The "Quick Create" area of the overview page provides entry points for creating the three dataset types.

    Data Center overview page with the "Quick Create" area
    Figure 2-2 Data Center overview page with the "Quick Create" area

3. Creating an API Push Dataset

When to use: your business data is complex and needs some processing and formatting first. We recommend assembling the data and then pushing it to the dataset via API.

💡 Tip: In most cases, prefer the API Push method.

Step 1: Create the dataset

  1. On the overview page, click "API Push" in the "Quick Create" area to open the dataset creation page.

    Click "API Push" in the "Quick Create" area
    Figure 3-1 Click "API Push" in the "Quick Create" area

  2. Set the name of the ID field. Every dataset must have an ID field; the default name is "id", and you can change it to fit your business.

  3. Click "Next", read the data push instructions, then click "Create" to finish creating the dataset.

    Read the data push instructions and finish creation
    Figure 3-2 Read the data push instructions and finish creation

Step 2: Open the dataset detail page

  1. The overview page provides a "Dataset List" entry. Click it to view all datasets.

    The "Dataset List" entry on the overview page
    Figure 3-3 The "Dataset List" entry on the overview page

  2. The list is sorted by creation time in descending order. Newly created datasets are named automatically by the system.

  3. Click a dataset name to open its detail page.

    The dataset list page
    Figure 3-4 The dataset list page

Step 3: "Basic Info" on the detail page

The dataset detail page mainly contains "Basic Info", "Field List", "Preview", and other areas. "Basic Info" provides the following functions:

# Function Description
1 Rename Click the edit button next to the dataset name to set the dataset name
2 Start Sync Begin receiving pushed data; if syncing has not started, the dataset rejects incoming data
3 Connection Settings View the data push address and the corresponding API Key
4 How to push data? Click to open the data push instructions on the right side of the page
5 Field Mapping View all fields of the dataset; right after creation there is only the ID field. Once data is pushed, the full field list appears based on the pushed data structure
6 Linked Applications See which applications use this dataset; the dataset cannot be deleted while the linked-application count is not 0

The "Basic Info" area of the dataset detail page
Figure 3-5 The "Basic Info" area of the dataset detail page

⚠️ Caution: The API Key is the credential for pushing data. Keep it safe and never disclose it.

Step 4: Start syncing and push data

After clicking "Start Sync" on the detail page, follow the data push instructions to push data to the dataset.

Push data following the instructions after starting sync
Figure 3-6 Push data following the instructions after starting sync

4. Creating a MySQL Dataset

When to use: your data is already prepared and stored in a single MySQL table. Create a MySQL dataset and the platform syncs the data automatically.

Step 1: Connect to the database

  1. On the overview page, click "MySql" in the "Quick Create" area to open the dataset creation page.

    Click "MySql" in the "Quick Create" area
    Figure 4-1 Click "MySql" in the "Quick Create" area

  2. Enter the database connection information and click "Test Connection". After the test passes, click "Next".

    Enter database connection info and run the connection test
    Figure 4-2 Enter database connection info and run the connection test

Step 2: Choose a sync mode

Three sync modes are supported: full snapshot, scheduled incremental, and real-time incremental:

Sync Mode Permission Required Time Field Needed Update Behavior Notes
Full snapshot SELECT permission only No Syncs once; no incremental data afterwards Not recommended for more than 100,000 rows: syncing takes longer and puts pressure on the data source
Scheduled incremental SELECT permission only Yes: you must specify a valid time field and set the sync interval Syncs on the schedule you set The time field must be a real, valid time type or timestamp; incorrect field contents cause data confusion
Real-time incremental Additional permissions required (syncs via binlog) No Real-time updates Syncing continuously occupies a database connection; assess the data source load before enabling it

Full snapshot mode
Figure 4-3 Full snapshot mode

Scheduled incremental mode
Figure 4-4 Scheduled incremental mode

Real-time incremental mode
Figure 4-5 Real-time incremental mode

Step 3: Set field mapping

After the permission test passes, click "Next" to enter the field mapping settings:

  1. Set the ID field: every dataset must have exactly one ID field, which uniquely identifies each record. The table's primary key is not necessarily the ID field — select the target field and click "Set as ID Field".

  2. Field name mapping: you can set dataset field names, mapping data source field names to dataset field names. By default they stay the same as the source field names.

  3. Field comments: you can edit the comments of dataset fields. By default they stay the same as the source field comments.

    Field mapping settings
    Figure 4-6 Field mapping settings

Step 4: Set filter conditions (optional)

Click "Next" to set filter conditions for the sync. These conditions are applied during syncing to ensure only valid data enters the dataset; if you do not need filtering, skip this step.

Sync filter condition settings
Figure 4-7 Sync filter condition settings

Step 5: Create and start sync

  1. Click "Create" to create the MySQL dataset with the configuration above.

  2. Return to the MySQL dataset detail page and click "Start Sync" in the "Basic Info" area to start dataset syncing.

    Click "Start Sync" on the detail page
    Figure 4-8 Click "Start Sync" on the detail page

5. Creating a Behavior Dataset

When to use: you need to collect user behavior data on your pages.

Step 1: Create the dataset

  1. On the overview page, click "Behavior Data" in the "Quick Create" area to open the dataset creation page.

    Click "Behavior Data" in the "Quick Create" area
    Figure 5-1 Click "Behavior Data" in the "Quick Create" area

  2. The behavior dataset is fed automatically by the behavior data SDK, and its data structure is determined by the SDK, so no manual field definition is needed — just click "Create".

Step 2: "Basic Info" on the detail page

Back on the behavior dataset detail page, the "Basic Info" area provides:

  1. Click "Start Sync" to start dataset syncing; only after syncing starts can the dataset receive data reported by the SDK.

  2. Click "How to integrate behavior data" and the integration instructions open on the right side of the page.

  3. In the "Connection Settings" area, you can view the behavior data push address and the corresponding Access Key.

    The "Basic Info" area of the behavior dataset detail page
    Figure 5-2 The "Basic Info" area of the behavior dataset detail page

Step 3: Start syncing and integrate behavior data

After dataset syncing starts, follow the integration instructions to integrate behavior data on the frontend. The SDK then pushes behavior data automatically.

Behavior data is reported automatically after SDK integration
Figure 5-3 Behavior data is reported automatically after SDK integration

6. Viewing and Managing Datasets

Field List and Semantic Tags

After data syncing starts, return to the "Field List" on the dataset detail page to view the full field list of the pushed data. To change field settings, click the "Edit Configuration" button.

The "Field List" and "Edit Configuration"
Figure 6-1 The "Field List" and "Edit Configuration"

You can set semantic tags and remarks for fields:

💡 Tip: Semantic tags help the system better understand your business data. We recommend setting them.

  1. You can first read the detailed explanation of semantic tags to understand what setting them means;

  2. Click "Add Semantic Tag" to set a semantic tag for a field;

  3. You can choose a suitable tag from the tag types supported by the system by default;

  4. You can also leave them unset for now, and come back to set them later when a feature that depends on semantic tags requires it.

    Add a semantic tag to a field
    Figure 6-2 Add a semantic tag to a field

Previewing Data

In the "Preview" area of the dataset detail page, you can inspect the pushed data:

  1. Click "Preview" and the system samples a batch of data by default, giving you a basic sense of the dataset's contents;

  2. Click "Resample" to sample a new batch of data;

  3. Click "View Details" to inspect the contents of a single record.

    Sampled data viewing in the "Preview" area
    Figure 6-3 Sampled data viewing in the "Preview" area


Appendix: Glossary

Term Description
ID field The field that uniquely identifies each record in a dataset; every dataset must have exactly one
Semantic tag A tag describing a field's business meaning, helping the system better understand your business data
Full sync / incremental sync Full sync copies all existing data at once and no incremental data afterwards; incremental sync only syncs new or changed data, either on a scheduled interval (scheduled incremental) or via binlog (real-time incremental)
binlog The binary log of MySQL, which records data changes; real-time incremental sync is based on the binlog and does not depend on a time field
← Previous: Tengence Search API Reference Next: Tengence Search User Guide: Add Search to a Business System in Four Steps →
Consult
QR code

WeCom