In this article, we will look at the schema information of the supported APIs and tables for Neon Pixel.

Find the links to other articles related to Neon Pixel below:

• Essential Attributes and Supported Tables for Neon Pixel
• Setup Instructions for Neon Pixel 

Tables/APIs Supported

The tables and APIs associated with the Neon Pixel connector are as follows.

CTV_Blended

Purpose: The CTV_Blended endpoint of Neon_Pixel is designed to provide a unified performance view of connected TV (CTV) campaigns, combining impression, visit, and conversion data into a single, queryable report for analysis and optimization. It lets advertisers pull day-level metrics like impressions, visits, conversions, order value, spend, ROAS, frequency, CPM, and related ratios over a chosen date range so they can evaluate and improve CTV campaign effectiveness.

Source API Documentation: NA — the API is private and not exposed publicly.

Replication Type: Key Based

Primary Key: Please choose according to the business need.

TV_Network

Purpose: The TV_Network field in the Neon Pixel API identifies the specific television network associated with ad campaign performance data. It enables advertisers and analysts to segment and compare campaign effectiveness across different TV networks. By using this field, users can evaluate metrics such as impressions, conversions, visits, and spend by network, allowing for more precise budget allocation and performance optimization. This capability supports data-driven decisions on which networks deliver the highest return on ad spend (ROAS) and engagement, helping refine media strategies for better audience reach and campaign efficiency.

Source API Documentation: NA — the API is private and not exposed publicly.

Replication Type: Key Based

Primary Key: Please choose according to the business need.

Display_Publisher

Purpose: The Display_Publisher field in the Neon_Pixel API represents the platform, website, or network where a digital advertisement is displayed. It enables advertisers to identify which publishers are delivering impressions, visits, and conversions, allowing detailed performance comparisons across different sources. By using this parameter in data queries, users can analyze key metrics such as spend, impressions, ROAS, conversion rate, and order value for each publisher. This helps advertisers measure the effectiveness of various display channels, optimize budget allocation, and refine their media strategy for maximum campaign impact.

Source API Documentation: NA — the API is private and not exposed publicly.

Replication Type: Key Based

Primary Key: Please choose according to the business need.

Creative

Purpose: The Creative endpoint in Neon_Pixel provides functionality for retrieving and analyzing creative-level advertising data, enabling marketers to evaluate the effectiveness of individual ad assets. By using API calls (such as via cURL), users can access key performance metrics like impressions, conversions, spend, ROAS, and conversion rate for each creative. This helps advertisers understand which creatives drive engagement and sales, optimize ad performance, and allocate budgets efficiently. The API supports filtering, sorting, and date-based queries, allowing real-time, data-driven insights into campaign and creative performance.

Source API Documentation: NA — the API is private and not exposed publicly.

Replication Type: Key Based

Primary Key: CreativeID