- Introduction
-
Getting Started
- Creating an Account in Hevo
- Subscribing to Hevo via AWS Marketplace
- Subscribing to Hevo via Snowflake Marketplace
- Connection Options
- Familiarizing with the UI
- Creating your First Pipeline
- Data Loss Prevention and Recovery
- Upgrading Pipeline from Standard to Edge
-
Data Ingestion
- Types of Data Synchronization
- Ingestion Modes and Query Modes for Database Sources
- Ingestion and Loading Frequency
- Data Ingestion Statuses
- Deferred Data Ingestion
- Handling of Primary Keys
- Handling of Updates
- Handling of Deletes
- Hevo-generated Metadata
- Best Practices to Avoid Reaching Source API Rate Limits
-
Edge
- Data Ingestion
- Core Concepts
-
Pipelines
- Familiarizing with the Pipelines UI
- Creating an Edge Pipeline
- Working with Edge Pipelines
- Pipeline Job History
- Pipeline Overview
- Needs Attention
- Object and Schema Management
- Activity Log
-
Sources
- Connect AI
- PostgreSQL
- Oracle
- MySQL
- SQL Server
- CockroachDB
- MongoDB
- Troubleshooting Database Sources
- Salesforce Bulk API V2
- Ordergroove
- BambooHR
- Stripe
- NetSuite SuiteAnalytics
- Shopify
- Slack
- ClickUp
- Monday.com
- Pipedrive
- Workable
- Fathom
- HubSpot
- Salesforce Marketing Cloud
- Google Analytics 4
- Google Ads
- Facebook Ads
- Microsoft Ads
- LinkedIn Ads
- Xero
- Instagram Business
- Amazon Selling Partner
- TikTok Ads
- StackAdapt
- Amazon Ads
- Pinterest Organic
- Zendesk Support
- Snapchat Ads
- TikTok Organic
- Google Search Console
- Klaviyo v2
- Braintree Payments
- Facebook Pages
- Tempo
- PayPal
- Auth0
- Pinterest Ads
- Apple Search Ads
- Permit.io
- Amplitude Analytics
- Customer.io
- Paddle
- Jira Cloud
- GitHub
- WorkOS
- ActiveCampaign
- Campaign Monitor
- Mailgun Send
- Metaplane
- Recharge
- sevdesk
- Statuspage
- Teamwork.com
- Workday RaaS
- Yotpo
- TikTok Shop Partner Center
- Naming Conventions for Source Data Entities
- Destinations
- Transformations
- Alerts
- Activate
- Custom Connectors
-
Releases
- Edge Release Notes - October 2026
- Edge Release Notes - September 2026
- Edge Release Notes - August 2026
- Edge Release Notes - July 2026
- Edge Release Notes - June 2026
- Edge Release Notes - May 2026
- Edge Release Notes - April 2026
- Edge Release Notes - March 2026
- Edge Release Notes - February 2026
- Edge Release Notes - January 2026
- Edge Release Notes - December 2025
- Edge Release Notes - November 2025
- Edge Release Notes - October 2025
- Edge Release Notes - September 2025
- Edge Release Notes - August 2025
- Edge Release Notes - July 2025
- Edge Release Notes - November 2024
-
Data Loading
- Loading Data in a Database Destination
- Loading Data to a Data Warehouse
- Optimizing Data Loading for a Destination Warehouse
- Deduplicating Data in a Data Warehouse Destination
- Manually Triggering the Loading of Events
- Scheduling Data Load for a Destination
- Loading Events in Batches
- Data Loading Statuses
- Data Spike Alerts
- Name Sanitization
- Table and Column Name Compression
- Parsing Nested JSON Fields in Events
-
Pipelines
- Data Flow in a Pipeline
- Familiarizing with the Pipelines UI
- Working with Pipelines
- Managing Objects in Pipelines
- Pipeline Jobs
-
Transformations
-
Python Code-Based Transformations
- Supported Python Modules and Functions
-
Transformation Methods in the Event Class
- Create an Event
- Retrieve the Event Name
- Rename an Event
- Retrieve the Properties of an Event
- Modify the Properties for an Event
- Fetch the Primary Keys of an Event
- Modify the Primary Keys of an Event
- Fetch the Data Type of a Field
- Check if the Field is a String
- Check if the Field is a Number
- Check if the Field is Boolean
- Check if the Field is a Date
- Check if the Field is a Time Value
- Check if the Field is a Timestamp
-
TimeUtils
- Convert Date String to Required Format
- Convert Date to Required Format
- Convert Datetime String to Required Format
- Convert Epoch Time to a Date
- Convert Epoch Time to a Datetime
- Convert Epoch to Required Format
- Convert Epoch to a Time
- Get Time Difference
- Parse Date String to Date
- Parse Date String to Datetime Format
- Parse Date String to Time
- Utils
- Examples of Python Code-based Transformations
-
Drag and Drop Transformations
- Special Keywords
-
Transformation Blocks and Properties
- Add a Field
- Change Datetime Field Values
- Change Field Values
- Drop Events
- Drop Fields
- Find & Replace
- Flatten JSON
- Format Date to String
- Format Number to String
- Hash Fields
- If-Else
- Mask Fields
- Modify Text Casing
- Parse Date from String
- Parse JSON from String
- Parse Number from String
- Rename Events
- Rename Fields
- Round-off Decimal Fields
- Split Fields
- Examples of Drag and Drop Transformations
- Effect of Transformations on the Destination Table Structure
- Transformation Reference
- Transformation FAQs
-
Python Code-Based Transformations
-
Schema Mapper
- Using Schema Mapper
- Mapping Statuses
- Auto Mapping Event Types
- Manually Mapping Event Types
- Modifying Schema Mapping for Event Types
- Schema Mapper Actions
- Fixing Unmapped Fields
- Resolving Incompatible Schema Mappings
- Resizing String Columns in the Destination
- Changing the Data Type of a Destination Table Column
- Schema Mapper Compatibility Table
- Limits on the Number of Destination Columns
- File Log
- Troubleshooting Failed Events in a Pipeline
- Mismatch in Events Count in Source and Destination
- Audit Tables
- Activity Log
-
Pipeline FAQs
- Can multiple Sources connect to one Destination?
- What happens if I re-create a deleted Pipeline?
- Why is there a delay in my Pipeline?
- Can I change the Destination post-Pipeline creation?
- Why is my billable Events high with Delta Timestamp mode?
- Can I drop multiple Destination tables in a Pipeline at once?
- How does Run Now affect scheduled ingestion frequency?
- Will pausing some objects increase the ingestion speed?
- Can I see the historical load progress?
- Why is my Historical Load Progress still at 0%?
- Why is historical data not getting ingested?
- How do I set a field as a primary key?
- How do I ensure that records are loaded only once?
- Why can't I see my Pipelines after logging in?
- Events Usage
-
Sources
- Free Sources
-
Databases and File Systems
- Data Warehouses
-
Databases
- Connecting to a Local Database
- Amazon DocumentDB
- Amazon DynamoDB
- Elasticsearch
-
MongoDB
- Generic MongoDB
- MongoDB Atlas
- Support for Multiple Data Types for the _id Field
- Example - Merge Collections Feature
-
Troubleshooting MongoDB
-
Errors During Pipeline Creation
- Error 1001 - Incorrect credentials
- Error 1005 - Connection timeout
- Error 1006 - Invalid database hostname
- Error 1007 - SSH connection failed
- Error 1008 - Database unreachable
- Error 1011 - Insufficient access
- Error 1028 - Primary/Master host needed for OpLog
- Error 1029 - Version not supported for Change Streams
- SSL 1009 - SSL Connection Failure
- Troubleshooting MongoDB Change Streams Connection
- Troubleshooting MongoDB OpLog Connection
-
Errors During Pipeline Creation
- SQL Server
-
MySQL
- Amazon Aurora MySQL
- Amazon RDS MySQL
- Azure MySQL
- Generic MySQL
- Google Cloud MySQL
- MariaDB MySQL
-
Troubleshooting MySQL
-
Errors During Pipeline Creation
- Error 1003 - Connection to host failed
- Error 1006 - Connection to host failed
- Error 1007 - SSH connection failed
- Error 1011 - Access denied
- Error 1012 - Replication access denied
- Error 1017 - Connection to host failed
- Error 1026 - Failed to connect to database
- Error 1027 - Unsupported BinLog format
- Failed to determine binlog filename/position
- Schema 'xyz' is not tracked via bin logs
- Errors Post-Pipeline Creation
-
Errors During Pipeline Creation
- MySQL FAQs
- Oracle
-
PostgreSQL
- Amazon Aurora PostgreSQL
- Amazon RDS PostgreSQL
- Azure PostgreSQL
- Generic PostgreSQL
- Google Cloud PostgreSQL
- Heroku PostgreSQL
- Upgrading Pipelines with PostgreSQL Sources to Use the pgoutput Plugin
-
Troubleshooting PostgreSQL
-
Errors during Pipeline creation
- Error 1003 - Authentication failure
- Error 1006 - Connection settings errors
- Error 1011 - Access role issue for logical replication
- Error 1012 - Access role issue for logical replication
- Error 1014 - Database does not exist
- Error 1017 - Connection settings errors
- Error 1023 - No pg_hba.conf entry
- Error 1024 - Number of requested standby connections
- Errors Post-Pipeline Creation
-
Errors during Pipeline creation
-
PostgreSQL FAQs
- Can I track updates to existing records in PostgreSQL?
- How can I migrate a Pipeline created with one PostgreSQL Source variant to another variant?
- How can I prevent data loss when migrating or upgrading my PostgreSQL database?
- Why do FLOAT4 and FLOAT8 values in PostgreSQL show additional decimal places when loaded to BigQuery?
- Why is data not being ingested from PostgreSQL Source objects?
- Troubleshooting Database Sources
- Database Source FAQs
- File Storage
- Engineering Analytics
- Finance & Accounting Analytics
-
Marketing Analytics
- ActiveCampaign
- AdRoll
- Amazon Ads
- Apple Search Ads
- AppsFlyer
- CleverTap
- Criteo
- Drip
- Facebook Ads
- Facebook Page Insights
- Firebase Analytics
- Freshsales
- Google Ads
- Google Analytics 4
- Google Analytics 360
- Google Play Console
- Google Search Console
- HubSpot
- Instagram Business
- Klaviyo v2
- Lemlist
- LinkedIn Ads
- Mailchimp
- Mailshake
- Marketo
- Microsoft Ads
- Onfleet
- Outbrain
- Pardot
- Pinterest Ads
- Pipedrive
- Recharge
- Segment
- SendGrid Webhook
- SendGrid
- Salesforce Marketing Cloud
- Snapchat Ads
- SurveyMonkey
- Taboola
- TikTok Ads
- Twitter Ads
- Typeform
- YouTube Analytics
- Product Analytics
- Sales & Support Analytics
- Source FAQs
-
Destinations
- Familiarizing with the Destinations UI
- Cloud Storage-Based
- Databases
-
Data Warehouses
- Amazon Redshift
- Amazon Redshift Serverless
- Azure Synapse Analytics
- Databricks
-
Google BigQuery
- Clustering in BigQuery
- Partitioning in BigQuery
- Structure of Data in the Google BigQuery Data Warehouse
- Loading Data to a Google BigQuery Data Warehouse
- Near Real-time Data Loading using Streaming
- Modifying BigQuery Destinations to Use Service Account Authentication
- Troubleshooting Google BigQuery
- Google BigQuery FAQs
- Hevo Managed Google BigQuery
- Snowflake
- Troubleshooting Data Warehouse Destinations
-
Destination FAQs
- Can I change the primary key in my Destination table?
- Can I change the Destination table name after creating the Pipeline?
- How can I change or delete the Destination table prefix?
- Why does my Destination have deleted Source records?
- How do I filter deleted Events from the Destination?
- Does a data load regenerate deleted Hevo metadata columns?
- How do I filter out specific fields before loading data?
- Transform
- Alerts
- Account Management
- Activate
- Glossary
-
Releases- 2026 Releases
-
2025 Releases
- Release 2.44 (Dec 01, 2025-Jan 12, 2026)
- Release 2.43 (Nov 03-Dec 01, 2025)
- Release 2.42 (Oct 06-Nov 03, 2025)
- Release 2.41 (Sep 08-Oct 06, 2025)
- Release 2.40 (Aug 11-Sep 08, 2025)
- Release 2.39 (Jul 07-Aug 11, 2025)
- Release 2.38 (Jun 09-Jul 07, 2025)
- Release 2.37 (May 12-Jun 09, 2025)
- Release 2.36 (Apr 14-May 12, 2025)
- Release 2.35 (Mar 17-Apr 14, 2025)
- Release 2.34 (Feb 17-Mar 17, 2025)
- Release 2.33 (Jan 20-Feb 17, 2025)
-
2024 Releases
- Release 2.32 (Dec 16 2024-Jan 20, 2025)
- Release 2.31 (Nov 18-Dec 16, 2024)
- Release 2.30 (Oct 21-Nov 18, 2024)
- Release 2.29 (Sep 30-Oct 22, 2024)
- Release 2.28 (Sep 02-30, 2024)
- Release 2.27 (Aug 05-Sep 02, 2024)
- Release 2.26 (Jul 08-Aug 05, 2024)
- Release 2.25 (Jun 10-Jul 08, 2024)
- Release 2.24 (May 06-Jun 10, 2024)
- Release 2.23 (Apr 08-May 06, 2024)
- Release 2.22 (Mar 11-Apr 08, 2024)
- Release 2.21 (Feb 12-Mar 11, 2024)
- Release 2.20 (Jan 15-Feb 12, 2024)
-
2023 Releases
- Release 2.19 (Dec 04, 2023-Jan 15, 2024)
- Release Version 2.18
- Release Version 2.17
- Release Version 2.16 (with breaking changes)
- Release Version 2.15 (with breaking changes)
- Release Version 2.14
- Release Version 2.13
- Release Version 2.12
- Release Version 2.11
- Release Version 2.10
- Release Version 2.09
- Release Version 2.08
- Release Version 2.07
- Release Version 2.06
-
2022 Releases
- Release Version 2.05
- Release Version 2.04
- Release Version 2.03
- Release Version 2.02
- Release Version 2.01
- Release Version 2.00
- Release Version 1.99
- Release Version 1.98
- Release Version 1.97
- Release Version 1.96
- Release Version 1.95
- Release Version 1.93 & 1.94
- Release Version 1.92
- Release Version 1.91
- Release Version 1.90
- Release Version 1.89
- Release Version 1.88
- Release Version 1.87
- Release Version 1.86
- Release Version 1.84 & 1.85
- Release Version 1.83
- Release Version 1.82
- Release Version 1.81
- Release Version 1.80 (Jan-24-2022)
- Release Version 1.79 (Jan-03-2022)
-
2021 Releases
- Release Version 1.78 (Dec-20-2021)
- Release Version 1.77 (Dec-06-2021)
- Release Version 1.76 (Nov-22-2021)
- Release Version 1.75 (Nov-09-2021)
- Release Version 1.74 (Oct-25-2021)
- Release Version 1.73 (Oct-04-2021)
- Release Version 1.72 (Sep-20-2021)
- Release Version 1.71 (Sep-09-2021)
- Release Version 1.70 (Aug-23-2021)
- Release Version 1.69 (Aug-09-2021)
- Release Version 1.68 (Jul-26-2021)
- Release Version 1.67 (Jul-12-2021)
- Release Version 1.66 (Jun-28-2021)
- Release Version 1.65 (Jun-14-2021)
- Release Version 1.64 (Jun-01-2021)
- Release Version 1.63 (May-19-2021)
- Release Version 1.62 (May-05-2021)
- Release Version 1.61 (Apr-20-2021)
- Release Version 1.60 (Apr-06-2021)
- Release Version 1.59 (Mar-23-2021)
- Release Version 1.58 (Mar-09-2021)
- Release Version 1.57 (Feb-22-2021)
- Release Version 1.56 (Feb-09-2021)
- Release Version 1.55 (Jan-25-2021)
- Release Version 1.54 (Jan-12-2021)
-
2020 Releases
- Release Version 1.53 (Dec-22-2020)
- Release Version 1.52 (Dec-03-2020)
- Release Version 1.51 (Nov-10-2020)
- Release Version 1.50 (Oct-19-2020)
- Release Version 1.49 (Sep-28-2020)
- Release Version 1.48 (Sep-01-2020)
- Release Version 1.47 (Aug-06-2020)
- Release Version 1.46 (Jul-21-2020)
- Release Version 1.45 (Jul-02-2020)
- Release Version 1.44 (Jun-11-2020)
- Release Version 1.43 (May-15-2020)
- Release Version 1.42 (Apr-30-2020)
- Release Version 1.41 (Apr-2020)
- Release Version 1.40 (Mar-2020)
- Release Version 1.39 (Feb-2020)
- Release Version 1.38 (Jan-2020)
- Early Access New
TikTok Shop Partner Center (Edge)
On This Page
- Supported Features
- Prerequisites
- Register as a Seller Developer
- Create a Custom App in Partner Center
- Obtain the App Key, App Secret, and Authorization URL
- Configure TikTok Shop Partner Center as a Source in your Pipeline
- Data Replication
- Schema and Primary Keys
- Data Model
- Handling of Deletes
- Source Considerations
- Limitations
- Revision History
TikTok Shop is a social commerce platform that lets sellers sell products directly on TikTok through videos, LIVE sessions, and the shop tab. TikTok Shop Partner Center is the developer platform of TikTok Shop, where sellers create apps that access their shop data through the TikTok Shop APIs.
Hevo uses the TikTok Shop APIs to replicate the order, return, cancellation, promotion, finance, and analytics data of your shop to the Destination of your choice. To connect, you create your own app in Partner Center, provide Hevo with the App Key, App Secret, and Authorization URL of the app, and then authorize Hevo to access your shop.
Supported Features
| Feature Name | Supported |
|---|---|
| Capture deletes | Yes (for some objects) |
| History mode | No |
| Custom data (user-configured tables & fields) | No |
| Data blocking (skip objects and fields) | Yes |
| Resync (objects and Pipelines) | Yes |
| API configurable | No |
Prerequisites
-
An active TikTok Shop seller account from which data is to be ingested. The account must have passed the KYB or KYC verification of TikTok Shop and have an assigned account manager, to register as a seller developer.
-
A Custom app in TikTok Shop Partner Center, with the API scopes required by Hevo enabled.
-
The App Key, App Secret, and Authorization URL of the app are available.
-
You can log in to the main account of the TikTok Shop seller, to authorize Hevo to access your shop. Sub-accounts cannot authorize apps.
Register as a Seller Developer
To create an app, you must register in TikTok Shop Partner Center as a seller developer, with your TikTok Shop seller account. A seller developer can create apps that access only the data of their own shop. If your shop is a US local shop with a US business license, use the US Partner Center. For all other shops, use the Partner Center.
To register, follow the steps in Seller Developer Onboarding. If you are already registered, skip to Create a Custom App in Partner Center.
Create a Custom App in Partner Center
Hevo connects to your shop through an app that you create in TikTok Shop Partner Center. To create the app, follow the steps in Create your App. While you create the app, make sure that:
-
The app type is Custom, and the service category is TikTok Shop Seller.
-
Enable API is turned on, and the Redirect URL is set to https://westeros.hevodata.com/edge/oauth/callback. This URL is the same for all Hevo regions.
-
The API scopes required by Hevo are enabled for the app. Read Access scope for the steps to manage the scopes of your app.
-
The app is published. Sellers can authorize a Custom app only after it is published, as publishing generates its authorization link. Before you can publish the app, it must complete the reviews that Partner Center requires. Read Publish a custom App and App launch overview.
Scopes Required by Hevo
Your Custom app must be granted the scopes that allow Hevo to read data from your shop. Hevo requires the following types of scopes:
-
Mandatory scopes: Allow Hevo to establish a connection with your shop.
-
Optional scopes: Allow Hevo to ingest data from the corresponding objects in your shop.
Mandatory Scopes
Your app must be granted the following scope for Hevo to connect to your shop. If this scope is not granted, the connection test fails when you click Test & Continue while configuring your Source.
| Scope Name | Scope Key |
|---|---|
| Shop Authorized Information | seller.authorization.info |
Optional Scopes
Grant the following scopes based on the objects for which you want Hevo to ingest data. If a scope is not granted, Hevo does not ingest data for the objects associated with it, and marks those objects as Inaccessible on the Configure Objects page.
If your app already has the FS Order&Fulfillment Management scope, Hevo uses it in place of Order Information. Similarly, Hevo uses the Customer Service scope in place of Promotion Information.
| Scope Name | Scope Key | Objects |
|---|---|---|
| Order Information | seller.order.info | orders and external_order |
| Read External Order References | seller.order.ext_ref.read | external_order |
| Promotion Information | seller.promotion.info | coupon |
| Return & Refund Basic | seller.return_refund.basic | return and cancellation |
| Finance Information | seller.finance.info | statement, transactions_by_statement, transactions_by_order_sku_transaction, and payment |
| TikTok Shop Analytics | data.shop_analytics.public.read | shop_product_performance, shop_video_performance, shop_sku_performance_interval, shop_video_performance_detail_interval, and shop_live_performance |
Obtain the App Key, App Secret, and Authorization URL
To configure the Source in Hevo, you need the App key, App secret, and authorization link of your app. You can find these on the details page of your app in Partner Center. Read Authorization overview.
The authorization link contains the service ID of your app. For example, https://services.tiktokshop.com/open/authorize?service_id=<your service id>. For US shops, the link starts with https://services.us.tiktokshop.com. Save these values securely.
Configure TikTok Shop Partner Center as a Source in your Pipeline
Perform the following steps to configure your TikTok Shop Partner Center Source:
-
Click Pipelines in the Navigation Bar.
-
Click + Create Pipeline in the Pipelines List View.
-
On the Select Source Type page, select TikTok Shop Partner Center.
-
On the Select Destination Type page, select the type of Destination you want to use.
-
In the Configure Source screen, specify the following:

-
Source Name: A unique name for your Source, not exceeding 255 characters. For example, TikTok Shop Partner Center Source.
-
In the Connect to your TikTok Shop account section, specify the following:
-
App Key: The App key that you obtained from your app in Partner Center.
-
App Secret: The App secret of your app.
-
Authorization URL: The authorization link of your app. For example, https://services.tiktokshop.com/open/authorize?service_id=<your service id>.
-
Click Authorize Your TikTok Shop Account, log in with the main account of your TikTok Shop seller, and authorize the app to access your shop. The button is available once you specify the App Key, App Secret, and Authorization URL.
-
-
In the Select your shop section, which appears after you authorize your account, specify the following:
- Shop: The shop from which you want to ingest data. The list contains the shops that you authorized the app to access. If you authorized only one shop, you can leave this field blank. If you authorized more than one shop, you must select one.
-
(Optional) In the External orders (optional) section, specify the following:
- External order platforms: The systems from which the external order references of your orders were added, such as Shopify or ERP System. You can select one or more platforms. You must select at least one platform to ingest data for the external_order object.
-
-
Click Test & Continue to test the connection to your TikTok Shop Partner Center Source. Once the test is successful, you can proceed to set up your Destination.
Test & Continue
When you click this button, Hevo performs the following validations:
-
The App Key and App Secret are specified, and you authorized your TikTok Shop account.
-
The Shop Authorized Information scope is granted to the app.
-
Hevo can retrieve the list of shops that you authorized, and the authorization includes at least one shop.
-
The shop that you selected is still accessible. If you did not select a shop, the authorization includes only one shop.
Data Replication
Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. To select a child object, you must also select its parent object.
Hevo ingests the following types of data from your Source objects:
-
Historical Data: The first run of the Pipeline ingests all the historical data of the selected objects that is available through the API. For the analytics objects, such as shop_product_performance, Hevo ingests the data from January 1, 2021.
-
Incremental Data: Once the historical load is complete, Hevo ingests new and updated data as per the sync frequency:
-
orders, return, and cancellation: Hevo ingests the records created or updated since the previous run.
-
statement, transactions_by_statement, transactions_by_order_sku_transaction, and payment: Hevo ingests the data since the previous run, and also re-ingests the data of the last 2 days in each run and the last 7 days once a day, to capture late changes.
-
shop_product_performance, shop_video_performance, shop_sku_performance_interval, and shop_live_performance: Hevo re-ingests the data of the last 3 days in each run, and the last 7 days once a day, as TikTok Shop may update recent metrics.
-
external_order: Hevo ingests the external order references of the orders created or updated since the previous run.
-
coupon and shop_video_performance_detail_interval: Hevo ingests the entire data in each run.
-
Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.
Schema and Primary Keys
Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.
The primary key of most objects is id. The following objects use other primary keys:
-
shop_product_performance and shop_video_performance:
id,start_date, andend_date. -
shop_sku_performance_interval and shop_video_performance_detail_interval: The ID of the SKU or video,
index,start_date, andend_date. -
transactions_by_order_sku_transaction:
order_idandindex. -
external_order:
idandorders_id.
Data Model
The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:
| Object | Description |
|---|---|
| orders | Contains the orders placed in your shop, including the buyer, recipient, delivery, payment, and fulfillment details. It includes the following child objects: - orders_package - orders_line_item - orders_line_item_tax - orders_line_item_sub_item_info |
| external_order | Contains the references that link the orders in your shop to the orders in an external system, such as an order management system. |
| coupon | Contains the coupons created for your shop, along with their configuration and status. It includes the following child objects: - coupon_display_channel - coupon_live_task - coupon_product_id |
| return | Contains the return requests raised for the orders in your shop. It includes the following child objects: - return_line_item - return_sub_line_item - return_discount_amount - return_shipping_fee_amount - return_next_action |
| cancellation | Contains the cancellation requests raised for the orders in your shop. It includes the following child objects: - cancellation_line_item - cancellation_sub_line_item - cancellation_next_action |
| statement | Contains the settlement statements generated for your shop. |
| transactions_by_statement | Contains the statements for which transactions are retrieved. It includes a child object, transactions_by_statement_transaction, which contains the transactions of each statement. |
| transactions_by_order_sku_transaction | Contains the transactions of your shop at the order and SKU level. |
| payment | Contains the automated payments made to the bank account of your shop. |
| shop_product_performance | Contains the daily performance metrics of the products in your shop. |
| shop_sku_performance_interval | Contains the performance metrics of the SKUs in your shop for each time interval. It includes the following child objects: - shop_sku_performance_interval_gmv_breakdown - shop_sku_performance_interval_items_sold_breakdown |
| shop_video_performance | Contains the daily performance metrics of the videos that promote your shop. It includes a child object, shop_video_performance_product, which contains the products linked to each video. |
| shop_video_performance_detail_interval | Contains the detailed performance metrics of each video for each time interval. It includes the following child objects: - shop_video_performance_detail_interval_sales_breakdown - shop_video_performance_detail_viewer_profile |
| shop_live_performance | Contains the daily performance metrics of the LIVE sessions of your shop. |
Additional Information
Read the detailed Hevo documentation for the following related topics:
Handling of Deletes
For the coupon and shop_video_performance_detail_interval objects and their child objects, Hevo uses a full data refresh approach to capture delete actions. If a record exists in the Destination but is no longer returned by the Source, the record is marked as deleted by setting the value of the metadata column __hevo__marked_deleted to True.
For all the other objects, Hevo does not capture deletes. For example, a cancelled order remains in the Destination with its updated status.
Source Considerations
-
Each Pipeline ingests data from one shop. To ingest data from multiple shops, create a Pipeline for each shop.
-
If an API scope is not enabled for your app, Hevo does not ingest the objects that need that scope. To ingest these objects, enable the scope for the app in Partner Center, and then modify the Source configuration to authorize your account again.
-
The access to your shop is valid for the authorization duration that you grant when you authorize the app. Once it expires, or if you revoke the authorization, the Pipeline fails. To resume data ingestion, modify the Source configuration and authorize your account again.
-
TikTok Shop does not provide payment data for shops in Southeast Asian markets. For these shops, the payment object contains no data.
-
In each run, Hevo ingests the entire data of the shop_video_performance_detail_interval object and its child objects from January 1, 2021. This increases the duration of each run and the number of API calls, and Hevo displays a warning for the object. Deselect the object if you do not need it.
-
For the external_order object, Hevo makes one API call for each order and each external order platform that you select. Hevo ingests the references only for the orders created or updated since the previous run. To ingest the references added to an order that is not updated, resync the object. Hevo displays a warning for this object, as the first run for a shop with many orders can take a long time. Deselect the object if you do not need it.
-
TikTok Shop applies dynamic API rate limits, which depend on factors such as the number of authorized shops and the load on the API. If a limit is exceeded, Hevo retries the request. If the limit is still exceeded, Hevo ingests the object in the next run. Read Rate limits.
-
If you added an IP allow list to your app in Partner Center, add Hevo’s IP addresses for your region to it. Otherwise, TikTok Shop blocks the requests from Hevo.
Limitations
-
Hevo does not replicate the product, affiliate, and creator marketplace data of your shop.
-
For the analytics objects, Hevo does not ingest the data before January 1, 2021.
Revision History
Refer to the following table for the list of key updates made to this page:
| Date | Release | Description of Change |
|---|---|---|
| Oct-20-2026 | NA | New document. |